Qualimetry Qualimetry Enterprise
SDLC health

The health of how your teams build and ship

Beyond code quality, Qualimetry measures the health of repository management across the delivery lifecycle: which repositories are active or stale, where change concentrates, how pull requests flow and how quickly work reaches production.

Book a Demo See Enterprise Reporting
Repositories and branches

See what is active, and what has gone stale

Qualimetry shows which repositories are in scope, which are actively changing, and which branches have gone quiet, so nothing drifts out of view.

  • Repositories in scope across the estate, in one place.
  • Active versus stale so you can see where work is really happening.
  • Branch age that surfaces long-lived branches before they diverge.
app.qualimetry.io/analytics/repositories
Repositories and branches
Repositories and branches: active, stale and in-scope across the estate.
app.qualimetry.io/analytics/code-churn
Code churn
Line churn, rework and knowledge spread, with key-person risk.
Churn and knowledge

Find where change and knowledge concentrate

Line churn and rework show where code is being reworked, while a bus-factor view highlights single-owner files and key-person risk, read as team health rather than a judgement of individuals.

  • Line churn and rework that reveal where change concentrates.
  • Knowledge spread across the people touching each area.
  • Key-person risk where a single owner holds too much.
Pull-request flow

Understand how pull requests move

See merges, open and stale pull requests, merge lead time and throughput, alongside review load and the balance of bot versus human activity.

  • Merge lead time and throughput from open to merge.
  • Open and stale pull requests that need attention.
  • Review load and bot versus human activity across the flow.
app.qualimetry.io/analytics/pr-workflow
PR workflow
Merges, open and stale PRs, merge lead time and review load.
app.qualimetry.io/analytics/delivery-health
Delivery health
Promotion lead time and cadence, and drift between development and live.
Delivery flow

Measure how quickly work reaches production

Promotion lead time and cadence show how quickly work moves toward release, while the drift between development and live branches shows how far apart they have grown.

  • Promotion lead time from development toward production.
  • Release cadence that shows how regularly work ships.
  • Development to live drift between branches over time.
One estate view

Repository health across every team

Active vs stale
repositories
Key-person
risk
Merge lead
time
Delivery
flow
Questions

SDLC health, answered

What is key-person risk?
It is a measure of how much knowledge is concentrated in single owners: files or areas that only one person has worked on. Qualimetry shows it as a risk to plan around, not a ranking of individuals.
What is merge lead time?
It is the time from when a pull request is opened to when it is merged. Tracked across the estate, it shows how quickly review and integration are happening.
Does it cover all our repositories?
It covers the repositories onboarded to Qualimetry. As you bring more repositories into scope, they appear in the same active, stale and health views alongside the rest of the estate.
Where does the data come from?
It comes from your source control activity: repositories, branches, commits and pull requests. Qualimetry reads that activity and turns it into the health and flow measures shown here.

See how your teams really ship

Book a demo to see repository and delivery health across a real estate.

Book a Demo