@socketsecurity/cli@1.1.162
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk findings are vendored dependency behavior or explicit CLI functionality, not an automatic attack chain. The package has no lifecycle script and source inspection found credential redirect protection rather than unrestricted forwarding.
Decision evidence
public snapshot- The manifest exposes command-line entrypoints and contains no install lifecycle hook.
- The launcher only starts the packaged CLI with the caller's arguments and inherited standard I/O.
- The reported dynamic evaluation is terminal capability formatting code in vendored blessed.
- Registry authentication is selected from the destination URI and credentials are removed when redirects change hostname.
- The large vendor bundle's fetch helper uses caller-supplied request options.
- The Maven archive is loaded only by the CLI's Maven-analysis path, which creates a temporary records file.
Source & flagged code
18 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.162.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.162 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.