Installer golangci-lint avec Homebrew, apk, chocolatey, dnf, MacPorts, Nix, pacman, zypper, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• golangci-lint

Historique du projet

The GitHub repository was created in May 2018. The project grew around a simple premise: run many Go linters together, make the result fast enough for local and CI use, and centralize configuration in `.golangci` files.

By 2019 and 2020 the changelog shows the project adding Go version support, more linters, GitHub Actions output, bash completions, junit-xml output, auto-fixing improvements, and a dedicated website. The May 2020 changelog entry records the launch of `golangci-lint.run`.

The v1 line accumulated a long compatibility history and ended with the project documenting v1.64.2 as the last minor v1 release before v2. The v2 changelog begins in 2025 and introduced product-level changes such as a new `golangci-lint fmt` command and separated v1/v2 changelog documentation.

Historique d'adoption

golangci-lint became a default Go quality gate because it packaged many independent analyzers behind one binary and one config file. Its README advertises installation for local machines and CI/CD systems, and the batch input records packages across apk, Homebrew, Chocolatey, dnf, MacPorts, Nix, pacman, Scoop, winget, and zypper.

The project also maintains an official GitHub Action, listed in GitHub Marketplace, for running golangci-lint and reporting issues in GitHub workflows. The repository had over 19,000 stars and more than 1,500 forks in the 2026 GitHub API snapshot used for this batch.

Modes d'utilisation

The normal package-manager workflow is to install `golangci-lint`, add a `.golangci.yml` or equivalent config to the repository, and run `golangci-lint run` locally or in CI. The project documents integrations for editors and shells as well as CI installation paths.

Its value comes from combining speed and policy. Teams can enable a curated set of linters, cache work between runs, use generated output formats for CI annotations, and keep Go lint rules close to the source tree in a checked-in config file.

Pourquoi les passionnés de paquets s'y intéressent

For package nerds, golangci-lint is one of the canonical Go toolbox binaries: version-sensitive, CI-facing, heavily bottled, and commonly pinned in development environments. It is also a stress test for package ecosystems because it embeds many analyzers whose compatibility tracks Go releases.

It matters culturally because it made Go linting feel like installing one dependable command instead of assembling a personal pile of analyzer binaries. That is exactly the kind of tool Homebrew, Nix, Arch, and CI images tend to converge on.

Chronologie

• 2018: GitHub repository created for a fast Go linters runner.
• 2019: Changelog records Go 1.12 and Go 1.13 support, new linters, junit-xml output, bash completions, and improved auto-fixing.
• 2020: Dedicated website launched at `golangci-lint.run`; GitHub Actions output and additional linters added.
• 2025: v1.64.2 documented as the last minor v1 release before v2.
• 2025: v2 changelog begins with product changes including formatting support and separated v1/v2 documentation.

Related projects

• The official `golangci-lint-action` runs golangci-lint in GitHub Actions.
• golangci-lint wraps and coordinates many Go analyzers, including tools from the Staticcheck and go/analysis ecosystem.
• golangci-lint-langserver and editor integrations adapt the CLI's diagnostics for local development.

Sources

• https://github.com/golangci/golangci-lint
• https://github.com/marketplace/actions/golangci-lint
• https://golangci-lint.run/docs/product/changelog-v1/
• https://golangci-lint.run/docs/product/changelog/
• https://golangci-lint.run/docs/welcome/install/
• https://golangci-lint.run/docs/welcome/integrations/