Socket
Socket is a developer-first software supply chain security platform that protects applications from supply chain attacks by deeply inspecting open source dependencies across npm, PyPI, Maven, Go, NuGet, RubyGems, Cargo and more. Socket detects malware, hidden code, typosquats, install scripts, protestware, and risky capabilities in packages, scores their quality and risk, and enforces security and license policies across repositories through a REST API, CLI, GitHub App, MCP server, and static reachability analysis. Founded by Feross Aboukhadijeh and backed by a16z, Socket is used by engineering teams at organizations including Vercel, Replit, and Brave.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Socket the way a machine reads it — 28 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Socket scores 55.0/100 (developing), with a separate agent-readiness read of 85/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Socket
Each block below is one kind of artifact we hold for Socket. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Socket alerts API
The alerts API from Socket — 6 operation(s) for alerts.
Socket api-tokens API
The api-tokens API from Socket — 6 operation(s) for api-tokens.
Socket audit-log API
The audit-log API from Socket — 1 operation(s) for audit-log.
Socket dependencies API
The dependencies API from Socket — 2 operation(s) for dependencies.
Socket deprecated API
The deprecated API from Socket — 17 operation(s) for deprecated.
Socket diff-scans API
The diff-scans API from Socket — 7 operation(s) for diff-scans.
Socket fixes API
The fixes API from Socket — 1 operation(s) for fixes.
Socket full-scans API
The full-scans API from Socket — 13 operation(s) for full-scans.
Socket license-policy API
The license-policy API from Socket — 4 operation(s) for license-policy.
Socket metadata API
The metadata API from Socket — 5 operation(s) for metadata.
Socket org-settings API
The org-settings API from Socket — 2 operation(s) for org-settings.
Socket org-snapshots API
The org-snapshots API from Socket — 1 operation(s) for org-snapshots.
Socket packages API
The packages API from Socket — 2 operation(s) for packages.
Socket repo-labels API
The repo-labels API from Socket — 5 operation(s) for repo-labels.
Socket repos API
The repos API from Socket — 2 operation(s) for repos.
Socket security-policy API
The security-policy API from Socket — 1 operation(s) for security-policy.
Socket telemetry API
The telemetry API from Socket — 1 operation(s) for telemetry.
Socket threat-feed API
The threat-feed API from Socket — 1 operation(s) for threat-feed.
Socket triage API
The triage API from Socket — 2 operation(s) for triage.
Socket webhooks API
The webhooks API from Socket — 2 operation(s) for webhooks.
Scroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Socket MCP Server
Socket's official MCP server exposes the depscore tool so AI assistants can query dependency scores from the Socket API; hosted at https://mcp.socket.dev/ or run locally.
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Socket Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Socket Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Socket — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/socket · machine-readable index on apis.io