apiblaze@0.20.34
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package exposes a real conditional credential-forwarding capability to a dynamically supplied proxy destination. Explicit user setup and the absence of install-time activation reduce severity, but do not bind forwarded credentials to their intended service.
Decision evidence
public snapshot- The sidecar replaces the process-wide fetch function after registration.
- It copies existing request headers and sends them to a route base supplied by the APIblaze sidecar service, without removing Authorization or Cookie headers.
- The explicit setup command writes application configuration and instrumentation that activates the sidecar.
- The manifest has no install, preinstall, or postinstall hook; its only lifecycle-like script is prepublishOnly.
- Routing occurs only after an explicit sidecar setup and approval flow, so the source does not establish covert activation.
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.34.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.34 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.