fix: recognize jvm versions at DB build time #647
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
When processing CPEs in the NVD provider, if a CPE seems to be for a JVM based on its package namme, set its version type to be "jvm" so that grype knows at match time to use special comparison logic for JVM versions. Signed-off-by: Will Murphy <[email protected]>
915f88f to
8cd26bd
Compare
westonsteimel
approved these changes
Aug 22, 2025
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.
When processing CPEs in the NVD provider, if a CPE seems to be for a JVM based on its package namme, set its version type to be "jvm" so that grype knows at match time to use special comparison logic for JVM versions.