|author||Maceo Thompson <firstname.lastname@example.org>||Wed Sep 13 12:45:32 2023 -0400|
|committer||Maceo Thompson <email@example.com>||Thu Sep 14 17:21:05 2023 +0000|
internal/scan: update test names Renames the "no vulns" test to more accurately represent what it is testing - which is a case where there is one vulnerability that is only required at a module level but not part of an imported package. Change-Id: Id22c9cf99e5e4f8ea29f73d8743b2f7822ecda33 Reviewed-on: https://go-review.googlesource.com/c/vuln/+/528195 LUCI-TryBot-Result: Go LUCI <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.