@socketsecurity/cli@1.8.2
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected credential-transfer finding is consistent with vendored npm registry tooling, and no concrete attack was established. The CLI can invoke a bundled executable Maven extension whose class behavior remains unresolved, so manual review is warranted.
Decision evidence
public snapshot- The CLI invokes a bundled Maven extension during a Maven manifest scan, adding the JAR to Maven’s classpath and running validate.
- The archive contains executable Java class files whose behavior the offline analysis could not resolve.
- No concrete attack was established in the inspected credential-handling code; its auth headers are part of the vendored npm registry client.
- The package maps its executable aliases to CLI entrypoints, and the launcher starts the bundled CLI.
- The flagged libnpmpack module is lazily loaded by package tooling, and its inspected code builds npm authorization headers.
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 @socketsecurity/cli@1.8.2.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.8.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.