| commit | 39173892081a8614f56d165c34e7058db5a4c8e1 | [log] [tgz] |
|---|---|---|
| author | Zvonimir Pavlinovic <zpavlinovic@google.com> | Wed Sep 18 14:51:04 2024 +0000 |
| committer | Zvonimir Pavlinovic <zpavlinovic@google.com> | Thu Sep 19 16:28:06 2024 +0000 |
| tree | 5fcaaf4be87bdbcfd9f6cd3a922e62c9b350740d | |
| parent | 6a6005b5785ccb41a363c0da9f72bd262df567d3 [diff] |
internal/scan: reorganize trace text layout in trace mode As paths are relative, it is not immediately evident to what module symbols belong to in traces mode. We hence reorganize things to make that explicit while avoiding clutter. Fixes golang/go#69490 Change-Id: Ic43e22954cbe3ff0ac458f75ee3a07706295fb5d Reviewed-on: https://go-review.googlesource.com/c/vuln/+/614135 Reviewed-by: Maceo Thompson <maceothompson@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.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:
govulncheck ./...
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.
The privacy policy for 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.
Database entries available at https://vuln.go.dev are distributed under the terms of the CC-BY 4.0 license.