@pmate/cli@0.44.1
CLI utilities for the pMate project
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential and network behavior is consistent with the CLI’s service integrations: the OpenAI key comes from user configuration, while the role command targets pMate’s auth API. The manifest has no install lifecycle hook, and the entry point dispatches user-selected commands.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the CLI and main entry point; the entry point dispatches based on explicit command-line arguments.
- The OpenAI client reads an API key from the user’s pMate config and uses its configured base URL when provided.
- The role handler sends its session token to the pMate auth API by default, with an explicit base-URL override.
- The manifest contains build and development scripts but no install lifecycle scripts.
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.44.1.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.44.1 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.