Find the code only one person understands.
Depth estimates it from your git history in an hour, then checks it with two-minute questions after every merge.
44 of React's 45 modules have a bus factor under two.
- Bus factor
- 2+ (1)
- 1 (27)
- 0 (17)
High ground is understood by two or more people; what no active author understands is under water. Estimated from react/react's full git history: 19,035 commits, May 2013 to Oct 2026, counting people with a commit in the last six months. Bus factor as defined by Avelino et al. (2016).
Every merge raises the ground.
Git history is a guess about who understands what. Explain-backs turn the guess into evidence, one change at a time.
A change merges.
Merged #482
Retry bank timeouts
priya · payments/retry · +184 −62
Its author answers two questions.
Predict · about a minute
If the bank times out three times in a row, what happens to the order?
It stops and flags it for review. One idempotency key across attempts, so no double charge.
Solid. The idempotency key is exactly what prevents it.
The module rises.
Two minutes, in Depth or in Slack, and any question can be skipped. Answers and feedback are private to the engineer: managers see modules, never people. How we keep it fair
For the day it matters.
Someone resigns.
See what only they understand, and hand it over before their last day.
The Handover PackSomething breaks at 2 a.m.
Know before the pager goes off whether anyone awake can fix that module.
How it's measuredAI wrote most of a module.
Find out whether anyone on the team can still explain it.
Try it on a pull request
Free
for up to 5 engineers, no card. Then $15 per engineer a month, counting only those who merged code.
Pricing and questionsRead-only
on your code. Depth reads a change to write its questions, then discards it, and writes nothing to your repositories but its own check on pull requests.
Trust and securityChart your codebase.
Installing needs admin on your GitHub organisation. Not you? Send them the note.

