liveBook · Manning

Software bill of materials

As explained in Grokking Software Architecture

A software bill of materials is a machine-readable inventory of the software components and dependencies included in an application.

A software bill of materials (SBOM) is a machine-readable inventory of the third-party libraries, frameworks, and dependencies in an application. Like an ingredients label, it helps teams see what their software contains. In a CI/CD pipeline, automated scanners can check that inventory against known vulnerabilities and halt deployment when a component is flagged. section 11.7.1

When a tiny dependency disappears

The left-pad package was a small dependency used by many major projects. When it vanished from NPM, builds around the world failed. An SBOM helps make dependencies visible; scanning it helps teams respond when components are vulnerable or compromised. section 11.7.1

How Grokking Software Architecture covers it

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.
How it connects
Connects dependency inventories with CI/CD, dependency scanning, and software supply chain security.

Also explained in

Compare how 5 books explain software bill of materials →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.