apiblaze@0.21.40
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe configurable dashboard destination and bearer-token forwarding create a concrete conditional credential exposure capability. The inspected code does not establish hidden theft, and the manifest has no install-time hook, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The CLI can use an existing APIblaze session token from the environment or saved credentials.
- The dashboard recipient can be overridden with an environment variable, and API requests attach the session token there.
- The package writes Codex MCP configuration only through runtime setup code; the inspected manifest has no install hook that triggers it.
- The Codex configuration path is selected from CODEX_HOME or the user’s home directory.
- The manifest’s prepublishOnly hook runs build and typecheck; it is not an npm install hook.
- The inspected Codex setup requires a CLI option or interactive choice and performs registration after authorization.
Source & flagged code
9 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L32A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L32Findings
Affected versions and remediation
This report applies to apiblaze@0.21.40.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.40 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.