SQL built with string concatenation (JS/TS)
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A quoted SQL fragment is joined to a value with + instead of a parameterized query, which is a SQL injection risk when the value is user-controlled.
Why it matters
Joining a SQL fragment to a value with + builds the query from raw text, so a crafted value can rewrite it. This is the most common SQL injection shape in JavaScript code. It is a heuristic because concatenating a trusted constant is harmless, but the pattern cannot tell the two apart.
How to fix it
Replace the concatenation with a parameterized query: keep the SQL static and pass values through placeholders ($1 or ?) with an argument array. If you build queries dynamically, use a query builder such as Knex or your ORM rather than string math.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo