@tsuga/cli@1.31.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe package has no npm install hook, and the agent integration is activated by an explicit CLI command. Because that setup enables automatic updates for a first-party agent plugin, classify it as a warning under the agent extension policy; the source does not establish a concrete attack.
Decision evidence
public snapshot- The package exposes `dist/cli.js` as the `tsuga` command.
- The CLI’s explicit Claude Code plugin setup can patch the user’s settings file.
- That setup adds a Tsuga GitHub marketplace entry with automatic updates enabled by default.
- The setup command offers `--no-auto-update` to skip the settings change.
- The manifest has no install lifecycle hook, so npm installation does not trigger this setup.
- The setup runs through an explicit CLI command and installs the package’s named Tsuga plugin.
- API URL validation restricts non-localhost destinations to Tsuga HTTPS hosts.
Source & flagged code
17 flaggedFindings
Affected versions and remediation
This report applies to @tsuga/cli@1.31.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.31.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.