@node9/proxy 1.14.1 → 1.15.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -0
- package/dist/cli.js +3080 -2168
- package/dist/cli.mjs +3060 -2150
- package/dist/index.js +2110 -1367
- package/dist/index.mjs +2501 -1758
- package/package.json +5 -2
- package/dist/shields/builtin/aws.json +0 -59
- package/dist/shields/builtin/bash-safe.json +0 -92
- package/dist/shields/builtin/docker.json +0 -120
- package/dist/shields/builtin/filesystem.json +0 -30
- package/dist/shields/builtin/github.json +0 -26
- package/dist/shields/builtin/k8s.json +0 -92
- package/dist/shields/builtin/mcp-tool-gating.json +0 -7
- package/dist/shields/builtin/mongodb.json +0 -78
- package/dist/shields/builtin/postgres.json +0 -42
- package/dist/shields/builtin/project-jail.json +0 -64
- package/dist/shields/builtin/redis.json +0 -78
package/README.md
CHANGED
|
@@ -34,6 +34,8 @@ npx node9-ai scan
|
|
|
34
34
|
|
|
35
35
|
Reads your existing Claude / Gemini / Codex session history, runs the full Node9 policy engine, and shows every operation that would have been blocked or flagged.
|
|
36
36
|
|
|
37
|
+
> Runs entirely locally — no API calls, no telemetry on `scan`, nothing leaves your machine.
|
|
38
|
+
|
|
37
39
|
```
|
|
38
40
|
🔍 Scanning your AI history — what would node9 have caught?
|
|
39
41
|
|
|
@@ -67,6 +69,21 @@ The last line opens a live dashboard in your browser with collapsible drill-down
|
|
|
67
69
|
|
|
68
70
|
---
|
|
69
71
|
|
|
72
|
+
## How is this different from gitleaks / Snyk / TruffleHog?
|
|
73
|
+
|
|
74
|
+
Those scan **repositories** for credentials. Node9 scans **AI agent session history** — what your AI ran, what it read, what credentials passed through tool calls. Different surface area.
|
|
75
|
+
|
|
76
|
+
Node9 catches things gitleaks can't:
|
|
77
|
+
|
|
78
|
+
- Credentials the AI read but never committed
|
|
79
|
+
- Agent edit loops that burn tokens on retries
|
|
80
|
+
- Dangerous shell commands the AI ran without confirmation
|
|
81
|
+
- Blast radius — which credential files an AI agent on this machine could reach right now
|
|
82
|
+
|
|
83
|
+
Run gitleaks for committed code. Run Node9 for AI session history.
|
|
84
|
+
|
|
85
|
+
---
|
|
86
|
+
|
|
70
87
|
## Install
|
|
71
88
|
|
|
72
89
|
```bash
|