@socketsecurity/cli-with-sentry@1.1.154
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection shows an explicitly user-invoked Socket CLI with its declared Sentry integration, not an install-time or covert malicious chain. Scanner findings map to bundled dependency functionality and expected CLI behavior.
Decision evidence
public snapshot- Runtime Sentry telemetry is enabled in dist/instrument-with-sentry.js.
- package.json has no preinstall, install, postinstall, or prepare hook.
- bin/cli.js only launches the packaged CLI after explicit bin invocation.
- Sentry setup is explicitly the package's stated with-sentry variant and sets only environment/version tags.
- The reported libnpmpack network code is bundled npm/pacote packaging logic, not credential harvesting.
- external/blessed/lib/tput.js uses Function only to compile terminal capability formatting strings.
Source & flagged code
14 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.1.154.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.1.154 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.