Maintainability risk

What it means

Maintainability risk combines signals such as complexity, coupling, churn, ownership concentration, weak tests, and review friction. It is a risk assessment, not one universally defined metric. A useful assessment states which evidence supports it and what future change would expose the risk.

Example

A configuration subsystem has high churn, one owner, deep branching, and few tests. The team rates its maintainability risk as elevated and chooses a small boundary refactor before adding another integration.

Limitations

Risk indicators can conflict, and a stable mature component may be easier to change than a new low-complexity area. Avoid collapsing unrelated signals into one opaque score. Review the assessment with maintainers.

How to use the signal

Record the contributing signals separately so a team can remove a specific burden instead of chasing an opaque risk score.

Weave can help combine repository signals with review duration and rework evidence. Use a documented local rubric and treat Weave as supporting context, not as an automatic risk classifier.