search

octomation / go-service

🧩 Template for a typical service written on Go.
https://go-service.octolab.org/
MIT License
7 stars 0 forks source link

tools(deps): bump golang.org/x/vuln from 1.0.1 to 1.1.3 in /tools #292

Open dependabot[bot] opened 1 month ago

dependabot[bot] commented 1 month ago

Bumps golang.org/x/vuln from 1.0.1 to 1.1.3.

Release notes

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

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

The major feature brought by this release is govulncheck -mode extract option. It enables users to extract a blob abstraction of a binary whose size is typically much smaller than the binary itself. The blob can be passed to govulncheck for analysis with the -mode binary option. The users should not rely on the contents or the representation of the blob.

This release also brings several bug fixes (#65124, #65155, and #65130).

v1.0.2

This release brings minor improvements to the govulncheck textual output and fixes for error messages (#59623, #64681), fixed version suggestion (#62276), documentation (e.g., #60166), and issues in dependencies (e.g., #64112).

Support for analyzing stripped darwin binaries in govulncheck is added as well (#61051).

... (truncated)

Commits
  • 4ea4418 internal/openvex: update handler test
  • de0a0ad LICENSE: update per Google Legal
  • 1884dfa internal/vulncheck: add warning message for ancient binaries
  • d9ad522 all: remove build restrictions requiring go1.18
  • 44e45ea cmd/govulncheck: clarify unsafe/reflection limitations
  • 601dd9b cmd/govulncheck: update docs for old Go binaries
  • 0f7005f internal/openvex: omit vulns with no findings
  • f94421b cmd/govulncheck/integration: adjust k8s expectations
  • 684f5c9 all: remove skipIfShort
  • d52dedc all: remove unnecessary test lines for staticcheck
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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)