socket@1.6.2
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 24d ago · by lpm-firewall-aiInspected source does not establish the scanner’s alleged credential exfiltration or dynamic evaluation as malicious behavior. The bundled Maven extension archive remains unresolved, so the package cannot be cleared from source inspection alone.
Decision evidence
public snapshot- The manifest maps the package’s commands to its own CLI entrypoints.
- The main launcher starts the bundled CLI and forwards the caller’s arguments.
- The flagged token request requires Actions-provided environment values and uses the supplied request URL.
- The terminal capability code handles terminfo formatting directives.
- The CLI references a bundled Maven extension archive, whose contents could not be assessed as UTF-8 source.
- The inspected token helper does not show a fixed external recipient; it requests a token from the URL supplied by the Actions environment.
- The inspected terminal code is a terminfo formatter, not evidence of malicious evaluation.
Source & flagged code
17 flaggedPackage source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152Findings
Affected versions and remediation
This report applies to socket@1.6.2.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.6.2 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.