Which releases and units a vulnerability reaches
const url = 'https://example.com/v1/orgs/example/graph/traversals/blast-radius?vulnerability=example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://example.com/v1/orgs/example/graph/traversals/blast-radius?vulnerability=example' \ --header 'Authorization: Bearer <token>'The vulnerability resolves to every advisory whose ID it is or whose CVEs contain it (summary.resolved). Releases come from their uploaded SBOMs’ findings, with the matching components and the current VEX status; assessed releases stay listed (Finding.vex_status). Units come from their collector SBOMs, grouped by the release they are linked to, whose VEX status they inherit, or, unlinked, by the texts they reported (summary.unit_groups). Up to 500 releases and 200 units per group are listed, then truncated; the counts cover all of them.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Query Parameters
Section titled “Query Parameters”Any vulnerability ID we store, e.g. CVE-2024-3094 or a GHSA ID
Responses
Section titled “Responses”The releases, units, components and findings the vulnerability reaches
object
Traversal-specific (
object
object
Urn:affectra:… for tenant and shared nodes; public nodes keep their own IDs (CVE-…, CWE-79).
Composed from first-party data only; empty when the ID is the label.
Only the properties the ontology lists for the class (
object
A relation between two nodes. Agents cite edges as evidence.
object
Node ID.
Node ID.
The relation’s properties, e.g. MatchesEdgeProperties.
object
A limit cut the result.
Opaque cursor for the next page.
When the data was read.
The version of each feed the answer used (feed_state), e.g. osv, nvd, kev, epss.
object
How current each feed is, by feed_state key (osv:Debian, kev, epss, nvd), including feeds with no version yet. Say how old the data is from checked_at; state says whether that is old enough to matter. Times and states only.
object
object
The last attempt that succeeded, changed or not; null if the feed has never been checked.
False when the organization turned this feed off: findings that only it reports are hidden, not deleted (list_feeds names the feeds and who changed them). True for every other feed.
From the age of checked_at against the feed’s thresholds (libs/go/feedhealth); never checked is very_stale.
Which releases and units a vulnerability reaches, through which component, with the current VEX status, KEV and EPSS. Assessed releases are listed with their status, not dropped. Only releases with a finding are listed: one not listed has no affected component in its SBOMs, or no SBOM yet (neighbours with describedBy lists a release’s SBOMs). Units are found through their collector SBOM; a unit whose collector doesn’t report package URLs is never matched, so it isn’t counted. A unit linked to a release (runs) inherits that release’s VEX status; an unlinked one is judged on its own SBOM matches only.
object
The vulnerability IDs the parameter resolved to.
A CVE of the resolved IDs is in CISA’s KEV catalog, or on ENISA’s EU KEV list from a source other than CISA.
The earliest CISA KEV due date of those CVEs; ENISA’s list has none.
object
Releases with a finding not assessed not_affected or fixed.
Releases assessed not_affected or fixed.
Units whose collector SBOM matches, linked or not, less units_not_affected.
Linked units whose release is assessed not_affected or fixed for the vulnerability; they inherit it, whatever their own SBOM matches.
Matching units not linked to a release, judged on their own SBOM; they count in units_affected.
Matching units by the release they run (runs), linked first; units without a link by the product, variant and release texts they reported, with linked false. Up to 200 units of each group are in nodes.
object
The release node ID when linked; else the reported release text.
Linked, and the release is assessed not_affected or fixed: the group’s units count in units_not_affected.
Unlinked: the product key the units reported, or null. Linked: null.
Unlinked: the variant the units reported, or null. Linked: null.
All units of the group.
Units of the group in nodes.
Example
{ "nodes": [ { "class": "Artifact" } ], "edges": [ { "relation": "about" } ], "feed_status": { "additionalProperty": { "state": "ok" } }}Vulnerability is missing (request.fieldRequired)
No advisory we store has this ID (graph.vulnerabilityUnknown)
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1
The server runs without a database (catalog.unavailable), or the query ran past its statement timeout (graph.timeout); try again