@pmate/cli@0.29.7
CLI utilities for the pMate project
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings map to an administrative CLI with explicit command dispatch, fixed PMate endpoints, and a static SDK import. There are no install lifecycle hooks or source evidence of covert credential collection, third-party credential redirection, or automatic execution.
Decision evidence
public snapshot- The bundle uses a Function-created dynamic import, but its specifier is a fixed PMate SDK path.
- Some explicitly selected CLI commands can run SSH administrative actions, including remote nginx configuration removal.
- PMate session tokens are sent as Bearer authentication to the package's PMate auth API.
- package.json has no preinstall, install, or postinstall hook.
- The entrypoint runs only when invoked as the pmate CLI; importing it does not call main.
- No source evidence shows harvesting unrelated environment credentials or silently redirecting third-party API keys.
Source & flagged code
9 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.29.7.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.29.7 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.