apiblaze@0.20.3
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-aiStatic inspection shows a feature-rich API CLI with opt-in sidecar/project setup, not a malicious install or covert credential-exfiltration chain. Scanner findings arise from legitimate authenticated API, environment, and command functionality.
Decision evidence
public snapshot- dist/index.js stores CLI credentials and makes authenticated API calls.
- dist/index.js sidecar setup can edit a user-selected Next.js project and invoke its package manager.
- dist/sidecar/index.js wraps global fetch only when explicitly registered and token-configured.
- package.json has no preinstall/install/postinstall hook.
- Network calls target APIblaze service hosts and implement documented CLI/proxy features.
- Credential files are local and mode 0600; no unrelated file harvesting found.
- Sidecar reports origins only and routes only explicitly approved HTTPS origins.
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.3.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.3 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.