The Burden of Knowledge: Dealing With Open Source Risks
summary
Organization-wide SBOMs reveal scale: 30,000 internal repos average 125 dependencies each, totalling 117,000 packages and a single top dependency appearing in 19% of projects. Automated tools used include SBOM generation (internal Swift), OpenSSF Scorecard and a bespoke red flag checker; analysis finds 9 of top 10 score <5/10 on OpenSSF. Practical options tested are risk profiling, targeted sponsorship, co‑maintaining critical packages, centralized contribution teams, developer guidance, and selective engagement.
AI-written summary · about
chapters (7)
- 0:00Introduction to open source risks
- 1:42From assumptions to data
- 9:34Problems with passive metrics
- 15:32Scale of open source usage
- 22:30Strategic risk management options
- 27:45Call to action and collaboration
- 40:49Q&A session
related talks
45mPanel Discussion: Managing Open Source...
41mManaging the risk and growth of using Open Source Software
39mSOS: Sustainable Open Source
37mOpenSSF Best Practices for Everyone!
13mManaging Vulnerabilities in Open-Source Dependencies
16mKeynote: Back to Security Basics: Evaluating, Consuming, and Contributing Open Source Software
42mAssessing the Risk of Open-source Components Using OpenSSF's Scorecard
25mDefining the Limits of Risk
