ROX-32269: migrate to 2.0 NVD API #48
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
BradLugo
reviewed
Dec 12, 2025
BradLugo
approved these changes
Dec 12, 2025
Contributor
BradLugo
left a comment
BradLugo
left a comment
There was a problem hiding this comment.
Approved with some minor optional improvements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Fixes the croncheck CI job - it has been skipping all vulns since migration to the NVD 2.0 API
This PR adjusts reading of the NVD API response to support 2.0 data - and also adds support for optionally using an NVD API Key to speed up requests rates.
CI failing is expected because there are 31 vulns that have been missed over the years - we can address that in followup PR as needed.