How many people understand each part?
1 of 6 modules are close to a single owner
Is there a safety net for changes?
tests run in CI and live in a central test directory; tying them to individual modules would need a coverage run
How much scaffolding did nobody remove?
0 in source, 2 in tests (kept, not work), 0 untouched for 3+ years, 3 external issues to check
Does it build from scratch?
1 gap that makes the build less reproducible (no lockfile)
Is the documentation real?
3 day-one questions are unanswered: how to deploy it; how to restore a backup; where the secrets live and how to rotate them
Who holds the keys?
answered by a person, not by a scanner
Where knowledge is concentrated
Read from who changed what, not from a staffing plan. Contributors are labelled, not named: this is about how knowledge is spread, never about a person.
| Module | Changes | People | Reading |
|---|---|---|---|
.github |
80 | 14 | watch no single owner, but the busiest person made 55% of the changes |
Scaffolding nobody removed
Code written because of an external problem, oldest first, from the source only. A comment in a test that links to an issue is usually the regression test for that bug, so a closed issue there is a reason to keep the test, not to remove it. This project has 2 of those and they are not listed here.
| Untouched | Where | Recorded reason |
|---|---|---|
| No fences found. | ||
The same report, on your own repository
npx ancient-code .
Everything on this page came out of that one command, run against a full clone. It is free and open source, it needs no account, and your code never leaves your machine.