socket@1.9.0
CLI for Socket.dev
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe scanner's credential finding maps to a bundled npm/Sigstore helper, and the inspected code uses credentials with their provided Actions endpoint. The manifest and CLI entrypoint inspection showed no install-time trigger or separate package-directed credential transfer.
Decision evidence
public snapshot- package.json declares CLI entrypoints and build scripts; no install lifecycle hook is present.
- bin/cli.js forwards the user's arguments to the CLI process.
- The flagged npm helper is loaded by the package-packing function; its GitHub token flow uses the Actions-provided URL and token to request an OIDC token.
- The inspected dependency manifests contain no install lifecycle hooks.
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 socket@1.9.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.9.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.