|author||Maceo Thompson <email@example.com>||Tue Sep 05 13:47:46 2023 -0400|
|committer||Maceo Thompson <firstname.lastname@example.org>||Tue Sep 05 20:33:27 2023 +0000|
internal/scan: fix trace count bug This change updates the text output for govulncheck to properly count the number of called traces when printing (previously, if there were two findings emitted for the same vuln, one of which was called and one of which wasn't, it would count the uncalled vuln's traces when it shouldn't.) Change-Id: I54d52f8769901177835eb8501dc3f8dce380d882 Reviewed-on: https://go-review.googlesource.com/c/vuln/+/525755 Run-TryBot: Maceo Thompson <email@example.com> TryBot-Result: Gopher Robot <firstname.lastname@example.org> Reviewed-by: Ian Cottrell <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.