@pmate/cli@0.45.3
CLI utilities for the pMate project
AI Security Review
scanned 17h ago · by lpm-firewall-aiThe scanner's GitHub credential and dynamic execution leads are consistent with user-invoked CLI workflows: GitHub token handling is tied to repository configuration, and OpenAI credentials come from the user's pMate config. The executable only calls its command dispatcher when run directly; the reviewed source did not establish automatic credential exfiltration or malicious redirection.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the CLI and package main.
- GitHub token handling removes inherited GH_TOKEN and uses a repository-configured GitHub user.
- The OpenAI client reads its API key from the user's pMate config.
- The CLI calls main only when run directly, so importing the entry point does not start the command.
- Login exchanges a prompted login token with the configured auth API.
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.45.3.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.45.3 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.