Software bill of materials
A software bill of materials is a structured, machine-readable inventory of the components, dependencies, versions, and other composition details included in a software artifact.
Grokking Software Architecture
A software bill of materials is a machine-readable inventory of the software components and dependencies included in an application.
- How it is used
- Tracks application dependencies so automated security scanners can check them during CI/CD deployment.
- How deep it goes
- Defines the inventory and explains its scanning role, but does not specify SBOM formats or generation steps.
- Examples
- Uses the left-pad outage and a food ingredients label to illustrate dependency visibility and fragility.
- What you can do after
- Operate/configure CI/CD to generate an SBOM and scan dependencies before deployment.
Read how Grokking Software Architecture explains software bill of materials →
Developer Experience on Kubernetes
A software bill of materials is a machine-readable inventory of the components and dependencies contained in a software artifact such as a container image.
- How it is used
- Supports container-image security workflows by recording image contents for inspection and vulnerability scanning.
- How deep it goes
- Explains generation, retrieval, embedding, and publication, but does not detail SBOM formats or scanner implementation.
- Examples
- Demonstrates Pack SBOM download and ko image builds for the Java and Go Appointments services.
- What you can do after
- Apply it via Pack or ko to obtain image component inventories and feed them to vulnerability scanners.
Read how Developer Experience on Kubernetes explains software bill of materials →
AI Governance
A software bill of materials is a machine-readable or human-readable inventory of the components and dependencies included in a software product.
- How it is used
- Identifies software components and dependencies when assessing GenAI-library supply-chain risks.
- How deep it goes
- Flags missing or incomplete SBOMs as a risk but does not explain how to create or validate one.
- Examples
- Uses missing or incomplete SBOMs among risks found across 20 GenAI libraries in the LibVulnWatch study.
- What you can do after
- Evaluate GenAI-library supply-chain risk by noticing missing or incomplete SBOMs.
Read how AI Governance explains software bill of materials →
GitHub Actions in Action: Continuous integration and delivery for DevOps
A software bill of materials is a structured inventory of the components and dependencies contained in a software product.
- How it is used
- Tracks software components and dependencies to support artifact integrity and supply-chain security in CI/CD workflows.
- How deep it goes
- Explains workflow generation, SPDX output, and release storage, but does not detail SBOM validation or dependency analysis.
- Examples
- Uses Microsoft's SBOM tool in a GitHub Actions workflow to inventory buildOutput and produce release-ready package data.
- What you can do after
- Build an SBOM with Microsoft's tool in a GitHub Actions workflow and attach it to a software release.
Effective Platform Engineering
A software bill of materials is a structured inventory of the components and dependencies contained in a software product.
- How it is used
- Uses signed component inventories to establish software supply-chain confidence without time-consuming manual processes.
- How deep it goes
- Explains contents, signing, integrity verification, registry placement, and pipeline automation, but does not detail an SBOM format.
- Examples
- Uses a platform pipeline that builds an image, records external packages, signs the SBOM, and stores the image in a trusted registry.
- What you can do after
- Operate/configure CI/CD pipelines to generate signed SBOMs and enforce their inclusion in deployed images.
Read how Effective Platform Engineering explains software bill of materials →
Also covered in
What to know first
- Common Vulnerabilities and ExposuresCommon Vulnerabilities and Exposures (CVE) is a public system for assigning standardized identifiers to publicly disclosed cybersecurity vulnerabilities.
Related concepts
- custom softwareused by · Custom software is software developed specifically for a particular organization, user, application, system, or integration rather than provided as a general-purpose product.
- dependency scanuses · Dependency scanning is the automated examination of software dependencies to identify vulnerabilities, outdated or unapproved components, licensing issues, and other risks.
- dependencyuses · A dependency is a component, resource, or prerequisite that another software component or activity relies on to function, build, or proceed.
Questions about software bill of materials
What is software bill of materials?
A software bill of materials is a structured, machine-readable inventory of the components, dependencies, versions, and other composition details included in a software artifact.
Which Manning books explain software bill of materials?
Grokking Software Architecture, Developer Experience on Kubernetes, AI Governance, GitHub Actions in Action: Continuous integration and delivery for DevOps and Effective Platform Engineering.
What should I know before learning software bill of materials?
Manning books that teach software bill of materials usually introduce Common Vulnerabilities and Exposures and CycloneDX first.
What is software bill of materials also called?
Software bill of materials is also called SBOM.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




