registry / @tsuga/cli / 1.101.0
@tsuga/cli@1.101.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 5d ago · by lpm-firewall-aiThis is a Tsuga management CLI whose runtime telemetry is gated by a saved choice, an interactive prompt, or an explicit environment setting. Its network report goes to the configured Tsuga API, and the package has no install lifecycle hooks.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
A user opts in at the interactive prompt, sets TSUGA_TELEMETRY=1, or has previously saved telemetry consent.
Impact
Usage reporting can include command and option details, run status, timing and spans after consent; no install-time collection or unrelated data collector was found.
Mechanism
The CLI posts run metadata and spans to its configured Tsuga API using a detached Node process.
AI rationale
This is a Tsuga management CLI whose runtime telemetry is gated by a saved choice, an interactive prompt, or an explicit environment setting. Its network report goes to the configured Tsuga API, and the package has no install lifecycle hooks.
Evidence
dist/cli.js
Network endpoints3
api.tsuga.comapi.tsuga-staging.comTSUGA_API_URL
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is a CLI for managing Tsuga resources; its executable is dist/cli.js.
- Runtime usage reporting checks saved consent first and otherwise asks an interactive user before saving consent; CI and non-success runs do not prompt or send by default.
- When enabled, the report sends CLI version, platform, Node version, run data and spans to the configured Tsuga API; the transport is a detached child process.
- The telemetry helper posts the report body to the supplied URL and suppresses network errors.
Evidence against
- The package has no install lifecycle scripts.
- The telemetry prompt describes the data as usage data and provides a command to change the setting later.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
18 flaggeddist/cli.jsView file
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_pat
severity = critical
line = 273
Critical
273patternName = github_oauth
severity = critical
line = 273
Critical
273patternName = github_server_token
severity = critical
line = 273
Critical
Secret Pattern
GitHub server-to-server token in dist/cli.js
dist/cli.jsFindings
9 Critical9 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.101.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.101.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.