Lightning Talk: Criticality Scores Unveiled: A High Schooler’s Journey with OpenSSF
summary
Uses the Rob Pike algorithm to combine signals (last update, contributor count, commit frequency, closed issues) with per-signal thresholds to produce a weighted criticality number (example intermediate score 0.5807). Demo parses Golang repos from OSSF into parts.txt, fetches signal data, then runs the score with default weights and with a modified commit frequency weight 1→10, turning top scores from ~0.83/0.80 to ~0.69/0.66. Signals can be zeroed or removed so the metric focuses only on chosen repository fields.
AI-written summary · about
related talks
25mHow do you trust your open source software?
50mHow Do You Trust Open Source Software?
36mEstimating Security Risk Through Repository Mining
10mLightning Talk: Scoring Dependencies to Detect “Weak Links” in your Open-source So...
31mScorecard at Scale: Old and New Possibilities for Lifting Security on All Repositories
27mAn Open Book Test: Securing Open Source Software With OpenSSF’s Scorecard
42mAssessing the Risk of Open-source Components Using OpenSSF's Scorecard
20mBuilding Secure Software OpenSSF Best Practices for Everyone!