Git-history analysis of Yazi: does this ownership concentration match reality? #4048
SushantVerma7969
started this conversation in
2. Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I've been experimenting with a Git-history analysis tool that tries to infer maintenance risk, ownership concentration, and bus-factor signals from commit history.
I ran it against the Yazi repository and the results were much stronger than I expected.
Some major modules showed:
yazi-parser — 99.5%
yazi-plugin — 96.4%
yazi-core — 95.5%
yazi-fm — 94.9%
yazi-config — 91.4%
The analysis also flagged Bus Factor = 1 across many important areas, suggesting that a very large portion of historical knowledge is concentrated around the same contributor.
Of course, commit history is only a proxy and doesn't necessarily reflect actual maintainership, review activity, design ownership, or who could realistically maintain a subsystem today.
That's what made me curious.
For people familiar with the project:
Do these results roughly match reality?
Are there active contributors whose expertise is not visible from commit history alone?
Which important signals would you consider missing from a history-only analysis?
If you had to estimate the "real" bus factor of Yazi, would it be significantly higher than what the history suggests?
I thought the results were interesting enough to share and I'd love to hear where this kind of analysis is useful and where it becomes misleading.
Thanks!
All reactions