apiblaze@0.20.44
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real, high-impact agent-extension and traffic-routing capability, but it is guarded by explicit CLI commands or an interactive choice rather than an install-time hook. Source inspection found no automatic lifecycle execution or concrete covert exfiltration chain.
Decision evidence
public snapshot- The explicit MCP-install flow writes an APIblaze MCP server, including an API key when supplied, into the Codex configuration.
- The user-invoked sidecar setup rewrites project environment and instrumentation files and installs apiblaze in that project.
- The sidecar replaces global fetch, reports external origins, and relays approved requests with its token.
- package.json has no npm install lifecycle hook; prepublishOnly is publish-time only.
- MCP installation requires --install-mcp or an interactive selection and refuses a same-name non-APIblaze entry.
- The server client sends configured control-plane credentials to APIblaze service hosts for its stated API-management functions.
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L77A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L77Findings
Affected versions and remediation
This report applies to apiblaze@0.20.44.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.44 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.