socket@1.1.155
CLI for Socket.dev
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe flagged primitives are consistent with an authenticated security-scanning CLI and are user-invoked. No lifecycle script, covert credential collection, or unconsented persistence was found.
Decision evidence
public snapshot- dist/cli.js can modify shell aliases, but only through explicit wrapper commands or a prompted --postinstall argument.
- package.json has no lifecycle hooks.
- bin/cli.js only launches the packaged CLI after user invocation.
- dist/cli.js gates shell-profile changes behind confirmation or `socket wrapper on/off`.
- external/@socketsecurity/registry/external/libnpmpack.js is an npm pack implementation, not credential exfiltration.
- dist/utils.js telemetry is organization-scoped, disabled by default, and redacts token-like argv values.
Source & flagged code
15 flaggedPackage source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152Findings
Affected versions and remediation
This report applies to socket@1.1.155.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.155 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.