golangci-lint

What golangci-lint is

golangci-lint is a free, open-source runner for Go linters. It runs linters in parallel, uses caching, accepts YAML configuration, and includes more than a hundred linters. Results can be produced in text, JSON, tab, HTML, Checkstyle, Code Climate, JUnit-XML, TeamCity, and SARIF formats. The documentation lists integrations for GoLand, Visual Studio Code, GNU Emacs, Vim, the Language Server Protocol, and Sublime Text. For continuous integration, the project recommends its GitHub Action and documents integrations for GitLab CI and Buildkite. Installation instructions cover binaries and package managers on Linux, macOS, and Windows, as well as Docker. The FAQ says it supports the two latest minor Go versions, with the further limit that a supported version cannot be newer than the Go version used to compile golangci-lint. The project recommends installing a specific version in CI to help make builds reproducible. It favors binary installation and says several source-oriented installation methods are not guaranteed to work. Default settings are tuned to minimize false positives. The volunteer-built project accepts support through GitHub Sponsors, Open Collective, and Thanks.dev.

Who it suits

It suits Go developers who want to run multiple linters with configurable output and editor or CI integrations. Teams should check the stated Go version limits and installation guidance.

Limits

The FAQ limits support to the two latest minor Go versions, and a supported version cannot be newer than the Go version used to compile golangci-lint.

Getting started

1. Open https://golangci-lint.run/.
2. Choose a documented installation route for Linux, macOS, or Windows, or use Docker.
3. Install the binary or package using the project documentation.
4. Configure the runner with YAML if needed.
5. Connect an editor integration or CI option if useful.

Verdict

golangci-lint brings parallel linting, configuration, and integrations to Go workflows at no listed cost. Check its Go version conditions and use the project’s recommended binary installation approach.