v1.2.0

Triaged scan output

Once a run has more than 20 findings, sloppy groups the report into four sections:

• Fix first: defects such as swallowed exceptions, queries in loops and unfinished method bodies. They're ranked by risk and grouped by file and rule.
• Hotspots: maintainability findings, counted per file.
• By rule: a count for every rule, so nothing is hidden.
• Next: the commands that shorten the list without read

Use --all for the full list, --top=N to show more defece rule.

Clears the obvious findings for you

• sloppy fix now deletes comments that only restate theomments to keep them.
• A long first scan offers to baseline your existing findings, so later scans show only new ones. It only asks when you run it yourself at a terminal, never in CI.

Ranks by what changes

Findings in files that change often now rank higher. Slts, so the same checkout ranks the same way on any day.This affects the ranking, never the score.

Calibrated on real code

Tested against eight open-source Laravel apps, 782,578 lines in total:

• Findings dropped from 5,097 to 4,075.
• Scores now range from 25 to 90. Before, they ran from 0 to 87, and mature apps like Snipe-IT and Pixelfed scored 0.

What changed:

• SL101: "many calls" and "many collaborators" now counrately, they were the only trigger for 41% of itsfindings.
• Score: no single rule can take more than 30 points ofapping findings no longer count the same lines twice.
• SL109: no longer flags comments at the end of a block, or single lines of a multi-line comment.

Agent guardrails

• SL112 Placeholder Implementation catches method bodies left unwritten, such as // ... existing code ... or a "not implemented" throw.
• SL503 Weakened Test catches tests made to pass by cheth assertions removed, or given assertTrue(true).
• Claude Code hooks now work on Windows without Git Bash. Re-run sloppy agents install to update your settings.

Upgrade notes

• Different scores: expect different numbers from 1.1.x, usually higher on large codebases. The score stored in an existing baseline was calculated with the old formula, so it won't match ne
• JSON output: each finding gains a tier field.
• New config keys: score.rule_cap, risk.churn_weight, rrule tier option.

The full list of changes is in CHANGELOG.md.