@xship/cli@0.0.139
⚠ Under reviewConfigure Claude Code, Codex, Grok Build and other coding tools for Xship AI with one command
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe inspected package code does not establish a concrete attack: telemetry targets the configured service and plugin setup uses Claude’s official plugin mechanism. Several imported dependencies remained metadata-only, so their behavior is unresolved and a clean verdict is not supported.
Decision evidence
public snapshot- The manifest identifies the CLI entrypoints and package identity; the reviewed manifest excerpt shows no lifecycle hook.
- Telemetry sends event data to the configured service base URL and uses the configured API key for that request; telemetry can be disabled through its environment setting.
- Claude plugin setup is gated by a skip setting and uses Claude’s plugin command to add official plugins.
- Inspected TOML, Chalk, and Commander files are ordinary library modules without lifecycle scripts in the reviewed excerpts.
- Several imported runtime dependencies were available only as registry metadata, leaving their source behavior unresolved.
- The inspected telemetry code sends to a URL derived from the configured service base URL rather than a hardcoded unrelated recipient.
- The reviewed plugin setup installs official Claude plugins through Claude’s own plugin command.
Source & flagged code
6 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.139.
See all versions of @xship/cli for other recorded verdicts.
- Review the evidence and your use of @xship/cli@0.0.139 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.