apiblaze@0.21.26
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-aiInspected source supports a warning for explicit-command agent configuration mutation with persistent effects and later automatic refresh. The scanner's malicious label is not supported by a concrete covert attack chain.
Decision evidence
public snapshot- The manifest has a publisher build hook but no automatic npm install lifecycle hook.
- The CLI persists MCP entries in the user's Codex configuration.
- Agent setup asks the user to connect a proxy, or accepts an explicit installation option.
- Previously accepted MCP installations are automatically refreshed during later CLI runs.
- Setup also adds standing instructions to AGENTS.md or CLAUDE.md.
- The LLM credential is explicitly entered by the user and included in chat requests.
- No concrete covert credential harvesting or malicious install chain was established.
- Existing unrelated MCP entries receive conflict protection rather than unconditional replacement.
- The server client uses caller-supplied credentials for API operations.
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.26.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.26 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.