socket@1.1.158
CLI for Socket.dev
AI Security Review
scanned 3mo ago · by lpm-firewall-aiStatic hints reflect normal CLI networking, credential use, vendored npm code, and terminal parsing. Source inspection found no malicious chain or lifecycle-triggered behavior.
Decision evidence
public snapshot- CLI bins are explicit user-invoked entrypoints.
- Main launcher forwards user arguments to the local CLI process.
- Socket API endpoint and token handling are product-aligned.
- The eval hint is in vendored terminal capability parsing.
- No preinstall, install, postinstall, or prepare lifecycle hook found.
- No unconsented AI-agent configuration mutation found.
- No credential exfiltration or foreign endpoint was confirmed.
Source & flagged code
19 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.158.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.158 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.