registry / @tsuga/cli / 1.71.0
@tsuga/cli@1.71.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and source inspection found the reported credential redirect is prevented by a remote-host allowlist. Usage reporting is consent-gated, so the scanner signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI; usage reporting additionally requires saved consent or affirmative interactive consent after a successful command.
Impact
No confirmed unauthorized credential transfer or other attack impact was established.
Mechanism
The CLI validates its configured API URL before sending credentials and gates usage reporting through a consent check.
AI rationale
The manifest has no install lifecycle hook, and source inspection found the reported credential redirect is prevented by a remote-host allowlist. Usage reporting is consent-gated, so the scanner signals do not establish malicious behavior.
Evidence
package.jsondist/cli.js
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI entrypoint and lists no install lifecycle hook.
- The CLI refuses to send credentials to arbitrary remote hosts; remote API URLs must use HTTPS with an allowed Tsuga hostname, while localhost is also permitted.
- User session credentials are saved through the CLI’s config and credential store.
- Run telemetry is gated by a consent check; prompting occurs only in an interactive session after a successful command when no prior consent is saved.
Evidence against
- The scanner flagged credential redirection, but the inspected API URL validator blocks arbitrary remote destinations.
- The bundle contains network and environment-variable handling for ordinary Tsuga API requests and consent-gated usage reporting.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscation
Source & flagged code
13 flaggeddist/cli.jsView file
84patternName = github_pat
severity = critical
line = 84
Critical
84patternName = github_pat
severity = critical
line = 84
Critical
84patternName = github_oauth
severity = critical
line = 84
Critical
84patternName = github_server_token
severity = critical
line = 84
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.71.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.71.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.