It would be nice to have the advisory data as csv to use in places like spreadsheets and so we can do analysis and try to identify trends.

I think we want to go back as far as https://www.drupal.org/sa-core-2018-001 which is maybe the most modern one that has multiple vulnerabilities in a single advisory and is therefore a bit messy to analyze. We may want to try to clean those up some day.

Issue fork securitydrupalorg-3610945

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

greggles created an issue. See original summary.

greggles opened merge request !28

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Needs review

I built this initially a while ago for Drupalcon Chicago using a mix of gemini and my work. Then recently I polished it up with a mix of Claude and my work.

The data back to 2018 seems to work well. That's about 680 advisories currently.

I use the command csvcut -c 1,2,3,4,5,6,7,8,9,10 drupal_sa_report.csv | uniq to get data about just unique the advisories without information about the people involved. csvcut is part of csvkit https://github.com/wireservice/csvkit

  • greggles committed cff373d7 on 7.x-1.x 
    Fix #3610945: followup, fix deprecation warning and hopefully some...
greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Needs review » Fixed

Okeydoke.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.