@node9/proxy 1.7.0 → 1.8.2

package/README.md

@@ -203,20 +203,73 @@ Secrets are **never logged in full** — the audit trail stores only a redacted
 
 Shields add protection for specific infrastructure and services — only relevant if you actually use them.
 
+**Builtin shields** (ship with every install):
+
 | Shield       | What it protects                                                                                                |
-| :----------- | :-------------------------------------------------------------------------------------------------------------- |
+| :----------- | :-------------------------------------------------------------------------------------------------------------- | -------------------------------- | --------------------------------- |
 | `postgres`   | Hard-blocks `DROP TABLE`, `TRUNCATE`, `DROP COLUMN` (upgrades Layer 1 review → block); reviews `GRANT`/`REVOKE` |
 | `github`     | Blocks `gh repo delete`; reviews remote branch deletion                                                         |
 | `aws`        | Blocks S3 bucket deletion, EC2 termination; reviews IAM changes, RDS deletion                                   |
+| `bash-safe`  | Blocks pipe-to-shell (`curl                                                                                     | bash`), obfuscated exec (`base64 | sh`), `rm -rf /`, raw disk writes |
 | `filesystem` | Reviews `chmod 777`, writes to `/etc/`                                                                          |
 
 ```bash
 node9 shield enable postgres    # protect your database
 node9 shield enable aws         # protect your cloud infrastructure
-node9 shield list               # see all available shields
+node9 shield list               # see all builtin shields
+node9 shield list --community   # browse the community marketplace
 node9 shield status             # see what's currently active
 ```
 
+#### Community Marketplace
+
+Browse and install shields published by the community:
+
+```bash
+node9 shield list --community          # see what's available
+node9 shield install k8s               # download to ~/.node9/shields/k8s.json
+node9 shield enable k8s                # activate it
+```
+
+Installed shields are validated against the same schema as builtins and stored in `~/.node9/shields/`. They're picked up automatically on the next daemon start.
+
+#### Custom (Private) Shields
+
+Drop a JSON file directly into `~/.node9/shields/` to create a private shield — no install command needed:
+
+```json
+// ~/.node9/shields/my-company.json
+{
+  "name": "my-company",
+  "description": "Blocks ops our security team disallows",
+  "aliases": ["corp"],
+  "smartRules": [
+    {
+      "name": "shield:my-company:block-prod-deploy",
+      "tool": "bash",
+      "conditions": [{ "field": "command", "op": "matches", "value": "kubectl.*production" }],
+      "verdict": "block",
+      "reason": "Production deploys require a change ticket"
+    }
+  ],
+  "dangerousWords": []
+}
+```
+
+```bash
+node9 shield enable my-company
+```
+
+#### Per-rule overrides
+
+Tune individual rules within an active shield without disabling the whole shield:
+
+```bash
+node9 shield set aws review-rds-delete block   # escalate review → block
+node9 shield set postgres block-drop-table review --force   # downgrade block → review (requires --force)
+node9 shield unset postgres block-drop-table   # restore the default
+```
+
 ### 🔓 Trusted Hosts
 
 Node9 blocks any pipe-chain that sends sensitive files to the network. If the destination is **your own internal API or logging service**, that friction is unnecessary. Trusted hosts let you declare known-safe destinations:
@@ -626,24 +679,31 @@ When the daemon is not running the HUD shows `🛡 node9 | offline` instead of a
 
 ## 🖥️ CLI Reference
 
-| Command                              | Description                                                                           |
-| :----------------------------------- | :------------------------------------------------------------------------------------ |
-| `node9 setup`                        | Interactive menu — detects installed agents and wires hooks for you                   |
-| `node9 addto <agent>`                | Wire hooks for a specific agent (`claude`, `gemini`, `cursor`)                        |
-| `node9 setup hud`                    | Add the node9 security statusline to Claude Code (also done automatically by `init`)  |
-| `node9 init`                         | Create default config, wire detected agents, and set up the HUD                       |
-| `node9 status`                       | Show current protection status and active rules                                       |
-| `node9 doctor`                       | Health check — verifies binaries, config, credentials, and all agent hooks            |
-| `node9 shield <cmd>`                 | Manage shields (`enable`, `disable`, `list`, `status`)                                |
-| `node9 trust add <host>`             | Add a host to the trusted list — pipe-chain blocks to this host are downgraded        |
-| `node9 trust remove <host>`          | Remove a trusted host                                                                 |
-| `node9 trust list`                   | Show all trusted hosts                                                                |
-| `node9 tail [--history]`             | Stream live agent activity to the terminal (auto-starts daemon if needed)             |
-| `node9 explain <tool> [args]`        | Trace the policy waterfall for a given tool call (dry-run, no approval prompt)        |
-| `node9 undo [--steps N]`             | Revert the last N AI file edits using shadow Git snapshots                            |
-| `node9 mcp-gateway --upstream <cmd>` | Wrap an MCP server with Node9 security — intercepts every tool call                   |
-| `node9 mcp-server`                   | Run the Node9 MCP server — exposes undo and other tools to Claude, Cursor, and Gemini |
-| `node9 check`                        | Called by agent hooks; evaluates a pending tool call and exits 0 (allow) or 1 (block) |
+| Command                                      | Description                                                                           |
+| :------------------------------------------- | :------------------------------------------------------------------------------------ |
+| `node9 setup`                                | Interactive menu — detects installed agents and wires hooks for you                   |
+| `node9 addto <agent>`                        | Wire hooks for a specific agent (`claude`, `gemini`, `cursor`)                        |
+| `node9 setup hud`                            | Add the node9 security statusline to Claude Code (also done automatically by `init`)  |
+| `node9 init`                                 | Create default config, wire detected agents, and set up the HUD                       |
+| `node9 status`                               | Show current protection status and active rules                                       |
+| `node9 doctor`                               | Health check — verifies binaries, config, credentials, and all agent hooks            |
+| `node9 shield enable <name>`                 | Activate a shield                                                                     |
+| `node9 shield disable <name>`                | Deactivate a shield                                                                   |
+| `node9 shield list`                          | Show builtin shields and their enable/disable status                                  |
+| `node9 shield list --community`              | Browse the community marketplace                                                      |
+| `node9 shield install <name>`                | Download a community shield to `~/.node9/shields/`                                    |
+| `node9 shield status`                        | Show active shields with per-rule verdicts and any overrides                          |
+| `node9 shield set <shield> <rule> <verdict>` | Override a rule verdict (`block`, `review`, `allow --force`)                          |
+| `node9 shield unset <shield> <rule>`         | Remove a rule override, restoring the shield default                                  |
+| `node9 trust add <host>`                     | Add a host to the trusted list — pipe-chain blocks to this host are downgraded        |
+| `node9 trust remove <host>`                  | Remove a trusted host                                                                 |
+| `node9 trust list`                           | Show all trusted hosts                                                                |
+| `node9 tail [--history]`                     | Stream live agent activity to the terminal (auto-starts daemon if needed)             |
+| `node9 explain <tool> [args]`                | Trace the policy waterfall for a given tool call (dry-run, no approval prompt)        |
+| `node9 undo [--steps N]`                     | Revert the last N AI file edits using shadow Git snapshots                            |
+| `node9 mcp-gateway --upstream <cmd>`         | Wrap an MCP server with Node9 security — intercepts every tool call                   |
+| `node9 mcp-server`                           | Run the Node9 MCP server — exposes undo and other tools to Claude, Cursor, and Gemini |
+| `node9 check`                                | Called by agent hooks; evaluates a pending tool call and exits 0 (allow) or 1 (block) |
 
 ### `node9 doctor`
 
@@ -710,7 +770,8 @@ This can happen when the daemon's PID file (`~/.node9/daemon.pid`) is missing
 - [x] **Native OS Dialogs** (Sub-second approval via Mac/Win/Linux system windows)
 - [x] **Shadow Git Snapshots** (1-click Undo for AI hallucinations)
 - [x] **Identity-Aware Execution** (Differentiates between Human vs. AI risk levels)
-- [x] **Shield Templates** (`node9 shield enable <service>` — one-click protection for Postgres, GitHub, AWS)
+- [x] **Shield Templates** (`node9 shield enable <service>` — one-click protection for Postgres, GitHub, AWS, bash-safe, filesystem)
+- [x] **Shields Marketplace** (`node9 shield list --community`, `node9 shield install <name>` — community-published shields + private custom shields in `~/.node9/shields/`)
 - [x] **Content Scanner / DLP** (Detect and block secrets like AWS keys and Bearer tokens in-flight)
 - [x] **Flight Recorder** (Real-time activity stream in browser dashboard and `node9 tail` terminal view)
 - [x] **Universal MCP Gateway** (Transparent stdio proxy — wraps any MCP server for any AI agent: `node9 mcp-gateway --upstream <cmd>`)