@shipeasy/cli@2.18.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe source establishes conditional credential exposure: a saved api_base_url controls where command-error reports and the saved CLI token are sent. The default is the package’s service, so this supports a warning rather than a block.
Decision evidence
public snapshot- The launcher runs the bundled CLI, whose error handler sends command errors to a URL derived from saved credentials.
- The error report attaches the saved CLI token and posts without a recipient-specific consent check.
- Saved credentials are read from a local JSON file, and the report destination can come from its api_base_url field.
- Login initializes the API destination to api.shipeasy.ai, consistent with the package’s service.
- The package manifest declares no install lifecycle scripts; the report path is reached after a CLI command error.
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.18.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.18.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.