registry / @tsuga/cli / 1.104.0
@tsuga/cli@1.104.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a CLI with no install lifecycle hook. Its usage telemetry is sent only after consent, and API URL validation restricts the destination to Tsuga's official hosts or localhost.
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 can be sent after a CLI run only when consent is already stored, TSUGA_TELEMETRY enables it, or the user accepts an interactive prompt.
Impact
Usage data may include command-line arguments and spans, but the source gates transmission on consent.
Mechanism
The CLI posts usage data to the configured Tsuga API endpoint; the API URL validation limits hosts to Tsuga's official API hosts or localhost.
AI rationale
The package is a CLI with no install lifecycle hook. Its usage telemetry is sent only after consent, and API URL validation restricts the destination to Tsuga's official hosts or localhost.
Evidence
~/.config/tsuga/config.json
Network endpoints2
api.tsuga.comapi.tsuga-staging.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/cli.js as the CLI and declares no install lifecycle hook.
- Telemetry requires saved consent or an interactive prompt; noninteractive runs without consent return false.
- The telemetry report is sent after the CLI command runs and includes runtime and command metadata.
- The configured API host is restricted to Tsuga's official API hosts or localhost.
Evidence against
- The telemetry record includes command-line arguments and spans, which can contain user-provided values; transmission is gated by consent.
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.104.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.104.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.