460
361
+ 1
274

What is Code Climate?

After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots.
Code Climate is a tool in the Code Review category of a tech stack.

Who uses Code Climate?

Companies
182 companies reportedly use Code Climate in their tech stacks, including StackShare, Accenture, and Typeform.

Developers
255 developers on StackShare have stated that they use Code Climate.

Code Climate Integrations

GitHub, Slack, HipChat, Semaphore, and Flowdock are some of the popular tools that integrate with Code Climate. Here's a list of all 8 tools that integrate with Code Climate.
Private Decisions at about Code Climate

Here are some stack decisions, common use cases and reviews by members of with Code Climate in their tech stack.

Shared insights
on
Code ClimateCode Climate

Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file. Code Climate

See more
Riderman De Sousa Barbosa
Riderman De Sousa Barbosa
Front-end Developer | 1 upvotes 0 views
Shared insights
on
Code ClimateCode Climate

Code quality checker. Code Climate

See more
Sascha Manns
Sascha Manns
at bdvb e.V. | 1 upvotes 0 views
Shared insights
on
Code ClimateCode Climate

Codeclimate checks my code and helps me to write better code. Code Climate

See more
Romans Malinovskis
Romans Malinovskis
Shared insights
on
Code ClimateCode Climate

checking our repo code quality. Code Climate

See more
Andrew Gatenby
Andrew Gatenby
R&D Lead Developer at Visualsoft | 1 upvotes 18.9K views
Shared insights
on
Code ClimateCode Climate

We use it as part of CI process to check code quality, to ensure that we're not inadvertently making common mistakes and can keep the smells and scope of code changes in line and clean. Having this step here should make future support and additions much more efficient and easy to understand. Code Climate

See more
Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 11 upvotes 226.1K views

When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.

One of the issues I had with Netlify was I wanted to gzip my JavaScript files, I had this setup in my #Webpack file, however Netlify didn't offer an easy way to set this.

Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the content-encoding of the JavaScript files. - Buddy is also free if you only have a few pipelines, so I didn't need to pay anything 馃馃徎.

When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there code smells, issues, and other issues I've been super happy with it so far, on the free tier so its also free.

I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.

See more
Public Decisions about Code Climate

Here are some stack decisions, common use cases and reviews by companies and developers who chose Code Climate in their tech stack.

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 11 upvotes 226.1K views

When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.

One of the issues I had with Netlify was I wanted to gzip my JavaScript files, I had this setup in my #Webpack file, however Netlify didn't offer an easy way to set this.

Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the content-encoding of the JavaScript files. - Buddy is also free if you only have a few pipelines, so I didn't need to pay anything 馃馃徎.

When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there code smells, issues, and other issues I've been super happy with it so far, on the free tier so its also free.

I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.

See more
Jerome Dalbert
Jerome Dalbert
Senior Backend Engineer at StackShare | 5 upvotes 348K views

The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.

The CircleCI build is a workflow that runs the following jobs:

  • check for security vulnerabilities with Brakeman
  • check code quality with RuboCop
  • run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
  • upload test coverage to Code Climate

Code Climate checks the following:

  • code quality metrics like code complexity
  • test coverage minimum thresholds

The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.

Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git master branch. Code is then ready to deploy!

#ContinuousIntegration

See more
Andrew Gatenby
Andrew Gatenby
R&D Lead Developer at Visualsoft | 1 upvotes 18.9K views
Shared insights
on
Code ClimateCode Climate

We use it as part of CI process to check code quality, to ensure that we're not inadvertently making common mistakes and can keep the smells and scope of code changes in line and clean. Having this step here should make future support and additions much more efficient and easy to understand. Code Climate

See more
Romans Malinovskis
Romans Malinovskis
Shared insights
on
Code ClimateCode Climate

checking our repo code quality. Code Climate

See more
Shared insights
on
Code ClimateCode Climate

Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file. Code Climate

See more

Code Climate's Features

  • Automated Git Updates- Nothing to install. Code Climate runs everytime you push a new commit.
  • Activity Feeds- Up-to-the-minute information so you can see when and how code changes.
  • Instant Notifications- Major security and quality changes pushed to where you work: email, Campfire, HipChat, and RSS feeds.
  • Team Sharing- Instant access for your whole team to maximize code visibility across projects.
  • Hotspots- A hit list for refactoring. Target your messiest areas one-by-one.
  • Duplication Detection- Fuzzy matching algorithm finds DRY-violations that human reviewers might miss.
  • Email Notification- Instant email notifications to let you know when new security and code issues arise
  • Security Dashboard- Organized listing of your app's vulnerabilities, including when they were first introduced and how to address them.
  • Alerts for New Rails Disclosures- Going beyond Gemfile analysis to let you know whether you're at high risk based on how your specific code uses a vulnerable library.
  • Start Fixing with One Click- Full integration with Pivotal Tracker, GitHub Issues, and Lighthouse lets you open tickets instantly.
  • GitHub Integration- Post-receive hooks for instant updates and GitHub drilldown links throughout.
  • Test Coverage Integration- Surfacing coverage information at the repo, class, and source listing level.
  • Private, Safe, and Secure- All data is private by default. SSL encryption everywhere.

Code Climate Alternatives & Comparisons

What are some alternatives to Code Climate?
Codacy
Codacy automates code reviews to improve and standardize code quality across large enterprises. It identifies issues through static code analysis. Integrates with GitLab, GitHub & Bitbucket.
Codecov
Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
Coveralls
Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth.
SonarQube
SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving.
GitPrime
GitPrime uses data from GitHub, GitLab, BitBucket鈥攐r any Git based code repository鈥攖o help engineering leaders move faster, optimize work patterns, and advocate for engineering with concrete data.
See all alternatives

Code Climate's Followers
361 developers follow Code Climate to keep up with related blogs and decisions.
salbertperso
Reinhold Lauer
aledv
Sami Marrekchi
Eliana Ghantous
Edny Bracho
Srinivas Induri
Atish Narlawar
blair womack
Humayun Sohail