socket@1.1.175
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes an opaque, executable Maven extension but not a concrete attack. A warning is appropriate because the archive is actively loaded and cannot be cleared by source inspection alone.
Decision evidence
public snapshot- The CLI loads a bundled Maven extension archive and passes it to Maven as an extension class path.
- The archive contains Maven-extension metadata but its executable bytecode is not source-inspectable in this review.
- The flagged registry authentication code only reuses registry credentials for a same-host URI.
- The flagged dynamic Function calls are in terminal capability formatting code.
- The package exposes CLI binaries rather than an automatic install lifecycle hook.
- No npm preinstall, install, or postinstall hook was found in the manifest.
- The opaque archive is activated only when the user invokes the Maven manifest workflow; no malicious behavior was established from inspectable source.
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.175.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.175 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.