ompsure
  • Reviews
  • Pro
  • Pricing
  • Template
Sign InSign Up
ompsure

Code quality that happens automatically.
Free for personal use.

Audience

  • Who's It For?
  • For Creators
  • For Developers

Features

  • Code Graph
  • Security
  • Code Review
  • Testing
  • Deployment
  • Memory

Product

  • Plugins
  • Control Panel
  • Proof
  • Catalog
  • How It Works

Plans

  • Pricing
  • Pro Patterns
  • Commercial License
  • Starter Template

Resources

  • Getting Started
  • Documentation
  • Reviews
  • Affiliate Program

© 2026 Et'al Software Solutions. All rights reserved.

  • Template License
  • Plugin License
  • Refund Policy
  • GitHub
Enforcement catches
Viewing as
Enforcement catches

SQL template literal with interpolation

2026-06-09

enforcement hook — composure-pro · 2026-06-09
[composure:enforcement] The write you just attempted to session-db.ts matches a pattern this codebase doesn't want shipped. What the rule caught (1 item): - [security-sql-injection] SQL template literal with interpolation detected — SQL injection risk. Use parameterized queries (supabase.from().select(), pg prepared statements) instead.

The first retry still built the placeholder list ("?,?,?") by interpolation — values bound, string assembled. Blocked again, same rule. The version that landed used one fixed prepared statement per session id, no string assembly at all. The hook held its line until the shape was actually right.

Why this matters: Keys & accessThe failure mode this catch prevents — in App architecture, in practice.

Composure enforcement hook, firing mid-session in the composure-pro repo. Catch message reproduced verbatim.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install itNext: Supabase service_role key in app code