Back to using NIST for NVD data #139
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Henri Rosten <[email protected]>
Closed
ktusawrk
approved these changes
Oct 10, 2025
cazfi
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR #129 changed the NVD data source to https://github.com/fkie-cad/nvd-json-data-feeds as a workaround to replace the decommissioned legacy NVD data feeds that vulnix relied on.
However, NVD still provides JSON data feeds in a new 2.0 JSON format. This PR makes vulnix consume the JSON 2.0 feeds from NIST which is the canonical source of the NVD data.
Resolves: #134