json2.8 KB

OpenVEX Statement Document

An OpenVEX document covering all four status values, with the justification and impact statement OpenVEX requires alongside not_affected and the action statement it requires alongside affected. 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.

JSON parsing Schema validation Conversion testing

Preview — first 50 linesjson

{
  "@context": "https://openvex.dev/ns/v0.2.0",
  "@id": "https://vex.orchard.example/2ddc7cac-b207-4092-afcc-742f1d216c43",
  "author": "Example Softworks (fictional)",
  "role": "Document Creator",
  "timestamp": "2026-01-01T00:00:00Z",
  "version": 1,
  "tooling": "novus-examples-vex-fixture/1.0.0",
  "statements": [
    {
      "vulnerability": {
        "name": "NOVUS-SAMPLE-2026-0001",
        "@id": "https://advisories.orchard.example/NOVUS-SAMPLE-2026-0001",
        "aliases": [
          "SAMPLE-CVE-2026-0001"
        ]
      },
      "timestamp": "2026-01-01T00:00:00Z",
      "products": [
        {
          "@id": "pkg:npm/%40orchard-example/gateway@4.2.0",
          "subcomponents": [
            {
              "@id": "pkg:npm/example-logger@3.4.1"
            }
          ]
        }
      ],
      "status": "affected",
      "action_statement": "Upgrade example-logger to 3.5.0."
    },
    {
      "vulnerability": {
        "name": "NOVUS-SAMPLE-2026-0002",
        "@id": "https://advisories.orchard.example/NOVUS-SAMPLE-2026-0002",
        "aliases": [
          "SAMPLE-CVE-2026-0002"
        ]
      },
      "timestamp": "2026-01-01T00:00:00Z",
      "products": [
        {
          "@id": "pkg:npm/%40orchard-example/gateway@4.2.0",
          "subcomponents": [
            {
              "@id": "pkg:npm/example-cache@0.9.2"
            }
          ]
        }
      ],

… 100 lines total — download for the full file.

Specifications

Seed: 51200
Sample Only: true
Format: OpenVEX
Context: v0.2.0
Statements: 4
Statuses: affected, not_affected, fixed, under_investigation
Line Endings: LF

Testing contract

Expected to pass

Scenario: Validate OpenVEX conditional requirements, not just its JSON shape.
Expected result: Validator confirms every not_affected statement carries a justification and every affected statement carries an action_statement.

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

“OpenVEX Statement 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 · OpenVEX. 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("openvex-statement.json") as f:
    data = json.load(f)
print(type(data), len(data))

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