@socketsecurity/cli-with-sentry@1.12.2
CLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a Socket CLI with no declared install lifecycle scripts. The flagged credential flows support GitHub and npm operations, and shell alias changes are gated by confirmation; no unrelated exfiltration or automatic persistence was found.
Decision evidence
public snapshot- The package exposes CLI commands through bin entry points.
- The wrapper launches the package CLI and forwards its arguments and environment.
- The CLI uses a GitHub token for a GitHub API request to retrieve a repository file.
- The npm registry code sends credentials with registry requests and limits them when a tarball is hosted elsewhere.
- Shell profile changes are behind a confirmation prompt in an alias setup flow.
- No install lifecycle scripts are declared in the manifest.
- The reviewed credential flows serve GitHub and npm requests relevant to CLI and registry operations; no unrelated credential collector was identified.
- The shell profile modification is conditional on user confirmation.
Source & flagged code
18 flaggedFindings
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.12.2.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.12.2 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.