apiblaze@0.21.0
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-aiThe package is not malicious at installation, but it has explicit agent configuration persistence and forwards user-supplied LLM credentials through its service. This warrants a warning rather than a publish block.
Decision evidence
public snapshot- The chat path puts a locally stored LLM provider key into an outbound request body.
- The explicit apichat MCP feature writes an API key into Codex MCP configuration and adds standing agent instructions.
- This can route future agent sessions to a package-controlled MCP endpoint with the configured credentials.
- The manifest has only prepublishOnly, so registry installation has no install-time hook.
- The agent configuration behavior is reached through explicit CLI options, not import-time code.
- No self-dependency, obfuscated payload, or unsolicited environment harvesting was found.
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.21.0.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.0 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.