Hound vs SonarQube: What are the differences?
Developers describe Hound as "A hosted service that comments on Ruby style guide violations in your GitHub pull requests". Take care of pesky code reviews with a trusty Hound. Hound reviews GitHub pull requests for style guide violations. On the other hand, SonarQube is detailed as "Continuous Code Quality". 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.
Hound and SonarQube can be primarily classified as "Code Review" tools.
"Comments on style so I don't have to" is the top reason why over 3 developers like Hound, while over 9 developers mention "Tracks code complexity and smell trends" as the leading cause for choosing SonarQube.
Hound and SonarQube are both open source tools. SonarQube with 3.78K GitHub stars and 1.06K forks on GitHub appears to be more popular than Hound with 1.72K GitHub stars and 393 GitHub forks.
Starbucks, Dial Once, and Policygenius are some of the popular companies that use SonarQube, whereas Hound is used by thoughtbot, Verba, and Edufii. SonarQube has a broader approval, being mentioned in 105 company stacks & 61 developers stacks; compared to Hound, which is listed in 10 company stacks and 3 developer stacks.
What is Hound?
What is SonarQube?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Hound?
What are the cons of using SonarQube?
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
To increase our code quality and make vulnerabilities visible, we added SonarQube to our Git(lab) workflow, so every commit is analyzed and code flaws are shown directly at the Mergerequest.