@tsuga/cli@1.60.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe concrete concern is automatic updates enabled by the explicit Claude Code plugin setup command. The credential warning is not supported: requests use an API URL restricted to Tsuga's HTTPS API hosts or localhost.
Decision evidence
public snapshot- package.json points to dist/cli.js and lists build and prepack scripts, with no install lifecycle hook.
- The Claude Code setup command writes autoUpdate=true to the user's Claude settings file.
- The explicit plugin command installs Tsuga's plugin from its own marketplace; automatic updates are enabled by default and can be skipped with --no-auto-update.
- The API URL validation restricts non-localhost destinations to HTTPS on api.tsuga.com or api.tsuga-staging.com.
- Authenticated requests send a bearer token to the resolved API URL.
- The plugin settings change is reached through an explicit CLI setup command, not an npm install hook.
- The credential destination is restricted to Tsuga API hosts or localhost, so the scanner's credential-redirection hint is not supported by the inspected source.
Source & flagged code
13 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.60.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.60.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.