registry / @wirecat/max-cli / 0.68.0
@wirecat/max-cli@0.68.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-aiThe inspected postinstall path is limited to global npm installs, and agent skill installation requires an explicit environment selection. I could not resolve the source of the required @wirecat/cli-core dependency after attempting inspection, so the package cannot be cleared.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Use of @wirecat/cli-core during CLI runtime.
Impact
The dependency's behavior remains unknown; no specific impact is established.
Mechanism
The package declares this runtime dependency, but its supplied source archive was truncated and its behavior could not be resolved.
AI rationale
The inspected postinstall path is limited to global npm installs, and agent skill installation requires an explicit environment selection. I could not resolve the source of the required @wirecat/cli-core dependency after attempting inspection, so the package cannot be cleared.
Evidence
package.json
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json runs the postinstall script, which only loads its follow-up for global npm installs.
- The global install path leaves the agent skill uninstalled unless MAX_INSTALL_AGENT or TG_INSTALL_AGENT selects a target; the skill path points to user agent skill folders.
- package.json declares @wirecat/cli-core@0.380.0 as a runtime dependency, but its source archive could not be fully inspected in this snapshot.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
6 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
4 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitydist/session/browser.js
HighSemantic Analysis Limiteddist/bot/transport.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/client/values.js
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.68.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.68.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.