@socketsecurity/cli-with-sentry@1.10.0
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and inspected CLI telemetry is disabled by default and gated on organization configuration. I cannot mark it clean because the Maven command loads an opaque bundled JAR whose behavior is unresolved.
Decision evidence
public snapshot- package.json exposes command-line entrypoints; its scripts are build and development tasks, with no install lifecycle hook.
- The CLI entrypoint launches the bundled CLI when a user runs a command.
- CLI telemetry defaults to disabled; event tracking also requires a configured organization, and arguments are sanitized before inclusion.
- The credential-related match is a vendored Sigstore provider that uses GitHub Actions OIDC environment values to request a token.
- The Maven analysis path loads a bundled Java extension, whose behavior could not be resolved from source inspection.
- No concrete attack was established in the inspected executable source.
- The bundled Maven extension is opaque binary content, so its behavior remains unresolved.
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.10.0.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.10.0 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.