registry / @wirecat/max-cli / 0.67.0
@wirecat/max-cli@0.67.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 14d ago · by lpm-firewall-aiInspected lifecycle code shows a global-install guard and explicit selection for agent-skill installation; the prepare script installs Lefthook. The selected runtime dependency @wirecat/cli-core could not be inspected, so review remains unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Runtime use of the CLI, which imports @wirecat/cli-core.
Impact
Behavior implemented by this dependency remains unassessed, so a clean verdict cannot be established from the inspected source.
Mechanism
The package imports @wirecat/cli-core for CLI and transport functions, but the supplied dependency snapshot was unavailable for source review.
AI rationale
Inspected lifecycle code shows a global-install guard and explicit selection for agent-skill installation; the prepare script installs Lefthook. The selected runtime dependency @wirecat/cli-core could not be inspected, so review remains unresolved.
Evidence
package.jsondist/bot/transport.js
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package declares @wirecat/cli-core@0.370.0 as a runtime dependency, and its code imports that dependency for transport operations; the available snapshot could not be inspected.
- The postinstall hook runs global-install completion only when npm_config_global is true; the completion code limits agent-skill installation to an explicitly supplied agent setting.
- The prepare script runs lefthook install, and the CLI entrypoint loads the app and runs the requested command.
Evidence against
- No concrete attack was identified in the inspected lifecycle or runtime excerpts.
- The required agent-skill target maps a skill path under .claude or .agents; the inspected global-install caller requires an explicit agent selection.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedpackage.jsonView file
•scripts.postinstall = node install/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/session/browser.jsView file
1import { spawn } from "node:child_process";
L2: import { existsSync, mkdtempSync, realpathSync, rmSync } from "node:fs";
...
L9: };
L10: const WEB_MAX = "https://web.max.ru/";
L11: const AUTH_KEY = "__oneme_auth";
...
L17: export const findChromium = () => {
L18: const named = process.env.MAX_BROWSER;
L19: if (named)
L20: return named;
L21: if (process.platform === "darwin") {
L22: return [
...
L129: // Chrome writes to the profile while it shuts down; removing it first leaves half of it behind.
Findings
3 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitydist/session/browser.js
HighSemantic Analysis Limiteddist/bot/transport.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperinstall/windows.ps1
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wirecat/max-cli@0.67.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.67.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.