Express + expert help

View pricing →
Skip to main content

Practical template

Yocto SPDX demo execution record

Use this template with your own product details and evidence. Copy the text into your document to complete the fields and add rows as needed.

Execution record template. Fill in the results of your own build and coverage checks.

Documentation: https://docs.yoctoproject.org/5.0.13/dev-manual/sbom.html Poky tag: yocto-5.0.13. Commit the tag points to, checked 2026-11-19: f16cffd030d21d12dd57bb95cfc310bda41f8a1f (the value git rev-parse HEAD prints after the clone). The annotated tag object has a different hash, 529843b1c189ab7b133b7fdf197d4b2a4b71a6db. Record your actual checkout commit below; a tag reference alone is not a completed build.

  • Host/distribution/dependencies: [fill in]
  • Disk available: [fill in]
  • Start/end/log: [fill in]
  • Checkout commit: [fill in]
  • Layers/commits: [fill in]
  • MACHINE: qemux86-64 Configuration: INHERIT += "create-spdx"; SPDX_PRETTY = "1"
  • Effective INHERIT and INHERIT_DISTRO values: [fill in]
  • Target: core-image-minimal
  • Effective local.conf/bblayers.conf: [fill in]
  • spdxVersion found in the generated documents (SPDX-2.2 is expected at this tag): [fill in]
ArtefactActual pathSHA256Coverage/limitations
Image[fill in][fill in][fill in]
SPDX archive[fill in][fill in][fill in]
Package manifest[fill in][fill in][fill in]

Compare selected packages, custom application recipes, static libraries, boot/recovery and coprocessor/vendor firmware. Failures/warnings and corrective steps: [fill in]. Embedded reviewer/date: [fill in]. Do not fill results from expected output.