Codacy Reviews & Product Details

We have been using Codacy for the past few years for the https://github.com/apereo/cas project with much success. The Github integration is very easy, and there are excellent instructions on how to set up the pipeline with Github Actions. Codacy has fantastic support for coverage tools specifically for Java projects, such as Jacoco. The results are accurately explained and shown on the Codacy dashboard, and there are a lot of configuration settings that would allow one to customize the coverage data and analysis to assist with better code quality. The UI is intuitive, and Codacy comes with a lot of customizable built-in patterns, recommendations and security checks that help spot issues and fix issues. We also take advantage of metrics on duplication and complexity to identify areas that need attention for all developers and contributors to the project as PRs get submitted and merged. Codacy is also free for Open Source projects, which is something we very much appreciate. Review collected by and hosted on G2.com.

For a Java-based project such as https://github.com/apereo/cas, I think the integration could use a few improvements:

1. It seems like Codacy does not support or recognize Lombok. As a result, many quality recommendations turn out to be inapplicable.

2. It could be excellent if Codacy could recognize one's Checkstyle rules and exclude or include certain rules accordingly.

3. Not sure if a developer can run the code analysis tool locally before submitting a PR or a commit. This makes the review process easier since the Codacy feedback sometimes can be overwhelming. Review collected by and hosted on G2.com.

I use codacy in my open source projects, and helps me a lot reviewing all the pull requests. I can see if there are some issues that could lead to errors, or some duplicated code that needs to be refactored. The integration with GitHub is one of my favorite feature, since the pull requests errors can be seen directly on the line of code. From their website you can also ignore some files or directories that doesn't need checks, like tests or demo projects, or anything that is not production and can have issues. Review collected by and hosted on G2.com.

Something that required me some time to understand how it works it's the Code Pattern settings page, there are a lot of tools for checking the code, and understanding all the options is not always clear, but once configured. I had hard times migrating from TSLint to ESLint, since some rules were different, and I don't remember any migration tool. Anyway, once set up it works perfectly. Something's missing is a monorepo support, I have different ESLint configurations between all the packages, and you have to find your minimum common rules to set on the Code Pattern settings page, to avoid more issues than expected. Review collected by and hosted on G2.com.

- Deep C++ static code analysis

- Native integration into the GitHub development cycle

- Quality of results, including a detailed description of the detected issues Review collected by and hosted on G2.com.

Sometimes the detected issues do not apply to our codebase, and it could be easier to just ignore them in the future. I understand that the topic is difficult, so this is just a "nice to have" rather than too big criticism. Review collected by and hosted on G2.com.

- Easy integration as part of your development flow, including this tool on the PRs check and aligning everyone on the team to the defined code quality standards.

- Simple sharing of existing static code configuration between the project and the platform allows you to keep only one source of truth.

- Dashboard and monitoring make it easy to visualize and track the tech debt and all quality standards from one place.

- Reduce the time on the code reviews, important for large teams and not only. Allowing engineers to focus completely on the logic, edge cases, architecture decisions rather than code style, code duplication, issues, etc...

- Self-hosted solution, is especially important for large companies where the source code needs to complain about internal security standards.

- BONUS: Company principles, by supporting open-source projects and startups. Definitely, something that large companies should take note of. Review collected by and hosted on G2.com.

- No SOC2 certification, it may be something important if your organisation have some security standards about third parties, but possible to address it by using a self-hosted solution. Unfortunately, this makes the integration a bit more difficult. Apparently, they are working on getting it (roadmap https://roadmap.codacy.com/c/74-soc2-compliance). Review collected by and hosted on G2.com.

C++ is a complex language that is easy to use in the wrong way. The integration of Codacy into our CI setup on Github ensures that our quality requirements are checked on every pull request. This ensures the high quality of our codebase. Review collected by and hosted on G2.com.

We'd like to see more tools on Codacy that target C++. Otherwise we have no remarks are very happy with what is available. Review collected by and hosted on G2.com.

As an author of an open-source product, it is very important to check the quality of the code, and he can help us quickly know the bad taste of the code. Review collected by and hosted on G2.com.

No， I think it has been perfect and I have recommended all my community friends and open-source authors to use it. Review collected by and hosted on G2.com.

Codacy is simple to integrate with our typical workflow on GitHub while being pleasantly unobtrusive in everyday work. It makes itself noticed when appropriate but doesn't require any attention otherwise. Review collected by and hosted on G2.com.

Ignoring antipatterns on a per-file basis doesn't seem to be possible. We use this feature with a different static code analyzer. Review collected by and hosted on G2.com.

- Easy Integration

- Clean Interface

- Coverage Support

- GitHub integration

- Fast feedback Review collected by and hosted on G2.com.

- No detailed Coverage statistics with graph

- Main Screen shows the issues with percentage, hard to see improvements in graph in big projects Review collected by and hosted on G2.com.

- The integration of codacy with a new code base is quick and easy

- The graphs showing the evolution of the issues/coverage are easy to understand and give a good overview thanks to the guidelines shown

- The integration with github is simple and means that most developers do not need to know about yet another tool in order to benefit from it Review collected by and hosted on G2.com.

- The complexity metric is pretty opaque. I'm not sure what it shows

- The logs are meaningless Review collected by and hosted on G2.com.

It's automatic, with like zero config to be functionnal. Review collected by and hosted on G2.com.

Sometimes obscur to understand why this line do not pass validations. Review collected by and hosted on G2.com.