Codacy's integration with our continuous integration and continuous delivery workflow (CICD ) and with third party technologies like Slack , provides us with real time notifications on our code either as pull request commands or as Slack comments , ensuring that we avoid critical code vulnerabilities, that potentially affects our developed software. Codacy makes configuration of code analysis rules , to be saved as configuration files . The major benefit of this , is that we are able to tweak our code analysis rules to future needs, by simply editing the saved configuration file documentation as against configuring the entire Codacy setup from scratch everytime we need it for a new project.

I have used Codacy for various projects, both in closed and open source development. I found Codacy to be a very flexible tool for ensuring common coding standards and detecting possible code issues early. - Support for a large variety of programming and markup languages. Even medium-sized projects quickly use a multitude of languages. For example, in addition to the project's primary programming languages, there might be parts written in, e.g., C or JavaScript; the build makes use of Makefiles or shell scripts; the configuration is provided in XML or JSON; infrastructure is configured with Docker and Terraform etc. Codacy allows me to monitor code quality for all these parts of an application in one place. - Flexible configuration by using configuration files. While you can also configure the tools in the Codacy UI, it allows you to have the rules for code analysis saved in configuration files as part of the analyzed project. That enables the team to easily adjust the rules to their needs while having the configuration versions controlled and documented. - Integration into your CI workflow: I have used Codacy with both GitHub and Gitlab. The integration into the CI process gives instant feedback to developers and allows the team to ensure that only validated code makes it into the project.

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.