A software bill of materials (SBOM) is a machine-readable inventory of the components and dependencies contained in a software artifact, such as a container image. Image-building workflows generate it alongside the artifact so security tools can inspect what the image contains. section 3.2.3 section 3.2.4
Container-image workflows use SBOMs in several practical ways:
- Cloud Native Buildpacks include SBOM generation as one stage in a sequence of buildpacks used to containerize an application. section 3.2.3
- The Pack CLI can download the SBOM for a locally built image into an output directory. section 3.2.3
- ko embeds an SBOM in the built image, publishes it with registry images, and makes it available to vulnerability scanners. section 3.2.4
Inspecting an image SBOM
Build the Appointments image with Pack, then run `pack sbom download appointments:0.0.1-SNAPSHOT --output-dir image-sboms`. With ko, build locally using `ko build --local -B -t 0.0.1-SNAPSHOT`; the resulting image includes an SBOM, although a locally built image has not published it to a registry. section 3.2.3 section 3.2.4
pack sbom download appointments:0.0.1-SNAPSHOT \ --output-dir image-sboms
Use the Pack command listing to inspect the concrete workflow for downloading an image SBOM. section 3.2.3




