apiblaze@0.21.52
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest declares no install-time lifecycle hook; prepublishOnly only builds and typechecks. Source inspection traced the credential-bearing requests to chat flows and the agent configuration writes to CLI setup or refresh of a previously installed entry.
Decision evidence
public snapshot- package.json maps the CLI and main entry to dist/index.js; its only lifecycle-like script is prepublishOnly, which runs the build and typecheck.
- dist/index.js writes the Codex MCP entry during CLI setup. The forced setup path uses --install-mcp, while automatic refresh applies to an entry already recorded as installed.
- The React bundles use the supplied endpoint or a project-specific runtime URL. Their message handlers send a bearer token returned by the caller’s getToken callback.
- In both React bundles, suggestion clicks, Enter, and the Send button call the message send routine.
- The CLI saves a user-supplied LLM provider key locally and includes it in a request to the project runtime chat endpoint.
Source & flagged code
8 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.52.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.52 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.