@shipeasy/cli@2.19.0
⚠ Under reviewCLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package’s own source did not establish a concrete attack, and the flagged config schema appears to parse local JSON. The imported runtime SDK remains unresolved, so the source review cannot support a clean verdict.
Decision evidence
public snapshot- The manifest declares a CLI entry point and lists no install lifecycle hook.
- The executable source imports the declared runtime dependency @shipeasy/sdk/client, whose implementation could not be resolved from the inspected package source.
- On command parsing errors, the CLI reports sanitized arguments and platform details to its configured API endpoint, attaching the session key when present; the default endpoint is ShipEasy’s API.
- The highlighted config schema reads and parses a local JSON file before merging it with defaults.
- The package manifest contains build and development scripts but no preinstall, install, or postinstall script.
- The observed error report defaults to the package’s own API host, and its caller is the CLI command parser error handler.
- The inspected config schema uses JSON parsing and validation; the reviewed excerpt shows no execution or network behavior.
Source & flagged code
7 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.19.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.19.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.