Code Climate CLI

Code Climate





On macOS, we recommend using Docker for Mac.


docker pull codeclimate/codeclimate


docker run \
  --interactive --tty --rm \
  --volume "$PWD":/code \
  --volume /tmp/cc:/tmp/cc \
  codeclimate/codeclimate help


The above is very transparent. It’s clear what’s happening, and any changes required to work with your specific Docker setup can be discovered easily. That said, it can be unwieldy to invoke such a command on a regular basis.

For this reason, we also provide packages that include a small wrapper script for the above invocation:


brew tap codeclimate/formulae
brew install codeclimate

To update the brew package, use brew update first:

brew update
brew upgrade codeclimate


curl -L | tar xvz
cd codeclimate-* && sudo make install

To upgrade to a newer version, just run those steps again.

Updating existing Code Climate configuration

If you are already using Code Climate and have a .codeclimate.yml file within your repository, you will probably want to run:

codeclimate init --upgrade

This will generate .yml files that will enable CodeClimate CLI to run with the configuration that is automatically generated by Code Climate, ensuring that the output matches between the two.


A list of available commands is accessible by running codeclimate or codeclimate help.

$ codeclimate help

Available commands:
    analyze [-f format] [-e engine(:channel)] [--dev] [path]
    engines:disable <engine_name>
    engines:enable <engine_name>

The following is a brief explanation of each available command.

  • analyze Analyze all relevant files in the current working directory. All engines that are enabled in your .codeclimate.yml file will run, one after another. The -f (or format) argument allows you to set the output format of the analysis (using json, text, or html). The --dev flag lets you run engines not known to the CLI, for example if you’re an engine author developing your own, unreleased image.

You can optionally provide a specific path to analyze. If not provided, the CLI will analyze your entire repository, except for your configured exclude_paths. When you do provide an explicit path to analyze, your configured exclude_paths are ignored, and normally excluded files will be analyzed.

You can also pipe in source in combination with a path to analyze code that is not yet written to disk. This is useful when you want to check if your source code style matches the project’s. This is also a good way to implement integration with an editor to check style on the fly. * console start an interactive session providing access to the classes within the CLI. Useful for engine developers and maintainers. * engines:disable engine_name Changes the engine’s enabled: node to be false in your .codeclimate.yml file. This engine will not be run the next time your project is analyzed. * engines:enable engine_name Installs the specified engine (engine_name). Also changes the engine’s enabled: node to be true in your .codeclimate.yml file. This engine will be run the next time your project is analyzed. * engines:install Compares the list of engines in your .codeclimate.yml file to those that are currently installed, then installs any missing engines. * engines:list Lists all available engines in the Code Climate Docker Hub . * engines:remove engine_name Removes an engine from your .codeclimate.yml file. * help Displays a list of commands that can be passed to the Code Climate CLI. * init Generates a new .codeclimate.yml file in the current working directory. * validate-config Validates the .codeclimate.yml file in the current working directory. * version Displays the current version of the Code Climate CLI.

Environment Variables

  • To run codeclimate in debug mode:
  CODECLIMATE_DEBUG=1 codeclimate analyze

Prints additional information about the analysis steps, including any stderr produced by engines.

  • To increase the amount of time each engine container may run (default 15 min):
  # 30 minutes
  CONTAINER_TIMEOUT_SECONDS=1800 codeclimate analyze
  • You can also configure the default alotted memory with which each engine runs (default is 512,000,000 bytes):
  # 100,000,0000 bytes
  ENGINE_MEMORY_LIMIT_BYTES=1000000000 codeclimate analyze



Related Repositories



Code Climate CLI ...



ApexMetrics - Code Climate engine for Apex ...



:rainbow: Learn how to use CodeClimate to track the quality of your JavaScript/Node.js code. ...



Code Climate Engine for ESLint ...



Code Climate engine for code duplication analysis ...

Top Contributors

pbrisbin GordonDiggs wfleming ABaldwinHunter fhwang dblandin jpignata brynary mrb noahd1 jacooobi BlakeWilliams ivantsepp dbergey ablyler sysadmiral squaresurf diegoamc dread-uo eliotsykes lucasmazza maxjacobson mikz rolandhawk sgerrand


-   v0.37.0 zip tar
-   v0.36.0 zip tar
-   v0.35.2 zip tar
-   v0.35.1 zip tar
-   v0.35.0 zip tar
-   v0.34.1 zip tar
-   v0.34.0 zip tar
-   v0.33.0 zip tar
-   v0.32.1 zip tar
-   v0.32.0 zip tar
-   v0.31.1 zip tar
-   v0.31.0 zip tar
-   v0.30.1 zip tar
-   v0.30.0 zip tar
-   v0.29.0 zip tar
-   v0.28.0 zip tar
-   v0.27.2 zip tar
-   v0.27.1 zip tar
-   v0.27.0 zip tar
-   v0.26.0 zip tar
-   v0.25.1 zip tar
-   v0.25.0 zip tar
-   v0.24.3 zip tar
-   v0.24.2 zip tar
-   v0.24.1 zip tar
-   v0.24.0 zip tar
-   v0.23.0 zip tar
-   v0.22.3 zip tar
-   v0.22.2 zip tar
-   v0.22.1 zip tar