VCIO-next: Migrate improvers to V2 #1945

Activity

1. TG1999

   added a parent issue on Jul 15, 2025

   • VCIO-next: Improve advisories model and update pipelines #1944
2. TG1999 commented on Jul 15, 2025

   

   TG1999

   on Jul 15, 2025

   ContributorAuthor

   More actions

   This is done now!

   PRs for references:
   #1866

   To test this:
   Set up Vulnerablecode on your system locally and run a new V2 importer pipeline for example:

   ./manage.py improve --l

   You will be able to see

   enhance_with_exploitdb_v2
   enhance_with_kev_v2
   flag_ghost_packages_v2
   enhance_with_metasploit_v2
   compute_package_risk_v2
   compute_version_rank_v2
   collect_fix_commits_v2

   All of these importers are migrated to V2 and are ready to improve Advisory level info
3. TG1999

   closed this as completedon Jul 15, 2025
4. TG1999

   self-assigned this

   on Jul 15, 2025
5. github-project-automation

   added this to 00-AboutCodePlanneron Jul 22, 2025
6. pombredanne

   moved this to Done in 00-AboutCodePlanneron Jul 22, 2025
7. tsteenbe

   changed the title [-]VCIO-next: Migrate imrpovers to V2[/-] [+]VCIO-next: Migrate improvers to V2[/+] on Jul 23, 2025
8. pombredanne

   moved this from Done to Validated in 00-AboutCodePlanneron Aug 12, 2025
9. pombredanne

   assigned

   pombredanne

   and unassigned

   TG1999

   on May 12, 2026