So I generated over 3000 SBOMS for the CNCF ecosystem
summary
A CNCF-wide pipeline generates 12,500 SBOMs from landscape-sourced releases, using Wayel for multi‑language SBOMs, GitHub Actions in 2,500+ parallel jobs, S3 storage, ClickHouse ingestion and the bombhorde UI/API. Scans cover 228 projects plus ~1,700 repos; common findings are missing/incorrect license metadata, archived or unused transitive deps, and inconsistent SBOM formats. Problems encountered: GitHub artifact/UI breakage and API rate limits. Outcome: automated enrichment with OSV/GitHub license checks, queriable DB, and planned VEX auto-generation (LLM-assisted) for maintainer sign-off.
AI-written summary · about
chapters (7)
- 0:00Introduction and SBOM basics
- 4:29CNCF projects and license challenges
- 8:45Generating SBOMs at scale
- 13:46Introducing BombHorde platform
- 23:01Tool stack and open source contributions
- 27:28Open source sustainability and CRA
- 30:20Key takeaways and next steps
related talks
43mUsing SBOMs for Linux Foundation Projects
22mBuilding a Robust SBOM Solution with Backstage.io
38mEnhancing SBOM Generation: Filling the Gaps To Make Actionable SBO...
36mSBOMs, VEX, and Kubernetes
50mRealities of SBOM: What Is Under the Hood of SBOM?
38mThe State of SBOMs
47mThe Missing Link - How we collect and leverage SBOMs
57mSBOMs – The Missing Link
