Open data · CC0
Data exports
The factual, structured release record is free to take: every recorded version, channel appearance, verified build, documented change, citation locator, and provenance trail, as versioned JSON and CSV files. No API key, no rate limits, no scraping required.
Datasets (schema v1.0.0)
| Dataset | Contents | Download |
|---|---|---|
releases | One row per recorded software version, with lifecycle status and public release date. Columns: id, vendor, platform, family, version, status, public_release_date, release_notes_url, provenance_status, updated_at | JSON · CSV |
events | Observed channel appearances: developer betas, public betas, release candidates, and public releases with dates. Columns: id, vendor, platform, family, version_id, version, label, route_alias, channel, appearance_date, version_label_at_appearance, availability_state, build_id, build_number, is_revision, audience, device_scope, region_scope, language_scope, provenance_status, index_eligible, source_count, updated_at | JSON · CSV |
builds | Verified build numbers only, linked to the channels in which each build appeared. Columns: id, vendor, platform, family, version_id, version, build_number, display_build_number, canonical_slug, status, device_scope, provenance_status, index_eligible, updated_at | JSON · CSV |
changes | The reusable change library: features, fixes, and modifications recorded across releases. Columns: id, title, category, updated_at | JSON · CSV |
occurrences | Release-specific change occurrences with delta/inherited scope and documentation status. Columns: id, change_id, change_title, action, inheritance, target_kind, target_id, vendor, platform, family, version, build_number, documented_status, evidence_state, applicability, source_count, updated_at | JSON · CSV |
citations | Source metadata and locators backing material claims. Never mirrored publisher copy. Columns: id, target_kind, target_id, source_id, source_url, source_title, publisher, author, publication_date, accessed_date, archive_url, source_class, locator | JSON · CSV |
provenance | Audit batches and correction records describing how each fact earned its place. Columns: id, record_type, title, status, verification_date, scope, snapshot_identity, affected_target_ids, reason_category, published_at | JSON · CSV |
A machine-readable index of all files is published at /exports/v1/manifest.json.
License
The structured factual fields in these files are dedicated to the public domain under CC0 1.0. CC0 applies to the factual structured fields in this export. Original editorial prose, design, media, and third-party material are excluded.
Attribution is appreciated but not required. If the archive saved you a scrape, a link back to Version Record helps others find the source.
Data model in one paragraph
A release event is an observed channel appearance — a developer beta, public beta, release candidate, or public release on a date. A build exists only when a build number has been verified by sources, and multiple events can share one build. Occurrences attach documented changes to events or builds. Every material fact carries citations, and material corrections are recorded in a public ledger. The methodology page explains the evidence standards.