|author||Maceo Thompson <email@example.com>||Thu Aug 24 15:23:21 2023 -0400|
|committer||Maceo Thompson <firstname.lastname@example.org>||Tue Aug 29 17:17:24 2023 +0000|
internal/vulncheck: add LoadModules using go.mod Instead of finding modules via the package imports graph, this uses the go list command to list all dependent modules. This will eventually enable module mode to work as intended (fixing edge cases where if a module was only imported within a test file or a file with a specific build rule, it wouldn't be considered for vulnerabilities in module mode even though it should.) Change-Id: I13944936d5b8df4ecfdef38c8874adcb54b1131d Reviewed-on: https://go-review.googlesource.com/c/vuln/+/522755 Run-TryBot: Maceo Thompson <email@example.com> TryBot-Result: Gopher Robot <firstname.lastname@example.org> Reviewed-by: Zvonimir Pavlinovic <email@example.com>
Go's support for vulnerability management includes tooling for analyzing your codebase and binaries to surface known vulnerabilities in your dependencies. This tooling is backed by the Go vulnerability database, which is curated by the Go security team. Go’s tooling reduces noise in your results by only surfacing vulnerabilities in functions that your code is actually calling.
You can install the latest version of govulncheck using go install
go install golang.org/x/vuln/cmd/govulncheck@latest
Then, run govulncheck inside your module:
See the govulncheck tutorial to get started, and https://go.dev/security/vuln for more information about Go's support for vulnerability management. The API documentation can be found at https://pkg.go.dev/golang.org/x/vuln/scan.
govulncheck can be found at https://vuln.go.dev/privacy.
Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.