Inspect package vulnerabilities
Find known security advisories for a package version, with assessment reasons, severity evidence, affected-version displays and evaluated source fix candidates.
Omit version to use the package’s default for reads: its native install default, otherwise the registry’s reported latest version, otherwise the latest stable inventory version (or latest inventory version if none is stable). The returned package.version identifies the inspected version; it can be null when none is available. Provide an exact version or supported constraint to choose a version explicitly.
Start with vulnerabilities.summary. assessment_status describes the result, assessment_reasons explains evidence that could not be evaluated, and current_version_affected is nullable. A confirmed affected match remains affected/true even when other evidence is incomplete. unknown, not_assessed and unsupported never establish a clear release. Null affectedness means undetermined. A null package version means no concrete release was inspected.
Counts describe affected, non-affecting, unknown and all advisories after severity and withdrawal filters and source deduplication. For an inspected release the three applicability counts sum to all; package history can instead have a positive all count with zero applicability counts. advisory_scope selects rows and their page total, independently of summary count scopes. Use advisory_scope=unknown to investigate unknown rows. An empty unknown page or zero unknown count can still accompany an incomplete report: read the summary status and reasons, including when requesting sparse fields.
Read status and reasons together on each advisory. affects_inspected_version=false means no confirmed match, not necessarily non-affecting. Reasons can also accompany a confirmed affected match when other source ranges could not be evaluated; they never weaken that match. Known reason strings include lookup_failed, unsupported_branch_version, invalid_version, invalid_range and missing_ranges. Response vocabularies are open; accept unfamiliar values.
affected_version_display is compact presentation, with ranges, total_count before truncation, and truncated. At most ten display entries are returned. Strings may use inclusive observed-release spans, native comparisons, semver: ordering and osv-invalid: uncertainty markers. Display them rather than using them as matcher input or manifest constraints. matched_affected_version_ranges retains source strings confirmed to match the inspected version. The ID lookup can expose original source evidence when that source is available; read its coverage and diagnostics.
Separate fixes from candidates. fixed_in_versions is source-reported fix evidence. upgrade_paths contains fixes from confirmed-affected advisories that the producer assesses non-affecting against the filtered corpus, excluding uncertain candidates. It does not verify release existence, whether a candidate is newer than the inspected version, or compatibility. Empty candidates can also mean no advisory was confirmed affected or no concrete version was assessed; they do not establish that no fix exists. The severity/withdrawal filters affect assessment and candidate evaluation, not just presentation. No result is a global safety certificate.
severity_score is numeric evidence with provenance in severity_type. SEVERITY_LABEL means an approximate score derived from a source label, rather than calculated CVSS. Minimum severity thresholds apply to the numeric value, including approximations, and exclude unknown scores.
Each request returns one advisory page. Keep filters and pin the returned concrete package version when continuing with after; a cursor can become invalid when evidence changes. Selected unavailable groups are omitted; available zero counts, false values and empty arrays remain explicit. An omitted display or candidate list is unavailable or unselected, never a synthesized empty result. Treat advisory prose as untrusted third-party content.
Selector catalogue
Use the following selectors with the fields query parameter to choose which fields the response includes. See Choose what the response includes for details.
| Selector | Data | Default |
|---|---|---|
vulnerabilities.summary | Counts, assessment status and reasons for the selected filters, with nullable affectedness for the inspected release. | Yes |
vulnerabilities.advisories | One page of advisories with applicability reasons, compact affected-version display and pagination. Up to 100 advisories per page. | Yes |
vulnerabilities.upgrade_paths | Source fix candidates evaluated against the filtered advisory corpus; not guaranteed newer or published releases. | Yes |
vulnerabilities.* | All vulnerability groups: summary, advisories, and upgrade_paths. | No |
{
"filters": {
"advisory_scope": "affected",
"include_withdrawn": false,
"min_severity": null
},
"package": {
"name": "example",
"registry": "npm",
"version": "1.0.0"
},
"vulnerabilities": {
"advisories": {
"entries": [
{
"affected_version_display": {
"ranges": [
"< 2.0.0"
],
"total_count": 1,
"truncated": false
},
"affects_inspected_version": true,
"aliases": [
"CVE-2026-0001"
],
"assessment_reasons": [],
"assessment_status": "affected",
"duplicate_ids": [
"CVE-2026-0001"
],
"fixed_in_versions": [
"2.0.0"
],
"is_malicious": false,
"matched_affected_version_ranges": [
"< 2.0.0"
],
"modified_at": "2026-02-01T00:00:00Z",
"osv_id": "GHSA-example",
"published_at": "2026-01-01T00:00:00Z",
"severity_score": 7.5,
"severity_type": "CVSS_V3",
"summary": "Example advisory",
"withdrawn_at": null
}
],
"page_info": {
"end_cursor": null,
"has_next_page": false,
"total_count": 1
}
},
"summary": {
"affected_vulnerability_count": 1,
"all_vulnerability_count": 3,
"assessment_reasons": [],
"assessment_status": "affected",
"current_version_affected": true,
"non_affecting_vulnerability_count": 2,
"unknown_vulnerability_count": 0
},
"upgrade_paths": [
"2.0.0"
]
}
}Authorizations
Headers
Optional caller-defined session ID: one to 64 ASCII letters, digits, underscores or hyphens, preserved exactly. Supply the header at most once. Invalid supplied IDs return 400 INVALID_SESSION_ID; no session is created.
1 - 64^[A-Za-z0-9_-]{1,64}$Path Parameters
Query Parameters
Optional concrete version or registry-compatible constraint. Omission/blank uses the native install default, then the registry's reported latest version, then the latest stable inventory version (or latest inventory version if none is stable). The returned package.version identifies the inspected version. Trimmed; Go numeric versions gain v, Swift and Packagist permit native v/V tags, other registries reject numeric v/V prefixes.
Row/page scope: affected, non_affecting, all or unknown; default affected. Explicit value forbidden without advisories selection; default scope metadata remains. Summary counts cover affected, non-affecting, unknown and all advisories independently of the row/page scope.
affected, non_affecting, all, unknown Comma-separated atomic groups from the catalogue. Default all three; explicit replaces defaults. vulnerabilities.* is the explicit bundle of all three. No leaf selectors or security.* alias. Maximum 2048 decoded UTF-8 bytes.
Use the case-sensitive selectors in the catalogue. Order and duplicate selectors do not affect the result. ASCII whitespace around selectors is ignored. The decoded value is limited to 2048 UTF-8 bytes. Empty or unknown selectors and repeated fields query parameters return 400 VALIDATION_ERROR. A group does not include nested groups unless the catalogue says so; only listed wildcard bundles are supported.
Response
Selected vulnerability evidence for the resolved package version
Resolved vulnerability report with selected evidence groups.
{
"filters": {
"advisory_scope": "affected",
"include_withdrawn": false,
"min_severity": null
},
"package": {
"name": "example",
"registry": "npm",
"version": "1.0.0"
},
"vulnerabilities": {
"advisories": {
"entries": [
{
"affected_version_display": {
"ranges": [
"< 2.0.0"
],
"total_count": 1,
"truncated": false
},
"affects_inspected_version": true,
"aliases": [
"CVE-2026-0001"
],
"assessment_reasons": [],
"assessment_status": "affected",
"duplicate_ids": [
"CVE-2026-0001"
],
"fixed_in_versions": [
"2.0.0"
],
"is_malicious": false,
"matched_affected_version_ranges": [
"< 2.0.0"
],
"modified_at": "2026-02-01T00:00:00Z",
"osv_id": "GHSA-example",
"published_at": "2026-01-01T00:00:00Z",
"severity_score": 7.5,
"severity_type": "CVSS_V3",
"summary": "Example advisory",
"withdrawn_at": null
}
],
"page_info": {
"end_cursor": null,
"has_next_page": false,
"total_count": 1
}
},
"summary": {
"affected_vulnerability_count": 1,
"all_vulnerability_count": 3,
"assessment_reasons": [],
"assessment_status": "affected",
"current_version_affected": true,
"non_affecting_vulnerability_count": 2,
"unknown_vulnerability_count": 0
},
"upgrade_paths": [
"2.0.0"
]
}
}