CSAF 2.0 VEX Document
A CSAF 2.0 VEX advisory with the nested product tree that CSAF requires — vendor, product name, product version — and product_status buckets rather than a per-statement status field. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
{
"document": {
"category": "csaf_vex",
"csaf_version": "2.0",
"title": "SAMPLE VEX for Orchard Gateway 4.2.0 (fictional)",
"publisher": {
"category": "vendor",
"name": "Example Softworks (fictional)",
"namespace": "https://orchard.example"
},
"tracking": {
"id": "ORCHARD-SAMPLE-VEX-0001",
"status": "final",
"version": "1",
"initial_release_date": "2026-01-01T00:00:00Z",
"current_release_date": "2026-01-01T00:00:00Z",
"generator": {
"engine": {
"name": "novus-examples-vex-fixture",
"version": "1.0.0"
}
},
"revision_history": [
{
"number": "1",
"date": "2026-01-01T00:00:00Z",
"summary": "Initial SAMPLE release."
}
]
},
"notes": [
{
"category": "legal_disclaimer",
"text": "Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.",
"title": "SAMPLE data"
}
]
},
"product_tree": {
"branches": [
{
"category": "vendor",
"name": "Example Softworks (fictional)",
"branches": [
{
"category": "product_name",
"name": "orchard-gateway",
"branches": [
{
"category": "product_version",Specifications
- Seed
- 51200
- Sample Only
- true
- Format
- CSAF
- Csaf Version
- 2.0
- Category
- csaf_vex
- Product Tree Depth
- 3
- Vulnerabilities
- 4
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Resolve CSAF product ids through the product tree before applying statuses.
- Expected result
- CSAFPID-0001 resolves to Orchard Gateway 4.2.0 via three branch levels, and the four product_status buckets classify one advisory each.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“CSAF 2.0 VEX Document” is a deterministic Novus Examples fixture for JSON parsing, Schema validation, Conversion testing. Flat, deeply nested, JSON Lines, and intentionally invalid JSON for testing parsers and error handling.
Documented properties for this file: seed 51200 · LF · CSAF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
SBOM, lockfile, provenance, and advisory fixtures describe the same fabricated component tree across formats, so a converter or scanner can be diffed against a known answer. Every package name, version, hash, and advisory ID is invented — never treat a finding here as real.
Feed the file to your parser and assert it handles the documented quirks — quoted delimiters, embedded newlines, ragged rows, or invalid syntax; the valid↔invalid distinction is labelled in the title.
Code examples
import json
with open("csaf-2.0-vex.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsoncargo-audit Report (JSON)A cargo-audit report that shows three findings while a fourth is on the ignore list, plus an unmaintained-crate warning — so a gate must decide whether warnings count against it. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonGrype Scan Report (JSON)A Grype-shaped report of the same four SAMPLE advisories, with the match detail block that explains WHY each package matched — the field that makes false positives diagnosable. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonnpm audit Report (auditReportVersion 2)An npm audit v2 report keyed by package name, with the via chain, the effects list showing which fictional parents are impacted, and npm's own severity vocabulary where MEDIUM is spelled 'moderate'. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonOSV Vulnerability Record (JSON)A single OSV-schema advisory record for a fictional package, with a SEMVER range expressed as introduced/fixed events rather than as a version string — the part naive parsers get wrong. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonOSV-Scanner Report (JSON)An OSV-Scanner report that nests full OSV records under each affected package and adds the groups array that collapses aliases into one finding — the structure de-duplication depends on. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

- jsonOWASP Dependency-Check Report (JSON)A Dependency-Check-shaped JSON report, including the evidence-collection block that records how a package was identified and the confidence attached to that identification. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.

Generated by generation/supply_chain.py. Free for any use, no attribution required — license.