socket@1.1.171
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time attack, credential theft, or unconsented persistence was established. The user-triggered opaque Maven extension warrants a warning because its compiled behavior could not be fully inspected.
Decision evidence
public snapshot- The CLI loads a bundled Maven extension JAR into Maven when the manifest command is run.
- The bundled Maven extension is opaque compiled bytecode, so its behavior cannot be fully verified from source.
- A vendored terminal library dynamically compiles generated terminal-formatting code.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The package is a user-invoked CLI; its launcher forwards explicit command-line arguments to dist/cli.js.
- The flagged registry code contains npm registry handling, and no source evidence showed secret harvesting or exfiltration by this package.
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.171.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.171 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.