apiblaze@0.19.32
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-aiSource disproves the scanner's implied install-time credential theft: there is no install hook and the relevant behavior is explicit CLI setup. The documented proxy can handle credentials and request data, so it merits a warning rather than a clean verdict.
Decision evidence
public snapshot- dist/sidecar/index.js replaces globalThis.fetch and routes approved HTTPS origins through APIblaze.
- Routed requests preserve body and forward an existing x-api-key as x-abz-fwd-x-api-key.
- Explicit sidecar setup writes project configuration and invokes a package-manager install command.
- package.json has only prepublishOnly; no install-time lifecycle hook.
- Sidecar modification is reached only through documented apiblaze init/sidecar setup commands.
- Unapproved, local, and listed telemetry origins go direct; no broad environment harvesting found.
- Endpoints and credential handling are APIblaze service functionality, not a hidden unrelated destination.
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.19.32.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.19.32 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.