GRASP.
Grasp · Comprehension Index Scan Report

Who still understands pallets/flask?

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

Grasp Score
83
touch-weighted living knowledge across the repo
Active humans
3 / 44
contributors active in last 90 days vs. all-time
AI-attributed minimum
≥ 0.5%
hard evidence only. Just 13% of commits here carry any attribution signal, so the real share is higher
Inactive share
10.0%
work by authors with no commit in the window; silence, not proof of departure
Composition
26/16/49/8%
source / tests / docs / config share of scored work
Living, source only
79%
the headline recomputed over hand-written source alone
Score stability
stable
90-day-cliff variant reads 90%–90% 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
srcLOW 20
77%
0%17%124
(root)LOW 20
77%
2%16%125
docsLOW 13
84%
0%10%18
testsLOW 10
88%
0%5%116
.githubLOW 8
91%
0%2%126
examplesLOW 8
89%
0%4%15
requirementsLOW 7
90%
0%2%10

One commit touched 90% 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 28% 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.