apiblaze@0.21.53
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no malicious behavior. Chat credentials are used for the package’s user-invoked chat features, while Codex configuration changes occur through CLI setup and the manifest has no install lifecycle hook.
Decision evidence
public snapshot- The manifest defines only a prepublishOnly lifecycle hook, which runs the build and type check.
- The React widget sends a caller-provided token to a URL derived from the caller’s endpoint or project configuration, after the user submits a message.
- The CLI chat feature saves a user-provided model key locally and sends it with chat messages to the provisioned APIblaze runtime chat endpoint.
- The Codex configuration helper is reached through an explicit CLI setup flow; it writes the MCP server entry to the user’s Codex configuration.
- The CLI sends a run-count request to APIblaze during a CLI command, with command and run identifiers; the request can be disabled with DO_NOT_TRACK.
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.53.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.53 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.