@wirecat/max-cli@0.76.0
⚠ Under reviewMAX Messenger bots through the official Bot API, and a personal MAX account, from the terminal — built for agents and scripts
AI Security Review
scanned 10d ago · by lpm-firewall-aiInspected source shows gated global-install setup and a browser-based MAX login flow, without a confirmed attack. The required clean citation coverage exceeds the citation limit, so the package needs further review to resolve the verdict.
Decision evidence
public snapshot- The manifest defines a postinstall hook that runs install/postinstall.mjs.
- The lifecycle wrapper runs the install module only for global npm installs; skill installation also requires MAX_INSTALL_AGENT to select a target.
- The browser login flow reads a token from the MAX web client’s local storage and returns it for login.
- The package’s credential store reads the profile token through its credential interface.
- The global install hook skips skill installation when MAX_INSTALL_AGENT is unset or set to none.
- The browser flow uses a temporary profile and closes the browser session after retrieving a token; inspected excerpts show no token upload.
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.76.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.76.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.