Bump golang.org/x/vuln from 1.0.0 to 1.1.4 in /internal/tools

[dependabot]

Bumps golang.org/x/vuln from 1.0.0 to 1.1.4.

Release notes

Sourced from golang.org/x/vuln's releases.

v1.1.4

This release fixes some minor govulncheck bugs (#70157) and introduces performance improvements, saving up to 15% of execution time for large programs in our experiments.

Govulncheck now emits an SBOM message in the JSON output, containing minimal information about the artifacts being scanned. This information is used to communicate a more informative progress message in the textual -show verbose mode.

This release also brings a new feature when scanning binaries. Govulncheck now also checks for known vulnerabilities in the main module of the binary, in addition to transitive dependencies. This is useful when, say, one downloads and wants to check a binary developed in a third-party module that might have its own vulnerabilities.

v1.1.3

This release brings a few bug fixes (#68034, #68256, and #68338) and an increased support for analyzing Go binaries. Binaries built with Go versions prior to go1.18 are now checked, but only for standard library vulnerabilities.

v1.1.2

This release brings the support for the VEX output format.

Integration

Govulncheck now supports OpenVex output format via -format openvex flag option. Please see here for more details on the actual encoding.

v1.1.1

This release brings some minor improvements to govulncheck textual output and performance optimizations for package and module scan modes.

The major change brought by this release is the support for SARIF output format.

Integration

Govulncheck now supports Static Analysis Results Interchange Format (SARIF) output format via -format sarif flag option. Please see here for more details on the actual encoding.

v1.1.0

This release brings minor improvements to govulncheck inner workings and a few bug fixes (#66139, #65590).

Integration

Govulncheck JSON now also contains scan mode as part of the Config message.

Further, the Position in trace frames now contains only paths relative to their enclosing module. This could potentially break some existing clients, hence the bump of the minor version.

Note that this change is made to allow for easier preservation of privacy by the clients as now the file positions do not contain information about the local machine. This is also a portable solution. Clients can reconstruct full paths for their local machine by joining the Position relative paths with paths of the enclosing modules on the local machine.

v1.0.4

This release brings an improved overhaul of the govulncheck textual output. Findings at each detected level of precision (symbol, package, or module) are communicated in their own section.

By default, only the section with the user-specified precision mode is shown followed by a summary of other sections. A detailed description with all of the sections can be obtained using a newly introduced -show verbose option.

This release also brings improvements and fixes for error messages and binaries (#59731).

Integration

govulncheck (streaming) JSON now includes the code position of the vulnerable symbol. Where applicable, the .Position of the last entry of a finding's trace is the code location defining the .Function.

v1.0.3

... (truncated)

Commits

• d1f3801 go.mod: update golang.org/x dependencies
• 681aa92 go.mod: update golang.org/x dependencies
• 58ab492 cmd/govulncheck: remove unnecessary fixups
• e45fa10 cmd/govulncheck: better mask new (sbom) versions
• bf472d2 cmd/govulncheck: mask dirty dependency versions
• 072d4ef cmd/govulncheck: add missing test data
• 0481857 cmd/govulncheck: set gotypesalias=1 when using >=1.23 toolchain
• d0fc691 go.mod: update golang.org/x dependencies
• dba032f internal/sarif: use empty arrays instead of nils
• 47cd072 cmd/govulncheck/testdata: expand set of go versions in fixup
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)