@socketsecurity/cli-with-sentry@1.9.1
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected CLI and telemetry paths do not establish malicious behavior, and the credential-related match is consistent with runner-directed Sigstore token retrieval. The packaged Maven extension binary could not be resolved from source, so manual review is needed.
Decision evidence
public snapshot- The CLI wrapper starts the packaged CLI with the caller’s arguments.
- CLI telemetry is conditional on a configured default organization, and its context uses sanitized arguments.
- The flagged bundled helper obtains a GitHub Actions token only when runner-provided URL and token variables are present.
- The Maven extension artifact could not be inspected as source, leaving its behavior unresolved.
- The credential-related scanner match is consistent with a bundled Sigstore CI identity provider that uses GitHub Actions’ supplied token endpoint; it does not establish an unrelated recipient or credential theft.
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-with-sentry@1.9.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.9.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.