Codacy vs Code Climate: What are the differences?
What is Code Climate? Automated Ruby Code Review. 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.
Codacy and Code Climate can be categorized as "Code Review" tools.
Some of the features offered by Codacy are:
- Monitoring of Technical Debt
- Automated Code Review
- New and Fixed Issues per commit
On the other hand, Code Climate provides the following key 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.
"Automated code review" is the primary reason why developers consider Codacy over the competitors, whereas "Auto sync with Github" was stated as the key factor in picking Code Climate.
According to the StackShare community, Code Climate has a broader approval, being mentioned in 144 company stacks & 48 developers stacks; compared to Codacy, which is listed in 44 company stacks and 23 developer stacks.
What is Codacy?
What is Code Climate?
Want advice about which of these to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
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!
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.
Check duplicate code, complexity and common pitfalls. Code coverage indicator for Github README file.
checking our repo code quality.