socket@1.8.2
CLI for Socket.dev
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe package manifest has no install lifecycle hook, and the flagged behaviors resolve to user-run CLI features or bundled tooling. The source review found no concrete attack chain.
Decision evidence
public snapshot- package.json exposes CLI binaries and lists development and build scripts; it defines no install lifecycle hook.
- bin/cli.js forwards supplied arguments to the local CLI; the Maven extension is attached by the Maven manifest path.
- The pnpm wrapper scans user-issued install, add, and dlx commands before launching pnpm.
- The registry bundle uses GitHub Actions-provided credentials to request an audience-scoped OIDC token.
- The flagged dynamic-code sites generate terminal capability functions and schema validators.
- Offline analysis identifies the flagged archive as a ZIP; the CLI loads it for Maven manifest processing.
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.8.2.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.8.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.