@pmate/cli@0.42.6
CLI utilities for the pMate project
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged OpenAI credential flow uses a key and optional base URL from the user's configuration, with no fixed unrelated gateway in the client constructor. The package has no install hook, and its CLI main routine runs only when directly executed.
Decision evidence
public snapshot- The manifest points the CLI and package main entry to dist/index.js and declares no install lifecycle hook.
- The CLI calls main() only when dist/index.js is executed as the main module.
- The OpenAI client reads its key and optional base URL from the user's pMate configuration; this constructor does not set a publisher-controlled gateway.
- GitHub handling removes inherited GH_TOKEN and retrieves a token with gh only when repo configuration names a GitHub user.
- The package uses network APIs and child-process execution for its CLI features, which can resemble exfiltration or shell activity in static scans.
- The OpenAI configuration supports a custom base URL, so the user can choose where that configured key is sent.
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.6.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.42.6 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.