@xship/cli@0.0.151
Configure Claude Code, Codex, Grok Build and other coding tools for Xship AI with one command
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package performs default runtime telemetry without disclosure in the inspected README, although it provides a TELEMETRY opt-out and sends data to its configured gateway. This warrants a warning, not a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI, except for dry runs and version-only invocations.
Impact
The gateway receives command metadata and potentially error text; home paths and certain secret formats are masked.
Mechanism
The CLI records command flags and telemetry events, then posts batches to the gateway’s /api/platform/vibecode/telemetry endpoint. TELEMETRY can disable collection.
AI rationale
The package performs default runtime telemetry without disclosure in the inspected README, although it provides a TELEMETRY opt-out and sends data to its configured gateway. This warrants a warning, not a malicious verdict.
Evidence
dist/lib/telemetry.jsdist/lib/command.js
Network endpoints1
Configured gateway: /api/platform/vibecode/telemetry
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runtime telemetry is enabled by default; it can be disabled with TELEMETRY=0, false, or off.
- Telemetry events include command steps, status, optional details, and error messages capped at 2,000 characters; home paths and some secret formats are masked.
- Each event batch is posted to /api/platform/vibecode/telemetry through the configured gateway.
- Invoking the CLI automatically records the command and most flag arguments, excluding arguments containing “key”.
- The package manifest declares no lifecycle scripts.
Evidence against
- Telemetry identifies the CLI, version, install ID, platform, OS release, architecture, and Node version; the inspected code does not show unrelated credential collection.
- The manifest’s entry points are the CLI and a library module; telemetry is triggered by CLI execution, not package installation.
Behavioral surface
ChildProcessEnvironmentVarsNetworkShell
HighEntropyStrings
Source & flagged code
7 flaggeddist/lib/tools/chatgpt-desktop.jsView file
1import{spawnSync as t}from"child_process";import{logger as n}from"../../utils/logger.js";import{brand as e}from"../brand.js";import{powerShellEnv as r}from"../powershell-env.js";im...
High
Child Process
Package source references child process execution.
dist/lib/tools/chatgpt-desktop.jsView on unpkg · L1dist/lib/tools/tool-installs.jsView file
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
High
1import{spawnSync as t}from"child_process";import{existsSync as n,realpathSync as r,statSync as e}from"fs";import{delimiter as o,dirname as s,isAbsolute as i,join as a}from"path";im...
Findings
1 Critical5 High4 Medium3 Low
CriticalPrevious Version Dangerous Deltadist/lib/components.js
HighChild Processdist/lib/tools/chatgpt-desktop.js
HighShelldist/lib/tools/tool-installs.js
HighSame File Env Network Executiondist/lib/tools/claude-desktop-cli.js
HighTrigger Reachable Persistencedist/lib/env-cleanup.js
HighRuntime Package Installdist/lib/tools/tool-installs.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/lib/persistent-env.js
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @xship/cli@0.0.151.
See all versions of @xship/cli for other recorded verdicts.
- Review the evidence and your use of @xship/cli@0.0.151 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.