Update go-cve-dictionary submodule about vulncode-db HOT 3 CLOSED

Hi Shivam,

Thanks a lot for raising this! I've just tried to reproduce this but for me it seems to work:

# Gopkg.lock is out of sync with Gopkg.toml and project imports:
github.com/pkg/errors: imported or required, but missing from Gopkg.lock's input-imports

Root project is "github.com/kotakanbe/go-cve-dictionary"
 13 transitively valid internal packages
 21 external packages imported from 15 projects
(0)   ✓ select (root)
(1)	? attempt github.com/asaskevich/govalidator with 1 pkgs; at least 1 versions to try
(1)	    try github.com/asaskevich/govalidator@v9
(1)	✓ select github.com/asaskevich/govalidator@v9 w/1 pkgs
(2)	? attempt github.com/cheggaaa/pb with 1 pkgs; at least 1 versions to try
[...]

as you can see Docker keeps building the container from the image successfully.

Having said that I want to update the go-cve-dictionary dependency in any case but it can lead to some other issues down the line in regard to an unexpected database layout. Particularly, the database layout provided by go-cve-dictionary needs to be consistent with the data Vulncode-DB expects. I'll investigate any potential mismatches and check how complex it would be to update this soon.

from vulncode-db.

Fortunately, only minor changes were required to update this :).
This has now been resolved with a6505c6.

from vulncode-db.

@evonide thanks for the super fast reply. I tried the old version again and that's working fine, probably the issue was caused due to my network connection. So feel free to close this.

FWIW https://github.com/kotakanbe/go-cve-dictionary/blob/5fe52611f0b8dff9f95374d9cd7bdb23cc5fc67a/models/models.go hasn't been changed since last 2 years so on the models side it should be fine. Atleast my VulnCode-db fork with latest go-cve-dictionary worked fine, but again I am not done with exploring all the goodies :)

from vulncode-db.