Skip to main content
A Software Bill of Materials (SBOM) lists the packages and components in an image. SBOMs help you understand provenance, license obligations, and exposure to vulnerabilities.

Why SBOMs matter

  • Transparency for security audits and compliance
  • Faster triage when new CVEs are disclosed
  • Confidence in reproducible builds

Generate or fetch an SBOM

Use common tools to produce or download SBOMs:
If the image publishes signed attestations, you can retrieve them with cosign:

Best practices

  • Store SBOMs alongside release artifacts for traceability
  • Pair SBOMs with periodic vulnerability scans (e.g., Trivy/Grype)
  • Pin image tags (e.g., :1.2) and record the digest for immutability