apiblaze@0.21.27
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-aiThe scanner's blocking conclusion is unsupported by the inspected activation and credential flows. Explicit agent configuration mutation and subsequent updates justify a warning under the supplied policy.
Decision evidence
public snapshot- The manifest has no automatic installation hooks or runtime self-dependency.
- Explicit CLI setup writes MCP configuration into Codex config.toml.
- Agent setup adds persistent instructions to project CLAUDE.md or AGENTS.md files.
- Interactive setup asks which agent to connect; an explicit install option also activates setup.
- Saved installation consent enables automatic MCP configuration refresh during later CLI use.
- Agent authentication can use a newly minted tenant credential; chat optionally forwards a caller-supplied LLM key to the proxy runtime.
- No covert credential harvesting or malicious installation chain was established.
- Codex setup refuses to replace a conflicting server belonging to another provider.
- The inspected server client sends caller-supplied credentials to configured API service endpoints.
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.27.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.27 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.