Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there any way to use depcheck with NVD data from zipped json instead of the data feed? #7183

Open
shikida opened this issue Nov 22, 2024 · 1 comment
Labels

Comments

@shikida
Copy link

shikida commented Nov 22, 2024

It's just easier to download the NVD data from zipped json files from https://nvd.nist.gov/vuln/data-feeds sometimes.

Is there any option currently to use data from https://nvd.nist.gov/feeds/json/cve/1.1/nvdcve-1.1-modified.json.zip (for example) instead of NVD APIs? (which demands API key)

If not, anyone can point in the source code where I could implement such a change?

thanks

Leo

@aikebah
Copy link
Collaborator

aikebah commented Nov 23, 2024

After version 8.4.3 the switch to the API was made in response to NVD indicating that the datafeeds would soon be dismantled and replaced by the API.

Overall putting some automation to get the API contents populated to a locally cached NVD CVE-db and running ODC (without updating) against that local cache is a more future-proof setup, which would still isolate temporary NVD troubles like the past few days from your build-jobs (only your 'update the cached data job' would be in trouble, all your CI/build jobs would run fine (only lacking new CVEs that cannot also be discovered on other sources than the NVD).

On our (my day-job) build-CI we have one job taking care of updating the CVEdb with NVD data (which is currently frequently and in past intermittently failing). All software builds are re-using this prepopulated database and run in no-update mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants