@pmate/cli@0.42.5
CLI utilities for the pMate project
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe reported credential indicators are explained by service-specific CLI integrations: the OpenAI key comes from user configuration, and GitHub tokens are obtained for `gh` commands. There is no install hook, fixed unofficial OpenAI gateway, or import-time CLI startup in the reviewed source.
Decision evidence
public snapshot- The manifest has no install, preinstall, or postinstall hook.
- The OpenAI key is read from the user’s ~/.pmate/config.yaml configuration.
- The OpenAI client uses an optional base URL from that same configuration; no fixed foreign gateway is set in the inspected code.
- The CLI starts only when the file is run as the main module, so importing it does not launch the command handler.
- GitHub tokens are retrieved through `gh auth token` for the GitHub command flow.
Source & flagged code
10 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.42.5.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.42.5 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.