cc-safety-net vs stop-that-shit
The two are close in size: 1.5k stars for cc-safety-net, 1.6k for stop-that-shit.
cc-safety-net leads on setup ease. stop-that-shit does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Parses command semantics (including shell wrappers and interpreter one-liners) to block destructive commands and secret access before they execute across many coding agent CLIs.
- Stars
- 1.5k
- Tracked growth
- +2.9%
- Maturity
- ●●●●●
- Last commit
- 56m ago
- Language
- TypeScript
- License
- MIT
- Cost to run
- Free, local install (requires Node.js)
Implements executable, evidence-backed Guards and Skills that intercept unrequested hashes, dependency/subagent launches and scope creep across multiple agent hosts, turning policy statements into machine-enforceable checks.
- Stars
- 1.6k
- Tracked growth
- not tracked long enough
- Maturity
- ●●●●●
- Last commit
- 2d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free, local install; uses the host agent's model access (may require provider subscriptions).
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | cc-safety-net | stop-that-shit |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Command + related files | ●●●●● Diff + related files |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Presets + audit | ●●●●● Armed / observing gating |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Rulebooks & per-project | ●●●●● Command flags & policies |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Local-only | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multiple agent CLIs | ●●●●● Multiple specific providers |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● Install + restart |
Which one to pick
Pick cc-safety-net if…
Safety-first — Blocks destructive git/filesystem commands and secret access before AI agents run them, using semantic command analysis, configurable rulebooks, presets, and a local audit trail.
- Setup ease: One-command install (5/5 against 3/5)
Pick stop-that-shit if…
Privacy-first — a local-first plugin that enforces task-boundary guardrails across Codex, Claude Code, OpenCode and Hermes Agent CLI without relying on a centralized service.
What people want from each one
lennney/stop-that-shit
Questions people ask
Is cc-safety-net better than stop-that-shit?
cc-safety-net leads on setup ease. stop-that-shit does not take any axis by a clear margin. cc-safety-net is worth picking when safety-first — Blocks destructive git/filesystem commands and secret access before AI agents run them, using semantic command analysis, configurable rulebooks, presets, and a local audit trail.
Which of cc-safety-net and stop-that-shit keeps my code private?
cc-safety-net: Local-only (5/5). stop-that-shit: Self-hostable (4/5).
What does each one cost to run?
cc-safety-net: Free, local install (requires Node.js). stop-that-shit: Free, local install; uses the host agent's model access (may require provider subscriptions)..
Full profiles: kenryu42/cc-safety-net and lennney/stop-that-shit. Everything else in Security & guardrails.