Skip to content

Datasets

  • Generated artifacts checked by automation only, still a draft
    Files generated from the slsa schema and never edited by hand, committed or git-ignored: the two merged schemas in docs/schema/, the Python data models, project/ (JSON Schema, OWL, SHACL, Java and more), docs/elements/ and the bundle’s domain schema .lokf/slsa.yaml, which a release also attaches as its schema asset.

  • slsa LinkML schema checked by automation only, still a draft
    The modular LinkML schema of the SLSA specification v1.2 (schema id https://w3id.org/lmodel/slsa): slsa.yaml imports a core module and one module per track, predicate or study, covering the Build, Source, Dependency and Build Environment tracks; the core imports the in-toto statement layer from lmodel/in-toto’s vendored core module and adds SlsaStatement; its lokf adapt copy in .lokf/slsa.yaml is the bundle’s domain schema.

  • SLSA specification copy checked by automation only, still a draft
    The SLSA specification’s Markdown pages, images and provenance schemas (.proto, .cue) copied into src/slsa/schema/spec/: all 39 files are identical to docs/spec/draft/ at SLSA tag v1.2, and a weekly workflow watches for a newer release.

  • Test data checked by automation only, still a draft
    Example YAML instances of the slsa schema in tests/data/, valid and invalid, named ClassName-###.yaml after the class they instantiate (SlsaStatement, InTotoDigestSet, SlsaBuildPlatform and the rest); pytest and linkml-run-examples check them.