@socketsecurity/cli-with-sentry@1.8.1
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 23d ago · by lpm-firewall-aiSource inspection did not establish malicious behavior, but the Maven extension is executable and its lifecycle participant bytecode could not be inspected. Manual review is needed to resolve that material gap.
Decision evidence
public snapshot- The CLI invokes the bundled Maven extension through Maven's extension class path during the manifest workflow.
- The extension includes binary lifecycle participants whose behavior the offline analysis could not inspect.
- The CLI runs Maven's validate phase to trigger the extension and collect manifest records.
- The flagged npm client performs ordinary requests using the URI and request options supplied by its caller.
- The inspected extension caller runs as part of a specific CLI workflow; the source review did not confirm a credential transfer or other attack.
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 @socketsecurity/cli-with-sentry@1.8.1.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.8.1 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.