GRASP.
Grasp · Comprehension Index Scan Report

Who still understands serde-rs/serde?

Computed from git metadata only; no source code contents were read.
touch-weighted · 3-year history window · last commit 43d ago · scores are comparable only against same-mode scans

Grasp Score
67
touch-weighted living knowledge across the repo
Active humans
1 / 22
contributors active in last 90 days vs. all-time
AI-attributed minimum
≥ 0.0%
hard evidence only. Just 0% of commits here carry any attribution signal, so the real share is higher
Inactive share
28.2%
work by authors with no commit in the window; silence, not proof of departure
Composition
53/40/3/5%
source / tests / docs / config share of scored work
Living, source only
65%
the headline recomputed over hand-written source alone
Score stability
stable
90-day-cliff variant reads 72%–72% across 60/90/180-day activity windows; read the width before the middle value

Dark-code ranking

Modules ranked by comprehension risk: the unknown share, amplified by ongoing change and thin ownership. The green meter is living knowledge.

ModuleRiskLiving knowledgeAI-attr. InactiveBusHeat/180d
serde_deriveLOW 31
62%
0%38%117
serdeLOW 26
67%
0%26%14
serde_coreLOW 26
67%
0%26%14
test_suite/testsLOW 24
69%
0%26%12

One commit touched 76% of every file changed in this window. Wide, shallow commits, a formatter run or a license-header pass, add weight for their author across the whole surface while changing little. Worth looking at what that commit was before crediting the score to its author.

One commit accounts for 27% of the analysed lines. In a repository this size a single large change can move the score on its own, and git cannot tell a thoughtfully written thousand-line change from a thousand lines a formatter rewrote. Worth looking at what that commit actually was before reading much into the number; the touch-weighted view, which counts each file-touching commit once, is the cross-check.

Public-repo caveat: "departed" includes drive-by contributors, overstating attrition relative to a company repo with a real roster. Engagement is a proxy for comprehension. Treat it as a potential indicator rather than a diagnosis.