@xship/cli@0.0.145
Configure Claude Code, Codex, Grok Build and other coding tools for Xship AI with one command
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source sends runtime usage telemetry by default, with an opt-out but no evident disclosure in the inspected documentation. The observed fields do not establish credential exfiltration, so this warrants a telemetry warning rather than a publish block.
Decision evidence
public snapshot- Runtime telemetry is enabled by default; it can be disabled with the package-prefixed TELEMETRY setting.
- Telemetry events include command, step, status, duration, errors, and optional details; command-start details include only non-key flag names.
- The telemetry payload includes an install ID, CLI version, brand, operating system, OS release, architecture, and Node.js version.
- The CLI starts tracking during command execution and flushes telemetry when execution finishes.
- Telemetry is posted to /api/platform/vibecode/telemetry; the package’s default gateway host is ai.xship.live.
- The telemetry fields inspected are usage and machine metadata; command-start details omit positional values and flags containing “key”.
- Telemetry is sent to the package’s own configured gateway, and an environment setting provides an opt-out.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/lib/tools/desktop-process.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xship/cli@0.0.145.
See all versions of @xship/cli for other recorded verdicts.
- Review the evidence and your use of @xship/cli@0.0.145 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.