- cross-posted to:
- opensource@programming.dev
- cross-posted to:
- opensource@programming.dev
Did you know that the OpenSSF defined how to compute a “criticality score” which evaluates open source projects? This score defines the influence and importance of a project.
You must log in or register to comment.
Kewl. But.
A core criticism of the OpenSSF Criticality Score is that it’s a popularity contest, not a security audit. Paraphrasing.
The score is good at identifying widely used projects based on metrics like the number of contributors and dependencies. However… it can give a low score to a crucial, stable project that simply isn’t very active. Most importantly, it doesn’t actually check the code or security practices. A high score means a project is a big target, not that it’s a secure one.



