Skip to main content

Tools

Socket

Dependency supply-chain scanner that inspects packages before install.

Detection Pre-generation Fully autonomous Hybrid Stable Activity band E Environment
Activity band details

Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.

Computed band: E (raw score 3.5). Shown band: E .

Facets: documented_in=0evaluated_on=0integration_surfaces=1.5paper_citations=0recent_push=2stars=0

Source of truth: pipeline/maturity/score.py

Description

Commercial dependency-security platform that analyzes packages in real time for supply-chain risks (typosquats, install-time scripts, network/file/shell capability changes, obfuscation, sudden maintainer churn, known malware). Integrates as a GitHub App, CLI, and package-manager wrapper (socket-npm/pip) that evaluates dependencies before install lands. Supervision locus is the manifest (package.json, requirements.txt, go.mod): risks are flagged pre-install rather than relying on known-CVE databases alone.

Why it's included

Occupies detection × pre_generation × fully_autonomous for the supply-chain-attack failure mode. Scanning manifests before install is the specific supervision primitive that separates Socket from post-install vulnerability scanners — it catches slopsquatted and typosquatted packages at the moment of adoption, which is when coding agents are most likely to introduce them.

Security notes

Proprietary hosted platform. Dependency metadata — and, for some analyses, source — is sent to Socket's backend for scanning; review data-handling terms before enabling on private code. The GitHub App requires repo read permissions. CLI and wrappers are distributed via npm/pip; pin versions to audited releases.

Addresses failure modes

These tags are the catalog's claim about what Socket is built to catch or prevent. A tag is not a test result. SAICA-Bench has not measured Socket, so none of these tags is tested here.

  • Supply-chain attack — Slopsquatting, typosquatting, compromised MCP servers.
  • Obsolescence — Using deprecated APIs, retired packages, or outdated library versions — often because the model's training data pre-dates current releases.

Techniques

dependency-manifest-scancapability-difftyposquat-detectioninstall-script-analysispull-request-gating

View raw YAML on GitHub →