@pmate/cli@0.46.0
CLI utilities for the pMate project
AI Security Review
scanned 12h ago · by lpm-firewall-aiThe flagged credential and network references are consistent with pMate CLI integrations: the OpenAI key comes from user configuration, and GitHub token lookup is conditional on repository configuration. The reviewed paths do not show credentials being sent to an unrelated host or executed code being concealed.
Decision evidence
public snapshot- The manifest identifies this as the pMate CLI and exposes dist/index.js as its command entry point.
- The OpenAI client reads its API key from the user's ~/.pmate/config.yaml and accepts a configured base URL.
- GitHub token retrieval is conditional on a repository configuration naming a GitHub user and uses `gh auth token`.
- The agent resource handler uses the pMate agent API host and a pMate session token.
Source & flagged code
9 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L90A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L90Findings
Affected versions and remediation
This report applies to @pmate/cli@0.46.0.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.46.0 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.