-
Notifications
You must be signed in to change notification settings - Fork 18.6k
Closed as not planned
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.vulncheck or vulndbIssues for the x/vuln or x/vulndb repoIssues for the x/vuln or x/vulndb repo
Milestone
Description
govulncheck version
Go: go1.24.2
Scanner: govulncheck@v1.0.1
DB: https://vuln.go.dev
DB updated: 2025-04-10 16:27:06 +0000 UTC
Does this issue reproduce at the latest version of golang.org/x/vuln?
According to https://github.com/golang/tools/blob/ce1c5d5963f44e413084a90b6e9011d97ba36888/gopls/go.mod#L15 and https://github.com/golang/tools/blob/ce1c5d5963f44e413084a90b6e9011d97ba36888/gopls/internal/vulncheck/vulntest/report.go#L16
it is using the unmaintained https://github.com/go-yaml/yaml ?
Output of go env in your module/workspace:
issue with source not usageWhat did you do?
look at source
What did you see happen?
gopkg.in/yaml.v3 is used
What did you expect to see?
different yaml package
Metadata
Metadata
Assignees
Labels
NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.vulncheck or vulndbIssues for the x/vuln or x/vulndb repoIssues for the x/vuln or x/vulndb repo