spillage
No liveness check has reached it yet; it is registered on GitHub and PyPI and has been in the index since 10 Oct 2026. How this is checked
Spillage is an open-source CLI security tool for coding agents including Claude Code, Codex, and Gemini CLI. It provides hooks to block credential leaks, scans logs from multiple agents for previously exposed secrets, and scrubs detected credentials.
Inferred · not functionally tested
Overview
6 featuresPurpose: Preventing and removing exposed API keys and credentials from coding-agent activity and logs.
Inferred · not functionally tested
Audience: developers and DevSecOps teams using coding agents
Inferred · not functionally tested
Functions: monitoring, data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
spillage is an AI & LLM security project. Inferred · not functionally tested: It focuses on preventing and removing exposed API keys and credentials from coding-agent activity and logs. Inferred · not functionally tested: spillage is an open-source project aimed at developers and DevSecOps teams using coding agents. Basis unknown · not verified: spillage is open source under the MIT license. Basis unknown · not verified: It runs on the command line, and it can be self-hosted.
It is developed by Maximilian Feix, and it first shipped in 2026. The project is developed in the open on GitHub with 53 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are leak prevention hooks, API key scanning, and agent log scanning. Inferred · not functionally tested: Catalogued interfaces include a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Leak prevention hooks
- API key scanning
- Agent log scanning
- Credential scrubbing
- Secret redaction
- Multi-agent support
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 22207c54929b · since Sep 2026
Trust & compliance
Indexing history
2What PulseGate has recorded for this listing
Frequently asked questions about spillage
- What does spillage do?
- Inferred · not functionally tested: Spillage focuses on preventing and removing exposed API keys and credentials from coding-agent activity and logs. It is catalogued under AI & LLM security on PulseGate.
- Who is spillage for?
- Inferred · not functionally tested: spillage is an open-source project built for developers and DevSecOps teams using coding agents.
- Does spillage have a free plan?
- Basis unknown · not verified: Yes — spillage is open source under the MIT license and free to use.
- What platforms does spillage run on?
- Basis unknown · not verified: spillage runs on the command line. It can also be self-hosted.
- Is spillage still maintained?
- The GitHub repository shows 53 commits in the last 90 days.
- What are alternatives to spillage?
- Similar projects tracked by PulseGate include sentinelforge-ai, stillos-ratings-mcp, and Cloud Armor WAF Patrol MCP.sentinelforge-aistillos-ratings-mcpCloud Armor WAF Patrol MCP
- Who makes spillage?
- spillage is developed by Maximilian Feix.
- How long has spillage been around?
- spillage first shipped in 2026.
Also in AI & LLM security
Same category — not a similarity match