CodeScene stands out by focusing on behavioral code analysis rather than just static rule checks. The hotspot analysis highlights the most critical and frequently changed parts of the system, making it clear where technical debt truly matters. I especially value the GitHub PR integration, where CodeScene posts automated, intelligent review comments — combining code health, test coverage, and change coupling. This ensures that risky changes are caught early, before they reach production. Review collected by and hosted on G2.com.

The platform has a bit of a learning curve, especially for teams unfamiliar with concepts like hotspots or change coupling. The UI, while feature-rich, can feel slightly heavy on very large repositories. Integration with coverage tools like JaCoCo is powerful, but it requires some manual configuration, unlike the plug-and-play model of other tools. Review collected by and hosted on G2.com.

Codescene helps to quickly identify various issues within your codebase, no matter how big it is - I've used it for projects ranging from 500 lines of code to over 4 million. The issues are tangible and actionable, not just "good to know" - you really see the immediate impact of addressing them. Aside from code quality, you can also view things like hidden dependencies (e.g., files that often change together), team knowledge sharing levels, planned vs. unplanned work (when integrated with a PM tool such as Jira), and much more information - all measurable and nicely presented. Easy to define KPIs and quality gates which are easy to integrate and enforced via pull request and CI/CD pipelines. The integration with developer IDE (mainly VSCode) is also extremely useful to catch issues early on and encourage developers to follow the "boy scout rule" when working on existing code. The only reason I didn't give a 10 is because what's lacking for me was support for code coverage - it was recently added to the product, but I have yet to try it out. Review collected by and hosted on G2.com.

It can be a bit overwhelming at first, especially for a large codebase with a large team that does not have clear boundaries or separation. It could take some time to define the team structure and code architecture to really utilize Codescene's full potential (although even without it there is still a lot of value). Review collected by and hosted on G2.com.

I love CodeScene's simplicity and the concrete advice it gives on how to improve. I also appreciate how it anchors suggestions on improving the codebase from literature and well-known development practices. The initial setup was very straightforward, with running the docker locally and pointing it to codebases being very easy. Review collected by and hosted on G2.com.

It was not so easy to understand the portfolio and all the menu navigation. I would love to see more metrics or insights at a glance instead of hidden beneath each menu item. Review collected by and hosted on G2.com.

I like CodeScene's easy setup and how quickly it gives me a really good understanding of our codebase. The documentation is very good, and if I need personal help, they are swift in replying. It's also a very good starting point when I need help configuring the application to suit my specific needs. It's very easy to get going, and I can tweak the settings to better match my requirements. Review collected by and hosted on G2.com.

There is a lot of functionality that I don't use, but that is more related to my, and my company's, use case for CodeScene. Review collected by and hosted on G2.com.

What I appreciate most about CodeScene is how it transforms code analysis into actionable insights. The platform surpasses standard static analysis by identifying hotspots, technical debt, and aspects of team dynamics, which supports engineering teams in making well-informed decisions. Its visualizations are easy to understand, and the recommendations are genuinely useful, making it simpler to prioritize refactoring efforts and enhance code health over time. Additionally, the course content is thoughtfully organized—concise, targeted, and readily applicable to real-world situations. It’s evident that CodeScene is designed with developers’ needs in mind. Review collected by and hosted on G2.com.

While CodeScene offers powerful insights and visualizations, one area that could be improved is the initial onboarding experience. For new users, some of the advanced features and terminology might feel overwhelming without additional context or examples. A more guided walkthrough or interactive tutorials could help users get up to speed faster. Review collected by and hosted on G2.com.

There are multiple quality characteristics (see ISO 25000 or the Heuristic Test Strategy Model) but the Maintainability-characteristic has always been a sore spot for me: Very important but difficult to test. Using Codescene I've gotten an excellent overview of the code health (the code quality so to speak) and helps setting targets.

The Pull Request reviews are especially fantastic and works as an additional senior code reviewer that reviews every piece of code that comes into the main or develop branches for all teams. This feature alone makes it possible for me to guarantee maintainability of all new code up to a certain level. For the pilot team we measured roughly a frequency of a couple of pull request analysis per day for a development team of 6-7 people.

As a Test and Quality manager it is perfect to get an overview and the developers in the teams feel that it helps them produce better code. It also helps teams do better describe the cost benefit of increasing code health/quality by spending time on refactoring certain hotspots, a benefit that can be tricky to explain to stakeholders lacking development expertise.

All in all my expectation on this tool is that the maintenance cost of our development lifecycle will decrease by a substantial degree in the future.

I had to set the server up by myself but the fast deployment using Docker was great. The software also works with common authentication methods which made it easy to connect to the software I wanted it to pull information from.

The customer support has been good, I've had a contact that replied in a quick manner and this helped us delpoy Codescene rahter quickly. Review collected by and hosted on G2.com.

The downsides so far have been few, but there are some features that are difficult to use when you work with an organization where opening firewall ports or working with proxies are a challenge. There is for example an excellent integration with Azure DevOps for automatic code reviews, but if your Azure DevOps instance is on the outside of the network where Codescene is running they cannot connect without proxy or opening a firewall port. This can be handled by using local Azure DevOps agents running that can call the Codescene API, but some features such as counting the number of analyzed PR's are then not activated. Review collected by and hosted on G2.com.

CodeScene's metrics focus on the code quality in terms of reading, understanding and maintaining instead of technical details. It doesn't just analyze the code and aggregate data, it also interprets the data and provides valuable insights. The delta analyses and IDE integrations provide immediate feedback for the developers. The customer support is fast and helpful. Review collected by and hosted on G2.com.

It takes some time to understand the different analyses in depth and dense visualizations (the documentation helps). Sometimes it's not immediately clear how some of the aggregations are calculated. Review collected by and hosted on G2.com.

CodeScene is straightforward to set up and configure, making it easy to get started. The visualizations are excellent, and once you become familiar with navigating the tool, it is a true game changer both for developers prioritizing their work and communicating these priorities to business.

What makes CodeScene stand out in the jungle of solutions, are their dedication to the science behind good code health. I'm confident in the choices they make and the product baseline for code analysis. Review collected by and hosted on G2.com.

The main challenge we face with CodeScene is getting developers to incorporate it into their daily workflow. While there are several shift-left solutions available, such as the CLI and VS Code IDE, the absence of a Visual Studio IDE integration is a significant drawback for our team. We also find the lack of out-of-the-box configurations that integrate seamlessly with our CI/CD tools to be a limitation. Review collected by and hosted on G2.com.

It identifies which hotspot files or modules have been changed by multiple people. This insight helps the team understand where changes are happening and who has tested them. Review collected by and hosted on G2.com.

I haven't encountered any difficulties so far; everything is working well. Review collected by and hosted on G2.com.

Our teams really like the knowledge base feature that has helped us identify the areas where we were missing knowledge after a teams reorganization that changed the people in every team one year ago. The tool helped us identifying the high risk areas and we got the chance to improve our knowledge base in the new teams. Another very useful feature is the code health since we are working on some monoliths and this feature helped us identify the repositories with the worst health of code so that we could fix them right away. Review collected by and hosted on G2.com.

The integration with YouTrack is a new feature and it still needs some improvement to personalize the configuration in order to correctly define what is unplanned work. Review collected by and hosted on G2.com.