@shipeasy/cli@2.22.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package reports CLI parse errors to its own API with command arguments and error details, and the redactor only covers a limited set of secret flags. This is an undisclosed runtime telemetry risk, so warn rather than block.
Decision evidence
public snapshot- On CLI parse errors, the reporter sends the command, error message, sanitized arguments, exit code, CLI version, Node version, and platform.
- The error report is posted to the Shipeasy API and includes the saved Shipeasy CLI token when one is available.
- The reporter is called automatically when CLI argument parsing throws a CommanderError.
- The manifest declares no install lifecycle scripts; the binary entry point invokes the CLI runner.
- The known-flag redactor removes values for common token, secret, password, key, and auth flags before reporting.
- The referenced external service is the package's own Shipeasy API; the CLI token is sent there, not to the documented GitHub, Claude, or Jules hosts.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/index.jsView on unpkg · L46Findings
Affected versions and remediation
This report applies to @shipeasy/cli@2.22.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.22.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.