Code ownership concentration

What it means

Code ownership concentration describes how work is distributed across authors or reviewers for a repository area. High concentration may reflect expertise or a bottleneck. A healthy interpretation distinguishes intentional ownership from single points of failure and considers onboarding, documentation, and review capacity.

Example

A deployment package receives 90 percent of its changes from one engineer. The team pairs another maintainer, documents the release path, and watches whether review wait time decreases.

Limitations

Concentration measures can misrepresent pair work, bots, generated commits, or teams that share one service account. Broadening ownership without preserving expertise can increase risk. Define the population and time window.

How to use the signal

Compare contributor concentration with reviewer availability and operational responsibility before broadening or changing ownership.

Weave can help connect ownership concentration to reviewer load, queue time, and delivery resilience. Use repository permissions and contribution history for the calculation; Weave provides context about workflow effects.