@shipeasy/cli@2.16.0
CLI for the Shipeasy platform (flags, experiments, translations, bugs)
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an explicit-user-command, same-vendor agent integration rather than install-time malware. Warn for the broad AI-agent configuration capability and bearer propagation.
Decision evidence
public snapshot- dist/index.js: `mcp install` defaults to all detected AI clients and writes/registers a Shipeasy MCP server.
- dist/index.js: explicit setup/upgrade commands invoke agent CLIs and can install/refresh skills or the CLI.
- dist/index.js: user-scope MCP entries may carry the stored Shipeasy bearer token.
- dist/index.js: error reporting sends OS platform/architecture and sanitized CLI errors to the Shipeasy API.
- package.json has no preinstall, install, or postinstall hook.
- bin/shipeasy.js only invokes the bundled CLI after a user runs the binary.
- Agent-config mutation is behind explicit `setup`, `mcp install`, or `upgrade` commands.
- No eval, remote code download-and-execute chain, credential harvesting, or destructive broad file operation was found.
Source & flagged code
5 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.16.0.
See all versions of @shipeasy/cli for other recorded verdicts.
- Review the evidence and your use of @shipeasy/cli@2.16.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.