registry / @tsuga/cli / 1.102.0
@tsuga/cli@1.102.0
Tsuga CLI - manage resources from the command line
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a CLI whose bundled entry point reports limited runtime usage metadata only after telemetry consent is present or explicitly enabled. The reviewed telemetry fields contain command metadata and runtime details, not captured command output or credentials.
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 follows a CLI run only when telemetry consent is enabled; otherwise it returns without sending.
Impact
No malicious impact was identified in the reviewed source.
Mechanism
The CLI submits usage metadata to the configured Tsuga API. The reviewed payload construction does not include command output.
AI rationale
The package is a CLI whose bundled entry point reports limited runtime usage metadata only after telemetry consent is present or explicitly enabled. The reviewed telemetry fields contain command metadata and runtime details, not captured command output or credentials.
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 CLI entry point.
- Runtime telemetry is reported only after the consent check allows it.
- The telemetry payload contains CLI command and flag metadata, runtime version, platform, and trace identifiers; it does not include captured command output.
- Agent session identifiers are accepted only in UUID form and hashed before inclusion.
- The CLI prompts interactively for telemetry consent and saves the choice; TSUGA_TELEMETRY can explicitly enable or disable it.
Evidence against
- The scanner flags command execution and network behavior in the bundled CLI, but the reviewed excerpts show these as CLI functionality and consent-gated usage reporting.
- The secret-pattern matches include credential-detection patterns and examples; the reviewed evidence does not show a hard-coded operational 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.102.0.
See all versions of @tsuga/cli for other recorded verdicts.
- Review the evidence and your use of @tsuga/cli@1.102.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.