internal/vulnchec: improve comments and names for imports level logic

Before, we computed module-level information alongside the package-level
one and the names and comments of the related functions reflected that.
These functions are now doing simply computing package-level info so the
comments and names should reflect that as well. This CL fixes that.

Change-Id: I38e8d4575f1274e46f7f1e921549425758819768
Run-TryBot: Zvonimir Pavlinovic <>
Reviewed-by: Maceo Thompson <>
TryBot-Result: Gopher Robot <>
1 file changed
tree: bc599fcd9256485648467a2b6458e01f8d120e2c
  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.