apiblaze@0.21.42
APIblaze CLI — Chat with your APIs, Manage your API keys, users and groups with the APIblaze serverless proxy
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe package has no automatic install-time agent configuration mutation, but an explicit CLI flow persists agent configuration and project instructions. Under the agent integration policy, this merits a warning for explicit-user-command configuration mutation; the inspected credential is directed to the selected APIblaze proxy.
Decision evidence
public snapshot- The manifest’s only lifecycle hook is prepublishOnly, which runs build and typecheck.
- The Codex integration destination is derived from CODEX_HOME or the user’s .codex directory.
- The CLI offers MCP installation through an interactive choice, and the integration writes MCP configuration and a project instruction file.
- The configured MCP URL and optional API key come from the selected APIblaze proxy.
- No package install hook was found that automatically changes agent configuration.
- The inspected credential flow targets the selected APIblaze MCP proxy; no unrelated recipient was established.
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.42.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.42 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.