Codacy is easy to integrate and its new security dashboard provides useful insights into metrics across the company. The support team is really helpful and provides immediate assistance.

From the point of view of a company that processes card transactions and is subject to Compliance/Certifications with card scheme standards, automated code review and detection of security problems is the most useful thing. Codacy helps developers save time in code reviews, so developers can focus on other things. Codacy centralizes customizable code patterns and enforces them within engineering teams so that everyone's code goes through static analysis and is evaluated before being put into production. Easy integration with GitLab. Customer Support is of high quality, responds quickly to inquiries, always helps us as much as possible.

The high number of programming languages that are supported by Codacy helped a lot in our situation, once we had different tech stacks. It was also very easy to integrate with our CI/CD flows, and we are seeing a really cool product roadmap.

I like how Codacy works to build strong partnerships with its customers. I like the focus on developers and the developer experience. I like that Codacy gives me a hassle-free single pane of glass view into code quality across my organization.

The Codacy team follows up and ensures that we are getting the most out of the platform. My team members consider it crucial to the success of our projects. It is quite easy to integrate and does its job without human interaction

Codacy's integration with our 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'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.

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.

Codacy is fantastic! I absolutely love the UI/UX. The great amount of customizations around rules for code review. Great language support. Love the GitHub integrations with statuses. Still fairly new to the test coverage review feature.

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 Request 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.

- 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.

- Easy Integration

- Clean Interface

- Coverage Support

- GitHub integration

- Fast feedback

- Deep C++ static code analysis

- Native integration into the GitHub development cycle

- Quality of results, including a detailed description of the detected issues