@shipeasy/cli@2.23.1
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI sends error details and command arguments to its own service without a disclosed consent or opt-out control in the reviewed source. The flow is limited to CLI errors and sanitizes arguments, so this is suspicious telemetry rather than a malicious attack.
Decision evidence
public snapshot- The CLI calls reportCliError for non-silent Commander errors during command execution.
- The error report includes the error message, sanitized command arguments, exit code, CLI and Node versions, platform, and timestamp; it adds the Shipeasy CLI key when available.
- The reporter POSTs that report to the configured Shipeasy worker’s /cli/errors endpoint.
- The manifest has no install lifecycle script; the package exposes a CLI and program entry point.
- The error report goes to the Shipeasy service and sanitizes arguments before sending them.
- The CLI entry point runs the command handler when invoked.
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.1.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.23.1 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.