One enhancement I think we could make here is to generalize this to something like: "package impact" - specifically other axes/metrics I think are relevant:
size (trivial to compute)
update frequency (Obviously data exists, but is a bit more work to collate)
RHEL ACG level (Data exists, I assume in some programmatic form)
I could imagine tweaking things slightly here such that we help offer a tool which aids folks in gauging the overall "impact" of the presence of a package. Its CVE load is a big one, but not the only one.
Nice tool!
One enhancement I think we could make here is to generalize this to something like: "package impact" - specifically other axes/metrics I think are relevant:
I could imagine tweaking things slightly here such that we help offer a tool which aids folks in gauging the overall "impact" of the presence of a package. Its CVE load is a big one, but not the only one.