@wirecat/max-cli@0.80.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 flagged lifecycle scripts perform git-hook setup during development and conditional PATH or agent-skill setup for global installs. The browser code reads a MAX login token from web.max.ru in a dedicated temporary profile; no unrelated exfiltration or unsolicited account action was identified.
Decision evidence
public snapshot- The package describes a MAX Messenger CLI and exposes dist/bin/max.js as its command entry point.
- The prepare script installs git hooks; the postinstall wrapper runs setup only for global installs.
- Global setup updates the Windows user PATH or installs an agent skill only when MAX_INSTALL_AGENT is explicitly set.
- The browser login flow visits web.max.ru and reads its session token from that site’s localStorage for the requested login.
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.80.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.80.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.