RELEASE HIGHLIGHTS
The first big new feature release of 2025 — the first of many!
NEW FEATURE: GIT BRANCH ANALYSIS
Statistics and best-practice visibility across every branch, not just your default one.
This has been in development since the end of 2024, after we spoke to many customers who were struggling to monitor GIT branch usage and practises across their entire organization. They wanted a way to see statistics on how branches are being used, and delve into single branches to see what’s being worked on and whether best practises were being followed.
So far, everything within our platform focused on a single GIT branch — the one users pick when they first sync their code. With this new feature, we now analyze all other branches in your repository and generate statistics on every one, including a focus on branch status.
THE CORE BRANCH STATUSES
Completed branches
merged back into your default branch and not worked on since — they've served their purpose
Stale branches
not complete and haven't been worked on in at least 30 days
Active branches
worked on within the last 30 days
From there we can generate statistics on interesting things like
Authors with the most stale branches
Authors with the most merges
The most stale branches
How many active contributors there are
What your average Time To Merge (TTM) is
What your completion rate is
Most common branch source and most common merge target
And many, many more!
You can also see a full list of all detected branches, and click into each one to see detailed statistics — including our proprietary developer productivity statistics, just for that one branch. We hope you find this data very interesting and get real value out of it.
Branch analysis in the summary and metrics dashboard pages
The dedicated branch statistics dashboard
Viewing the full list of all branches
Viewing a single branch’s productivity metrics
CODE ESCROW RELATED FILES
Free and paid code escrow users can now upload related files.
Users using our Free Code Escrow functionality — or paying users using our “Public Code Escrow Access” feature to give customers access to their escrow vaults — can now upload related files for each vault. This matters because there could be documentation, installation guides, credentials, and more that people need access to alongside the escrowed code.
And for free code escrow users, when you transfer your escrowed code vault, the files get transferred to the new users too.
Managing related escrow files
Viewing and downloading them as a public viewer
OTHER CHANGES
Improvements to Our Team Selection UI
We’ve made adjustments to this part of our UI as we believe it could be clearer what team you’re currently viewing, what other teams you have access to, and what subscriptions those teams have. We’ve tried to make it clearer that every team in The Code Registry has its own subscription and access to platform features.
More Infrastructure Scaling Improvements
Similar to our last release, we continue to monitor our resources and infrastructure, and have made important improvements to our reliability and resource scaling.
BUG FIXES
- Fixed a bug that stopped our code replicator from recovering if it had an error.
- Fixed a bug in our user invite mechanism in some cases.
- Fixed a bug where distribution partner code vault PDF reports didn’t generate automatically.
- Fixed a bug in the security scanner function due to some Azure temporary filesystem issues.
FROM COMPLEXITY TO CLARITY
Move from uncertainty to complete code confidence.
Get the independent intelligence you need to understand, verify and protect your software.
Book a demo