registry / @tsuga/cli / 1.135.0
@tsuga/cli@1.135.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and the bundle’s command execution and outbound request are used for CLI operation and consent-gated usage telemetry. The reviewed flow does not show secret or unrelated file exfiltration.
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 reporting runs during CLI operation only when existing consent or the environment setting enables it, or after an interactive user accepts the prompt.
Impact
No unauthorized credential or file collection was found in the reviewed flow.
Mechanism
The CLI filters command arguments and sends a usage payload to its configured Tsuga API using a short-lived Node fetch process.
AI rationale
The manifest has no install hooks, and the bundle’s command execution and outbound request are used for CLI operation and consent-gated usage telemetry. The reviewed flow does not show secret or unrelated file exfiltration.
Evidence
dist/cli.js
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI and declares no install lifecycle scripts.
- Runtime usage reporting is gated by saved telemetry consent, an explicit TSUGA_TELEMETRY setting, or an interactive consent prompt; the prompt explains how to change the setting.
- The telemetry report includes filtered command names, duration, runtime and platform details, and session trace identifiers; it is sent only after the consent check.
- The child-process call launches a small Node fetch helper to submit the telemetry payload; the helper does not execute package-downloaded code.
Evidence against
- The bundle includes child-process and network APIs, but the reviewed use is CLI telemetry and normal command execution.
- The static scanner flagged a critical-looking secret pattern, but the searched match was ordinary credential-pattern documentation or example text, not evidence of a live secret.
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.135.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.135.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.