Skip to content

SLSA specification copy

Datasetreferencedatasets/slsa-spec-copy

Checked by automation only

still a draft

Written 2026-10-23 by ktl-librarian (automation). Last checked 2026-10-30 by ktl-librarian (automation).

The full record
Checks
  • 2026-10-30 by ktl-librarian (automation)
Sources
Derived from
Pointed to by
Graph
Open this concept in the knowledge graph
IRI
https://w3id.org/lmodel/slsa/knowledge/datasets/slsa-spec-copy
Licence
CC BY 4.0
Files
MarkdownJSON-LDSource on GitHubHistory on GitHub

src/slsa/schema/spec/ holds a copy of the SLSA specification’s pages as Markdown with Jekyll front matter: the tracks, the build, source, dependency and build environment track pages, threats, provenance and verification summary formats, and the terminology. images/ holds the specification’s SVG diagrams, and schema/ holds provenance.proto and provenance.cue.

index.md says that this is “the Working Draft of what the next version of the SLSA specification might be” and “Version 1.2 of the SLSA specification, which defines the SLSA Build and Source tracks”. The copy also holds dependency-track.md and build-env-track-basics.md for the other two tracks. The pages keep their Jekyll template tags, for example the {%- for section in site.data.nav.main %} loop in index.md.

CONTRIBUTING.md says never to edit the copy in place, but to replace it from a SLSA release and update NOTICE.

NOTICE says that every file is identical to its counterpart in docs/spec/draft/ in the SLSA repository at tag v1.2 (commit 19e4e2f), and that the copy holds nothing else. A comparison by git blob hash bears this out: all 39 files of the copy match the 39 files of that folder at that tag.

The SLSA specification page gives the license and its attribution condition.

.github/workflows/upstream-watch.yaml runs scripts/check_upstream_release.py every Monday at 07:00 UTC, and by hand. The script compares every copied file with its blob in the pinned tree, PINNED_TAG = "v1.2", by git object hash, and checks whether the SLSA repository has tagged a newer version. It fails on a newer version or on a difference it does not list as known. Its KNOWN_DIFFERENCES list is empty, because the copy is exact. A failure opens an issue, or comments on the one already open.