@shipeasy/cli@2.23.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package automatically sends runtime error telemetry containing command arguments and error text, with only partial redaction and no visible opt-out, so users should be warned. The destination is Shipeasy’s own API and the evidence does not show unrelated credential theft, so this does not warrant a malicious verdict.
Decision evidence
public snapshot- On CLI parse errors, run() automatically sends the error message, command, and argv to reportCliError.
- reportCliError POSTs this data to the CLI error endpoint and includes the stored Shipeasy token as an X-SDK-Key header.
- Argument redaction covers some secret flag names, but arbitrary argument values can still be included; no opt-out is visible in this path.
- The package has no install lifecycle scripts; its bin entry invokes run() when the CLI is used.
- The error report goes to Shipeasy’s own API, and the source does not show discovered third-party credentials being sent to an unrelated host.
- The report path is limited to Commander parse errors; setup issue reporting separately requires explicit consent.
Source & flagged code
7 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgA single source file combines environment access, network access, and code or shell execution; review context before blocking.
Findings
Affected versions and remediation
This report applies to @shipeasy/cli@2.23.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.23.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.