Cross-project vulnerability findings (admin, install-scoped).
curl --request GET \ --url 'https://stratum.example.com/v1/inventory/findings?state=open&sort=priority&limit=100' \ --header 'Authorization: Bearer <token>'. Findings across ALL projects — the operator’s install-wide posture lens. Same InventoryFinding shape (carries projectId + instanceId) and filters as the per-project list, plus optional projectId/organizationId narrowing, paginated. Requires the install-scoped inventory:ReadAll action.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Filter by ladder-v1 priority (repeatable).
Narrow to a single project.
Narrow to a single organization.
Opaque cursor from a previous response’s nextPageToken.
A keyset cursor: it names the last row of the previous page, so pages stay stable while findings are inserted or resolved underneath the caller. Findings are written in bulk by the vulnerability feed, so that happens routinely.
A token issued before encoded an offset. Those are not accepted and fall back to the first page rather than resuming at a wrong position.
Responses
Section titled “Responses”Cross-project findings page.
object
object
CVE / GHSA / OSV id
Open/acknowledged/suppressed are operator-facing; resolved is matcher-owned (package no longer matches).
ladder-v1 rank derived from CVSS x EPSS x KEV. KEV membership forces critical; missing enrichment degrades to a severity-derived score, never unranked.
CISA KEV membership — exploited in the wild.
FIRST EPSS 30-day exploit probability (0.0-1.0), null if unknown.
Normalized CVSS base score (0.0-10.0), null if unknown.
Opaque cursor for the next page; absent when there are no more.
Example
{ "items": [ { "state": "open", "priority": "critical" } ]}Authenticated but not authorized.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}