apiblaze@0.21.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 published package is an APIblaze CLI and optional sidecar whose network and file writes match that product and start only after a user command or an explicit register call. There is no install lifecycle hook and no hidden exfiltration or agent-control hijack.
Decision evidence
public snapshot- package.json has a CLI bin and no preinstall, install, or postinstall hooks; scripts are build, typecheck, prepublishOnly, release, and test.
- dist/index.js is a commander CLI that runs only through program.parse(process.argv).
- Default control-plane hosts are https://dashboard.apiblaze.com and https://api.apiblaze.com.
- Agent MCP, Codex config, and Next.js sidecar wiring run from explicit CLI commands, not from npm install.
- The sidecar fetch wrapper is exported and activates only when register or withApiblaze is called, and it sends the caller API key to https://sidecar.abz.run.
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.21.11.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.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.