Skip to main content
Zero separates concrete security issues, publications, affected software, reusable taxonomies, and source evidence. This keeps related concepts connected without treating them as interchangeable.

Layered ontology

The diagram is a visual summary. The tables below define every concept and relationship in text.

Graph relationships

Core concepts

Important cardinalities

These cardinalities describe customer-visible meaning, not database implementation.

Identifiers are not entities

Assessments and exploitation evidence

An assessment is an issuer-owned measurement or decision about a vulnerability. CVSS, EPSS, SSVC, and CISA KEV inclusion retain their method, value, issuer, and assessment time rather than becoming one blended risk fact. Exploitation evidence is a source-backed claim about exploit availability or observed exploitation. Public proof-of-concept availability and active exploitation are separate states, and missing evidence is not evidence that exploitation has not occurred. Affected assertions relate vulnerabilities to software with an affected, fixed, unaffected, or investigating version scope. Remediation remains scoped to the relevant vulnerability and software rather than applying to every related release.

Software and releases

Software is a versionless identity for a package, application, operating system, appliance, hardware device, or firmware. A Software record can have many registry-observed release children. A release records an exact version and registry metadata; it does not create another Software identity. Release assessments join a registry-observed release to a normalized affected assertion. The API aggregates those rows by vulnerability or advisory using explicit conflict semantics: agreeing sources produce one status and source count, while disagreement produces unknown with conflicting_sources. Release and nested subject lists are deterministically capped at 100 and expose totals and truncation metadata. The registry supplies release observations, while vulnerability databases and publisher advisories supply the affected-version claims being evaluated; general web search does not create release records.

Derived classifications

Zero-day, actively exploited, newly disclosed, and high priority are computed views over entities, evidence, assessments, and time. They are not entity types. A vulnerability is classified as exploited as a zero-day only when accepted source evidence reports exploitation in the wild before an official vendor fix was available. A CVE assigned later does not erase that history.

Provenance

Zero preserves the derivation chain from a fetched artifact to an immutable record version, its source claims, and the resolved values returned to customers. This follows the W3C PROV model while keeping the product language focused on sources and evidence.

Provenance

Trace normalized values back to immutable source evidence.

Data sources

See the public datasets that contribute records and evidence.