apiblaze@0.21.8
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is a first-party API proxy CLI with no registry install lifecycle hook and no self-dependency chain. Agent config writes and fetch proxying are user-invoked product features aimed at APIblaze hosts.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall script; scripts are build, typecheck, prepublishOnly, release, and test.
- dist/index.js is the CLI entry and only dispatches commands by calling program.parse on process.argv.
- Claude MCP registration is invoked through the claude CLI from command handlers and replaces a server only after the caller runs that install path.
- Default control-plane base is the first-party host https://api.apiblaze.com.
- The sidecar can wrap global fetch and report approved HTTPS origins to sidecar.abz.run, but only after an application calls register with an APIblaze key.
- --install-mcp and skill --install can write Claude or Codex config, and those paths are explicit CLI options rather than install hooks.
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.21.8.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.8 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.