Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariCodacy automates code reviews and monitors code quality on every commit and pull request reporting back the impact of every commit or pull request, issues concerning code style, best practices, security, and many others. It monitors changes in code coverage, code duplication and code complexity. Saving developers time in code reviews thus efficiently tackling technical debt. JavaScript, Java, Ruby, Scala, PHP, Python, CoffeeScript and CSS are currently supported. Codacy is static analysis without the hassle.
SpecsUpdate
Question Ranking
Pros
Pro Free for open-source projects
Pro Tons of features, plugins to check code
The list is never ending: they use a lot of open sourced linters for many different languages, allowing to configure them one by one, add custom rules... It checks duplicates, issues, security AND is customizable.
Cons
Con Reports tons of noisy, irrelevant "quality" metrics
You want code coverage, not someone to tell you where to put semicolons in your markdown documents. It spots dozens of "issues" in your code and Markdown sources, none of which are in any way valid, most of which were random opinions from people with no justification and not accepted best practices. (In fairness, on the Python side, this was due largely to Pylint itself being way too prescriptive.)
Con Can't handle combined coverage
When there are multiple environments that contribute coverage to different branches it just picks one at random and says that the rest of the code isn't covered at all.
Con Dashboard causes Safari to freeze, crash
Con API Tokens need to be hard coded
Most CIs have options for that in safe environment variables, but that makes it unavailable in PRs anyways. The support says they're working on it.
Commonly Compared
