Vuls vulnerability database upgrade stability and expansion #1345

iamwlb posted onGitHub

We want to expand on the existing vulnerability database of vuls. But not sure what is the correct way? Can we create our own vulnerability library, and then seamlessly integrate with vuls.
Updating the vulnerability database will be interrupted due to network or other reasons. At this time, do I need to delete the database and update it again? How does vuls ensure data consistency? How to ensure that there will be no duplicate data in the re-update?

Fund this Issue

$0.00

Funded

Only logged in users can fund an issue

Pull requests