fedcode-next: Code, UI and models to assign and qualify the weakness exposed by a CVE (or CWE) #1718

Activity

1. pombredanne

   added this to 00-AboutCodePlanneron Jul 22, 2025
2. keshav-space

   self-assigned this

   on Mar 19, 2026
3. keshav-space

   added a parent issue on Mar 19, 2026

   • fedcode-next: Create curation queue for VulnerableCode data enrichment #1726
4. TG1999

   moved this to Needs prep in 00-AboutCodePlanneron Apr 9, 2026
5. keshav-space

   moved this from Needs prep to In progress in 00-AboutCodePlanneron Jul 7, 2026
6. keshav-space commented on Jul 17, 2026

   

   keshav-space

   on Jul 17, 2026

   Member

   More actions

   This is completed in

   • Add support for CWE weakness curation #2380

   The simplest way to try this out is:

   Run the below command after cloning VulnerableCode repo:

    docker compose build
    docker compose up -d

   This will collect the advisories from all the supported source and detect the conflicting weaknesses reported by different source and make it available at http://127.0.0.1:8001/advisories/todos/?issue_type=CONFLICTING_WEAKNESSES where individual conflicts can be curated by humans.

   OR

   Simply visit https://public2.vulnerablecode.io/advisories/todos/?issue_type=CONFLICTING_WEAKNESSES on staging instance.

   Advisory Weakness Curation List

   Advisory Weakness Curation View
7. keshav-space

   closed this as completedon Jul 17, 2026
8. github-project-automation

   moved this from In progress to Done in 00-AboutCodePlanneron Jul 17, 2026
9. pombredanne

   moved this from Done to Reviewed in 00-AboutCodePlanneron Jul 21, 2026
10. pombredanne

    moved this from Reviewed to Validated in 00-AboutCodePlanneron Aug 5, 2026