apiblaze@0.21.39
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe reported agent configuration behavior is guarded by an explicit user choice, and the package has no npm install lifecycle hook. The inspected network and proxy configuration are consistent with the package's API proxy function; the scanner hints alone do not establish credential exfiltration.
Decision evidence
public snapshot- The manifest defines only a prepublishOnly build and typecheck lifecycle script; it has no install hook.
- Codex configuration is under the user's Codex home directory, and the bundle exposes it through explicit MCP setup.
- The setup flow asks the user whether to add this proxy to an installed client before proceeding with registration.
- The MCP install specification uses the proxy host and project values supplied by the package's proxy record.
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.39.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.39 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.