apiblaze@0.20.5
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner combination is explained by a documented API-management CLI and an explicit sidecar command, not covert credential harvesting or lifecycle execution. Source inspection found no install-time hook, remote code loading, stealth persistence, or unconsented control-surface mutation.
Decision evidence
public snapshot- dist/sidecar/index.js replaces global fetch after explicit setup and can route approved HTTPS origins through APIblaze.
- dist/index.js sidecar setup writes project integration files and invokes the chosen package manager only when the user runs the setup command.
- package.json has no install, preinstall, or postinstall hook; prepublishOnly is publish-time only.
- dist/index.js sends CLI credentials only to documented apiblaze.com API endpoints.
- dist/sidecar/index.js leaves unapproved, local, private, and denylisted origins direct.
- Sidecar routing requires an explicit user setup plus per-origin approval; source contains no stealth trigger or foreign AI-agent configuration write.
- The only shell execution opens the login URL; setup package-manager execution is explicit user-command behavior.
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.5.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.5 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.