@wirecat/max-cli@0.82.0
MAX Messenger bots through the official Bot API, and a personal MAX account, from the terminal — built for agents and scripts
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe lifecycle hook performs no setup for ordinary local installs and only writes an agent skill when a target is explicitly selected. The flagged browser code supports interactive MAX login and reads the token from MAX’s own web client; the reviewed paths show no unrelated credential destination or automatic account action.
Decision evidence
public snapshot- The postinstall wrapper only invokes setup for global npm installs.
- Global setup installs an agent skill only when MAX_INSTALL_AGENT is explicitly set to a supported target; otherwise it reports that no skill was installed.
- Browser token retrieval is part of a MAX web login flow, and the temporary browser profile is removed when the flow ends.
- The client’s session connection uses MAX’s web service, and the package describes itself as a terminal client for MAX Messenger.
- The package defines postinstall and prepare lifecycle scripts; prepare runs lefthook installation.
- The interactive login flow reads the MAX authentication token from the MAX web client’s local storage.
Source & flagged code
6 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @wirecat/max-cli@0.82.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.82.0 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.