Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

revive review

Free#24 of 33 in Linters

A configurable, open-source Go linter with strong integration and output options.

6.8/10Editor score
Visit revive
revive6.8 Visit revive

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

revive is an open-source command-line linter and static code analysis framework for Go. It suits teams that want configurable policy rules instead of a fixed linting setup, including projects moving from golint. Rules are configured with TOML files, and optional type checking adds another layer of analysis. The tool also supports security rules, custom rules, custom formatters, exclusions, and customizable error and warning exit codes.

Its ecosystem fit is a major strength for Go development workflows. revive provides editor integrations for VS Code, GoLand, and Vim, while GitHub Actions support can add annotations to code changes. Docker distribution supports container-based workflows, and integrations with golangci-lint and MegaLinter make it suitable for teams that manage multiple linters through an aggregator. Output formatters include JSON, Checkstyle, and SARIF, helping teams route findings into different reporting and CI processes.

revive is free and open source, with distribution under the MIT License. Its configurable rules, exclusions at file, directory, package, and rule level, and extensibility make it a strong choice for teams defining detailed Go standards. However, the project supports one language, and automatic fixing is not documented as a feature. Teams that need focused Go analysis, editor support, CI annotations, or custom policy logic should consider revive. Teams seeking broad multi-language coverage or documented automatic remediation should choose a different linter.

revive pros and cons

  • Where it wins
    • TOML configuration supports custom rules, exclusions, and exit codes
    • Outputs include JSON, Checkstyle, SARIF, and other formatters
    • Works with editors, GitHub Actions, Docker, and linter aggregators
  • Where it doesn't
    • Supports Go rather than a broad range of programming languages
    • Automatic fixing is not documented
    • Configuration depth may exceed the needs of simple linting workflows

revive fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update