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 14d ago · scores are comparable only against same-mode scans

Grasp Score
66
touch-weighted living knowledge across the repo
Active humans
133 / 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
39.1%
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
68%
the headline recomputed over hand-written source alone
Score stability
moderate
90-day-cliff variant reads 60%–70% 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/RoutingLOW 44
56%
0%54%157
src/Illuminate/ValidationLOW 44
56%
0%57%177
src/Illuminate/ContractsLOW 44
51%
0%51%129
src/Illuminate/DatabaseLOW 43
57%
0%55%1365
src/Illuminate/MailLOW 42
57%
0%53%146
src/Illuminate/ViewLOW 41
54%
0%56%128
src/Illuminate/RedisLOW 40
56%
1%52%131
src/Illuminate/CacheLOW 40
60%
0%51%1104
src/Illuminate/CollectionsLOW 40
60%
1%51%153
src/Illuminate/HashingLOW 40
48%
0%59%15
src/Illuminate/ConsoleLOW 39
61%
0%50%188
src/Illuminate/FilesystemLOW 37
60%
0%51%135
src/Illuminate/BroadcastingLOW 37
54%
0%60%111
src/Illuminate/PaginationLOW 37
54%
0%58%112
src/Illuminate/TranslationLOW 37
54%
0%55%111
src/Illuminate/HttpLOW 36
64%
1%43%191
src/Illuminate/FoundationLOW 36
64%
1%41%1360
src/Illuminate/EncryptionLOW 36
53%
0%53%14
src/Illuminate/TestingLOW 35
61%
0%48%130
src/Illuminate/CookieLOW 35
55%
0%48%14

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.