@tsuga/cli@1.66.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its credential destination check restricts where credentials can be sent. Its explicit Claude plugin setup command enables automatic updates for the Tsuga plugin by default, which warrants a warning for agent configuration capability.
Decision evidence
public snapshot- The manifest exposes dist/cli.js and has no install lifecycle hook.
- The Claude setup writes to the user's Claude settings and sets automatic updates for the Tsuga marketplace entry.
- The settings change is part of the explicit Claude plugin setup command; automatic updates are enabled by default and can be skipped.
- The API URL check rejects credential transfers to destinations outside the allowed Tsuga HTTPS hosts or localhost.
- The agent configuration change requires running the plugin setup command; the package manifest has no preinstall, install, or postinstall hook.
- The inspected credential check restricts destinations, so the scanner's credential redirect signal does not establish an unrelated recipient.
Source & flagged code
13 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.66.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.66.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.