3 ms·
This is a great write-up. It's a very serious issue. I don't really know if there is any "one solution." I suspect that each project needs to set its own bar,
by ChrisMarshallNY 3y ago
This is a great write-up.
It's a very serious issue. I don't really know if there is any "one solution." I suspect that each project needs to set its own bar, and that any dependency that falls out of maintenance should be removed as quickly as possible (which was good practice, beforehand, but even more important, now).
[EDITED TO ADD]
I would also think about "scoring" the sensitivity of projects. Things like cryptography and low-level drivers would be highest-rated, while user-space chrome might not be as important.
- transpute 3y agoScoring framework: https://securityscorecards.dev/ https://securityscorecards.dev/ Code: https://github.com/ossf/scorecard https://github.com/ossf/scorecard April 2024 ranking of OSS projects by criticality, 100MB CSV: https://commondatastorage.googleapis.com/ossf-criticality-score/index.html?prefix=2024.04.01/230012/ https://commondatastorage.googleapis.com/ossf-criticality-sc...
- ChrisMarshallNY 3y agoThanks! I have a friend that used to work for a company called “SecurityScorecard.” Different beast, though. I think the idea was similar.
- guappa 3y agoThe scorecard stuff is flawed. You want to decide if something is secure or insecure but without reading the code. It's never going to have any correlation.