Inside the curation tool, there should be a place where contributors can search for a vulnerability they can curate.
Items that contributors should filter by (optional filters):
Curation Level: Filter between curations that are new (Lvl 0), work-in-progress (Lvl 1), or finished (Lvl 2+).
Project: Which project(s) does a curator want to work on?
Language: What programing language(s) does a curator want to work with?
Auto-Discovered VCC: If it's a curator's first time, they may want an easier commit. Conversely, they could find a CVE without an auto-discovered VCC and make a large impact..
Difficulty: Direct newer contributors to easier CVEs while moving veterans towards difficult CVEs. This tag is arbitrary but could be useful for onboarding.
This idea would primarily be used for the "Find me a vulnerability" Randomizer inside the curate tool. However, I would also recommend that a search page would be useful for browsing the different CVEs outside of GitHub.
Inside the curation tool, there should be a place where contributors can search for a vulnerability they can curate.
Items that contributors should filter by (optional filters):
Curation Level: Filter between curations that are new (Lvl 0), work-in-progress (Lvl 1), or finished (Lvl 2+).
Project: Which project(s) does a curator want to work on?
Language: What programing language(s) does a curator want to work with?
Auto-Discovered VCC: If it's a curator's first time, they may want an easier commit. Conversely, they could find a CVE without an auto-discovered VCC and make a large impact..
Difficulty: Direct newer contributors to easier CVEs while moving veterans towards difficult CVEs. This tag is arbitrary but could be useful for onboarding.
This idea would primarily be used for the "Find me a vulnerability" Randomizer inside the curate tool. However, I would also recommend that a search page would be useful for browsing the different CVEs outside of GitHub.