registry / @tsuga/cli / 1.58.0
@tsuga/cli@1.58.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe suspicious scanner signal is explained by a configurable API URL that is validated before credentials are sent; the validator permits only Tsuga HTTPS hosts or localhost. The only agent configuration mutation inspected is tied to explicit Claude plugin installation, and the package has no install lifecycle hook.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI or runs its plugin installation command.
Impact
No confirmed credential redirection or unconsented install-time agent configuration change was found.
Mechanism
The CLI resolves credentials for its configured API URL, checks that URL against an allowlist, and persists authentication through the keychain or local config. Claude auto-update configuration is written only when enabled during plugin installation.
AI rationale
The suspicious scanner signal is explained by a configurable API URL that is validated before credentials are sent; the validator permits only Tsuga HTTPS hosts or localhost. The only agent configuration mutation inspected is tied to explicit Claude plugin installation, and the package has no install lifecycle hook.
Evidence
dist/cli.jspackage.json
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes the CLI through dist/cli.js and declares no npm install lifecycle hook.
- The required Claude settings location belongs to an explicit plugin installation command; its optional auto-update setting writes to ~/.claude/settings.json.
- The API URL validator restricts credential destinations to HTTPS on api.tsuga.com or api.tsuga-staging.com, or localhost.
- User authentication is saved through the keychain when available, with a local config-file fallback.
- API requests use the resolved Tsuga API URL and the selected credential.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
13 flaggeddist/cli.jsView file
83patternName = github_pat
severity = critical
line = 83
Critical
83patternName = github_pat
severity = critical
line = 83
Critical
83patternName = github_oauth
severity = critical
line = 83
Critical
83patternName = github_server_token
severity = critical
line = 83
Critical
Findings
9 Critical4 High2 Medium4 Low
CriticalCritical Secretdist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
CriticalSecret Patterndist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighSecret Patterndist/cli.js
HighSecret Patterndist/cli.js
HighSecret Patterndist/cli.js
Affected versions and remediation
This report applies to @tsuga/cli@1.58.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.58.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.