apiblaze@0.20.9
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 flagged primitives implement a disclosed, user-invoked API proxy sidecar rather than hidden execution or install-time compromise. No concrete credential harvesting, foreign control-surface mutation, or covert exfiltration chain was found.
Decision evidence
public snapshot- Explicit sidecar setup writes project configuration and instrumentation.
- The sidecar can report observed HTTPS origins using its configured API key.
- No install, preinstall, or postinstall lifecycle hook; only prepublishOnly is present.
- Sidecar activation requires a token and can be disabled; local/private hosts are excluded.
- Routing occurs only for server-provided approved origins, otherwise requests stay direct.
- Credential files are written locally with mode 0600.
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.9.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.9 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.