apiblaze@0.20.10
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 flags reflect an explicit API-proxy/sidecar feature, including project setup and outbound routing. Source inspection found no lifecycle-triggered execution or concrete covert credential-exfiltration chain.
Decision evidence
public snapshot- Explicit `init`/`sidecar setup` commands modify a chosen Next.js project and enable the sidecar.
- The sidecar can wrap `globalThis.fetch`, report external origins, and route only service-approved origins.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- Project writes and package-manager execution occur only in explicit setup commands.
- Without an APIBLAZE token the sidecar returns without changing fetch.
- Unapproved origins remain direct; observed reporting sends only the origin.
- No credential harvesting, stealth persistence, remote code loading, or foreign AI-agent configuration writes found.
Source & flagged code
8 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.10.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.10 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.