git history diagnostics
Understand a codebase
through its history
Paste any public GitHub repository. Wayfinder answers three questions a new contributor or maintainer actually cares about — when it got harder to work in, what nobody is maintaining, and what to read first.
Try:
01
When did this codebase get harder to work in?
We sample commits across history, score complexity and coupling at each one, and flag the specific commit ranges where they jumped — not just a graph to eyeball.
02
What has nobody looking after it anymore?
We find files that used to have one dominant owner and now sit untouched — bus-factor and ownership-decay risk, ranked by how long they've been neglected.
03
What order should I read the files in?
We rank the codebase by AI-assessed importance — the files that form the heart of the system first — with import count breaking ties, each with a one-line reason.