Publisher CVEs: Prefer ECOSYSTEM fixed event
#197
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
toph-allen
approved these changes
Jun 24, 2025
Collaborator
toph-allen
left a comment
toph-allen
left a comment
There was a problem hiding this comment.
Looks good! No comments per se.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a preference to the
publisher-cvesextension to show the latestECOSYSTEMfix version from Posit Package Manager'sGET /repos/{repo}/vulnsAPI endpoint.The
ECOSYSTEMtype range is described as: package ecosystem specific version range.Previously the first
fixedrange version was used which resulted in a Git commit hash version for some vulnerability + package combinations.Deployed on Dogfood here.
Fixes #195