apiblaze@0.20.11
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source establishes consented external-agent configuration and tool invocation, which the supplied policy classifies as a warning. No unconsented install-time agent mutation or other concrete malicious chain was identified.
Decision evidence
public snapshot- package.json has no registry install lifecycle hooks or runtime self-dependency.
- dist/index.js writes an MCP server entry into the user's Codex config.toml.
- dist/index.js replaces a named Claude MCP registration and can launch Claude with that server's tools allowed.
- Agent setup requires the explicit installMcp option or an interactive choice offering consent and refusal.
- Saved installation or refusal preferences suppress later automatic offers; consent does not enable automatic updates.
- MCP configuration uses the project's data-plane key, omitting it when consumer login authentication applies.
- The inspected setup is user-invoked and guarded by consent.
- The credential belongs to the API proxy being configured; no unrelated credential recipient or covert theft was established.
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.11.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.11 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.