@shipeasy/cli@2.21.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI automatically reports command arguments and error messages to its publisher’s API when parsing fails, with only limited secret redaction and no visible opt-out. This is suspicious runtime telemetry, but the inspected code does not show credential theft or transfer to a foreign host.
Decision evidence
public snapshot- The CLI entry point calls `run()` from `dist/index.js`.
- When command parsing throws a nonstandard `CommanderError`, `run()` passes the command, error message, and arguments to the reporter.
- The reporter includes command arguments and error details in a POST to `/cli/errors` and attaches the stored ShipEasy CLI token.
- The argument filter redacts recognized secret flags and SDK-key-shaped values, but passes other arguments through.
- The report is sent to the package publisher’s `api.shipeasy.ai` service, not a foreign host.
- Reporting is triggered by command errors rather than on every invocation; no install lifecycle scripts are declared.
- The code inspected does not show collection of Google AI or GitHub credentials.
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.21.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.21.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.