Semgrep
Semgrep is a fast, open-source static analysis engine and an associated AppSec Platform (Semgrep Code, Semgrep Supply Chain, and Semgrep Secrets) that finds bugs, security issues, and policy violations across source code, dependencies, and credentials. The open-source CLI runs pattern-based rules locally or in CI; the AppSec Platform layers a managed control plane on top with organization-wide policy, triage workflows, findings management, and an OpenAPI-described REST API for deployments, projects, findings, scans, secrets, and supply chain data. Editor, CI, and SCM integrations (VS Code, JetBrains, GitHub, GitLab, Bitbucket, Azure DevOps) round out the developer surface.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Semgrep the way a machine reads it — 12 machine-readable artifacts across 6 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 — Semgrep scores 22.5/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 Semgrep
Each block below is one kind of artifact we hold for Semgrep. 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 6
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.
Semgrep AppSec Platform REST API
OpenAPI-described REST API for the Semgrep AppSec Platform. Lists deployments, projects, findings, scans, secrets, and supply chain data, and supports CI/CD and triage automatio...
Semgrep CLI
Open-source command-line static analysis engine. Runs locally and in CI to scan code with community and custom rules, emit SARIF/JSON output, and enforce policies. Authored prim...
Semgrep Community Rules
Community and Semgrep-maintained rule packs covering security, correctness, best-practice, and supply chain findings across many languages and frameworks. Consumed by the CLI an...
Semgrep VS Code Extension
Visual Studio Code extension that surfaces Semgrep findings inline while developers edit code, with quick-fix and triage actions tied to the AppSec Platform.
Semgrep Interfaces
Shared interface definitions (ATD-generated types) used between the Semgrep CLI, AppSec Platform, and language-specific clients to keep output schemas in sync.
Semgrep Documentation
Source for the Semgrep product documentation site, including CLI reference, rule-writing guides, AppSec Platform docs, and API reference.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate 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.
Semgrep Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semgrep Finops
FINOPSSecurity 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.
Resources
Every other property we hold for Semgrep — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/semgrep · machine-readable index on apis.io