We’re proud to announce a new release of CodeScene, version 4.1!


This release expands on the features from CodeScene 4.0, and includes several improvements to scale the UI to ultra-large codebases. We also provide new options for integrating more complex life cycles via Jira and GitHub issues, as well as direct support for GitHub Checks as a quality gate. Finally, CodeScene 4.1 also supports a new deployment option that lets you host CodeScene’s database in a SQL Server of your choice.




New Features


  • Automated integration with GitHub Checks: In addition to our existing support for automated comments on pull requests, we now also offers a GitHub checks integration for CodeScene. This is a natural integration that lets you use CodeScene as a quality gate to keep track of hotspots and goals:



CodeScene’s quality gate triggers in a GitHub check on code health decline.


  • Support a standalone SQL Server: CodeScene’s comes with its own embedded database out of the box. However, for larger organizations, integrating with an external SQL server might simplify backups and disaster recoveries. With the new CodeScene you can chose the option that works best for you.

  • Integrate cost and defect statistics from GitHub issues: CodeScene now integrates with GitHub issues to deliver the same functionality as the previous Jira/Trello/Azure DevOps integrations: put costs on your hotspots, and visualize defect densities and trends.



CodeScene integrates with GitHub issues to visualize defect densities, as well as providing defect and cost trends.


  • Add the Code Health details to each hotspots in the REST API: Access detailed information about each hotspot via the REST API. This lets you export the CodeScene data into custom dashboards.

  • Full Code Health support for EcmaScript Modules: Full support for .mjs files, common in the React ecosystem.

  • Support for exporting the project configuration via the REST API.

  • New analysis of knowledge distribution: A high portion of code written by a smaller group of people might be a risk. When a core developer leaves, the lower system mastery makes it more risky to maintain the system. Using the new Knowledge Risk view lets you reason about knowledge distribution pro-actively based on data.

  • Support advanced cost models with multiple Jira/Trello/Azure boards: Integrate data from multiple boards and workflows, each one supporting separate issue types and life-cycles.




Improvements and Bug Fixes


  • Interactive search and filtering of the hotspot and social maps.
  • Improve the absence of expected change warning in the delta analysis by specifying the co-changing files.
  • Adapt the code review comments for Azure integrations.
  • Map commits to issues via GitHub and Azure DevOps pull requests.
  • Allow concurrent delta analysis requests to the same local repository.
  • Improved delta feedback for changed brain methods.
  • Improved supervision of new code, e.g. Rising Hotspots.
  • Consistent rules for author experience in multi-repository projects.
  • Introduce a sliding window for the team analyses.
  • Add support for PR:s from forks to GitHub webhooks.
  • Minor bug fixes and improvements.




We hope you will enjoy these new features as much as we do! Remember that you can read more about CodeScene here.