x/vuln/cmd/govulncheck: surface a "fixed" version when the fix is in a subsequent major version #56206
Labels
FrozenDueToAge
NeedsFix
The path to resolution is known, but the work has not been done.
UX
Issues that involve UXD/UXR input
vulncheck or vulndb
Issues for the x/vuln or x/vulndb repo
Milestone
There are reports with no fixed version in a module, but a fix exists in the next major version. We should find a way to surface this info in govulncheck
Example (https://vuln.go.dev/ID/GO-2022-0386.json):
The text was updated successfully, but these errors were encountered: