@pmate/cli@0.44.11
CLI utilities for the pMate project
AI Security Review
scanned 19h ago · by lpm-firewall-aiThe flagged credential and execution patterns resolve to normal CLI and service behavior: GitHub credentials are passed to gh wrappers, while OpenAI settings come from the user's configuration. The added Electron runtime sends a logged-in pMate identity to the pMate issue API only when its methods are invoked.
Decision evidence
public snapshot- The manifest describes a pMate CLI and declares dist/index.js as its executable and main entry point.
- The CLI calls main() only when run directly, so importing the entry point does not start the command loop.
- GitHub tokens are resolved from the user's configured GitHub account and supplied to gh command wrappers.
- The OpenAI client uses the API key and optional base URL from the user's pMate configuration.
- The Electron runtime sends its logged-in identity token to pMate's issue API when an allowed method is invoked.
- The manifest has no install lifecycle scripts.
- The flagged shell matches in dependency files are shell syntax-highlighting rules, not evidence of executing those commands.
- No automatic transfer of GitHub credentials to an unrelated host was identified.
Source & flagged code
11 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.44.11.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.44.11 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.