apiblaze@0.21.17
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-aiAgent configuration is a first-party, user-invoked capability with a confirm prompt or an explicit flag, and install hooks are absent. That is a guarded agent-config write, so it is a warning rather than a publish block or an unmarked clean package.
Decision evidence
public snapshot- User-run CLI calls claude mcp add or remove and writes ~/.codex/config.toml for an APIblaze MCP entry.
- Interactive create asks before connecting Claude or Codex; --install-mcp is an explicit flag.
- skill --install writes .claude/skills under the current project only when --install is passed.
- package.json has build and prepublishOnly scripts and no preinstall, install, or postinstall hook.
- Existing Claude or Codex MCP entries that are not APIblaze proxies are left untouched.
- Network defaults stay on apiblaze.com product hosts.
- No eval, self-dependency, or install-time agent config write.
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L77A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L77Findings
Affected versions and remediation
This report applies to apiblaze@0.21.17.
See all versions of apiblaze for other recorded verdicts.
- Review the evidence and your use of apiblaze@0.21.17 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.