Phabricator vs bitHound

bitHound vs Phabricator: What are the differences?

Developers describe bitHound as "Continuous analysis for Node.js projects. Identify risks and priorities in your dependencies and code". With faster deployment cycles, a hundred competing priorities and tight deadlines to juggle– your team has a lot on their plate. Uncover and focus on the critical issues impacting your team, avoid software pitfalls and ship with confidence. 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.

bitHound and Phabricator can be categorized as "Code Review" tools.

Some of the features offered by bitHound are:

• Do you know when your third party dependencies are at risk? bitHound gives you insight into the insecure, deprecated, outdated and unused packages impacting your software.
• We analyze your code to help your team determine where focus is needed. Understand the mechanical issues impacting your codebase, reduce complexity and clutter, and gain insights that go beyond the command line with bitHound.
• Whether it's formal issue management or the team's pending tech debt, it's important to get on top of these issues. bitHound offers an improved understanding of how the team is performing together and whether or not items are being left behind.

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

"Automatic dependency analysis" is the primary reason why developers consider bitHound over the competitors, whereas "Open Source" was stated as the key factor in picking Phabricator.