A release's finding groups without a current VEX statement, in triage order
const url = 'https://example.com/v1/orgs/example/graph/traversals/unassessed?release=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/unassessed?release=example' \ --header 'Authorization: Bearer <token>'One item per finding group: one CVE however many advisories report it, or one advisory without a CVE. Ranked in the fixed triage order (docs/ontology.md): known exploited first, then KEV due date, affected units, EPSS and CVSS, then the CVE (or advisory) ID. summary.ranking lists the groups with the inputs for the rank and their advisories; there is no score. The nodes hold each group and, through groups, the findings of its advisories. conflict=true keeps only the groups whose sources disagree. Up to 100 groups; truncated when there are more.
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”A release node ID (urn:affectra:release:…)
True: only the groups whose sources disagree about a component’s version (another advisory with the CVE excludes a component a member matched); false or absent: all
Responses
Section titled “Responses”The release, its unassessed finding groups, their findings and vulnerabilities, KEV entries and EPSS scores
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.
A release’s finding groups without a current VEX statement, in triage order. A group is one CVE however many advisories (NVD, OSV, a distro, CSAF) report it, or one advisory without a CVE; its advisories’ findings come with it (groups). conflict=true lists only groups whose sources disagree about a component’s version.
object
Unassessed finding groups in the release (with conflict=true, those that conflict); more than ranking lists when truncated.
How many of them are known exploited.
The listed finding groups in rank order, each with the inputs for its rank. No score.
object
The finding group node.
The group’s finding ref (Gateway/rev-b@1.4.0:CVE-2024-1234): cite it to people; explain_finding and similar_assessments take it as finding.
The Finding node of the group’s primary advisory.
Node ID.
The group’s CVE; the primary advisory’s ID for a group without one.
The IDs of the group’s advisories, the primary first.
The sources disagree about a component’s version: see excludedBy on the group’s components.
In CISA’s KEV catalog, or on ENISA’s EU KEV list from a source other than CISA.
The earliest KEV due date of its CVEs.
The organization’s units whose current collector SBOM matches the vulnerability, less units linked to a release assessed not_affected or fixed for it: blast_radius’s units_affected.
Example
{ "nodes": [ { "class": "Artifact" } ], "edges": [ { "relation": "about" } ], "feed_status": { "additionalProperty": { "state": "ok" } }, "summary": { "ranking": [ { "vex_status": "not_affected" } ] }}Missing release
No such object in this organization, no such organization, or the caller does not belong to it
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