Skip to main content
Provenance enriches field values on a Zero entity with the public evidence behind them. It is not a separate entity or a graph that clients need to model. The base entity remains simple: fields such as severity, publication time, affected ranges, and exploitation status contain normalized values. When provenance is included, Zero adds source context for those fields without replacing each value with a wrapper.

What provenance adds

Provenance entries are associated with entity fields by normalized paths. This allows one field to have evidence from several sources while the field itself continues to expose one usable value.

How to use it

  • Show attribution alongside a risk or remediation value.
  • Review disagreements before automating a remediation decision.
  • Explain why Zero selected one value from several public claims.
  • Preserve an auditable reference to the exact source data used at the time.
For example, a vulnerability can expose one preferred CVSS assessment while its provenance identifies every contributing assessment, the selected source, and the reason it was preferred. An affected range can similarly retain evidence from multiple advisories without changing the normalized range shape.

Source record versions

A source record version is the immutable evidence behind a provenance entry. It preserves the raw payload, retrieval time, payload hash, upstream schema version, and source identity. Most clients do not need to retrieve source record versions during normal use. Follow one only when you need the original upstream payload for verification, audit, or debugging.

API pages

Provenance is an optional projection on entity detail requests. See the relevant retrieval page for its complete response schema: