How one of the release's findings came about, and why
const url = 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/findings/osv/example/timeline';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/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/findings/osv/example/timeline \ --header 'Authorization: Bearer <token>'The finding’s timeline, computed when read: published upstream, in Affectra (first loaded), matched to this release, known exploited (the list’s date and ours, per CVE and list: CISA’s KEV or ENISA’s), and the organization’s VEX statements on it, oldest first. Times marked approx are upper bounds (“before”): records Affectra had before it recorded load times.
The cause, with F the first match in the release (never before the SBOM that brings it in), S the earliest of the release’s SBOMs with a matched component, and L the last logged load of the record’s feed (the matched components’ OSV data sets, or nvd) that started at or before F. The first that applies:
- mapping: the first match came through the organization’s own CPE mapping or CSAF product mapping (named, with its creation time).
- upload: S is no earlier than the record’s first load and, if there is L, than L’s start.
- new_advisory: the record was first loaded in L (at: L’s end). Not for approximate load times.
- advisory_changed: the record is older than L, which updated it (at: L’s end). What changed isn’t said.
- unknown: none of these can be shown.
A record the release has no finding for is a 404, like another organization’s release.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
The finding’s record ID, e.g. “DSA-5343-1”, “CVE-2023-0286”, “siemens:SSA-104023” (csaf)
Responses
Section titled “Responses”The timeline
object
Published upstream
Last modified upstream
When Affectra first had the record
object
At is an upper bound: show it as “before
The earliest of the release’s SBOMs that brings the finding in
First matched to this release
The record’s CVEs on an exploited list: CISA’s KEV catalog, or ENISA’s list (EU KEV) for entries from a source other than CISA. A CVE on both lists has an entry for each.
object
Cisa: CISA’s KEV catalog; enisa: ENISA’s exploited list
Added by the list
When Affectra first had the entry
object
At is an upper bound: show it as “before
The EUVD IDs (ENISA’s EU Vulnerability Database, e.g. EUVD-2025-4893) of the record’s CVEs, sorted; empty when ENISA has none or this installation doesn’t sync the EUVD.
The organization’s VEX statements on the record or its CVEs for this release, oldest first
object
Why the finding is there; the rules are in the operation’s description
object
Mapping: created; upload: S; new_advisory, advisory_changed: the load’s end
New_advisory, advisory_changed: the source
OSV data set, e.g. “Debian”, or CSAF provider, e.g. “siemens”
A CPE mapping has vendor and product; a CSAF product mapping provider, kind and value
object
What of a CSAF product the value names
Example
{ "source": "osv", "matched_via": "purl", "known_exploited": [ { "list": "cisa" } ], "assessed": [ { "status": "not_affected" } ], "cause": { "kind": "mapping", "feed": "osv", "mapping": { "kind": "model_number" } }}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