GRASP.
Grasp · Comprehension Index Scan Report

Who still understands laravel/framework?

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

Grasp Score
56
touch-weighted living knowledge across the repo
Active humans
80 / 1315
contributors active in last 90 days vs. all-time
AI-attributed minimum
≥ 0.5%
hard evidence only. Just 26% of commits here carry any attribution signal, so the real share is higher
Inactive share
40.7%
work by authors with no commit in the window; silence, not proof of departure
Composition
65/31/2/2%
source / tests / docs / config share of scored work
Living, source only
58%
the headline recomputed over hand-written source alone
Score stability
moderate
90-day-cliff variant reads 52%–69% across 60/90/180-day activity windows; read the width before the middle value
Squash-merged history: 71% of the commits analysed here collapsed a whole pull request into one commit by one author. Squashing credits a single person for everyone's work and can strip the co-author trailers that name the rest (measured across heavy squashers, roughly a quarter to a third of squash commits still carry them, and those are credited), so for this repository the concentration figures are an upper bound, the bus factors are a lower bound, and the AI-attribution minimum is lower than it would be with the same work merged conventionally. That information is destroyed at merge time and cannot be recovered from the repository, so it is reported rather than corrected. Comparisons against a project that does not squash are comparisons across two different record-keeping systems.

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
src/Illuminate/RoutingMED 52
48%
0%57%157
src/Illuminate/DatabaseMED 52
48%
0%57%1365
src/Illuminate/ValidationMED 52
48%
0%60%177
src/Illuminate/ContractsMED 51
43%
0%51%129
src/Illuminate/MailMED 50
49%
0%55%146
src/Illuminate/CacheLOW 49
51%
0%54%1104
src/Illuminate/CollectionsLOW 49
51%
1%56%153
src/Illuminate/ConsoleLOW 48
52%
0%51%188
src/Illuminate/ViewLOW 48
46%
0%56%128
src/Illuminate/RedisLOW 47
48%
1%55%131
src/Illuminate/HashingLOW 46
41%
0%63%15
src/Illuminate/HttpLOW 45
55%
1%48%191
src/Illuminate/FoundationLOW 45
55%
1%42%1360
src/Illuminate/FilesystemLOW 45
51%
0%51%135
src/Illuminate/PaginationLOW 44
46%
0%58%112
src/Illuminate/TranslationLOW 44
46%
0%56%111
src/Illuminate/BusLOW 43
54%
1%49%136
src/Illuminate/TestingLOW 43
52%
0%51%130
src/Illuminate/BroadcastingLOW 43
46%
0%61%111
typesLOW 43
52%
0%43%245

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

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.