GRASP.
01: The number no dashboard tracks

Who still understands your code?

AI writes more of your code every quarter, authors leave, and reviews keep getting thinner. Grasp measures how much of your codebase someone still here genuinely understands, from git metadata alone, without reading a line of your source.

LIVE SPECIMEN: CURL/CURL
96
GRASP SCORE / 10052 ACTIVE HUMANS25 YEARS OLD

Scan a public repo, free

SIXTY SECONDS · NO SIGNUP · NO CODE ACCESS

TRY ONE NOW:

Prefer to look before you scan? See a full sample report, the 22-repo benchmark. Curious how the number is made? The methodology is published in full.

02: What was found in 22 major repos
12%
openai/openai-python
living commit-authorship (a codegen-built repo; see the report's scope note)
40%
expressjs/express
three fifths of the web's workhorse was written by inactive authors
1%
langchain-ai/langchain
contributor survival: 42 active of 4,548 all-time
96%
curl/curl
25 years old and healthier than all but one repo in the benchmark

Read the full report: The State of Comprehension Debt 2026. 22 repositories measured, what the numbers mean, and the method behind them.

03: Why teams trust the number
A
Metadata only. Grasp reads commit history and PR events, never file contents.
B
Hard evidence only. AI attribution counts co-author trailers and bot accounts; it is reported as a minimum, not a guess.
C
Honest limits. The Grasp Score is a potential indicator. It tells you where to look, and every report says so.
D
No AI inside. Every score is deterministic, reproducible arithmetic over git metadata. Run it twice and you get the same number, and the raw data lets you re-derive it yourself.

Acquiring a codebase, auditing your own, or losing a key engineer? Fixed-fee diligence reports, with deeper analysis delivered in five business days.

DILIGENCE REPORTS