
Codacy
Static analysis and quality gates for engineering teams.
Discover top open-source software, updated regularly with real-world adoption signals.

Automated lint feedback directly in pull‑request reviews.
reviewdog streams linter results into code‑hosting platforms, posting comments, checks, or annotations on changed lines, supporting GitHub, GitLab, Bitbucket and major CI pipelines.
reviewdog bridges the gap between static analysis tools and code‑hosting platforms. By ingesting the output of any linter—through Vim‑style errorformat strings, predefined formats, or the generic RDFormat—it determines which findings intersect the current diff and posts them as review comments, checks, or annotations.
The tool runs in CI environments such as GitHub Actions, GitLab CI, Travis, CircleCI, Bitbucket Pipelines, and Jenkins, as well as locally on a developer’s machine. Installation is straightforward via a curl script, Homebrew, Scoop, or , and a dedicated GitHub Action () automates setup. With built‑in reporters for GitHub PR checks, GitHub PR reviews, GitLab merge‑request discussions, and Bitbucket Code Insights, teams can enforce quality gates without leaving their familiar workflow. reviewdog’s extensible configuration also allows custom reporters, making it adaptable to emerging platforms.
go installreviewdog/action-setupWhen teams consider reviewdog, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
GitHub PR lint enforcement
Automated golint warnings appear as review comments on new code, preventing merges with style violations.
GitLab merge request quality gate
Static analysis tools post discussion threads on changed files, allowing reviewers to address issues before approval.
Bitbucket Pipelines code insights
Security scanner findings are reported as Code Insights, visible in the pipeline summary and pull request.
Local pre‑commit diff check
Developers run reviewdog locally to see linter output only for staged changes, keeping the console clean.
It compares linter output against the diff of the current commit or pull request, posting comments only for lines present in the diff.
Yes. Provide an appropriate errorformat string or use the generic RDFormat to parse the tool’s output.
GitHub Actions, Travis CI, Circle CI, GitLab CI, Bitbucket Pipelines, Jenkins, and generic local execution.
Via a curl install script, Homebrew, Scoop, or `go install`; a GitHub Action also sets up the binary automatically.
No. It only posts comments, checks, or annotations; it never commits changes.
Project at a glance
ActiveLast synced 4 days ago