socket@1.10.1
CLI for Socket.dev
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has CLI entrypoints and no install lifecycle hook, while the credential flag resolves to conditional GitHub Actions OIDC support rather than a package-selected recipient. Other flagged items map to bundled terminal and registry tooling or an explicitly invoked Maven extension; the inspected evidence does not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes CLI commands and lists no install lifecycle hook; bin/cli.js launches the CLI with forwarded arguments.
- The flagged credential handling requires GitHub Actions OIDC environment values and requests a token from the URL supplied by that environment; it is vendored signing support, not evidence of export to a package-selected recipient.
- The flagged generated function is in Blessed terminal capability handling; inspected sources also identify bundled registry, terminal, and glob libraries.
- The Maven archive is a bundled extension invoked by the explicit Maven manifest command; the offline analysis ties it to the packaged archive but reports limits on some class context.
- Scanner flags include credential handling, dynamic evaluation, and a limited Maven archive analysis; these indicators warranted source review but did not establish a malicious transfer or action.
Source & flagged code
17 flaggedPackage source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152Findings
Affected versions and remediation
This report applies to socket@1.10.1.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.10.1 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.