socket@1.1.170
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malware, exfiltration, persistence, or install-hook abuse was established. The opaque Maven extension and broad executable capability prevent a clean decision.
Decision evidence
public snapshot- The manifest exposes a command-line entrypoint.
- The launcher forwards caller arguments and environment to a child Node process.
- A Maven command loads the bundled JAR as a Maven extension.
- The package includes dynamic code generation in a bundled terminal library.
- The bundled registry component imports process, network, filesystem, and child-process modules.
- No npm preinstall, install, or postinstall hook is declared.
- The observed execution paths are activated by explicit CLI commands, not package installation.
- Inspection found no confirmed credential collection, exfiltration endpoint, or destructive action.
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.170.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.170 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.