The Code Registry – New release v1.1.5 – 22nd July 2024

Release highlights

This is a fairly large Quality of Life (QoL) release with many fixes, optimisations and other improvements.

New Ada AI capabilities 

Ada can now answer the following questions:

What’s changed since the last replication / code sync?

This is a question that can only be asked at the single code vault level (not at the overall project level).

This is a simple yet powerful question. Let’s say you have code replication set to replicate and analyze your code once per month. With this simple question Ada will review everything that’s changed between the last code replication and the latest one, and summarise it in an easy to understand answer.

Ada’s answer to this question reviews:

  • Lines of code added
  • Total code source size (in MB)
  • Language changes
  • File type changes
  • Open source component changes (components added, removed and versions changed)
  • Code complexity changes
  • AIQ (code quality) changes, including a summary of what issue types were increased or decreased
  • Security issue changes, including new security issue types detected or no longer detected
  • GIT changes (how many contributors, new contributors, what contributors have made new changes, examples of recent change messages)
  • “Cost to Replicate” valuation changes

Time needed for Ada to give you this answer: about 5 seconds!

How long would it take you to gather this data yourself?

Who’s made code changes with security issues?

This is a very interesting question which compares changes made by code contributors with detected security vulnerabilities.

If a developer has been working on a file with detected security vulnerabilities, Ada will flag them in the response.

This disclaimer is included and is important!

“Please note that this information is based on file paths and may not be 100% accurate. It provides an approximation of the code contributors who have made changes in areas with potential security vulnerabilities.”

This data doesn’t mean that these code contributors caused the detected issues, but it could be used to start a conversation with that code contributor, or a deeper dive into the code changed and the detected issue and how / if they are related.

Other changes

Refactored the mechanism used to load project / vault data whilst it’s still being analysed

When you add a project / vault to our platform and you’re waiting for it to be analysed, you see the various widgets and facets of data with a loading animation, which checks for the results every little while and updates the page with the data once it’s ready.

This needed to be optimised as we scale and this is now done. This functionality is now smoother, more optimal and uses less resources behind the scenes.

Improvements to our new user onboarding process 

We’ve made the following improvement to our onboarding process for new users to make the experience better:

  • Options to set your user’s name and team name
  • Field values are saved in case you need to continue later
  • Start with an empty project, if you need to come back after getting your code source detailed
  • The connections to GitHub and GitLab using our native integrations now return you back to the exact same page and onboarding section to continue exactly where you were (previously you had to connect to GitHub / GitLab from your team settings page)

Simplifying the subscription cancellation process 

There is a new cancellation form in the team billing area to simply submit your cancellation request and cancel your subscription.

Dynamic homepage layout for displaying more projects 

The main app homepage is now dynamic – if you have more than 10 projects they will now display in a more traditional table format to make it easier to find the project you’re looking for. If you have more than 20 projects there is also a project search function.

Bug fixes

  • Fixed a bug in the team settings functionality, where in some cases a team member would receive an automated email PDF report for a project they didn’t have access to
  • Similar to above, fixed an issue where a team member could receive emails relating to “broken code source credentials” for a project they don’t have access to
  • Fixed a bug where the number of projects / vaults a team member has access to could be inaccurate in some cases
  • Fixed a bug in the main app navigation where the “add code vault” button would sometimes not show for a project with many code vaults

Want to Learn More?

Our simple sign-up process takes less than 5 minutes, once we’ve replicated your code and created your dedicated IP Code Vault you’ll be able to start understanding more about your code immediately! Why not book a non obligation demo today to see our platform in action.