Claude Code Safety Net
Prevents accidental data loss by intercepting destructive git and filesystem commands before execution.
Catches destructive git and filesystem commands before they execute. Acts as a safety net preventing accidental data loss.
- Prevent accidental force-pushes that overwrite team code
- Block destructive file deletion commands before they execute
- Catch dangerous resets in shared repositories automatically
Prevents accidental data loss by intercepting destructive git and filesystem commands before execution. A 1.2K-star safety layer that catches the mistakes Claude makes when it misreads intent.
Teams onboarding to Claude Code who want a guardrail against force-pushes, rm -rf, and hard resets — especially useful in shared repos.
How to Get It
Claude Code only: Hooks are configured in your project's .claude/settings.json file. They run automatically before or after Claude takes actions. You can ask Claude to set up a hook for you by describing what you want in your conversation. Not available in Claude Cowork or Claude Chat.
claude plugins install claude-code-safety-net
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Help me prevent accidental force-pushes that overwrite team code
Trust Signals Reviewed
Not yet scanned. Learn how to check this tool yourself.
Data & Access
Community Pulse Active
Discussed on Hacker News, Reddit
- Claude code source code has been leaked via a map file in their npm registry — Reddit · 3926 pts
- Claude Shipped insane Features this week. Full overview. — Reddit · 609 pts
- I built a Claude Code plugin that extracts any website's full design system — Reddit · 516 pts
3 mentions across 1 sources
Reviewer notes
Reviewed review. These are observations, not a security certification.
1.2K stars. Catches destructive commands before execution. Important safety tool.
Community tool. Source reviewed.
Things to check
- Hook-based interception may have gaps if Claude bypasses standard git/shell APIs or if the tool runs in sandboxed environments where hooks don't apply. Requires proper configuration per repository and developer environment.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
1.2K stars. Catches destructive commands before execution. Important safety tool.