aboutcode-org / aboutcode-org/vulnerablecode
Process unstructured data sources, such as issues
- Dominant language
- Python
- Stars
- 702
- Forks
- 328
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 3
Description
These contain valuable data nuggets among an ocean of junk and we need to be able to find the good things there.
Some sources are:
- mailing lists such as:
- https://github.com/nexB/vulnerablecode/issues/100
- https://github.com/nexB/vulnerablecode/issues/104
- https://github.com/nexB/vulnerablecode/issues/108
- changelogs https://github.com/nexB/vulnerablecode/issues/233
- reflogs of commit (see also the commits from vulncodedb and SAP/Eclipse steady KB)
- bug and issue trackers (such as Django, etc)
- actual description of a CVE or the text body of advisories. See https://github.com/nexB/vulnerablecode/issues/551
We can either automate it all, but that's going to be super difficult, or rather start to craft a curation queue and parse as much as we can to make it easy to curate by humans
- https://github.com/nexB/vulnerablecode/issues/218
... and progressively also improve some mini AI and classification to help further automate the work.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.