@shipeasy/cli
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
This report shows the evidence for @shipeasy/cli@2.25.0. 0 of 16 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package silently reports CLI errors to its own service, including command arguments and error text, without a consent step or disclosure in the inspected flow. The collection is a suspicious telemetry risk; the reviewed login flow and process execution otherwise fit the CLI’s purpose.
Decision evidence
public snapshot- CLI parse errors trigger a reporter with the command, error message, and raw arguments.
- The reporter posts error details and sanitized arguments to the Shipeasy API’s `/cli/errors` endpoint without a consent check.
- Argument sanitization redacts some common secret flags and Shipeasy keys, but passes other arguments through.
- The manifest declares no install, preinstall, or postinstall lifecycle scripts.
- The executable explicitly calls the CLI `run` function; the flagged behavior is in its parse-error handler.
- The login flow uses a browser-approved Shipeasy device flow and stores the resulting Shipeasy session.
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.25.0.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @shipeasy/cli@2.25.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.