Skip to content

Add benchmark trust note to README #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benvinegar merged 2 commits into from
Apr 19, 2026
Merged

Add benchmark trust note to README #16

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dbd08d2
Clarify README benchmark trust copy
benvinegar Apr 19, 2026
cac4c61
Tighten README benchmark wording
benvinegar Apr 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,6 @@ Deterministic CLI for finding **AI-associated slop patterns** in JavaScript and

Scan a repo, surface the hotspots, and compare codebases using normalized slop metrics.

> `slop-scan` is a **slop scanner**, not an authorship detector. It reports explainable patterns and suspicious density. It does **not** claim who wrote the code.

## Why use it

- **Find the hotspots fast** — see which files and directories concentrate the most suspicious patterns
Expand All @@ -24,6 +22,10 @@ Scan a repo, surface the hotspots, and compare codebases using normalized slop m
- finding low-judgment boilerplate in your own codebase
- iterating on deterministic slop heuristics

## Why can you trust it?

Every rule is tested and benchmarked against popular, mature OSS repos pinned to exact commit SHAs from before AI coding was common. See [Benchmarks](#benchmarks).

## Install

Install globally with npm:
Expand Down
Loading