@pmate/cli@0.44.9
CLI utilities for the pMate project
AI Security Review
scanned 19h ago · by lpm-firewall-aiThe flagged credential flow uses a supplied pMate token with pMate’s auth service, while the GitHub token use is for repository commands. The newly added runtime installer is reached through an explicit method, and the manifest has no install lifecycle scripts.
Decision evidence
public snapshot- The manifest identifies `dist/index.js` as the CLI entry point and package main, with no lifecycle scripts.
- The CLI’s managed session flow is conditional on `HEBO_MEMORY_TOKEN` and uses the pMate auth service.
- The added Electron runtime exposes installation through an explicit `runtime.install` method; install behavior is not an npm lifecycle hook.
- The CLI performs network requests and uses credentials for pMate services as part of its stated CLI purpose.
- The Electron runtime can clone and install its runtime repository when its install method is called.
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.9.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.44.9 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.