apiblaze@0.21.59
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner's credential and execution leads resolve to product functionality: users deliberately configure a provider key for chat, and requests go to the configured APIblaze endpoint. The inspected manifest has no install hook; the CLI's prepublishOnly script builds and typechecks.
Decision evidence
public snapshot- The manifest maps the CLI and package entry to dist/index.js; its prepublishOnly script only builds and typechecks.
- Users explicitly add their own LLM key with `apiblaze llm set-key`; the CLI says the key is stored locally and sent to APIblaze only per chat turn.
- A chat turn includes the saved LLM key in its request body and sends that request to the configured MCP host's runtime-chat endpoint.
- The React widget sends a token returned by the caller-provided getToken function to its configured chat URL.
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.59.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.59 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.