@frostbridge/imdl 0.1.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.
Files changed (3) hide show
  1. package/README.md +107 -0
  2. package/dist/index.js +5667 -0
  3. package/package.json +33 -0
package/README.md ADDED
@@ -0,0 +1,107 @@
1
+ # @frostbridge/imdl
2
+
3
+ AI Agent Security CLI — monitor, govern, and protect AI coding agents across your organization.
4
+
5
+ ## What It Does
6
+
7
+ IMDL (Intelligent Mediation & Detection Layer) sits between AI coding agents and your codebase, providing:
8
+
9
+ - **Session monitoring** — Track every tool call, file access, and command execution
10
+ - **Policy enforcement** — Block dangerous operations in real-time (Bifrost engine)
11
+ - **Permission scanning** — Discover what permissions developers have granted to their AI agents
12
+ - **MCP security** — Score and audit MCP servers for supply chain risks
13
+ - **Shell interception** — Wrap terminal commands for policy evaluation
14
+
15
+ Supports: Claude Code, Cursor, Windsurf, GitHub Copilot, Codex
16
+
17
+ ## Installation
18
+
19
+ ```bash
20
+ # Requires Node.js 20+
21
+ npm install -g @frostbridge/imdl
22
+ ```
23
+
24
+ Since this is a private package, add an `.npmrc` with your team's read token:
25
+
26
+ ```
27
+ //registry.npmjs.org/:_authToken=${FROSTBRIDGE_NPM_TOKEN}
28
+ @frostbridge:registry=https://registry.npmjs.org/
29
+ ```
30
+
31
+ ## Quick Start
32
+
33
+ ```bash
34
+ # Initialize — auto-detects installed agents and configures hooks
35
+ imdl init
36
+
37
+ # Check current status
38
+ imdl status
39
+
40
+ # Scan MCP servers for vulnerabilities
41
+ imdl scan
42
+
43
+ # View agent permissions across your machine
44
+ imdl permissions
45
+ ```
46
+
47
+ ## Setup with Team
48
+
49
+ ```bash
50
+ # Join your organization (token from admin)
51
+ imdl init --token <setup-token>
52
+
53
+ # Or configure API endpoint manually
54
+ imdl init --api https://your-api.example.com
55
+ ```
56
+
57
+ ## Commands
58
+
59
+ | Command | Description |
60
+ |---------|-------------|
61
+ | `imdl init` | Initialize monitoring for detected agents |
62
+ | `imdl status` | Show current protection status |
63
+ | `imdl scan` | Scan installed MCP servers for risks |
64
+ | `imdl permissions` | Show all agent permissions on this machine |
65
+ | `imdl permissions --report` | Send permission report to your org |
66
+ | `imdl lock` | Generate an MCP allowlist from current installs |
67
+ | `imdl tool-verify` | Verify tool integrity and behavior |
68
+ | `imdl gateway` | AI Gateway management |
69
+
70
+ ## How It Works
71
+
72
+ ### Hook Mode (Claude Code, Codex)
73
+
74
+ Installs into the agent's hook system (e.g., `~/.claude/hooks.json`). Every tool call is evaluated against your org's policies in <5ms before execution.
75
+
76
+ ### MCP Proxy Mode (Cursor, Windsurf, Copilot)
77
+
78
+ Registers `@frostbridge/imdl-mcp-proxy` as a middleware between the editor and MCP servers. Intercepts tool calls transparently.
79
+
80
+ ### Shell Wrapper Mode
81
+
82
+ `@frostbridge/imdl-shell-wrapper` wraps terminal sessions to catch dangerous commands before they execute.
83
+
84
+ ## Architecture
85
+
86
+ ```
87
+ AI Agent → IMDL Hook/Proxy → Bifrost Policy Engine → Allow/Block
88
+
89
+ Event Buffer → API → Dashboard
90
+ ```
91
+
92
+ ## Privacy
93
+
94
+ - All policy evaluation happens locally (no network call in the critical path)
95
+ - Session data is buffered and sent to your org's API endpoint
96
+ - No telemetry to Frostbridge — your data stays in your infrastructure
97
+ - Developers can view exactly what is monitored via `imdl status`
98
+
99
+ ## Requirements
100
+
101
+ - Node.js 20+
102
+ - macOS, Linux, or Windows
103
+ - One or more supported AI agents installed
104
+
105
+ ## License
106
+
107
+ Proprietary — Frostbridge Security, Inc.