getaegis/aegis
Credential isolation for AI agents. Local-first transparent proxy — your agent never sees your API keys.
What's novel
Credential isolation for AI agents. Local-first transparent proxy — your agent never sees your API keys.
Code Analysis
11 files read · 3 roundsA local-first credential isolation proxy that sits between AI agents and external APIs, injecting secrets at the network boundary so agents never see real API keys, while enforcing domain restrictions, rate limits, body inspection for exfiltration, policy-based access control, and full audit logging
Strengths
Genuinely deep implementation with real cryptography (AES-256-GCM, Shamir secret sharing over GF(256), ChaCha20-Poly1305 DB encryption), a 30+ pattern body inspector for exfiltration detection, a full policy engine with time windows and timezone support, and a complete MCP server that replicates the entire security pipeline. The architecture is clean with clear separation between gate, vault, policy, agent, ledger, and MCP layers.
Weaknesses
The rate limiter is in-memory only (resets on restart), and the gate.ts file at 61KB is a monolith that could benefit from further decomposition. The body inspector uses regex patterns that could produce false positives on legitimate API payloads containing long base64 or hex strings.
Score Breakdown
Signal breakdown
Innovation
Craft
Traction
Scope
Evidence
Commits
25
Contributors
0
Files
190
Active weeks
3
Repository
Language
TypeScript
Stars
8
Forks
1
License
Apache-2.0