Need help with gerritstats?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

168 Stars 49 Forks MIT License 244 Commits 25 Opened issues


Tool for creating statistics from a Gerrit repository

Services available


Need anything else?

Contributors list

# 299,957
211 commits
# 22,558
11 commits
# 623,236
5 commits
# 155,958
2 commits
# 240,090
1 commit
# 763,505
1 commit


TL;DR: This tool is unmaintained.

If you need a GitHub version of this tool, go to .

I originally built this tool in my spare time while working for Nokia, my former employer. Gerrit is an awesome code review tool, but I have not used Gerrit at work for several years.

I rewrote GerritStats in early 2021 so it works for GitHub - . Its initial version does not have support for Gerrit, but it's designed in a way that it's easy to extend to include support for Gerrit's REST API. A bit of TypeScript needs to be written to make the data loading and analysis for Gerrit analysis and connectivity work. PRs very much accepted!


This project provides tools to display statistics from a Gerrit repository. It generates output in HTML format.

The tool can be useful for analysing how efficiently code reviews are implemented in an organization, and what kind of virtual teams are formed in the review process.

The tool will generate a set of HTML files that include graphs and charts, such as a proximity graph of the developers, based on how many review comments they write to each other, as well as a per-developer page that lists all their review comments and links back to the reviews.

There are two separate command-line tools:

  • GerritDownloader, which downloads JSON data from the server
  • GerritStats, which parses the json output provided by GerritDownloader, and generates HTML output.


A demo of the resulting HTML output is available at:

How to build

The tool should work fine on OS X and Linux. Windows is not supported; if it works, it's not intended.

Java 8 is required.

# Prerequisite: if using OS X, install brew from

brew install npm # or, if not using OS X, install npm some other way

./gradlew assemble

How to execute


Lists all command line options for the data download tool.


Lists all command line options for the statistics generator.

How to execute: saving data locally

Fetching data from Gerrit can take a while. Use GerritDownloader to get the JSON output from the server so that you can parse it later:

./ --server gerrit.instance.on.inter.nets --project YourProjectName --limit 7500 --output-dir gerrit_out/

The above command will download all data from the given Gerrit server and given project, and store the data in .json format in the given output directory.

If you have multiple projects in Gerrit and want to take a look at all the data, omit the --project argument. This will download data for all projects you have access to:

./ --server gerrit.instance.on.inter.nets --output-dir gerrit_out/

How to execute

Once you have the data, generate HTML output like so:

./ -f gerrit_out/

You can also pass several other arguments, like pointing to a specific file, or including only a subset of developers.

./ --file gerrit-json-out.txt --branches master --include [email protected],[email protected],[email protected] --list-commits-exceeding-patch-set-count 5

How to develop the UI

  1. ./gradlew assemble (or use e.g. IntelliJ to build)
  2. cd GerritStats && npm run generateData -- -f yourdatafile.json
  3. npm run webpack-watch
  4. Open the output in GerritStats/out-html and start development.


A fully functional demo can be found at but there are some screenshots below that illustrate what this tool provides.

The index page will provide you with a sortable overview table of some of the core statistics:

Overview table of all developers

In the overview page, you can also uncheck some users, like bots, so that they're excluded from the analysis.

The index page also contains a graph that illustrates how developers are connected to each other:

Proximity graph for the given branch and given set of identities

The Profile page contains detailed information about the selected user. Apart from some basic numbers also visible on the overview, there's several charts and graphs, illustrating how reviews are done by and for this person.

There's a chart and a table showing who this user adds as a reviewer, and how often they approve the changes:

A chart and table showing who this user adds as a reviewer, and how often they approve the changes

A team graph, centered around this user, shows with whom the reviews are done with, and how strong the relations between others in the team are:

Proximity graph around this user that displays only the users this person does reviews with

A per-day chart of the number of reviews done by this user.

There's a chart showing cumulative statistics of commits, and how many comments were written or received over time:

Cumulative statistics chart of commits, and comments written/received

There's also a chart that shows commits in which the user iterated, got reviews, and iterated some more - a highly time-consuming activity for all parties:

A timeline illustrating highly iterative commits where reviewers were involved

Apart from these, there's many other bits of data being shown, so take a look at the demo app linked above!

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.