socket@1.1.168
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install, persistence, credential theft, or unconsented control-surface mutation was established. The executable opaque Maven extension remains a real unresolved runtime risk.
Decision evidence
public snapshot- The CLI loads a bundled Maven extension JAR into Maven during a user-invoked manifest operation; the JAR cannot be source-reviewed here.
- The CLI uploads selected manifest paths to Socket's API for reachability analysis.
- package.json defines command-line entrypoints but no preinstall, install, postinstall, or prepare hook.
- The launcher only starts the package's compiled CLI with user arguments.
- The flagged terminal-library dynamic Function use is for compiling terminfo formatting code, not an observed payload loader.
- The registry vendored file is a large bundled package-management implementation; inspection did not establish credential exfiltration.
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 socket@1.1.168.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.168 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.