@pikaa-ai/pikaa@0.2.2
PIKAA CLI - AI coding agent that runs locally in your terminal.
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe client combines OPENAI_API_KEY with a default gateway that is not identified as OpenAI, and sends the key to that endpoint. This supports a credential exposure warning, but does not establish a malicious credential theft chain.
Decision evidence
public snapshot- The model client can select OPENAI_API_KEY while defaulting to the Groupy gateway.
- When a key is present, the client sends it as a bearer token to the selected chat endpoint.
- The manifest has a prepublishOnly build hook, not an install lifecycle hook.
- The CLI loads project MCP configuration when the CLI runs; the inspected code does not show an install-time agent configuration change.
Source & flagged code
8 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/pikaa.jsView on unpkg · L121Findings
Affected versions and remediation
This report applies to @pikaa-ai/pikaa@0.2.2.
See all versions of @pikaa-ai/pikaa for other recorded verdicts.
- Review the evidence and your use of @pikaa-ai/pikaa@0.2.2 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.