SlopCop

Caught, with the
lines that prove it.

Each scan reads your repository and reports what is worth fixing, with the evidence beside it.

See a sample report

What a scan finds

Confirmed findings
The AI review checks every candidate against your code and reports only what it confirms, with the lines that prove it.
Design review
AI reviewers find the technical debt and sprawl that low-judgement AI edits leave behind: code that does too much, sits in the wrong place or leans on more than it needs.
Possible credentials
Keys and tokens left in the code are listed by file and line, without repeating the value.
In your agent’s loop
The SlopCop CLI lets your coding agent scan each change and fix what it finds before you push.

The request URL is opened as a database connection

Connections.csLine 10
public static SqlConnection Open(string connectionString, string tag){    var connection = new SqlConnection(connectionString);    Audit.Tag(connection, tag);    return connection;···
Problem

Export passes url and ReportsDb to Open the wrong way round, so the request’s URL reaches new SqlConnection as its connection string.

Impact

Whoever sends the request chooses the database server the export connects to, and the reports database’s settings are recorded as the connection’s tag instead.

Recommended solution

Call Open(ReportsDb, url), and give Open named arguments or a settings type so the two strings can’t be swapped again.

Why this was flagged
Check

Resource injection matched Connections.cs:10.

Source read for this finding
  • Connections.cs:8-13
  • ReportsController.cs:13-18
Independent review

Kept with high confidence. The request’s display URL reaches the SqlConnection constructor in Connections.cs.

A synthetic example. See a whole sample report

Set it up with us.

Leave your email and we’ll arrange a call about running SlopCop in your team’s coding agents and CI, or anything else you’d like to know.

We’ll use your email to respond. No scan or report is needed.