Current VEX statements on the organization's other releases for the same vulnerability
const url = 'https://example.com/v1/orgs/example/graph/traversals/similar-assessments';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/similar-assessments \ --header 'Authorization: Bearer <token>'Each statement has a match class from the path signature: exact (same component version and path), same_component_other_path, or other_version. Only exact may back a carry-over; without dependency data on either side the best class is same_component_other_path. At most 100 statements, newest first. Another organization’s release answers 404, and its statements never appear.
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 ID (urn:affectra:release:…); required unless finding is given
Any ID we store: a CVE, a GHSA or another OSV ID; required unless finding is given
A finding ref (FindingGroup.ref), e.g. Gateway/rev-b@1.4.0:CVE-2024-1234: instead of release and vulnerability
Responses
Section titled “Responses”The statements in summary.statements, with their releases, findings and statements as nodes
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.
Current VEX statements on the organization’s other releases for the same vulnerability, each with a match class from the path signature: exact, same_component_other_path or other_version. Only exact may back a carry-over. Also the organization’s rejected proposals for the vulnerability whose finding has this release’s path signature, with the reviewer’s note: don’t file them again unchanged. Give release and vulnerability, or a finding ref (finding).
object
The finding’s path signature; null without dependency data, or when its SBOM lists more dependencies than the edges limit (truncated is then true).
object
Version-less PURLs between the root and the component, in order (a component without a PURL by name).
The statements, newest first. A release without a finding for the vulnerability has nothing to compare: none are listed.
object
Node ID.
Node ID.
Node ID.
Rejected VEX proposals of the organization, on this or another release, whose finding has an exact path signature match with this release, newest decision first; the decision note says why. Empty when the release has no finding for the vulnerability.
object
Node ID.
Example
{ "nodes": [ { "class": "Artifact" } ], "edges": [ { "relation": "about" } ], "feed_status": { "additionalProperty": { "state": "ok" } }, "summary": { "statements": [ { "status": "not_affected", "match_class": "exact" } ] }}Missing release or vulnerability, finding with release or vulnerability, or finding.refInvalid
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