Skip to content


Repository files navigation


Code Climate Test Reporter

Code Climate's test reporter is a binary that works in coordination with to report test coverage data. Once you've set up test coverage reporting you can:

  • view test coverage reports for each file alongside quality metrics like complexity, duplication, and churn,
  • toggle between viewing code issues and test coverage line-by-line in the same source listings,
  • block PRs from being merged if they don't meet your team's standards for test coverage percentage.

Code Climate accepts test coverage data from virtually any location, including locally run tests or your continuous integration (CI) service, and supports a variety of programming languages and test coverage formats, including Ruby, JavaScript, Go, Python, PHP, Java, and more.

For installation instructions, check out our docs on Configuring Test Coverage and Test Coverage Troubleshooting Tips.

To sign up for Code Climate, head here.


The test reporter's current version is documented in VERSIONING/VERSION, following the Semantic Versioning convention.



The test reporter is distributed as a pre-built binary named cc-test-reporter. You can fetch the pre-built binary from the following URLs:


Linux ARM64

Linux netcgo (recommended if you're using a VPN)




$ curl -L -O

Verifying binaries

Along with the binaries you can download a file with a SHA 256 checksum for the given version from the link shown below, or you can attach it to your clipboard from the docs page.

To download the file containing the checksum using curl:


$ curl -L -O

To check that a downloaded file matches the checksum, run it through shasum with a command such as:

$ grep test-reporter-${VERSION}-darwin-amd64  test-reporter-${VERSION}-darwin-amd64.sha256 | shasum -a 256 -c -

The GPG detached signature of SHA checksums can be download analogously from the following url:

You can use it with gpg to verify the integrity of your downloaded checksum. You will first need to import the GPG publick key. To import the key:

$ gpg --keyserver --recv-keys 9BD9E2DD46DA965A537E5B0A5CBF320243B6FD85

Then use the following command to verify the file's signature.

$ gpg --verify test-reporter-${VERSION}-darwin-amd64.sha256.sig test-reporter-${VERSION}-darwin-amd64.sha256


See the LICENSE.