apiblaze@0.21.45
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe source indicates an agent configuration capability with setup-time writes, but the reviewed path does not establish an unconsented install-time attack or credential exfiltration. This is a guarded agent capability, so it warrants a warning rather than a block.
Decision evidence
public snapshot- The package entrypoint is dist/index.js.
- The Codex setup code writes an MCP server block using the supplied name, URL, and optional API key.
- The agent setup flow takes a selected endpoint and may attach a key before calling the agent configuration installer.
- The installer updates Claude or Codex configuration as part of the setup flow.
- No install lifecycle hook was identified; configuration changes are tied to the agent setup flow.
- package.json exposes dist/index.js as the main entrypoint and defines prepublishOnly only for building and typechecking.
- The inspected agent configuration path does not show an npm install hook or an unrelated recipient for the key.
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L32A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L32Findings
Affected versions and remediation
This report applies to apiblaze@0.21.45.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.45 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.