registry / @tsuga/cli / 1.72.0
@tsuga/cli@1.72.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe shipped entrypoint’s credential and telemetry paths are consistent with the CLI’s stated function and include destination validation and effective telemetry consent. Scanner signals for process execution and network access correspond to telemetry transport and ordinary API use, not a confirmed attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI; telemetry additionally requires an opt-in setting or affirmative prompt response.
Impact
No confirmed unauthorized credential transfer or command-output exfiltration was established.
Mechanism
The CLI attaches credentials to API requests after validating the API destination. Its telemetry subprocess posts command and execution metadata, not captured command output.
AI rationale
The shipped entrypoint’s credential and telemetry paths are consistent with the CLI’s stated function and include destination validation and effective telemetry consent. Scanner signals for process execution and network access correspond to telemetry transport and ordinary API use, not a confirmed attack.
Evidence
package.jsondist/cli.js
Network endpoints1
api.tsuga.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 manifest points the CLI to dist/cli.js and lists no install lifecycle hook.
- The CLI validates its API URL, requiring HTTPS for Tsuga domains and otherwise allowing only localhost; its default is the Tsuga API.
- API requests use a bearer token derived from the configured credential and send it to the validated API URL.
- Login exchanges a browser authorization code and saves the resulting session locally.
- Run telemetry sends command and execution metadata only after explicit opt-in or affirmative consent; the subprocess posts that metadata and does not collect command output.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
17 flaggeddist/cli.jsView file
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_pat
severity = critical
line = 268
Critical
268patternName = github_oauth
severity = critical
line = 268
Critical
268patternName = github_server_token
severity = critical
line = 268
Critical
Findings
9 Critical8 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
HighChild Processdist/cli.js
HighSame File Env Network Executiondist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/cli.js
Affected versions and remediation
This report applies to @tsuga/cli@1.72.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.72.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.