@tsuga/cli@1.61.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the credential path is constrained to approved API hosts or loopback. The explicit plugin setup enables automatic updates by default, so this is a warning-level agent extension lifecycle risk rather than a confirmed attack.
Decision evidence
public snapshot- The manifest exposes a CLI and lists no install lifecycle hook.
- The API URL validator restricts credentials to HTTPS on approved hosts or loopback.
- Login exchanges a browser authorization code with the resolved API and saves the session.
- The Claude plugin setup writes to the user's Claude settings file.
- That setup adds the Tsuga GitHub marketplace with automatic updates enabled.
- The plugin setup is an explicit CLI command; automatic updates default on and can be disabled.
- No credential theft or other confirmed attack was identified; the CLI's credential destination is constrained by its URL validator.
- The agent configuration change is tied to an explicit plugin-install command, rather than an npm install hook.
Source & flagged code
13 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.61.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.61.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.