Is your feature request related to a problem? Please describe.
Some way to fetch processed CVEs. This would be helpful for other projects to use the data. For eg at Vulnerablecode for each CVE, we would like to have a reference to vulncode-db's entry for the same CVE, if it has a patch available. This would be helpful for users to see what's wrong at the "code" level, thanks to vulncode-db's ability to render code.
Describe the solution you'd like
Some way to fetch processed CVEs, this could be either via an API or data dump, whichever is more useful and aligning with your goals. IMHO the issue with API approach might be performance/scaling (fetching 3000+ entries is bit heavy)
Describe alternatives you've considered
The data dump approach might help, and I read somewhere that it's on the roadmap.
Additional context
If all goes well, we would get some vulnerablecode -> vulncode-db integration done during this Google summer of code.
Is your feature request related to a problem? Please describe. Some way to fetch processed CVEs. This would be helpful for other projects to use the data. For eg at Vulnerablecode for each CVE, we would like to have a reference to
vulncode-db's entry for the same CVE, if it has a patch available. This would be helpful for users to see what's wrong at the "code" level, thanks tovulncode-db's ability to render code.Describe the solution you'd like Some way to fetch processed CVEs, this could be either via an API or data dump, whichever is more useful and aligning with your goals. IMHO the issue with API approach might be performance/scaling (fetching 3000+ entries is bit heavy)
Describe alternatives you've considered The data dump approach might help, and I read somewhere that it's on the roadmap.
Additional context If all goes well, we would get some
vulnerablecode -> vulncode-dbintegration done during this Google summer of code.