Claude Tools / Plugins / project-boundary
Plugins · justi/claude-code-project-boundary
project-boundary
Blocks destructive commands outside the project directory. Allows file operations within the project (refactoring, cleanup) but prevents accidental damage outside it.
CLEARED_STATICclaude-onlyv1.11.0
Pipeline results
Coverage
CLEARED_STATIC
Tests run
7 / 8
Portability
Claude-only
Type
Plugins
Tests & results
What the pipeline checked
Coverage
Not assessed
- behavioural execution not run
- egress patterns logged (FLAG-INFO): 2 lexical match(es)
README
From the repository
# Project Boundary — Claude Code Plugin Allows destructive operations **within your project** but blocks them **outside** the project directory. Built for `--dangerously-skip-permissions` mode where Claude doesn't ask — this plugin is your safety net. ## How it differs from existing plugins - **[claude-code-safety-net](https://github.com/kenryu42/claude-code-safety-net)** — blocks `rm` everywhere; Project Boundary allows it inside the project so refactoring works normally. - **[destructive-command-guard](https://github.com/Dicklesworthstone/destructive_command_guard)** — only distinguishes `/tmp` vs everything else; Project Boundary uses `$CLAUDE_PROJECT_DIR` as the actual boundary. - **[claude-code-damage-control](https://github.com/disler/claude-code-damage-control)** — requires manually listing protected paths; Project Boundary automatically protects everything outside the project. ## What it does ### Boundary-checked (allowed inside project, blocked outside) | Operation | Inside project | Outside project | |-----------|---------------|-----------------| | `rm`, `rm -rf` | Allowed | **Blocked** | | `mv` (source and destination) | Allowed | **Blocked** | | `cp` (source and …