Codacy聽vs聽Code Climate聽vs聽Scrutinizer

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Codacy
Codacy

217
200
+ 1
203
Code Climate
Code Climate

429
296
+ 1
274
Scrutinizer
Scrutinizer

67
44
+ 1
20
- No public GitHub repository available -
- No public GitHub repository available -
- No public GitHub repository available -

What is Codacy?

Codacy is an automated code review tool for Scala, Java, Ruby, JavaScript, PHP, Python, CoffeeScript and CSS. It's continuous static analysis without the hassle. Save time in Code Reviews. Tackle your technical debt

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.

What is Scrutinizer?

Scrutinizer is a continuous inspection platform helping you to create better software.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Codacy?
Why do developers choose Code Climate?
Why do developers choose Scrutinizer?

Sign up to add, upvote and see more prosMake informed product decisions

What companies use Codacy?
What companies use Code Climate?
What companies use Scrutinizer?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Codacy?
What tools integrate with Code Climate?
What tools integrate with Scrutinizer?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Codacy, Code Climate, and Scrutinizer?
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.
Better Code Hub
Better Code Hub runs the first analysis of any GitHub repository with the default configuration. This default configuration is based on the programming languages reported by GitHub and supported by Better Code Hub. Better Code Hub further uses heuristics and commonly used conventions.
Codecov
Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
codebeat
codebeat helps you prioritize issues and identify quick wins. It provides immediate and continuous feedback on complexity and duplication
ESLint
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
See all alternatives
Decisions about Codacy, Code Climate, and Scrutinizer
Jerome Dalbert
Jerome Dalbert
Senior Backend Engineer at StackShare | 5 upvotes 249K views
atStackShareStackShare
GitHub
GitHub
CircleCI
CircleCI
Code Climate
Code Climate
Brakeman
Brakeman
RuboCop
RuboCop
RSpec
RSpec
Rails
Rails
Git
Git
#ContinuousIntegration

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
Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead | 15 upvotes 854.1K views
Codacy
Codacy
SonarQube
SonarQube
React
React
React Router
React Router
React Native
React Native
JavaScript
JavaScript
jQuery
jQuery
jQuery UI
jQuery UI
jQuery Mobile
jQuery Mobile
Bootstrap
Bootstrap
Java
Java
Node.js
Node.js
MySQL
MySQL
Hibernate
Hibernate
Heroku
Heroku
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Solr
Solr
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
Microsoft Azure
Microsoft Azure
Amazon EC2 Container Service
Amazon EC2 Container Service
Apache Maven
Apache Maven
Git
Git
Docker
Docker

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
SonarQube
SonarQube
codebeat
codebeat
Codacy
Codacy

It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.

See more
Interest over time
Reviews of Codacy, Code Climate, and Scrutinizer
Review ofCode ClimateCode Climate

This is one of the key tools I can't leave out when I'm working on a project, basically it is mandatory for me to use it on my Ruby on Rails projects. I think the price is a little expensive for a "Solo plan" but if you can get your client to pay, it's definitely worth it. You or the future developers that will continue with the project will thank you!

How developers use Codacy, Code Climate, and Scrutinizer
Avatar of Andrew Gatenby
Andrew Gatenby uses 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.

Avatar of Stefan Gojan
Stefan Gojan uses Code ClimateCode Climate

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

Avatar of Romans Malinovskis
Romans Malinovskis uses Code ClimateCode Climate

checking our repo code quality.

Avatar of Sascha Manns
Sascha Manns uses Code ClimateCode Climate

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

Avatar of GREGORY NICHOLAS
GREGORY NICHOLAS uses CodacyCodacy

for automated code review, static analysis.

Avatar of Publitory
Publitory uses Code ClimateCode Climate

We check our deployments with CodeClimate

Avatar of scott hutchinson
scott hutchinson uses CodacyCodacy

Real time AI for code reviews

Avatar of InstaGIS
InstaGIS uses CodacyCodacy

Review our code quality

Avatar of Bj枚rn Pfoster
Bj枚rn Pfoster uses ScrutinizerScrutinizer

Easy code analysis tool

Avatar of Dieter Adriaenssens
Dieter Adriaenssens uses ScrutinizerScrutinizer

Verifies code quality

How much does Codacy cost?
How much does Code Climate cost?
How much does Scrutinizer cost?
Pricing unavailable
News about Codacy
More news
News about Scrutinizer
More news