I'm an open source project maintainer. Given that I'm already donating thousands of hours of my time on my project, I absolutely love products which offer their tools free to Open Source projects. There are a variety of CI tools available, and no one tool checks every box, but Codacy is one that is really helpful to include. The most helpful feature for me is pull request integration; it notices issues and prompts authors to fix them before I even get a chance to review! It also has the most useful "duplicate detection" algorithms of any of the CI tools I've used, enabling me to refactor and simplify code.

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 affect 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 every time 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.