@socketsecurity/cli@1.1.178
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source shows a user-invoked CLI and ordinary bundled support libraries, not an install hook, credential theft path, or payload execution chain. No concrete malicious behavior was established.
Decision evidence
public snapshot- The manifest exposes a CLI and its listed scripts are development build and test tasks, with no install lifecycle hook shown.
- The launcher starts the packaged CLI with the user-supplied arguments and inherited standard streams.
- The terminal helper generates functions only for terminal capability formatting.
- The bundled process helper invokes an explicit command, argument array, and options object.
- The vendor HTTP wrapper sends only its supplied request options.
- The packaged Maven archive contains a standard manifest entry.
- The CLI includes normal telemetry and update-check calls during an explicit CLI invocation.
- Bundled dependencies contain child-process, dynamic-function, and HTTP primitives.
Source & flagged code
17 flaggedPackage source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152Findings
Affected versions and remediation
This report applies to @socketsecurity/cli@1.1.178.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.178 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.