When comparing Codacy vs ccguard, the Slant community recommends Codacy for most people. In the question“What are the best code coverage services?” Codacy is ranked 5th while ccguard is ranked 7th.
Specs
Ranked in these QuestionsQuestion 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.
Pro Your own server, your intellectual property
You don't trust a third party service to host your IP? Host your own server, at no cost (every cloud provider will host your server freely for the first year).
Pro Open source
Pro Distributed references
The code coverage "references" are the previous measurements of code coverage. These references are distributed: all the team members can share the references in the same way they share the source code.
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.
Con Not really user friendly
There is little/no graphical user interface. Everything is done via command line instructions.