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

Change-Id: I54d52f8769901177835eb8501dc3f8dce380d882
Run-TryBot: Maceo Thompson <>
TryBot-Result: Gopher Robot <>
Reviewed-by: Ian Cottrell <>
3 files changed
tree: faa5cdd1689d57eb2631bebc64be096edd0275dc
  1. cmd/
  2. devtools/
  3. doc/
  4. internal/
  5. scan/
  6. .gitignore
  7. all_test.go
  8. checks.bash
  10. go.mod
  11. go.sum

Go Vulnerability Management

Go Reference

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

Then, run govulncheck inside your module:

govulncheck ./...

See the govulncheck tutorial to get started, and for more information about Go's support for vulnerability management. The API documentation can be found at

Privacy Policy

The privacy policy for govulncheck can be found at


Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.

Database entries available at are distributed under the terms of the CC-BY 4.0 license.