fix: check if 'type' is in severity for the OSV source #5240
+1
−1
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.
Lately cve-bin-tool runs have been failing due to malformed (or outdated?) schemas in the OSV source. I'm constantly running into either
cve_bin_tool - Unable to fetch OSV CVEs, skipping OSV.
orFull traceback
This aims to work around the issue by checking first for the 'type' key to avoid running in an exception.