registry / @tsuga/cli / 1.117.0
@tsuga/cli@1.117.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe bundled CLI’s telemetry is consent-gated and reports command and runtime metadata to the configured Tsuga API. The process execution and networking serve the CLI’s stated purpose, and the manifest has no install lifecycle scripts.
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
Telemetry runs after a successful CLI command only when consent is saved, TSUGA_TELEMETRY is enabled, or the user accepts the interactive prompt.
Impact
No unauthorized collection or harmful behavior was identified in the reviewed source.
Mechanism
The CLI submits command and runtime metadata to its configured Tsuga API using a detached Node process.
AI rationale
The bundled CLI’s telemetry is consent-gated and reports command and runtime metadata to the configured Tsuga API. The process execution and networking serve the CLI’s stated purpose, and the manifest has no install lifecycle scripts.
Network endpoints1
Configured Tsuga API URL
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 exposes dist/cli.js as the tsuga command and declares no install lifecycle scripts.
- Run telemetry requires saved consent, TSUGA_TELEMETRY=1/true, or an interactive prompt after a successful run; users can change the setting.
- Telemetry records the CLI command path, duration, flags, output format, caller type, and a hashed agent session ID, plus runtime and trace fields.
- Telemetry is sent to the configured Tsuga API through a detached Node process; the endpoint description says runs are sent only by CLIs that opted in.
Evidence against
- The bundle references process execution, environment variables, filesystem operations, and network access; these support CLI operation and telemetry.
- The telemetry code uses process arguments to pass the API URL and JSON payload to its helper, but the helper posts those arguments as data rather than executing them.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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.117.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.117.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.