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

Integration

govulncheck (streaming) JSON now emits an OSV message for each vulnerability associated with user modules and its transitive dependencies, regardless of the module version.

As usual, govulncheck emits a module-level Finding if a vulnerability for a module applies to the current module version.

v1.0.1

This release introduces the govulncheck -version flag providing the version information on govulncheck itself and the related environment.

The release also updates dependencies for bug fixes (#62103).

v1.0.0

This release introduces a first stable version of govulncheck providing textual and (streaming) JSON output.