apiblaze@0.20.46
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 has no registry-install lifecycle hook or covert automatic trigger, so a malicious verdict is not supported. Its explicit setup commands nevertheless alter agent/project control surfaces and proxy credential-bearing traffic.
Decision evidence
public snapshot- An explicit CLI option installs an API proxy as an external agent MCP server without an additional prompt.
- The CLI writes MCP settings containing an API-key header into the Codex configuration file.
- The sidecar replaces application fetch destinations with service-supplied routes and forwards request bodies and any existing x-api-key.
- The explicit sidecar setup command modifies the consumer project and can run a package-manager install.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle hook is prepublishOnly.
- The risky operations are reached through named CLI setup and MCP-install commands, not package installation or import alone.
- The network hosts and proxy behavior are aligned with the package's stated API-proxy function.
Source & flagged code
7 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.46.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.46 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.