registry / @socketsecurity/cli-with-sentry / 1.1.144
@socketsecurity/cli-with-sentry@1.1.144
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection shows a Socket CLI with opt-in operational network calls, sanitized telemetry, and a Sentry-specific error-reporting build. No concrete malicious chain or prohibited install-time behavior was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
User invokes a CLI command, login, or explicitly accepts tab-completion setup.
Impact
No confirmed credential harvesting, remote payload execution, persistence, or destructive behavior.
Mechanism
User-invoked API, telemetry, and optional error-reporting client.
AI rationale
Source inspection shows a Socket CLI with opt-in operational network calls, sanitized telemetry, and a Sentry-specific error-reporting build. No concrete malicious chain or prohibited install-time behavior was found.
Evidence
package.jsonbin/cli.jsdist/instrument-with-sentry.jsdist/utils.jsdist/cli.jsexternal/@socketsecurity/registry/lib/spawn.js
Network endpoints2
api.socket.dev/v0/66736701db8e4ffac046bd09fa6aaced@o555220.ingest.us.sentry.io/4508846967619585
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- Runtime Sentry instrumentation is enabled only for this Sentry build.
- CLI telemetry sends invocation metadata for configured organizations.
- Explicit login can persist a Socket API token after user prompt.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- prepare only invokes Husky, not package runtime code.
- bin/cli.js runs the packaged CLI only when the user invokes its bin.
- Telemetry sanitizes token-like argv values and home-directory paths.
- API authorization is sent to configured Socket/GitHub endpoints for requested CLI operations.
- Completion and config writes occur only through explicit interactive commands.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStrings
Source & flagged code
14 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
external/blessed/lib/tput.jsView file
1152if (this.options.stringify && code.indexOf('return ') === 0) {
L1153: return new Function('', code)();
L1154: }
High
Eval
Package source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152bin/npm-cli.jsView file
4void (async () => {
L5: const Module = require('node:module')
L6: const path = require('node:path')
Findings
3 Critical5 High8 Medium8 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilityexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processbin/cli.js
HighShell
HighEvalexternal/blessed/lib/tput.js
HighCross File Remote Execution Contextdist/cli.js
HighShips High Entropy Blobdist/manifest-scripts/maven-extension/coana-maven-extension.jar
MediumDynamic Requirebin/npm-cli.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/cli.js
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.1.144.
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.144 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.