Vulnerability Management
Providers using this tag (121)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 36 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 30 Early or largely undocumented
Minimal 17 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (24)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 1 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 5 Early or largely undocumented
Companies reaching this through an API (3)
These companies publish an API, specification or operation carrying “Vulnerability Management” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Where this tag sits
121 providers carry this tag directly, and 148 counting the 4 narrower tags below — 27 more to reach.
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Software Supply Chain (SBOM, Signing, Open Source Security) | 30% |
| Security (EDR, SIEM, SOAR) | 24% |
Cohort brief
Auto-generatedThe 118 providers in the APIs.io catalog tagged Vulnerability Management, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 36.5 | 23.2 | +13.3 | 118 |
| Operational Transparency | 24.9 | 13 | +11.9 | 118 |
| Access Clarity | 34.2 | 23.9 | +10.3 | 118 |
| Contract Quality | 26.1 | 17.2 | +8.9 | 118 |
| Discoverability | 65.3 | 57.9 | +7.4 | 118 |
| Contract Governance | 10 | 6.5 | +3.5 | 118 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 27% | 13% | +14 |
| MCP server (first-party) | 24% | 12% | +12 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 18% | 16% | +2 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Snyk 79.1
- 2 ControlUp 75.6
- 3 Malwarebytes 69.1
- 4 Tenable 67.6
- 5 CrowdStrike 65.6
- 6 Sonatype 63.3
- 7 OpenText Cybersecurity 60.4
- 8 Feedly 59.6
- 9 Iru 59.6
- 10 Amazon IoT Device Defender 58.5
- 1 Feedly 65.3
- 2 Armis 49.3
- 3 Horizon3.ai 48.4
- 4 Snyk 45.7
- 5 Dependency-Track 45.7
- 6 CYRISMA 41.5
- 7 Upwind 40.3
- 8 OpenText Cybersecurity 38.5
- 9 Tenable 38.1
- 10 watchTowr 37.9
Coverage caveat. 101 of 118 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.