@socketsecurity/cli@1.4.0
CLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected behavior is consistent with the package's dependency-security CLI functionality. No concrete malicious chain was found; bundled command execution and generated functions have identifiable operational purposes.
Decision evidence
public snapshot- package.json defines CLI entrypoints without install lifecycle hooks or a runtime self-dependency.
- bin/cli.js forwards user arguments to the bundled CLI.
- The terminal library compiles formatting functions; bundled vendor code generates schema validators.
- The packing library runs directory packing hooks only when scripts are enabled.
- Maven analysis explicitly loads the bundled extension, whose archive contains dependency and workspace record engines.
- CLI telemetry sanitizes API token arguments before submission.
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.4.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.4.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.