A timeline of recent open source CVE intensity and volume
A timeline of recent open source CVE intensity and volume
I was curious what it would look like if I plotted the intensity and volume of software supply chain CVEs over time, given what seemed like a flood of compromises lately. It looked exactly as I expected, and I expect it to get worse before it gets better. Yes, an LLM was used but because I wanted the simplest possible architecture, I steered away from using any back end at all. Instead it's just GitHub pages with a static json document as the source of data, updated daily by a GitHub action which stores and parses the OSV repository. I wanted to include the Linux kernel but the complexities around how CVEs are assigned there made it difficult -- if I find a simple solution in future I'll add it.
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
SlideSelection, an Open Source Hooper Selection Implementation
Piki is now open source
Open Source CNC Beehive With Arduino and Sensors
An Open-Source Intro to WebApps Curriculum
An Open-Source Resource for Combating Burnout
Duckling – Open-source datetime expression parsing
Poll is now open-source
PinPoint open source geocoder
Crayfish, an open source, shareware newsreader
Cypht – Open Source webmail revisited