Detail
Path Parameters
Canonical advisory id, source advisory id, or alias
Response Body
application/json
curl -X GET "https://example.com/v1/advisories/CVE-2023-38545"{ "advisory_kind": "string", "aliases": [ "string" ], "canonical_id": "string", "how_it_attacks": [ "string" ], "package_totals": { "affected": 0, "not_affected": 0, "total": 0, "unknown": 0 }, "reference_groups": [ { "items": [ { "reference_type": "string", "url": "string" } ], "kind": "string", "total": 0 } ], "reference_total": 0, "severities": [ { "band": "string", "score": 0, "score_type": "string", "vector": "string" } ], "source_advisory_id": "string", "source_advisory_ids": [ "string" ], "source_kind": "string", "source_kinds": [ "string" ], "source_url": "string", "summary": "string"}`/v1/advisories/summary` — canonical advisory counts by headline severity band. This is the purpose-built aggregate behind browse summary tiles: it reuses the browse list's canonical universe (rollups joined back to their source records) and its headline-score bounds, but skips the per-group display metadata, search, sorting, and windowing that make the full browse query expensive, so callers no longer issue several `limit=1` browse requests just to read totals. GET
Previous Page
`/v1/advisories/{id}/packages` — one row per matched package. Match rows are grouped by package across all source records and identities before the name filter, the latest-version totals, sorting, and windowing. Ordering is deterministic: latest-affected groups first, then package name. GET
Next Page