Build Metadata Manifest (JSON)
The plain build record a CI job writes next to its artifacts — source ref and commit, builder identity, timings, toolchain versions and output digests — from which a provenance statement can be generated. Every package, version, hash and licence is fictional — the tree describes nothing real.
{
"schema": "novus-sample/build-metadata/1",
"product": {
"name": "orchard-gateway",
"version": "4.2.0"
},
"source": {
"repository": "https://git.orchard.example/orchard/gateway",
"ref": "refs/tags/v4.2.0",
"commit": "902ea810fbdd8ff73082bd2873585709f2ca500b",
"dirty": false
},
"build": {
"id": "8814",
"builder": "https://build.orchard.example/builders/hosted/v1",
"startedOn": "2026-01-01T00:00:00Z",
"finishedOn": "2026-01-01T00:06:12Z",
"durationSeconds": 372,
"trigger": "tag",
"reproducible": true
},
"outputs": [
{
"name": "orchard-gateway-4.2.0.tgz",
"sha256": "06af88e316cf889e0b72645f235f77c900d48972456b1ff6ba4df49ae24be734",
"bytes": 184320
},
{
"name": "gateway-4.2.0.sbom.json",
"sha256": "060bd96bd9eb91fc78c63d8db571ff7e56fb743b51bc1b670b60cce5299e4a76",
"bytes": 11500
}
],
"toolchain": {
"node": "20.11.1",
"npm": "10.4.0",
"os": "example-linux 3.20"
},
"novus_sample_note": "SAMPLE — fictional supply-chain data. Every package, registry, version, hash, licence, advisory identifier and signature in this document is invented."
}
Specifications
- Seed
- 51200
- Sample Only
- true
- Outputs
- 2
- Duration Seconds
- 372
- Trigger
- tag
- Dirty Worktree
- false
- Line Endings
- LF
Testing contract
Reference control- Scenario
- Generate a SLSA provenance statement from raw build metadata.
- Expected result
- Generated provenance carries the same commit, builder id and artifact sha256 as the SLSA v1 fixture in this family.
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
“Build Metadata Manifest (JSON)” is a deterministic Novus Examples fixture for JSON parsing, Metadata testing, Schema validation. Flat, deeply nested, JSON Lines, and intentionally invalid JSON for testing parsers and error handling.
Documented properties for this file: seed 51200 · LF. 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("build-metadata.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonSPDX 2.3 SBOM With Snippet RangesAn SPDX 2.3 JSON SBOM that uses the snippet section to attribute a fictional vendored fragment inside a file to a different licence, with both byte-offset and line-number ranges. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonJSON-LD @graph with @id cross-referencesA single @graph holding four nodes wired together by @id rather than by nesting - the shape most CMS plugins emit - including a SearchAction, a breadcrumb whose last item has no URL, and one reference to a product node that lives on another page. For testing graph flattening and reference resolution.
- jsonJSON-LD Event with offers and a locationA valid Event record for a hybrid event: both a physical Place with a postal address and geo coordinates and a VirtualLocation, plus a free Offer and a capacity. For testing array-valued properties and event date/timezone handling.
- jsonJSON-LD LocalBusiness with opening hoursA valid LocalBusiness (as a SportingGoodsStore subtype) with a postal address, geo coordinates, weekday and Saturday opening hours, and a 00:00-00:00 specification marking a holiday closure. For testing opening-hours parsing and the closed-all-day convention.
- jsonJSON-LD missing required properties (deliberately invalid)A deliberately invalid Product record: no name, an Offer with a currency but no price, a brand with no @type, a Review with no rating, an AggregateRating with no ratingValue, and an availability given as a bare token instead of a schema.org URL. Valid JSON throughout, so the failure is semantic.
- jsonJSON-LD NewsArticle with author and publisherA valid NewsArticle with two authors, a publisher whose logo carries explicit pixel dimensions, three images at the aspect ratios news results expect, and both publication and modification timestamps. For testing article extraction and date normalisation.
Generated by generation/supply_chain.py. Free for any use, no attribution required — license.