Code Climate vs. RuboCop vs. Scrutinizer
|
|
|
||||||
Code Climate |
RuboCop |
Scrutinizer |
||||||
Favorites35
|
Favorites7
|
Favorites3
|
||||||
Hacker News, Reddit, Stack Overflow Stats |
||||||||
GitHub Stats |
No public GitHub repository stats available
|
No public GitHub repository stats available
|
||||||
Description |
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 RuboCop?RuboCop is a Ruby static code analyzer. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide.
|
What is Scrutinizer?Scrutinizer is a continuous inspection platform helping you to create better software.
|
|||||
Pros about this tool |
|
|
|
|||||
Cons about this tool |
|
|
|
|||||
Pricing |
|
|||||||
Companies |
132 Companies Using Code Climate
|
30 Companies Using RuboCop
|
16 Companies Using Scrutinizer
|
|||||
Integrations |
Code Climate
Integrations
|
RuboCop
Integrations
|
Scrutinizer
Integrations
|
|||||
Latest News |
Launching Today: Velocity
February 07, 2018
New: Golang is here! 🏁
December 20, 2017
Filter issues by source and language 🔍
December 18, 2017
|
Find & Fix all RuboCop Inspections in one go
December 14, 2017
|
Reviews of Code Climate, RuboCop, and Scrutinizer
Once you know it you cannot stop using it.
February 04, 2014 03:58
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 Code Climate vs RuboCop vs Scrutinizer
hoschi uses Code Climate
Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file.
andrewgatenby uses Code 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.
