When comparing Phabricator vs Code Climate, the Slant community recommends Phabricator for most people. In the question“What are the best tools for Ruby code review?” Phabricator is ranked 1st while Code Climate is ranked 2nd. The most important reason people chose Phabricator is:
Phabricator is completely free and open source. It's source code is hosted on [GitHub](https://github.com/phacility/phabricator/).
Ranked in these QuestionsQuestion Ranking
Pro Free and open source
Phabricator is completely free and open source. It's source code is hosted on GitHub.
Pro Actively updated
Phabricator is quickly improving, with bug fixes and new features added often. There is an update to the changelog every couple of weeks.
Pro Bug tracker is included
Includes a bug tracker out of the box. Allows for managing bugs, creating issues, commenting on them and closing them.
Pro Built-in Q&A platform - Ponder
Instead of having to have separate Q&A tool, there's Ponder which takes out the hassle.
Pro Supports the three major version control systems
Support for Git, SVN and Mercurial is available.
Pro Super flexible bussiness rules (Herald)
Pro Able to review graphical asset changes as well as code.
Pro Built-in Wiki and pages support
Pro Code ownership
Users can subscribe to files or even repositories and notifications will be sent when code you are subscribed to is changed.
Pro Command Line Access (via arc)
Pro Able to track design mockups
You can track not only code bud also design mockups.
Pro Built-in voting
You can create voting in an instant and need not to rely on external tools.
Pro Built-in blogging platform
There's a great platform which you can use to post stuff, or use as an internal blog, dev blog, release anouncement place and many others.
Pro Fine grained access control
With using Spaces and Project and custom policies you can have any combination of access to any object inside of your own Phabricator instance.
Pro Built-in Chatrooms
Pro Able to manage legal agreements for open source projects
Pro Designed by software engineers for software engineers
The engineering workflow is far superior to Github style branching and merging. Phabricator separates local representations of the repository from remote, which enables a variety of workflow optimisations, like stacked diffs on a single branch.
Pro Fully customizeable workboard
You can configure your workspace to deal with tasks, bugs, todo's, etc.
Pro Gives code improvement suggestions
Code Climate gives you suggestions on how to improve the code which you can catalog on Jira.
Pro Free for open source
Code Climate is completely free for open source projects.
Pro Integration with team chat software
Code Climate directly integrates with team chat tools like Slack or HipChat.
Pro Shows test code coverage
Code Climate is fully integrated with test coverage statistics and metrics, giving you a complete view and understanding of them.
Con Difficult to configure
Compared to a solution like Bitbucket Server (granted Phabricator offers more options), it is difficult to configure. Settings are scattered everywhere and you must drill down through several screens to find some of them. Documentation is very complete but also not always in parity with the application itself.
Con Mostly for web development languages
Con Repository token must be set manually for open source projects
The other services tend to automatically integrate with CI services like Travis, but Code Climate requires you to copy your repo's token into your CI service's environment.
Con Web interface doesn't show hits per line
Most code coverage services show both what lines of code were run and how many times each line was run, but Code Climate only shows the former.