Code Climate聽vs聽Phabricator

Get Advice Icon

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

Code Climate
Code Climate

429
296
+ 1
274
Phabricator
Phabricator

172
189
+ 1
174
Add tool

Code Climate vs Phabricator: What are the differences?

Developers describe Code Climate as "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. On the other hand, Phabricator is detailed as "Open Source, Software Development Platform". Phabricator is a collection of open source web applications that help software companies build better software.

Code Climate and Phabricator belong to "Code Review" category of the tech stack.

Some of the features offered by Code Climate are:

  • 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.

On the other hand, Phabricator provides the following key features:

  • reviewing code before it hits master
  • auditing code after it hits master
  • hosting Git/Hg/SVN repositories

"Auto sync with Github" is the top reason why over 68 developers like Code Climate, while over 31 developers mention "Open Source" as the leading cause for choosing Phabricator.

StackShare, Typeform, and thoughtbot are some of the popular companies that use Code Climate, whereas Phabricator is used by Facebook, Dropbox, and Coursera. Code Climate has a broader approval, being mentioned in 144 company stacks & 48 developers stacks; compared to Phabricator, which is listed in 52 company stacks and 12 developer stacks.

- No public GitHub repository available -
- No public GitHub repository available -

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 Phabricator?

Phabricator is a collection of open source web applications that help software companies build better software.
Get Advice Icon

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

Why do developers choose Code Climate?
Why do developers choose Phabricator?

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

    Be the first to leave a con
    What companies use Code Climate?
    What companies use Phabricator?

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

    What tools integrate with Code Climate?
    What tools integrate with Phabricator?

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

    What are some alternatives to Code Climate and Phabricator?
    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
    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.
    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 Code Climate and Phabricator
    Jerome Dalbert
    Jerome Dalbert
    Senior Backend Engineer at StackShare | 5 upvotes 248.9K 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
    Interest over time
    Reviews of Code Climate and Phabricator
    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 Code Climate and Phabricator
    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 Publitory
    Publitory uses Code ClimateCode Climate

    We check our deployments with CodeClimate

    Avatar of Wellzesta
    Wellzesta uses PhabricatorPhabricator

    Wiki, feature backlog.

    How much does Code Climate cost?
    How much does Phabricator cost?
    News about Phabricator
    More news