SlopcheckDormant
A small Rust CLI that reports signs of AI-assisted development in a repository and its Rust or JavaScript dependencies: commits by known coding agents and files such as CLAUDE.md or .cursor.
- What it is
- Linters, formatters and type checkers (linters)
- Type
- Open source
- Made by
- mat (GitHub user mat-1, personal project)
- License
- None stated (no licence file)
- Status
- Dormant. Written over five days in March 2026; no commits since March 19, 2026.
- Facts checked
- 23 October 2026
What it is
Slopcheck is a personal project, and it is not a linter in the usual sense: it reads no code and reports no style or correctness problems. It answers one question, how much a project and everything it depends on was built with AI coding tools. In a Git repository it walks the history and counts commits whose author, or whose Co-authored-by: trailer, is a known agent address (Claude, Copilot, Codex, Cursor, Gemini, Jules, Junie, Qwen, GLM and review bots such as CodeRabbit and Greptile), separately for all time and the past 30 days, so it can tell current from former use. It also looks for agent files such as CLAUDE.md, AGENTS.md, .mcp.json, .cursor or .clinerules in the working tree, and in .gitignore for projects that hide them.
It then lists dependencies, with cargo metadata for Rust or by naively parsing package.json and walking npm for JavaScript, clones each dependency’s repository (metadata only, cached for 24 hours under ~/.cache/slopcheck) and runs the same checks, assuming each is on its latest version. Install it with cargo install --git https://github.com/mat-1/slopcheck and run slopcheck ./project. The README warns against running it on untrusted projects, because it may fetch arbitrary sources and run build scripts.
Why teams pick it
- Shows at a glance which dependencies are developed with AI coding agents, for teams with a policy on that
- Uses plain, checkable signals (commit metadata and config files) rather than guessing from the code’s style
Watch out for
- Only finds what is declared: agent work committed under a human’s name with no trailer or config file is invisible
- Only Rust and npm dependencies, checked at their latest version rather than the one you lock
- May run build scripts of the projects it inspects, so it is unsafe on untrusted code
- A personal project with no licence file and no releases (install from Git), dormant since March 2026
Alternatives
What all linters have in common →Compare side by side →TODO placeholders, “for now” deferrals, “should work” hedging in comments, empty stubs and placeholder data.
FallowOpen sourceA Rust analyzer for TypeScript and JavaScript repositories that finds unused files, exports and dependencies, circular imports, duplicated code, complexity hotspots and architecture violations from one module graph.
OxcOpen sourceThe JavaScript Oxidation Compiler: Rust building blocks (parser, transformer, minifier, resolver) under Rolldown and Vite, plus the Oxlint linter and Oxfmt formatter.+1 anti-slop
RuffOpen sourceA Python linter and formatter written in Rust that stands in for Flake8 and its plugins, isort, pyupgrade and Black, 10 to 100 times faster.How it fits with other technologies
See it in a real stack
No architecture uses Slopcheck yet. Drop it into the playground and wire it up yourself.Open playground →Where it came from2026
The developer mat (GitHub user mat-1) wrote Slopcheck in a burst between March 14 and 19, 2026: the first version checked Rust projects for agent commits and files, contributors and later commits added more agents and review bots, and JavaScript support arrived on March 16. It has not changed since.
Why it’s built this way
- Look at provenance, not at the code
- Commit authors, co-author trailers and agent config files are explicit records the tools leave behind, which a small program can count without judging the code itself.
- Check the whole dependency tree
- A project’s own history says little if the libraries it pulls in are written by agents, so it clones and checks each dependency’s repository too.
Timeline
- 2026
March 14: first version, for Rust projects
- 2026
March 16: initial JavaScript (npm) support
- 2026
March 19: last commit