registry / @tsuga/cli / 1.149.0
@tsuga/cli@1.149.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe command entry point’s network and subprocess behavior implements disclosed usage reporting for the Tsuga CLI. Reporting requires existing consent, an environment opt-in, or acceptance of an interactive prompt, so the scanner’s command-output and network signals do not establish malicious behavior.
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 CLI run reaches the reporting path; reporting proceeds only when telemetry is enabled or the user accepts the interactive prompt.
Impact
Opted-in users share usage data with Tsuga; the reviewed flow does not show credential collection or unrelated data transmission.
Mechanism
It posts CLI run metadata and spans to the configured Tsuga API’s `/v1/cli-runs` endpoint using a detached Node subprocess.
AI rationale
The command entry point’s network and subprocess behavior implements disclosed usage reporting for the Tsuga CLI. Reporting requires existing consent, an environment opt-in, or acceptance of an interactive prompt, so the scanner’s command-output and network signals do not establish malicious behavior.
Network endpoints1
/v1/cli-runs
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 identifies this as Tsuga’s resource-management CLI and exposes dist/cli.js as its command entry point.
- Run reporting checks saved telemetry consent first; otherwise it requires interactive mode and prompts “Send usage data?” before saving the choice.
- The report is sent to the configured Tsuga API at `/v1/cli-runs`; the source describes this as a run record sent only by opted-in CLIs.
- The detached sender posts the report payload and suppresses its output; the report includes CLI run metadata and spans.
Evidence against
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.149.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.149.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.