apiblaze@0.20.4
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 correspond to documented CLI functionality: credentialed API calls, optional BYO-LLM chat, and explicit sidecar setup. Source inspection found no install-time execution or unconsented credential exfiltration chain.
Decision evidence
public snapshot- dist/index.js explicitly stores an optional LLM key and sends it only during a user-initiated chat turn.
- dist/sidecar/index.js can forward approved HTTPS requests, including bodies and an x-api-key header, through APIblaze.
- package.json has no preinstall/install/postinstall hook; prepublishOnly is publish-time build/typecheck.
- dist/index.js network calls use disclosed APIblaze service endpoints and authenticated CLI commands.
- Sidecar routing activates only after explicit setup plus origin approval; other requests remain direct.
- Credentials are stored locally with mode 0600 in ~/.apiblaze.
- child_process use is limited to opening the login browser and explicit sidecar package installation.
- No eval/vm, payload download/execution, broad harvesting, or stealth persistence was found.
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.4.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.4 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.