apiblaze@0.20.1
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’s env/network/child-process combination maps to a documented, explicitly invoked API-proxy CLI. No lifecycle execution, covert credential harvesting, foreign agent-control mutation, or stealth payload execution was found.
Decision evidence
public snapshot- dist/index.js: explicit `init`/`sidecar setup` writes Next.js instrumentation and `.env.local`, then may invoke the chosen package manager.
- dist/sidecar/index.js: registered sidecar wraps global fetch and forwards approved origins with its API key.
- package.json has no preinstall/install/postinstall hook; only prepublishOnly.
- Setup mutations are reached only by explicit `apiblaze init` or `apiblaze sidecar setup` commands.
- Sidecar leaves unapproved, local, and denylisted origins direct; approval is a separate CLI command.
- Credentials are stored in package-owned ~/.apiblaze files with mode 0600.
- Network hosts and bearer/API-key use implement the documented API proxy, login, and sidecar functions.
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.1.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.20.1 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.