Create a way to track analyzer versions and compare to new releases

Today we don't have a singular place to track versions of open source analyzers we leverage, and watch for new versions becoming available.

In the spirit of having keeping our analyzers up-to-date, we should have a simple way to track this.

Current Process for releasing security products

ideas

  • Update existing docs to include version of scanners and link to changelogs so that we don't have to hunt for them everytime.
  • Update our scanner repos with clearer information in the readme files about what version the scanner is at, and where to find change logs

post MVC ideas

  • create automated scripts that continuously check for new versions of scanners and automatically open issues on scanner repositories with recommended issues/MRs.
Edited by Taylor McCaslin