"Quantifying Nebraska"
summary
Gives a concrete method for finding those tiny-but-critical projects rather than rehashing the trope: uses sift to generate an SBOM, correlates packages to repos and scorecards, and highlights surprises like 301 unique Python dependencies and the XZ backdoor case study. Shows what metrics actually matter (issue/PR triage rates, commit/maintainer ratios), gives tools to filter candidates, and lists practical responses — sponsor, donate engineer time for triage/reviews, or provide infrastructure credits.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:28XZ backdoor supply chain attack
- 7:49Open source dependency stability
- 9:12Evaluating project health
- 15:14Human factors in sustainability
- 20:53How to provide meaningful support to projects
- 24:24Conclusion
related talks
12mQuantifying Nebraska
36mPanel Discussion: OSS Viability and Project...
26mBuilding & Supporting Open Source Communities Through Metrics
46mPanel Discussion: What Our OSPOs Have...
43mDon't Start Over, Start Left: Choosing the Right Open Source...
34mCommunity Data: What to Measure and Why?
41mBuilding and Supporting Open Source Communities Through Metri...
35mThe Benefits and Pitfalls of OSS Project Metrics: Measuring Health and Risk in Open Source Communities
