Release highlights
This is a big one! We’ve been hard at work working on the changes in this release which we hope provide real value to our users.
New data analysis – AI Quotient™ (AIQ)
In a World First, you can now use The Code Registry to calculate how much of your code could be improved or enhanced by AI.
This is becoming an important question in the age of AI and we are keen to be at the forefront of how we can help businesses get the most value from AI tools and services.
Our AIQ will scan your codebase for common coding bad practises, structural issues and other problems which we know modern AI coding models are great at fixing, and compare these issues against your entire codebase. And as usual we then show you all of the results we’ve collected for you to browse if you want to dig deeper!
This data has automatically been calculated for all existing code vaults in our system! However, any existing PDF reports won’t contain this new data point, it will only show in new reports!
This is how AIQ looks:
AIQ on the CXO report
AIQ on the metrics dashboard
Dedicated AIQ page
AIQ with Ada
And of course you can ask Ada about your AI Quotient too!
Change “cost to replicate” to show as a range
This change is based on lots of early user feedback where we believe showing a range in the “cost to replicate” display will provide more value than specific dollars and cents.
Other changes
Added full Dart language support to code complexity analyser
Our other facet analysers (security, components etc) already supported Dart but our code complexity analyser did not, so we’ve added a Dart code complexity analyser now to fill in that gap!
Improved infrastructure scaling mechanism
We found that our scaling mechanism for some parts of our infrastructure setup weren’t as responsive as we would like when there was a spike in code vault analysis requests. So we’ve developed a proprietary scaling tool to improve this going forward, meaning for our customers, their analysis runs faster and more accurately.
Change to default code vault replication schedule
Prior to this change the default replication schedule for new vaults was set to monthly on the 1st of each month, at 1am. This didn’t make much sense because if you added a code vault to our platform on the 29th a month, it would automatically replicate again a few days later, and then not replicate for another month (if you didn’t set a custom replication schedule).
This is now changed so that the default replication schedule is monthly, set to 1 month after you originally created the code vault.
Include “lines not analyzed” in code complexity details
Our code complexity analyzer always ignored some files or lines of code based on various rules. For example if they were really simple, or single lines, or configuration files.
This meant there was a discrepancy on the “lines of code” in the code complexity graphs, verses other areas like the language data, which showed a total lines of code irrespective of those same rules.
We’ve now added this data into the charts so it’s clearer.
Bug fixes
- Fixed an issue where the “hide facets from report” code vault setting couldn’t be reset in some cases
- Fixed an issue where in some rare cases the language analyser reported a blank language name
Want to Learn More?
