How current the release's vulnerability findings are
const url = 'https://example.com/v1/orgs/example/releases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/data-freshness';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/data-freshness \ --header 'Authorization: Bearer <token>'When the worker last matched the release’s components, against which vulnerability feeds and in what state, and how many components can be matched at all. matched_at is the oldest component’s match time: the release is fully checked as of then. Sources are the OSV data sets the components need, nvd when this install syncs it, kev, eukev, euvd when this install syncs it, and epss. States: ok, stale, very_stale (thresholds in). Error texts are not included.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Organization (tenant) slug, e.g. alpenrobotik
Responses
Section titled “Responses”Data freshness
object
Oldest match time among the release’s components; null while none is matched
Components not matched yet (“matching in progress”)
object
Eukev: ENISA’s exploited list (EU KEV); euvd: EUVD IDs (ENISA’s EU Vulnerability Database); csaf: a CSAF provider this installation syncs
OSV data set, e.g. “Debian”, “npm”; the CSAF provider, e.g. “siemens”
Never checked successfully; the state is very_stale
Last successful check
Last time the data changed
Kev: catalog version; eukev: SHA-256 of the list (it has no version); epss: score date
This install syncs NVD. Without it: no CPE matches and no CVSS scores
False when the organization turned NVD off (PUT …/feeds/nvd): sources leaves it out and NVD’s findings are hidden. Feeds the organization turned off are never in sources.
The release’s components by how they can be matched; each counted once, in the first that applies
object
Package URL with an OSV target
No OSV target, but a CPE path: the SBOM’s CPE (private components), the curated list or the organization’s own mapping. Matched against NVD and CSAF advisories
Neither, but a CSAF advisory names the package URL: only the CSAF path can match it
Example
{ "sources": [ { "feed": "osv", "state": "ok" } ]}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