registry / @tsuga/cli / 1.86.0
@tsuga/cli@1.86.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s process and network signals correspond to a telemetry sender gated by consent, with destinations restricted to Tsuga API hosts or localhost. The manifest shows no install hook, and the inspected source did not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
A successful CLI run with telemetry enabled or consented.
Impact
A user who enables telemetry shares usage data with the configured Tsuga API. No independent malicious behavior was established.
Mechanism
The CLI serializes run metadata and spans, then posts them to its CLI-runs endpoint; the API URL is limited to Tsuga HTTPS hosts or localhost.
AI rationale
The scanner’s process and network signals correspond to a telemetry sender gated by consent, with destinations restricted to Tsuga API hosts or localhost. The manifest shows no install hook, and the inspected source did not establish a concrete attack surface.
Evidence
dist/cli.js
Network endpoints5
api.tsuga.comapi.tsuga-staging.comlocalhost127.0.0.1[::1]
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points the CLI command to dist/cli.js and lists build, test, and type-check scripts without an install hook.
- The telemetry sender checks saved consent first; otherwise it prompts on an interactive successful run, and TSUGA_TELEMETRY accepts explicit true values.
- When enabled, the CLI sends run metadata and spans to its CLI-runs endpoint. The API URL check restricts non-local destinations to HTTPS on Tsuga’s API hosts.
- The detected process execution and network request belong to this consent-gated telemetry sender.
Evidence against
- Telemetry includes command flags, so values supplied as flags may be included in the report when telemetry is enabled.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
16 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 Critical7 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
HighCommand Output Exfiltrationdist/cli.js
HighTrigger Reachable Command Output Exfiltration
Affected versions and remediation
This report applies to @tsuga/cli@1.86.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.86.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.