@pikaa-ai/pikaa@0.1.7
PIKAA CLI - AI coding agent that runs locally in your terminal.
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection confirms a concrete cross-service credential forwarding risk: OPENAI_API_KEY may be sent to the package's default Groupy gateway unless the user configures another base URL. The gateway is part of the package's stated service, but the OpenAI credential is not constrained to its intended service, so this warrants a warning rather than a malware block.
Decision evidence
public snapshot- The CLI accepts OPENAI_API_KEY and passes it to the model client; its base URL may remain unset when no service URL is configured. [dist/cli.js]
- The model client uses the package's Groupy gateway as the default base URL while selecting OPENAI_API_KEY as a credential source. [dist/index.js]
- The client adds that key as a bearer token to its request to the selected gateway. [dist/index.js]
- The flagged CLI location loads MCP configuration from the project directory; it does not itself establish an attack. [dist/cli.js]
- The package has no automatic install lifecycle hook; its only publication hook builds JavaScript. [package.json]
- The launcher runs a bundled native binary when present or imports the CLI entrypoint otherwise. [bin/pikaa.js]
Source & flagged code
9 flagged · loading sourcePackage source references dynamic require/import behavior.
bin/pikaa.jsView on unpkg · L79Findings
Affected versions and remediation
This report applies to @pikaa-ai/pikaa@0.1.7.
See all versions of @pikaa-ai/pikaa for other recorded verdicts.
- Review the evidence and your use of @pikaa-ai/pikaa@0.1.7 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.