@pmate/cli@0.35.10
CLI utilities for the pMate project
AI Security Review
scanned 22d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner's credential-redirection claim: the OpenAI key path is configuration-driven, while login tokens go to the auth API session exchange. The dynamic-code finding is a loader for the package's chat SDK; no malicious behavior was established.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI and main entry; its scripts contain no install lifecycle hook.
- The login flow sends its returned token to the auth API session exchange and checks that the response matches the requested app.
- The OpenAI client reads its key from the user's pMate config and uses a base URL only when one is configured.
- The Function constructor loads the package's @pmate/chat-sdk runtime through dynamic import.
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.35.10.
See all versions of @pmate/cli for other recorded verdicts.
- Review the evidence and your use of @pmate/cli@0.35.10 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.