@pmate/cli@0.44.4
CLI utilities for the pMate project
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged credential flows are consistent with pMate session setup and GitHub CLI use. The managed-session check runs at CLI startup, but the source sends the token to pMate’s auth API and removes its temporary session file on exit.
Decision evidence
public snapshot- The manifest lists build, clean, dev, release, start, test, and typecheck scripts; it declares no install lifecycle hook.
- CLI startup checks HEBO_MEMORY_TOKEN and sends it as a bearer token to the pMate auth API to establish a pmate:factory session.
- The delegated session is written to a temporary session.json file and its temporary directory is removed on process exit.
- GitHub credentials are resolved for a configured GitHub user and passed to gh subprocesses.
- The reviewed credential flows use service-specific APIs or tools, and no unrelated collector or credential theft behavior was identified.
- The new Electron runtime’s clone and dependency-install actions are reachable through explicit runtime install or repair methods.
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.4.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.44.4 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.