apiblaze@0.20.2
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-aiScanner signals arise from legitimate CLI authentication, API requests, and an opt-in sidecar. Source inspection found no malicious execution chain, exfiltration to an unrelated endpoint, or lifecycle-based persistence.
Decision evidence
public snapshot- package.json has no install/preinstall/postinstall hook; prepublishOnly is publishing-time build/typecheck.
- dist/index.js only runs CLI command parsing at entry; network and file actions are command-driven.
- Credentials are stored locally under ~/.apiblaze with mode 0600 and used for documented APIblaze requests.
- dist/sidecar/index.js only wraps fetch after an application explicitly imports/registers it and requires an APIBLAZE token.
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.2.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.2 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.