OpenTeams Score: A Way to Assess Open Source Projects
summary
OpenTeams Score assesses open source projects using five concrete components: popularity, community, security, license permissiveness and versioning. It pulls data from GitHub + package managers + Twitter + Stack Overflow and uses Security Scorecard for security signals. A dashboard proof of concept scores projects by converting component values to z-score normalization and the team reports having scored 1200 projects. Project pages and a GitHub repo are available so the system can be inspected and improved.
AI-written summary · about
related talks
27mHow Do You Trust Your Open Source Software?
25mHow do you trust your open source software?
27mAn Open Book Test: Securing Open Source Software With OpenSSF’s Scorecard
31mAssessing Open Source Software Projects in the Software Supply Chain
45mWhat’s Going On In A FOSS Project?
41mBack to Security Basics: Evaluating, Consuming, and Contributing Open Source...
31mScorecard at Scale: Old and New Possibilities for Lifting Security on All Repositories
42mAssessing the Risk of Open-source Components Using OpenSSF's Scorecard
