@wirecat/max-cli@0.91.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 4d ago · by lpm-firewall-aiThe reviewed install hook automatically changes the Windows user's PATH during a global install, which is suspicious under the install-time PATH setup rule. The credential, remote execution, and agent-configuration leads reviewed did not establish an attack: analysis uses the selected API endpoint, and agent skill writes are opt-in.
Decision evidence
public snapshot- The postinstall hook runs a helper that adds the CLI to the Windows user's PATH during a global install.
- The Windows helper verifies the CLI shim exists before changing PATH.
- Analysis credentials go to the selected API endpoint, defaulting to OpenAI or Anthropic; analysis requires an explicitly selected model.
- The postinstall helper skips non-global installs, and agent skill installation is opt-in.
- The agent skill command writes files only when explicitly invoked.
Source & flagged code
17 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.91.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.91.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.