A software bill of materials, or SBOM, is a machine-readable list of every component inside a piece of software, with versions and suppliers. It works like an ingredients list: it records the libraries and packages that went into a product, so that others can see what it contains.

It matters because when a vulnerability is announced in a component, an organization needs to know quickly which of its products use it. An SBOM turns that question into a search, instead of a manual investigation. Customers, regulators and procurement teams increasingly ask for one.

An SBOM has limits. It is a snapshot, so it is only as good as the way it was generated and can go out of date with each release, and it can miss components that were included in ways that tools do not detect. A list of components does not say whether a vulnerability in one of them can actually be exploited in the product. Its quality varies between suppliers.

To use one, generate it as part of the build, keep it with each release, check it against vulnerability data and ask suppliers how theirs were produced.