BUS FACTOR & KEY PERSON RISK

Know what you lose before someone quits.

Mapnostics reads your git history to show who really owns each part of your codebase, and exactly what knowledge walks out the door if they leave.

Analyze my codebase →See how it works
mapnostics.com/repo/acme-platform/bus-factor
Key Person Risk
Who holds the knowledge, and what happens if they leave
Rescan contributors
2

Key people

2 people wrote most of this codebase. If they leave, that knowledge goes with them.

Critical

One person owns more than half of a significant module.

4 contributors·112 files·9,240 attributed lines·scanned 31 Aug 2026, 09:31
Recommended
If dana-okafor leaves, components loses its main author. Schedule a knowledge transfer session for components.
If sam-whitfield leaves, app loses its main author. Schedule a knowledge transfer session for app.
Who owns what
1dana-okaforCritical
Lines owned

47%

4,342 lines

Files owned

43%

48 files

Speciality
componentslibapp
If dana-okafor leaves
components loses its only author66% of its lines
2sam-whitfieldCritical
Lines owned

31%

2,864 lines

Files owned

28%

31 files

Speciality
applibcomponents
If sam-whitfield leaves
app loses its only author55% of its lines
3priya-ramanLow
Lines owned

17%

1,571 lines

Files owned

20%

22 files

Speciality
libapp(root)
4lee-tanakaLow
Lines owned

5%

463 lines

Files owned

10%

11 files

Speciality
appcomponents
✓

Read from real git history

Ownership is computed from actual commits and authorship, not a survey or a guess about who "probably" wrote something.

✓

See what leaves with them

Each key person's card names the specific module they are the only author of, and what percentage of its lines go with them.

✓

A recommendation, not just a number

Every critical finding comes with a concrete next step — who to schedule a knowledge transfer with, and for what.

Find your key person risk in under 2 minutes.

Analyze my codebase →

No credit card required · Free tier available