Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
- staticcheck_darwin_386 11.4 MB
- staticcheck_darwin_386.sha256 89 Bytes
- staticcheck_darwin_amd64 13 MB
- staticcheck_darwin_amd64.sha256 91 Bytes
- staticcheck_freebsd_386 11.4 MB
- staticcheck_freebsd_386.sha256 90 Bytes
- staticcheck_freebsd_amd64 13.1 MB
- staticcheck_freebsd_amd64.sha256 92 Bytes
- staticcheck_linux_386 11.5 MB
- staticcheck_linux_386.sha256 88 Bytes
- staticcheck_linux_amd64 13.1 MB
- staticcheck_linux_amd64.sha256 90 Bytes
- staticcheck_windows_386.exe 11.3 MB
- staticcheck_windows_386.exe.sha256 94 Bytes
- staticcheck_windows_amd64.exe 12.9 MB
- staticcheck_windows_amd64.exe.sha256 96 Bytes
- Source code (zip)
- Source code (tar.gz)
Staticcheck 2019.1 makes some major changes to the structure of the tools. Please make sure to read the full changelog before deploying it.
Staticcheck 2017.2.2 fixes minor issues in unused, keyify and staticcheck:
- unused: correctly apply the NoCopy exemption when using the
- keyify: support external test packages (
- staticcheck: disable SA4005 – the check, in its current form, is prone to false positives and will be reimplemented in a future release.
Staticcheck 2017.2.1 fixes a small bug in the detection of deprecated objects, because of course no release can go without bugs!
The (admittedly very short) full changelog:
- Staticcheck 2017.2 made the detection of deprecated objects Go-version aware. Unfortunately, this only worked correctly for fields and methods, but not package-level objects. This release fixes that.
The 2017.2 release of the staticcheck suite of tools focuses on reducing friction – fewer false positives, more tools for suppressing unwanted output, and JSON output for easier integration with other tools.
The full changelog can be found at https://staticcheck.io/changes/2017.2