@shipeasy/cli@2.15.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection contradicts the malicious scanner label: there are no lifecycle hooks or covert execution chain. Its explicit agent-wiring and automation capabilities warrant a warning under the stated policy.
Decision evidence
public snapshot- `dist/index.js` runs an npm global install of `skills` during explicit setup.
- `shipeasy setup`/trigger commands write MCP and agent configuration for several coding agents.
- Copilot trigger setup can create a repo agent file and set a GitHub agent secret after prompting.
- CLI startup checks npm registry; command errors are posted to Shipeasy with sanitized argv.
- `package.json` has no preinstall/install/postinstall lifecycle hook.
- `bin/shipeasy.js` only invokes the CLI entrypoint.
- Agent/config writes are behind explicit CLI setup, upgrade, or trigger commands.
- No source evidence of credential harvesting, hidden payload execution, or destructive behavior.
Source & flagged code
6 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.15.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.15.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.