Public report of laravel/framework, published 23 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 23 October 2026, 06:38 UTC · Survey ID cd_3516fba4969e433396fca00cc8a1723b

laravel/framework

Measured 23 October 2026, 06:17 UTC, at code version 1de9acf

Regression: 2 dimensions fell since the last survey

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

CAI score 55out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Architecture 89 Strong Security and Compliance 83 Adequate Code Health 70 Adequate Production Readiness 65 Adequate Accessibility 49 Weak Maturity 48 Weak

A large codebase: 243,877 lines of product code in 38 projects, tests not counted · Estimated rebuild effort: about 3.3 person-years · Weakest lens: Maturity, 48

Findings by how serious they are

17 critical 798 serious 109 minor

23 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 06:17 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

60of 63 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
893of 924 findings point to an exact file and line, so you can open each one in the code. The other 31 concern the repository as a whole, such as missing documentation.
63dimensions across 6 lenses, read from 243,877 lines of product code in 38 projects.
Chapters

Executive summary

laravel/framework scores 55 out of 100 and is rated Adequate, while four of its six lenses score higher still: Architecture at 89, rated Strong, and Security and Compliance at 83, Code Health at 70 and Production Readiness at 65, all rated Adequate.

The score is lower than those four because the weakest lens counts most, and here that is Maturity, which scores 48 and is rated Weak. Its Architecture documentation dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to record your significant design decisions and to make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href, and if Maturity rose to 70, the score would rise from 55 to about 60.

17 findings are critical: eight in Secrets (history), three in Static Analysis (SAST), two in Knowledge Freshness, one in Change Coupling, one in Page structure, one in Secret Scanning and one in Test Quality.

Watchdog couldn't measure 22 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 243,877 lines, which would take an estimated 3.3 person-years, around €480,000, to rebuild.

Code Health 70 Adequate Architecture 89 Strong Maturity 48 Weak, capped by Architecture documentation Production Readiness 65 Adequate, capped by Outbound HTTP resilience Security and Compliance 83 Adequate, capped by Secrets (history), Static Analysis (SAST) and Supply-chain Provenance & Signing Accessibility 49 Weak, capped by Keyboard semantics

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Maturity 48 · counts for 46%Accessibility 49 · counts for 25%Production Readiness 65 · counts for 14%Code Health 70 · counts for 8%Security and Compliance 83 · counts for 4%Architecture 89 · counts for 2%

If Maturity rose from 48 to 70, the lowest score rated Strong, the score would rise from 55 to about 60.

Code composition: what the lines of code are
Product code 50%Tests 50%
New since the last survey: 48 findings

These 48 critical or serious findings weren't in the previous survey, on 9 October 2026.

  • Cyclomatic Complexity · Model.initializeModelAttributes (cyclomatic 17) src/Illuminate/Database/Eloquent/Model.php
  • Cyclomatic Complexity · Dispatcher.queueHandler (cyclomatic 17) src/Illuminate/Events/Dispatcher.php
  • Cognitive Complexity · Model.initializeModelAttributes (cognitive 18) src/Illuminate/Database/Eloquent/Model.php
  • Cognitive Complexity · Dispatcher.queueHandler (cognitive 18) src/Illuminate/Events/Dispatcher.php
  • Cognitive Complexity · MercureBroadcaster.broadcast (cognitive 17) src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php
  • Cognitive Complexity · QueueFake.push (cognitive 17) src/Illuminate/Support/Testing/Fakes/QueueFake.php
  • Cognitive Complexity · RedisStore.currentTags (cognitive 16) src/Illuminate/Cache/RedisStore.php
  • God Classes · MethodTooLong: Relations.test types/Database/Eloquent/Relations.php
  • God Classes · FileTooLong: Relations/BelongsToMany.php src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/Illuminate/Bus/BusServiceProvider.php
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Queue/BeanstalkdQueue.php
  • Code Duplication · Duplicated block (14 lines × 2) src/Illuminate/Cache/Limiters/ConcurrencyLimiter.php
  • Code Duplication · Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Builder.php
  • Code Duplication · Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Relations/HasOne.php
  • Test Quality · No assertions: testRetriesRemainingJobsWhenAJobsModelNoLongerExists tests/Queue/QueueRetryCommandTest.php
  • Test Quality · No assertions: testRetriesJobWithoutQueueableOptionsWhenItsModelNoLongerExists tests/Queue/QueueRetryCommandTest.php
  • Secret Scanning · REDACTED
  • Churn × Complexity Hotspots · Hotspot: src/Illuminate/Database/Eloquent/Model.php src/Illuminate/Database/Eloquent/Model.php
  • Churn × Complexity Hotspots · Hotspot: src/Illuminate/Events/Dispatcher.php src/Illuminate/Events/Dispatcher.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Collections/LazyCollection.php src/Illuminate/Collections/LazyCollection.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Database/Eloquent/Collection.php src/Illuminate/Database/Eloquent/Collection.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Process/PendingProcess.php src/Illuminate/Process/PendingProcess.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Queue/CallQueuedHandler.php src/Illuminate/Queue/CallQueuedHandler.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Cache/MemoizedTaggedCache.php src/Illuminate/Cache/MemoizedTaggedCache.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Console/Scheduling/CallbackEvent.php src/Illuminate/Console/Scheduling/CallbackEvent.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Translation/Translator.php src/Illuminate/Translation/Translator.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Filesystem/LocalFilesystemAdapter.php src/Illuminate/Filesystem/LocalFilesystemAdapter.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Knowledge Freshness · Orphaned knowledge src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php
  • Knowledge Freshness · Orphaned knowledge src/Illuminate/Database/Schema/Grammars/SqlServerGrammar.php
  • Change Coupling · Change coupling: SesTransport.php ↔ SesV2Transport.php src/Illuminate/Mail/Transport/SesTransport.php
  • Change Coupling · Change coupling: ManagesTransactions.php ↔ DatabaseTransactionsManager.php src/Illuminate/Database/Concerns/ManagesTransactions.php
  • Supply-chain Provenance & Signing · REDACTED
  • Outbound HTTP resilience · Outbound HTTP without resilience src/Illuminate/Mail/Transport/CloudflareTransport.php
  • Outbound HTTP resilience · Outbound HTTP without resilience src/Illuminate/Mail/Transport/CloudflareTransport.php
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/Illuminate/Foundation/resources/health-up.blade.php

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 11 findings

These 11 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.

  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) src/Illuminate/Bus/BusServiceProvider.php
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Queue/BeanstalkdQueue.php
  • Code Duplication · Duplicated block (14 lines × 2) src/Illuminate/Cache/Limiters/ConcurrencyLimiter.php
  • Code Duplication · Duplicated block (13 lines × 2) src/Illuminate/Foundation/Cloud/JsonFormatter.php
  • Churn × Complexity Hotspots · Hotspot: src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Support/Number.php src/Illuminate/Support/Number.php
  • Churn × Complexity Hotspots · Repeated repair: src/Illuminate/Cache/RedisTaggedCache.php src/Illuminate/Cache/RedisTaggedCache.php
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] src/Illuminate/Foundation/resources/exceptions/renderer/package-lock.json
  • Supply-chain Provenance & Signing REDACTED
  • Outbound HTTP resilience · Outbound HTTP without resilience src/Illuminate/Mail/Transport/CloudflareTransport.php
Rebuild cost: about €480,000 · Estimate
Cost to rebuild€160,000 to €800,000, for 2,661 to 8,441 hours of work, about 3.3 person-years for 1 to 7 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 243,877 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Raises the score by about 6 points · Medium effort · Architecture documentation
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 4 points · Medium effort · Keyboard semantics
3
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 2 points · Low effort · Secret Scanning

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €480,000 to build again, about 3.3 person-years of work. Its weakest lens is Maturity, at 48 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Record your significant design decisions. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.2 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 80,941 lines over the last 90 days, which is about 328,261 lines a year. At that pace, the extra work comes to an estimated 16.4 to 109.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch illuminate/broadcasting broadcasting illuminate/bus bus illuminate/broadcasting->illuminate/bus illuminate/collections collections illuminate/broadcasting->illuminate/collections illuminate/container container illuminate/broadcasting->illuminate/container illuminate/contracts contracts illuminate/broadcasting->illuminate/contracts illuminate/queue queue illuminate/broadcasting->illuminate/queue illuminate/reflection reflection illuminate/broadcasting->illuminate/reflection illuminate/support support illuminate/broadcasting->illuminate/support illuminate/bus->illuminate/collections illuminate/conditionable conditionable illuminate/bus->illuminate/conditionable illuminate/bus->illuminate/contracts illuminate/bus->illuminate/support illuminate/collections->illuminate/conditionable illuminate/collections->illuminate/contracts illuminate/macroable macroable illuminate/collections->illuminate/macroable illuminate/console console illuminate/console->illuminate/collections illuminate/console->illuminate/contracts illuminate/console->illuminate/macroable illuminate/console->illuminate/reflection illuminate/console->illuminate/support illuminate/view view illuminate/console->illuminate/view illuminate/container->illuminate/contracts illuminate/container->illuminate/reflection illuminate/database database illuminate/database->illuminate/collections illuminate/database->illuminate/conditionable illuminate/database->illuminate/container illuminate/database->illuminate/contracts illuminate/database->illuminate/macroable illuminate/database->illuminate/support illuminate/events events illuminate/events->illuminate/bus illuminate/events->illuminate/collections illuminate/events->illuminate/container illuminate/events->illuminate/contracts illuminate/events->illuminate/macroable illuminate/events->illuminate/reflection illuminate/events->illuminate/support illuminate/filesystem filesystem illuminate/filesystem->illuminate/collections illuminate/filesystem->illuminate/conditionable illuminate/filesystem->illuminate/contracts illuminate/filesystem->illuminate/macroable illuminate/filesystem->illuminate/support illuminate/http http illuminate/http->illuminate/collections illuminate/http->illuminate/conditionable illuminate/http->illuminate/macroable illuminate/http->illuminate/support illuminate/image image illuminate/image->illuminate/conditionable illuminate/image->illuminate/container illuminate/image->illuminate/contracts illuminate/image->illuminate/filesystem illuminate/image->illuminate/http illuminate/image->illuminate/macroable illuminate/image->illuminate/support illuminate/mail mail illuminate/mail->illuminate/collections illuminate/mail->illuminate/conditionable illuminate/mail->illuminate/container illuminate/mail->illuminate/contracts illuminate/mail->illuminate/macroable illuminate/mail->illuminate/support illuminate/notifications notifications illuminate/notifications->illuminate/broadcasting illuminate/notifications->illuminate/bus illuminate/notifications->illuminate/collections illuminate/notifications->illuminate/conditionable illuminate/notifications->illuminate/container illuminate/notifications->illuminate/contracts illuminate/notifications->illuminate/filesystem illuminate/notifications->illuminate/mail illuminate/notifications->illuminate/queue illuminate/notifications->illuminate/support illuminate/queue->illuminate/collections illuminate/queue->illuminate/console illuminate/queue->illuminate/container illuminate/queue->illuminate/contracts illuminate/queue->illuminate/database illuminate/queue->illuminate/filesystem illuminate/queue->illuminate/reflection illuminate/queue->illuminate/support illuminate/reflection->illuminate/collections illuminate/reflection->illuminate/contracts illuminate/routing routing illuminate/routing->illuminate/collections illuminate/routing->illuminate/conditionable illuminate/routing->illuminate/container illuminate/routing->illuminate/contracts illuminate/routing->illuminate/http illuminate/routing->illuminate/macroable illuminate/routing->illuminate/reflection illuminate/routing->illuminate/support illuminate/support->illuminate/collections illuminate/support->illuminate/conditionable illuminate/support->illuminate/contracts illuminate/support->illuminate/macroable illuminate/support->illuminate/reflection illuminate/view->illuminate/collections illuminate/view->illuminate/conditionable illuminate/view->illuminate/container illuminate/view->illuminate/contracts illuminate/view->illuminate/events illuminate/view->illuminate/filesystem illuminate/view->illuminate/macroable illuminate/view->illuminate/reflection illuminate/view->illuminate/support __more__ +18 more projects

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

233 modules, with 468 dependencies between them. 6 loops run through 27 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 193 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Illuminate.Contracts.Auth2 Illuminate.Contracts.Cache3 Illuminate.Contracts.Container4 Illuminate.Contracts.Events5 Illuminate.Contracts.Queue6 Illuminate.Contracts.Redis7 Illuminate.Contracts.Support8 Illuminate.Container9 Illuminate.Contracts.Foundation10 Illuminate.Contracts.View11 Illuminate.Support12 Illuminate.Session13 Illuminate.Http14 Illuminate.Image15 Illuminate.Mail16 Illuminate.Routing17 Illuminate.Broadcasting18 Illuminate.Filesystem19 Illuminate.Foundation.Http20 Illuminate.Console21 Illuminate.Foundation22 Illuminate.View23 Illuminate.Console.Scheduling24 Illuminate.Database25 Illuminate.Auth26 Illuminate.Bus27 Illuminate.Cache28 Illuminate.Database.Query29 Illuminate.Foundation.Cloud30 Illuminate.Foundation.Console31 Illuminate.Queue32 Illuminate.Validation33 Illuminate.Auth.Passwords34 Illuminate.Database.Eloquent35 Illuminate.Queue.Console36 Illuminate.Support.Testing.Fakes37 Illuminate.Database.Console38 Illuminate.Database.Eloquent.Relations39 Illuminate.Notifications40 (global)
1 Illuminate.Contracts.Auth
2 Illuminate.Contracts.Cache
3 Illuminate.Contracts.Container
4 Illuminate.Contracts.Events
5 Illuminate.Contracts.Queue
6 Illuminate.Contracts.Redis
7 Illuminate.Contracts.Support
8 Illuminate.Container3
9 Illuminate.Contracts.Foundation1
10 Illuminate.Contracts.View1
11 Illuminate.Support11611
12 Illuminate.Session11211
13 Illuminate.Http21
14 Illuminate.Image223
15 Illuminate.Mail122211
16 Illuminate.Routing161318
17 Illuminate.Broadcasting121111
18 Illuminate.Filesystem141
19 Illuminate.Foundation.Http1122
20 Illuminate.Console1112
21 Illuminate.Foundation2117312
22 Illuminate.View115311
23 Illuminate.Console.Scheduling62319
24 Illuminate.Database111351
25 Illuminate.Auth161231
26 Illuminate.Bus223231
27 Illuminate.Cache31211112
28 Illuminate.Database.Query2
29 Illuminate.Foundation.Cloud113121
30 Illuminate.Foundation.Console11114396411
31 Illuminate.Queue2221711181
32 Illuminate.Validation2111
33 Illuminate.Auth.Passwords711211
34 Illuminate.Database.Eloquent341121
35 Illuminate.Queue.Console2141172
36 Illuminate.Support.Testing.Fakes112261
37 Illuminate.Database.Console3572
38 Illuminate.Database.Eloquent.Relations335
39 Illuminate.Notifications123
40 (global)1512
Uses a module listed above itPart of a loopThe module itself
1 Illuminate.Contracts.Auth2 Illuminate.Contracts.Cache3 Illuminate.Contracts.Container4 Illuminate.Contracts.Events5 Illuminate.Contracts.Queue6 Illuminate.Contracts.Redis7 Illuminate.Contracts.Support8 Illuminate.Container9 Illuminate.Contracts.Foundation10 Illuminate.Contracts.View11 Illuminate.Support12 Illuminate.Session13 Illuminate.Http14 Illuminate.Image15 Illuminate.Mail16 Illuminate.Routing17 Illuminate.Broadcasting18 Illuminate.Filesystem19 Illuminate.Foundation.Http20 Illuminate.Console21 Illuminate.Foundation22 Illuminate.View23 Illuminate.Console.Scheduling24 Illuminate.Database25 Illuminate.Auth26 Illuminate.Bus27 Illuminate.Cache28 Illuminate.Database.Query29 Illuminate.Foundation.Cloud30 Illuminate.Foundation.Console31 Illuminate.Queue32 Illuminate.Validation33 Illuminate.Auth.Passwords34 Illuminate.Database.Eloquent35 Illuminate.Queue.Console36 Illuminate.Support.Testing.Fakes37 Illuminate.Database.Console38 Illuminate.Database.Eloquent.Relations39 Illuminate.Notifications40 (global)Illuminate.Contracts.Auth1Illuminate.Contracts.Cache2Illuminate.Contracts.Container3Illuminate.Contracts.Events4Illuminate.Contracts.Queue5Illuminate.Contracts.Redis6Illuminate.Contracts.Support7Illuminate.Container8Illuminate.Contracts.Foundation9Illuminate.Contracts.View10Illuminate.Support11Illuminate.Session12Illuminate.Http13Illuminate.Image14Illuminate.Mail15Illuminate.Routing16Illuminate.Broadcasting17Illuminate.Filesystem18Illuminate.Foundation.Http19Illuminate.Console20Illuminate.Foundation21Illuminate.View22Illuminate.Console.Scheduling23Illuminate.Database24Illuminate.Auth25Illuminate.Bus26Illuminate.Cache27Illuminate.Database.Query28Illuminate.Foundation.Cloud29Illuminate.Foundation.Console30Illuminate.Queue31Illuminate.Validation32Illuminate.Auth.Passwords33Illuminate.Database.Eloquent34Illuminate.Queue.Console35Illuminate.Support.Testing.Fakes36Illuminate.Database.Console37Illuminate.Database.Eloquent.Relations38Illuminate.Notifications39(global)40311116111121121223122211161318121111141112211122117312115311623191113511612312232313121111221131211111439641122217111812111711211341121214117211226135723351231512+193 more modules (most-connected shown)

At a glance — Code Health · 70% · Adequate ·

The Good
D3 · PHP God Classes 7.9 D4 · PHP Code Duplication 9.7 D17 · PHP Explicit Debt 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X4 · Repo Structured logging 10.0
The Bad
D2 · PHP Cognitive Complexity 6.2 X19 · Repo Unrestored process-global state 5.2 X3 · Repo Exception handling 5.4 X5 · Repo Nullable reference types 6.0
The Ugly
D1 · PHP Cyclomatic Complexity 4.8

At a glance — Architecture · 89% · Strong ·

The Good
D6 · PHP Cohesion (LCOM4) 8.2 D22 · PHP Internal API Consistency 7.0 D26 · PHP Project Cohesion 7.4 D27 · PHP Navigability 8.9 D35 · PHP Change Coupling 9.8 AX10 · Repo Code composition 9.2 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0
The Bad
D5 · PHP Coupling 6.9

At a glance — Maturity · 48% · Weak · gated by M2 ·

The Good
D15 · PHP Churn × Complexity Hotspots 10.0 D16 · PHP Bus Factor 9.5 D21 · PHP Naming Consistency 10.0 D34 · PHP Knowledge Freshness 9.2 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Ugly
M1 · Repo Documentation (README) 4.6 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 65% · Adequate · gated by P7 ·

The Good
D9 · PHP Test Distribution 10.0 D10 · PHP Test Quality 9.7 D14 · PHP License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 7.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 7.0 P6 · Repo Release Hygiene 10.0
The Bad
D13 · PHP Secret Scanning 5.0
The Ugly
P7 · Repo Outbound HTTP resilience 3.0

At a glance — Security · 83% · Adequate · gated by D28, D29, D36 ·

The Good
D30 · PHP Dependency Vulnerabilities 10.0 D31 · PHP IaC & Container Security 9.6 D37 · PHP Vulnerability-disclosure Policy 10.0 D43 · PHP Malicious Dependencies 10.0 D44 · PHP Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0
The Ugly
D28 · PHP Secrets (history) 2.0 D29 · PHP Static Analysis (SAST) 2.3 D36 · PHP Supply-chain Provenance & Signing 2.5

At a glance — Accessibility · 49% · Weak · gated by AC4 ·

The Good
AC1 · Repo Text alternatives 10.0 AC2 · Repo Forms & labels 10.0 AC5 · Repo ARIA correctness 10.0
The Bad
AC3 · Repo Page structure 5.2 AC6 · Repo Visual & motion safety 6.4
The Ugly
AC4 · Repo Keyboard semantics 1.0 AC7 · Repo A11y enforcement 4.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection21High / Critical
A07:2025 — Authentication Failures10High / Critical
A02:2025 — Security Misconfiguration4Medium
A03:2025 — Software Supply Chain Failures4Medium

Roadmap

Begin by documenting significant design decisions in a dedicated folder to establish architectural clarity and resolve the single leaked secret in REDACTED. Next, ensure the application is accessible by making custom controls keyboard-operable, adding a quick start guide to the README, and enforcing accessibility checks in the CI pipeline to catch issues early.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+6.0 ptsMediumArchitecture documentation
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+4.3 ptsMediumKeyboard semantics
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.+2.0 ptsLowSecret Scanning
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.+3.9 ptsMediumDocumentation (README)
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SQLiteGrammar.php, SqlServerGrammar.php.+1.9 ptsLowKnowledge Freshness
Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.+2.3 ptsMediumA11y enforcement
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with BusPendingBatchTest.php.+1.1 ptsLowTest Quality
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+1.6 ptsMediumPage structure

File quality

Per-file score 0–10 — a quality signature. Of 290 files carrying findings, judged against the Production bar: 0% slop · 45% mixed · 55% near-clean.

FileScoreBandWorst signal
src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php4.8MixedGod Classes: TooManyMethods: BelongsToMany
REDACTED5.1MixedSecrets (history): High secret: REDACTED
src/Illuminate/Database/Query/Builder.php5.5MixedCyclomatic Complexity: Builder.where (cyclomatic 18)
src/Illuminate/Database/Eloquent/Builder.php5.5MixedGod Classes: TooManyMethods: Builder
src/Illuminate/Http/Client/PendingRequest.php5.5MixedCyclomatic Complexity: PendingRequest.send (cyclomatic 22)
src/Illuminate/Database/Eloquent/Model.php5.5MixedCyclomatic Complexity: Model.initializeModelAttributes (cyclomatic 17)
src/Illuminate/Collections/Collection.php5.5MixedCognitive Complexity: Collection.sortByMany (cognitive 25)
src/Illuminate/Collections/LazyCollection.php5.6MixedCognitive Complexity: LazyCollection.select (cognitive 16)
src/Illuminate/Validation/Validator.php5.6MixedCognitive Complexity: Validator.passes (cognitive 18)
src/Illuminate/Mail/Mailable.php5.6MixedGod Classes: TooManyMethods: Mailable
src/Illuminate/Events/Dispatcher.php5.7MixedCyclomatic Complexity: Dispatcher.queueHandler (cyclomatic 17)
src/Illuminate/Database/Connection.php5.7MixedGod Classes: TooManyMethods: Connection
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
src/Illuminate/Database/Console/ShowCommand.php5.9MixedCyclomatic Complexity: ShowCommand.displayForCli (cyclomatic 19)
src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php5.9MixedCognitive Complexity: PostgresGrammar.compileUnique (cognitive 18)
src/Illuminate/Support/Testing/Fakes/BusFake.php5.9MixedCognitive Complexity: BusFake.assertDispatchedWithChainOfObjects (cognitive 17)
src/Illuminate/Foundation/Application.php5.9MixedGod Classes: TooManyMethods: Application
src/Illuminate/Routing/Route.php5.9MixedGod Classes: TooManyMethods: Route
src/Illuminate/Container/Container.php5.9MixedGod Classes: TooManyMethods: Container
src/Illuminate/Database/Query/Grammars/MySqlGrammar.php5.9MixedGod Classes: TooManyMethods: MySqlGrammar

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 17

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 798

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 109

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 23

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 60 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 63 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D16D17D21D22D26D27D28D29D30D31D34D35D36D37D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4C2M1M2M3M4P1P10P2P3P4P6P7X14X15X16X18X19X21X22X23X25X28X3X30X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 893 of 924 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16768-2636-7cba-a3eb-1afffff14a99.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
  • D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 40 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares composer.json, but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Composer dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Illuminate/Auth/Passwords/CacheTokenRepository.php`, `src/Illuminate/Auth/Passwords/DatabaseTokenRepository.php`, `src/Illuminate/Auth/SessionGuard.php`, `src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php`, `src/Illuminate/Broadcasting/Mercure/ChannelEncrypter.php`, … (+70 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Laravel's service container and a PSR-11 container (Psr\Container), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Illuminate/Database/Connectors/Connector.php:66), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Illuminate/Database/Connectors/Connector.php:66), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Illuminate/Database/Connectors/Connector.php:66), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'PDO' is imported (src/Illuminate/Database/Connectors/Connector.php:66), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
  • S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (3): D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity4.8 / 10Weak✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.8 / 10 · rule-coverage 100% · ceiling Prevented

24 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MessageSelector.getPluralIndex at 335. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HasAttributes.castAttribute at 27 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Illuminate/Console/GeneratorCommand.php (GeneratorCommand.promptForMissingArgumentsUsing at 24), src/Illuminate/Database/Query/Processors/PostgresProcessor.php (PostgresProcessor.processTypes at 24), src/Illuminate/Collections/Traits/EnumeratesValues.php (EnumeratesValues.operatorForWhere at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

MessageSelector.getPluralIndex (cyclomatic 335)src/Illuminate/Translation/MessageSelector.php:110
RouteUrlGenerator.formatParameters (cyclomatic 29)src/Illuminate/Routing/RouteUrlGenerator.php:184
EnvironmentEncryptCommand.handle (cyclomatic 26)src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php:63
InterventionDriver.process (cyclomatic 26)src/Illuminate/Image/Drivers/InterventionDriver.php:80
HasAttributes.originalIsEquivalent (cyclomatic 25)src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php:2389

+ 19 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with MessageSelector.getPluralIndex (cyclomatic 335). — Refactoring it lifts Cyclomatic Complexity from 4.8 to about 7.4/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity6.2 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Prevented

68 method(s) exceeded the cognitive complexity threshold of 15; the worst was MessageSelector.getPluralIndex at 86.

MessageSelector.getPluralIndex (cognitive 86)src/Illuminate/Translation/MessageSelector.php:110
RouteUrlGenerator.formatParameters (cognitive 47)src/Illuminate/Routing/RouteUrlGenerator.php:184
NotificationSender.queueNotification (cognitive 42)src/Illuminate/Notifications/NotificationSender.php:225
CronExpressionTimezoneConverter.shiftDaysOfMonth (cognitive 38)src/Illuminate/Console/Scheduling/CronExpressionTimezoneConverter.php:176
Batch.send (cognitive 37)src/Illuminate/Http/Client/Batch.php:265

+ 63 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with MessageSelector.getPluralIndex (cognitive 86). — Refactoring it lifts Cognitive Complexity from 6.2 to about 6.5/10.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.9 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 100% · ceiling Prevented

140 god class(es) detected.

TooManyMethods: Builder · ×97src/Illuminate/Database/Query/Builder.php:37
ClassTooLong: Builder · ×21src/Illuminate/Database/Query/Builder.php:37
FileTooLong: Query/Builder.php · ×18src/Illuminate/Database/Query/Builder.php
MethodTooLong: Builder.test · ×4types/Database/Eloquent/Builder.php:16

What to do

  1. Resolve the 97 TooManyMethods finding(s) in God Classes — start with Builder.php (3), Factory.php (3), Collection.php (2). — One of this dimension's main actionable groups (97 warning-level).
  2. Resolve the 21 ClassTooLong finding(s) in God Classes — start with Builder.php (2), Model.php, Str.php. — One of this dimension's main actionable groups (21 warning-level).
  3. Resolve the 18 FileTooLong finding(s) in God Classes — start with Builder.php (2), Collection.php (2), LazyCollection.php (2). — One of this dimension's main actionable groups (18 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.7 / 10Stronggated by 177 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

171 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 8 of the 177 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (5 lines × 2) · ×27src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:627
Duplicated block (9 lines × 2) · ×19src/Illuminate/Broadcasting/BroadcastManager.php:307
Duplicated block (11 lines × 2) · ×17src/Illuminate/Cache/CacheManager.php:141
Duplicated block (7 lines × 2) · ×14src/Illuminate/Database/Concerns/BuildsQueries.php:237
Duplicated block (8 lines × 2) · ×8src/Illuminate/Bus/ChainedBatch.php:124

+ 47 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 27 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with PostgresGrammar.php (4), Builder.php (2), BelongsToMany.php (2). — One of this dimension's main actionable groups (27 warning-level).
  2. Resolve the 19 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with TestComponent.php (2), BroadcastManager.php, Arr.php. — One of this dimension's main actionable groups (19 warning-level).
  3. Resolve the 17 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with Builder.php (3), MySqlGrammar.php (3), CacheManager.php. — One of this dimension's main actionable groups (17 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling6.9 / 10Adequate✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

38 production modules (Composer), 0 dependency cycle(s), 7 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence.

Off the main sequence: illuminate/conditionable · ×6
Unstable project illuminate/broadcasting
Unstable project illuminate/database
Unstable project illuminate/events
Unstable project illuminate/mail

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 Unstable project illuminate/broadcasting finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project illuminate/database finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.

D6 · Cohesion (LCOM4)8.2 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Verified

70 of 459 classes have LCOM4 above 3.

Low cohesion: PostgresGrammar (LCOM4 30) · ×70src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:11

What to do

  1. Resolve the 70 Low cohesion finding(s) in Cohesion (LCOM4) — start with Builder.php (2), Factory.php (2), PostgresGrammar.php. — One of this dimension's main actionable groups (70 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

10317 test methods: 10317 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality9.7 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

12 skipped (12 with a documented reason), 198 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 10317 tests.

No assertions (empty test): test_it_can_batch_a_closuretests/Bus/BusPendingBatchTest.php:262
No assertions: testBroadcastPublishesOneUnprivatedUpdateWhenEveryChannelIsPublic · ×196tests/Broadcasting/MercureBroadcasterTest.php:234
Skipped (documented): testNetworkExceptionIsConvertedToConnectionException · ×12tests/Http/HttpClientTest.php:5260
No assertions (declared): test_it_can_resolve_the_implicit_model_route_bindings_for_the_given_routetests/Routing/ImplicitRouteBindingTest.php:109

What to do

  1. Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with BusPendingBatchTest.php. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 196 No assertions finding(s) in Test Quality — start with AssertTest.php (49), ValidationEmailRuleTest.php (26), RouteRegistrarTest.php (20). — One of this dimension's main actionable groups (196 warning-level).
  3. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 5 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 5 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 2 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares composer.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 23 serious findings✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: src/Illuminate/Database/Eloquent/Model.php (13×17=221); src/Illuminate/Http/Client/PendingRequest.php (9×22=198); src/Illuminate/Queue/SqsQueue.php (9×15=135) Repeated repair below the complexity floor: src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php (7 of 13 changes were fixes); src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php (6 of 8 changes were fixes); src/Illuminate/Support/Str.php (5 of 7 changes were fixes)

Repeated repair: src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php · ×17src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:289
Hotspot: src/Illuminate/Database/Eloquent/Model.php · ×6src/Illuminate/Database/Eloquent/Model.php:445

What to do

  1. Resolve the 17 Repeated repair finding(s) in Churn × Complexity Hotspots — start with BelongsToMany.php, ResolvesJsonApiElements.php, Str.php. — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with Model.php, PendingRequest.php, SqsQueue.php. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

32 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Illuminate/Foundation/Application.php. Counted over 698 of the 1758 production source files in this repository: 1059 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 243877 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D22 · Internal API ConsistencyStrong◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Verified

3 API inconsistencies across a 400-member sample of 1646 exposed types.

Duplicate intent: Both methods appear to convert the exception into an HTTP response. In Laravel, `toResponse()` is the standard PSR-15/exception handling contract method, while `response()` is a legacy or convenience alias. Having both creates confusion about which entry point to use.
Inconsistent naming for status mutation: `AuthorizationException` uses `withStatus` (immutable-style builder pattern), while `Response` also uses `withStatus`. However, `AuthorizationException` also has `asNotFound()` which is a specific case of setting a status. While not strictly duplicate, the mix of `withStatus` (generic) and `asNotFound` (specific) on the Exception, versus `denyWithStatus` and `denyAsNotFound` on the Response, creates a slight asymmetry in how status codes are applied across the authorization domain.
Inconsistent error handling patterns: `Gate.authorize()` throws an exception (specifically `AuthorizationException`) on failure, whereas `HandlesAuthorization` traits provide methods like `denyWithStatus` and `denyAsNotFound` that likely throw or return specific responses. The naming `denyWithStatus` implies a return value or a specific exception construction, while `authorize` implies a void return on success and exception on failure. This mixes exception-throwing and potentially return-value-based APIs.

What to do

  1. Resolve the 1 Duplicate intent finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Inconsistent naming for status mutation finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Inconsistent error handling patterns finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion7.4 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 7.4 / 10 · rule-coverage 100% · ceiling Documented

5 of 38 build units (Composer) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability8.9 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Documented

23 % of calls cross a namespace and 8 % go through an interface, but 39 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

What to do

  1. Improve Navigability — currently 8.9/10. — 23 % of calls cross a namespace and 8 % go through an interface, but 39 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)2.0 / 10Critical✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 8 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)2.3 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 2.3 / 10 · rule-coverage 100% · ceiling Documented

21 finding(s): 0 critical, 3 high, 18 medium, 0 low. semgrep hit a parse error in 82 file(s) — `src/Illuminate/Auth/Passwords/CacheTokenRepository.php` (line 25), `src/Illuminate/Auth/Passwords/DatabaseTokenRepository.php` (line 24), `src/Illuminate/Auth/SessionGuard.php` (line 41), `src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php` (line 241), `src/Illuminate/Broadcasting/Mercure/ChannelEncrypter.php` (line 42), … (+77 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security9.6 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

4 finding(s): 0 critical, 0 high, 4 medium, 0 low.

REDACTED

What to do

  1. Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.2 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

54 of 699 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php. Counted over 699 of the 1758 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:1
Orphaned file · ×52src/Illuminate/Foundation/Http/Middleware/PreventRequestForgery.php:1
Further orphaned files (smaller)

What to do

  1. Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SQLiteGrammar.php, SqlServerGrammar.php. — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 52 Orphaned file finding(s) in Knowledge Freshness — start with Manager.php (2), PreventRequestForgery.php, Redirector.php. — One of this dimension's main actionable groups (52 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.8 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: BeanstalkdQueue.php↔DatabaseQueue.php 77%; BeanstalkdQueue.php↔RedisQueue.php 77%; BeanstalkdQueue.php↔SqsQueue.php 77%

Boundary-crossing change coupling: helpers.php ↔ Helpers.phpsrc/Illuminate/Support/helpers.php:1
Change coupling: ShowCommand.php ↔ TableCommand.php · ×9src/Illuminate/Database/Console/ShowCommand.php:1
Change coupling clique: BeanstalkdQueue.php, DatabaseQueue.php, RedisQueue.php, SqsQueue.phpsrc/Illuminate/Queue/BeanstalkdQueue.php

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with helpers.php. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 9 Change coupling finding(s) in Change Coupling — start with BelongsToMany.php (2), ShowCommand.php, EnvironmentDecryptCommand.php. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with BeanstalkdQueue.php. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 40 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure5.2 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×4) — src/Illuminate/Foundation/Exceptions/views/layout.blade.php:2, src/Illuminate/Foundation/resources/exceptions/renderer/components/layout.blade.php:3, src/Illuminate/Foundation/resources/health-up.blade.php:2, …
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — src/Illuminate/Foundation/resources/exceptions/renderer/components/layout.blade.php:6

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×3) — src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:5, src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:14, src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:33

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety6.4 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — src/Illuminate/Foundation/resources/health-up.blade.php:27

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 61 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition9.2 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

M1 · Documentation (README)4.6 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

  • 794 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 36 of 38 project(s) that lack one — worth up to 1.9 pts.
  • Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

What to do

  • Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

  • Dependabot is configured but does not watch `npm`, `composer` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `HttpClient::create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×3) — src/Illuminate/Broadcasting/Mercure/CreatesMercureDrivers.php:91, src/Illuminate/Mail/MailManager.php:500, src/Illuminate/Mail/Transport/CloudflareTransport.php:35
  • `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — src/Illuminate/Mail/Transport/CloudflareTransport.php:46

What to do

  • Give every client an explicit bound: `new Client(['timeout' => 10, 'connect_timeout' => 3])` for Guzzle (whose default is to wait forever), `CURLOPT_TIMEOUT`/`CURLOPT_CONNECTTIMEOUT` before `curl_exec`, `timeout`/`max_duration` on Symfony HttpClient (or `framework.http_client.default_options`), and a stream-context `timeout` or `connection_timeout` for `file_get_contents`/`SoapClient`. In Drupal, use the `http_client` service, which carries core's site-wide timeout, rather than `new Client()`. Add retries with back-off (Guzzle `Middleware::retry`, Symfony `RetryableHttpClient`, Laravel `->retry()`) around dependencies that fail.
X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

  • `runViaConcurrently` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `COLUMNS` environment variable (changed at line 157, reset at line 183) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path. — src/Illuminate/Foundation/Console/DevCommand.php:148

What to do

  • Each finding names the statement that changes the process-global value and the statement that puts it back. Confirm from the two that nothing between them is protected — then prefer removing the mutation over widening the restore: a `cwd` and `env` passed to Symfony `Process` or `proc_open`, an absolute path, or an explicit `DateTimeZone`/locale/encoding argument is scoped to that operation, which is what the save-and-restore was trying to approximate. Where the global genuinely must move (an error handler around a call that warns), a `try`/`finally` is the least that makes the restore unconditional.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — src/Illuminate/Auth/Access/Gate.php:495, src/Illuminate/Events/Dispatcher.php:575, src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:194, …
  • `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×30) — src/Illuminate/Bus/DatabaseBatchRepository.php:357, src/Illuminate/Database/Console/Migrations/MigrateCommand.php:169, src/Illuminate/Database/Console/Migrations/FreshCommand.php:78, …

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

X5 · Nullable reference types6.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 1/2 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.

What to do

  • Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health70%AdequateAcceptable, with room to improve.
Architecture89%StrongStrongest area.
Maturity48%Weak — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness65%Adequate — gated by P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security83%Adequate — gated by D28, D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility49%Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: this repository stores data through 'PDO' (src/Illuminate/Database/Connectors/Connector.php:66) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through 'PDO' (src/Illuminate/Database/Connectors/Connector.php:66) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through 'PDO' (src/Illuminate/Database/Connectors/Connector.php:66) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: this repository stores data through 'PDO' (src/Illuminate/Database/Connectors/Connector.php:66) but declares no persisted model this check reads (Laravel migration columns, Eloquent $fillable/$hidden lists, Doctrine #[ORM\Column] properties). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • D11 Test Reliability — Test reliability not included — no .php test runner
  • D12 Dependency Hygiene — Not scored — 40 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D19 Documentation Quality — LLM evaluation failed
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (types), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — 75 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 27 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 13 value object(s)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P8 Schema migrations — Laravel is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not applicable: PHP runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 17 finding(s)
D28 · Secrets (history) · High secret · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×2
  • Orphaned knowledge src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge src/Illuminate/Database/Schema/Grammars/SqlServerGrammar.php:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom src/Illuminate/Foundation/resources/exceptions/renderer/components/layout.blade.php:6 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
D10 · Test Quality · No assertions (empty test) · ×1
  • No assertions (empty test): test_it_can_batch_a_closure tests/Bus/BusPendingBatchTest.php:262 — Test method has an empty body — it asserts nothing and exercises no code.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: helpers.php ↔ Helpers.php src/Illuminate/Support/helpers.php:1 — `src/Illuminate/Support/helpers.php` (context Illuminate) and `types/Support/Helpers.php` (context types) sit in DIFFERENT parts of the tree yet change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `e54548fd` feat: improve higher order proxy generic types (#61418); `d4d36e86` Introduce `lazy` object and `proxy` object support helpers (#57831); `ddfbbf03` restore type-narrowing for `throw_*` helpers (#53154) (#53164) — run `git show` on any of them.
Serious — 798 finding(s)
D10 · Test Quality · No assertions · ×196
  • No assertions: testBroadcastPublishesOneUnprivatedUpdateWhenEveryChannelIsPublic tests/Broadcasting/MercureBroadcasterTest.php:234 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBroadcastPublishesOnePrivateUpdatePerGuardedChannel tests/Broadcasting/MercureBroadcasterTest.php:247 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBroadcastStripsTheSocketKeyFromThePayloadAndEmbedsItInTheEnvelope tests/Broadcasting/MercureBroadcasterTest.php:262 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBroadcastOmitsTheSocketKeyFromTheEnvelopeWhenAbsent tests/Broadcasting/MercureBroadcasterTest.php:273 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBroadcastSplitsAMixedBatchIntoTwoUpdates tests/Broadcasting/MercureBroadcasterTest.php:282 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testTopicsEncodeChannelNamesIntoASinglePathSegment tests/Broadcasting/MercureBroadcasterTest.php:295 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBroadcastPublishesOnePrivateUpdatePerEncryptedChannel tests/Broadcasting/MercureBroadcasterTest.php:503 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testWhenMethodOfConditionableTraitWithFalse tests/Bus/BusPendingDispatchTest.php:116 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testUnlessMethodOfConditionableTraitWithTrue tests/Bus/BusPendingDispatchTest.php:123 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: test_cache_spy_works_with_memoized_cache tests/Cache/CacheSpyMemoTest.php:43 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: test_cache_spy_tracks_remember_calls_on_memoized_cache tests/Cache/CacheSpyMemoTest.php:64 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testWithPivotValueMethodSetsWhereConditionsForFetching tests/Database/DatabaseEloquentBelongsToManyWithDefaultAttributesTest.php:18 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSerializesPivotsEntitiesId tests/Database/DatabaseEloquentCollectionQueueableTest.php:13 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSerializesModelEntitiesById tests/Database/DatabaseEloquentCollectionQueueableTest.php:26 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testFindMethodUseWritePdo tests/Database/DatabaseEloquentModelTest.php:736 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDestroyMethodCallsQueryBuilderCorrectly tests/Database/DatabaseEloquentModelTest.php:766 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDestroyMethodCallsQueryBuilderCorrectlyWithCollection tests/Database/DatabaseEloquentModelTest.php:771 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDestroyMethodCallsQueryBuilderCorrectlyWithEloquentCollection tests/Database/DatabaseEloquentModelTest.php:776 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDestroyMethodCallsQueryBuilderCorrectlyWithMultipleArgs tests/Database/DatabaseEloquentModelTest.php:785 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDoesntThrowWhenAssigningMissingAttributes tests/Database/DatabaseEloquentModelTest.php:3538 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testMapIgnoreGenericPivotClass tests/Database/DatabaseEloquentStrictMorphsTest.php:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testChunkPaginatesUsingIdWithCountZero tests/Database/DatabaseQueryBuilderTest.php:6417 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testDumpRemovesShadowTables tests/Database/DatabaseSqliteSchemaStateTest.php:58 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testMimeTypeIsNotCalledAlreadyProvidedToResponse tests/Filesystem/FilesystemAdapterTest.php:72 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSizeIsNotCalledAlreadyProvidedToResponse tests/Filesystem/FilesystemAdapterTest.php:84 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 171 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×97
  • TooManyMethods: Builder src/Illuminate/Database/Query/Builder.php:37 — TooManyMethods — 263 methods. The bar is 30 methods; this is 233 over it, 8.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Model src/Illuminate/Database/Eloquent/Model.php:45 — TooManyMethods — 167 methods. The bar is 30 methods; this is 137 over it, 5.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ValidatesAttributes src/Illuminate/Validation/Concerns/ValidatesAttributes.php:34 — TooManyMethods — 149 methods. The bar is 30 methods; this is 119 over it, 4.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Stringable src/Illuminate/Support/Stringable.php:15 — TooManyMethods — 140 methods. The bar is 30 methods; this is 110 over it, 4.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Blueprint src/Illuminate/Database/Schema/Blueprint.php:19 — TooManyMethods — 138 methods. The bar is 30 methods; this is 108 over it, 4.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: HasAttributes src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php:52 — TooManyMethods — 127 methods. The bar is 30 methods; this is 97 over it, 4.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Builder src/Illuminate/Database/Eloquent/Builder.php:40 — TooManyMethods — 125 methods. The bar is 30 methods; this is 95 over it, 4.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Collection src/Illuminate/Collections/Collection.php:24 — TooManyMethods — 115 methods. The bar is 30 methods; this is 85 over it, 3.83× the bar. Most of these members implement Support.Enumerable (88 of 115 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: Str src/Illuminate/Support/Str.php:24 — TooManyMethods — 113 methods. The bar is 30 methods; this is 83 over it, 3.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Connection src/Illuminate/Database/Connection.php:30 — TooManyMethods — 111 methods. The bar is 30 methods; this is 81 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LazyCollection src/Illuminate/Collections/LazyCollection.php:27 — TooManyMethods — 109 methods. The bar is 30 methods; this is 79 over it, 3.63× the bar. Most of these members implement Support.Enumerable (89 of 109 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: Grammar src/Illuminate/Database/Query/Grammars/Grammar.php:15 — TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Application src/Illuminate/Foundation/Application.php:40 — TooManyMethods — 104 methods. The bar is 30 methods; this is 74 over it, 3.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PendingRequest src/Illuminate/Http/Client/PendingRequest.php:42 — TooManyMethods — 103 methods. The bar is 30 methods; this is 73 over it, 3.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BelongsToMany src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:35 — TooManyMethods — 102 methods. The bar is 30 methods; this is 72 over it, 3.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Route src/Illuminate/Routing/Route.php:35 — TooManyMethods — 93 methods. The bar is 30 methods; this is 63 over it, 3.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MySqlGrammar src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:13 — TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Mailable src/Illuminate/Mail/Mailable.php:36 — TooManyMethods — 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Router src/Illuminate/Routing/Router.php:38 — TooManyMethods — 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Container src/Illuminate/Container/Container.php:26 — TooManyMethods — 88 methods. The bar is 30 methods; this is 58 over it, 2.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PostgresGrammar src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:11 — TooManyMethods — 86 methods. The bar is 30 methods; this is 56 over it, 2.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Validator src/Illuminate/Validation/Validator.php:24 — TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Rule src/Illuminate/Validation/Rule.php:63 — TooManyMethods — 81 methods. The bar is 30 methods; this is 51 over it, 2.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SQLiteGrammar src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:13 — TooManyMethods — 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EnumeratesValues src/Illuminate/Collections/Traits/EnumeratesValues.php:59 — TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 72 more in this group — see findings.md.
D6 · Cohesion (LCOM4) · Low cohesion · ×70
  • Low cohesion: PostgresGrammar (LCOM4 30) src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:11 — PostgresGrammar's methods fall into 30 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 30 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BladeCompiler (LCOM4 29) src/Illuminate/View/Compilers/BladeCompiler.php:18 — BladeCompiler's methods fall into 29 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 29 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: LazyCollection (LCOM4 24) src/Illuminate/Collections/LazyCollection.php:27 — LazyCollection's methods fall into 24 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 24 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Validator (LCOM4 19) src/Illuminate/Validation/Validator.php:24 — Validator's methods fall into 19 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 19 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TestResponse (LCOM4 18) src/Illuminate/Testing/TestResponse.php:37 — TestResponse's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Middleware (LCOM4 14) src/Illuminate/Foundation/Configuration/Middleware.php:21 — Middleware's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CallQueuedClosure (LCOM4 13) src/Illuminate/Queue/CallQueuedClosure.php:14 — CallQueuedClosure's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SendQueuedNotifications (LCOM4 12) src/Illuminate/Notifications/SendQueuedNotifications.php:23 — SendQueuedNotifications's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Model (LCOM4 11) src/Illuminate/Database/Eloquent/Model.php:45 — Model's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MailMessage (LCOM4 11) src/Illuminate/Notifications/Messages/MailMessage.php:14 — MailMessage's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Application (LCOM4 10) src/Illuminate/Foundation/Application.php:40 — Application's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ChainedBatch (LCOM4 9) src/Illuminate/Bus/ChainedBatch.php:13 — ChainedBatch's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: JsonResponse (LCOM4 9) src/Illuminate/Http/JsonResponse.php:12 — JsonResponse's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: RedirectResponse (LCOM4 9) src/Illuminate/Http/RedirectResponse.php:17 — RedirectResponse's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Request (LCOM4 9) src/Illuminate/Http/Request.php:29 — Request's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SendQueuedMailable (LCOM4 9) src/Illuminate/Mail/SendQueuedMailable.php:22 — SendQueuedMailable's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BroadcastNotificationCreated (LCOM4 9) src/Illuminate/Notifications/Events/BroadcastNotificationCreated.php:13 — BroadcastNotificationCreated's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BroadcastEvent (LCOM4 8) src/Illuminate/Broadcasting/BroadcastEvent.php:22 — BroadcastEvent's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Event (LCOM4 8) src/Illuminate/Console/Scheduling/Event.php:25 — Event's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Builder (LCOM4 8) src/Illuminate/Database/Query/Builder.php:37 — Builder's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: CallQueuedListener (LCOM4 8) src/Illuminate/Events/CallQueuedListener.php:12 — CallQueuedListener's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Response (LCOM4 8) src/Illuminate/Http/Response.php:15 — Response's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Envelope (LCOM4 8) src/Illuminate/Mail/Mailables/Envelope.php:10 — Envelope's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NotificationFailed (LCOM4 8) src/Illuminate/Notifications/Events/NotificationFailed.php:8 — NotificationFailed's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NotificationSending (LCOM4 8) src/Illuminate/Notifications/Events/NotificationSending.php:8 — NotificationSending's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • + 45 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×36
  • Swallowed exception (caught, then discarded) src/Illuminate/Auth/Access/Gate.php:495 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Bus/DatabaseBatchRepository.php:357 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Database/Console/Migrations/MigrateCommand.php:169 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Database/Console/Migrations/FreshCommand.php:78 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Database/Eloquent/Factories/Factory.php:1112 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Events/Dispatcher.php:575 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/CloudBootstrapper.php:422 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:117 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Bootstrap/HandleExceptions.php:194 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:173 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:249 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:261 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:280 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:330 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:459 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:477 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:523 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:620 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:668 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:896 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:997 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:1110 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:1122 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/ExceptionReporter.php:1340 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/Illuminate/Foundation/Cloud/Events.php:63 — `catch (Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • + 11 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×27
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:627 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:627-633 | src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:672-676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) types/Database/Eloquent/Builder.php:232 — types/Database/Eloquent/Builder.php:232-236 | types/Database/Query/Builder.php:63-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. Note first that the copies are not typed on the same thing: `Builder` names `Illuminate\Database\Eloquent\Builder` in one and `Illuminate\Database\Query\Builder` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (5 lines × 2) src/Illuminate/Broadcasting/BroadcastManager.php:463 — src/Illuminate/Broadcasting/BroadcastManager.php:463-467 | src/Illuminate/Queue/QueueManager.php:417-421 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) src/Illuminate/Cache/FileStore.php:189 — src/Illuminate/Cache/FileStore.php:189-193 | src/Illuminate/Cache/StorageStore.php:110-114 — before extracting anything, compare `src/Illuminate/Cache/FileStore.php` and `src/Illuminate/Cache/StorageStore.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Illuminate/Collections/Arr.php:849 — src/Illuminate/Collections/Arr.php:849-853 | src/Illuminate/Collections/LazyCollection.php:1921-1925 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Collections/Collection.php:1450 — src/Illuminate/Collections/Collection.php:1450-1454 | src/Illuminate/Collections/LazyCollection.php:1450-1454 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Console/QuestionHelper.php:80 — src/Illuminate/Console/QuestionHelper.php:80-84 | src/Illuminate/Console/View/Components/Mutators/EnsurePunctuation.php:17-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Eloquent/Builder.php:789 — src/Illuminate/Database/Eloquent/Builder.php:789-793 | src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php:300-304 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Eloquent/Casts/AsCollection.php:94 — src/Illuminate/Database/Eloquent/Casts/AsCollection.php:94-98 | src/Illuminate/Database/Eloquent/Casts/AsEncryptedCollection.php:89-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:668 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:668-672 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:215-219 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:951 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:951-955 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:357-361 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Eloquent/Relations/HasOne.php:27 — src/Illuminate/Database/Eloquent/Relations/HasOne.php:27-31 | src/Illuminate/Database/Eloquent/Relations/MorphOne.php:27-31 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/HasOne.php` and `src/Illuminate/Database/Eloquent/Relations/MorphOne.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:67 — src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:67-71 | src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:95-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:79 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:79-83 | src/Illuminate/Database/Query/Grammars/SqlServerGrammar.php:141-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:451 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:451-455 | src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:272-276 — before extracting anything, compare `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:695 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:695-699 | src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:457-461 — before extracting anything, compare `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Schema/Grammars/Grammar.php:208 — src/Illuminate/Database/Schema/Grammars/Grammar.php:208-212 | src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:686-690 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:130 — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:130-134 | src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:143-147 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Illuminate/Foundation/Console/EnvironmentDecryptCommand.php:164 — src/Illuminate/Foundation/Console/EnvironmentDecryptCommand.php:164-168 | src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php:249-253 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:74 — src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:74-78 | src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php:77-81 — before extracting anything, compare `src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php` and `src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Illuminate/Routing/PendingResourceRegistration.php:205 — src/Illuminate/Routing/PendingResourceRegistration.php:205-209 | src/Illuminate/Routing/PendingSingletonResourceRegistration.php:229-233 — before extracting anything, compare `src/Illuminate/Routing/PendingResourceRegistration.php` and `src/Illuminate/Routing/PendingSingletonResourceRegistration.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) src/Illuminate/Validation/Rules/ArrayKeys.php:26 — src/Illuminate/Validation/Rules/ArrayKeys.php:26-30 | src/Illuminate/Validation/Rules/ArrayRule.php:26-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) src/Illuminate/Cache/MemoizedTaggedCache.php:305 — src/Illuminate/Cache/MemoizedTaggedCache.php:305-309 | src/Illuminate/Cache/Repository.php:1082-1086 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/Illuminate/Mail/Transport/SesTransport.php:106 — src/Illuminate/Mail/Transport/SesTransport.php:106-110 | src/Illuminate/Mail/Transport/SesV2Transport.php:114-118 — before extracting anything, compare `src/Illuminate/Mail/Transport/SesTransport.php` and `src/Illuminate/Mail/Transport/SesV2Transport.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:122 — src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:122-126 | src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php:135-139 — before extracting anything, compare `src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php` and `src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • + 2 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×21
  • ClassTooLong: Builder src/Illuminate/Database/Query/Builder.php:37 — ClassTooLong — 1358 significant lines (blank, comment-only and punctuation-only lines excluded), 263 methods. The bar is 400 significant lines; this is 958 over it, 3.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Model src/Illuminate/Database/Eloquent/Model.php:45 — ClassTooLong — 819 significant lines (blank, comment-only and punctuation-only lines excluded), 167 methods. The bar is 400 significant lines; this is 419 over it, 2.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Str src/Illuminate/Support/Str.php:24 — ClassTooLong — 734 significant lines (blank, comment-only and punctuation-only lines excluded), 113 methods. The bar is 400 significant lines; this is 334 over it, 1.84× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Builder src/Illuminate/Database/Eloquent/Builder.php:40 — ClassTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded), 125 methods. The bar is 400 significant lines; this is 313 over it, 1.78× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PendingRequest src/Illuminate/Http/Client/PendingRequest.php:42 — ClassTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded), 103 methods. The bar is 400 significant lines; this is 270 over it, 1.68× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: LazyCollection src/Illuminate/Collections/LazyCollection.php:27 — ClassTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), 109 methods. The bar is 400 significant lines; this is 232 over it, 1.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Mailable src/Illuminate/Mail/Mailable.php:36 — ClassTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods. The bar is 400 significant lines; this is 209 over it, 1.52× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Validator src/Illuminate/Validation/Validator.php:24 — ClassTooLong — 563 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 400 significant lines; this is 163 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Collection src/Illuminate/Collections/Collection.php:24 — ClassTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded), 115 methods. The bar is 400 significant lines; this is 160 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ExceptionReporter src/Illuminate/Foundation/Cloud/ExceptionReporter.php:41 — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Container src/Illuminate/Container/Container.php:26 — ClassTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 88 methods. The bar is 400 significant lines; this is 135 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Connection src/Illuminate/Database/Connection.php:30 — ClassTooLong — 500 significant lines (blank, comment-only and punctuation-only lines excluded), 111 methods. The bar is 400 significant lines; this is 100 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: BelongsToMany src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:35 — ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 102 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Blueprint src/Illuminate/Database/Schema/Blueprint.php:19 — ClassTooLong — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 138 methods. The bar is 400 significant lines; this is 82 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Application src/Illuminate/Foundation/Application.php:40 — ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 104 methods. The bar is 400 significant lines; this is 70 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Route src/Illuminate/Routing/Route.php:35 — ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded), 93 methods. The bar is 400 significant lines; this is 46 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Vite src/Illuminate/Foundation/Vite.php:12 — ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 45 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Grammar src/Illuminate/Database/Query/Grammars/Grammar.php:15 — ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 105 methods. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MySqlGrammar src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:13 — ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 400 significant lines; this is 23 over it, 1.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Arr src/Illuminate/Collections/Arr.php:18 — ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PostgresGrammar src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:11 — ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 86 methods. The bar is 400 significant lines; this is 6 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×19
  • Duplicated block (9 lines × 2) src/Illuminate/Broadcasting/BroadcastManager.php:307 — src/Illuminate/Broadcasting/BroadcastManager.php:307-315 | src/Illuminate/Log/LogManager.php:226-234 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Broadcasting/BroadcastManager.php:307` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/Illuminate/Collections/Arr.php:786 — src/Illuminate/Collections/Arr.php:786-794 | src/Illuminate/Collections/LazyCollection.php:999-1007 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Illuminate/Database/Schema/MariaDbSchemaState.php:17 — src/Illuminate/Database/Schema/MariaDbSchemaState.php:17-25 | src/Illuminate/Database/Schema/MySqlSchemaState.php:76-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:64 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:64-72 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:103-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Illuminate/Auth/DatabaseUserProvider.php:157 — src/Illuminate/Auth/DatabaseUserProvider.php:157-165 | src/Illuminate/Auth/EloquentUserProvider.php:150-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Illuminate/Collections/LazyCollection.php:1360 — src/Illuminate/Collections/LazyCollection.php:1360-1368 | src/Illuminate/Collections/Traits/EnumeratesValues.php:346-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Illuminate/Collections/Traits/TransformsToResourceCollection.php:96 — src/Illuminate/Collections/Traits/TransformsToResourceCollection.php:96-104 | src/Illuminate/Database/Eloquent/Concerns/TransformsToResource.php:89-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1233 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1233-1241 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:731-739 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:651 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:651-659 | src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:411-419 — before extracting anything, compare `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) src/Illuminate/Database/Schema/MySqlBuilder.php:38 — src/Illuminate/Database/Schema/MySqlBuilder.php:38-46 | src/Illuminate/Database/Schema/PostgresBuilder.php:44-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Illuminate/Hashing/ArgonHasher.php:98 — src/Illuminate/Hashing/ArgonHasher.php:98-106 | src/Illuminate/Hashing/BcryptHasher.php:84-92 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Illuminate/Http/Client/Factory.php:274 — src/Illuminate/Http/Client/Factory.php:274-282 | src/Illuminate/Http/Client/PendingRequest.php:1659-1667 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Illuminate/Mail/Mailable.php:1017 — src/Illuminate/Mail/Mailable.php:1017-1025 | src/Illuminate/Notifications/Messages/MailMessage.php:289-297 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) src/Illuminate/Pagination/AbstractCursorPaginator.php:299 — src/Illuminate/Pagination/AbstractCursorPaginator.php:299-307 | src/Illuminate/Pagination/AbstractPaginator.php:229-237 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/Illuminate/Queue/BeanstalkdQueue.php:243 — src/Illuminate/Queue/BeanstalkdQueue.php:243-251 | src/Illuminate/Queue/RedisQueue.php:435-443 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) src/Illuminate/Bus/DebounceLock.php:161 — src/Illuminate/Bus/DebounceLock.php:161-169 | src/Illuminate/Bus/UniqueLock.php:96-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) src/Illuminate/Testing/TestComponent.php:54 — src/Illuminate/Testing/TestComponent.php:54-62 | src/Illuminate/Testing/TestView.php:131-139 — before extracting anything, compare `src/Illuminate/Testing/TestComponent.php` and `src/Illuminate/Testing/TestView.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) src/Illuminate/Testing/TestComponent.php:146 — src/Illuminate/Testing/TestComponent.php:146-154 | src/Illuminate/Testing/TestView.php:223-231 — before extracting anything, compare `src/Illuminate/Testing/TestComponent.php` and `src/Illuminate/Testing/TestView.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) src/Illuminate/Testing/TestResponse.php:1379 — src/Illuminate/Testing/TestResponse.php:1379-1387 | src/Illuminate/Testing/TestView.php:86-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D3 · God Classes · FileTooLong · ×18
  • FileTooLong: Query/Builder.php src/Illuminate/Database/Query/Builder.php — FileTooLong — 1390 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Builder (37-5017). The bar is 500 significant lines; this is 890 over it, 2.78× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Concerns/ValidatesAttributes.php src/Illuminate/Validation/Concerns/ValidatesAttributes.php — FileTooLong — 905 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 405 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Concerns/HasAttributes.php src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php — FileTooLong — 895 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 395 over it, 1.79× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Eloquent/Model.php src/Illuminate/Database/Eloquent/Model.php — FileTooLong — 859 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Model (45-3009). The bar is 500 significant lines; this is 359 over it, 1.72× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Support/Collection.php types/Support/Collection.php — FileTooLong — 786 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 286 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Support/Str.php src/Illuminate/Support/Str.php — FileTooLong — 754 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: Str (24-2354). The bar is 500 significant lines; this is 254 over it, 1.51× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Eloquent/Builder.php src/Illuminate/Database/Eloquent/Builder.php — FileTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Builder (40-2460). The bar is 500 significant lines; this is 239 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Client/PendingRequest.php src/Illuminate/Http/Client/PendingRequest.php — FileTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: PendingRequest (42-2206). The bar is 500 significant lines; this is 205 over it, 1.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Support/LazyCollection.php types/Support/LazyCollection.php — FileTooLong — 650 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 150 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Collections/LazyCollection.php src/Illuminate/Collections/LazyCollection.php — FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: LazyCollection (27-1981). The bar is 500 significant lines; this is 148 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Mail/Mailable.php src/Illuminate/Mail/Mailable.php — FileTooLong — 641 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Mailable (36-1939). The bar is 500 significant lines; this is 141 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Validation/Validator.php src/Illuminate/Validation/Validator.php — FileTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: Validator (24-1827). The bar is 500 significant lines; this is 83 over it, 1.17× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Cloud/ExceptionReporter.php src/Illuminate/Foundation/Cloud/ExceptionReporter.php — FileTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ExceptionReporter (41-1344). The bar is 500 significant lines; this is 80 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Collections/Collection.php src/Illuminate/Collections/Collection.php — FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Collection (24-2034). The bar is 500 significant lines; this is 72 over it, 1.14× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Container/Container.php src/Illuminate/Container/Container.php — FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: Container (26-1896). The bar is 500 significant lines; this is 57 over it, 1.11× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Database/Connection.php src/Illuminate/Database/Connection.php — FileTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Connection (30-1938). The bar is 500 significant lines; this is 25 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Relations/BelongsToMany.php src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php — FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: BelongsToMany (35-1895). The bar is 500 significant lines; this is 12 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: Foundation/Application.php src/Illuminate/Foundation/Application.php — FileTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: Application (40-1744). The bar is 500 significant lines; this is 5 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D15 · Churn × Complexity Hotspots · Repeated repair · ×17
  • Repeated repair: src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:289 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php changed 13 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is BelongsToMany.match at line 289), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Apply fixes from StyleCI (#62140)”; “Fix incrementOrCreate extra attributes on create (#61878)”; “Fix incrementOrCreate on relations (#61849)”; “[13.x] Fix `findOrNew()` and `chunkMap()` on HasManyThrough and BelongsToMany (#61855)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php:230 — src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ResolvesJsonApiElements.compileResourceRelationshipUsingResolver at line 230), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix N+1 queries on JSON:API resource collection includes (#62152)”; “Fix mergeWhen() in JSON:API resource attributes (#62023)”; “Fix N+1 queries on nested JSON:API includes (#62000)”; “Fix resource loading (#61323)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Http/Resources/JsonApi/Concerns/ResolvesJsonApiElements.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Support/Str.php src/Illuminate/Support/Str.php:1906 — src/Illuminate/Support/Str.php changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is Str.substrReplace at line 1906), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix trim strings algorithm”; “[13.x] Fix Str::camel() not lowercasing multibyte first characters (#61545)”; “[13.x] Fix Str::password() returning extra characters and throwing ValueError (#61521)”; “Fix Str::numbers() docblock to reflect array support (#61053)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Support/Str.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Collections/LazyCollection.php src/Illuminate/Collections/LazyCollection.php:986 — src/Illuminate/Collections/LazyCollection.php changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is LazyCollection.select at line 986), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “[13.x] Fix incorrect docblocks (#62097)”; “[13.x] Fix `LazyCollection::take()` with a negative limit larger than the collection (#61659)”; “[13.x] Fix containsStrict() returning false when a closure matches a null value (#61507)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Collections/LazyCollection.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Database/Eloquent/Collection.php src/Illuminate/Database/Eloquent/Collection.php:61 — src/Illuminate/Database/Eloquent/Collection.php changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is Collection.findOrFail at line 61), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Collection findOrFail with a model instance (#61999)”; “[13.x] Fix Eloquent Collection findOrFail() with a collection of ids (#61844)”; “[13.x] Fix `loadMissing()` with nested relations on mixed `morphTo` models (#61845)”; “[13.x] Fix Eloquent Collection duplicates() with a key or callback (#61597)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Collection.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Collections/Arr.php src/Illuminate/Collections/Arr.php:981 — src/Illuminate/Collections/Arr.php changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is Arr.random at line 981), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62097)”; “Fix collapse(), collapseWithKeys() and flatten() dropping lazy collections (#61811)”; “[13.x] Fix `Arr::forget()` removing the wrong element (#61023)”; “Fix null handling in Arr::last() method (#60887)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Collections/Arr.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:485 — src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is HasOneOrManyThrough.findOr at line 485), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incrementOrCreate() on through relations (#61997)”; “[13.x] Fix touch() query generation on HasOneOrManyThrough relations (#61942)”; “[13.x] Fix `findOrNew()` and `chunkMap()` on HasManyThrough and BelongsToMany (#61855)”; “Fix findOrFail() with an array of enum ids (#61765)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Validation/ValidationRuleParser.php src/Illuminate/Validation/ValidationRuleParser.php:126 — src/Illuminate/Validation/ValidationRuleParser.php changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ValidationRuleParser.prepareRule at line 126), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix validation stalling for minutes on large arrays (#60908) (#61232)”; “Revert "[13.x] Add if-related rector rules (#60930)" (#61027)”; “Fix validation stalling for minutes on large arrays (#60908)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Validation/ValidationRuleParser.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Process/PendingProcess.php src/Illuminate/Process/PendingProcess.php:377 — src/Illuminate/Process/PendingProcess.php changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is PendingProcess.resolveSynchronousFake at line 377), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “Fix sub-second process timeouts given as a CarbonInterval (#61979)”; “Fix PendingProcess losing falsy command strings (e.g. '0') on run()/start() (#60947)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Process/PendingProcess.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Queue/CallQueuedHandler.php src/Illuminate/Queue/CallQueuedHandler.php:133 — src/Illuminate/Queue/CallQueuedHandler.php changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is CallQueuedHandler.dispatchThroughMiddleware at line 133), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “Attempt at lock fix (#60906)”; “Revert "Fix ShouldBeUniqueUntilProcessing retries releasing locks they don't …" (#60905)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Queue/CallQueuedHandler.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php:77 — src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is CanBeOneOfMany.ofMany at line 77), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix existence and aggregate queries on self-referencing one-of-many relations (#62043)”; “[13.x] Fix ofMany() alias inside closures (#62051)”; “Revert "[13.x] Add if-related rector rules (#60930)" (#61027)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Cache/MemoizedTaggedCache.php src/Illuminate/Cache/MemoizedTaggedCache.php:80 — src/Illuminate/Cache/MemoizedTaggedCache.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is MemoizedTaggedCache.many at line 80), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “[13.x] Fix incorrect docblocks (#62097)”; “Fix memoized tagged cache many() returning null for numeric keys (#61780)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Cache/MemoizedTaggedCache.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Console/Scheduling/CallbackEvent.php src/Illuminate/Console/Scheduling/CallbackEvent.php:113 — src/Illuminate/Console/Scheduling/CallbackEvent.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is CallbackEvent.execute at line 113), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “[13.x] Fix incorrect docblocks (#62100)”; “[13.x] Fix scheduled callbacks rethrowing a previous exception on later runs (#61973)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Console/Scheduling/CallbackEvent.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Translation/Translator.php src/Illuminate/Translation/Translator.php:151 — src/Illuminate/Translation/Translator.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Translator.get at line 151), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62125)”; “fix translation loading issues”; “fix issues in translation loading”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Translation/Translator.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Filesystem/LocalFilesystemAdapter.php src/Illuminate/Filesystem/LocalFilesystemAdapter.php:39 — src/Illuminate/Filesystem/LocalFilesystemAdapter.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is LocalFilesystemAdapter.providesTemporaryUrls at line 39), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “[13.x] Fix incorrect docblocks (#62100)”; “fix route url generation under certain circumstances”; “fix route url generation under certain circumstances (#61475)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Filesystem/LocalFilesystemAdapter.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php:143 — src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is HasOneThrough.is at line 143), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix has() on self-referencing through one-of-many relations (#62040)”; “[13.x] Fix `HasOneThrough::is()` comparing the wrong keys (#61827)”; “[13.x] Fix `has()` and `withCount()` on `HasOneThrough` one-of-many relations (#61818)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Relations/HasOneThrough.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php:150 — src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is HasOneOrMany.matchOneOrMany at line 150), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix incrementOrCreate extra attributes on create (#61878)”; “Fix incrementOrCreate on relations (#61849)”; “[13.x] Fix `forceCreate()` ignoring `withAttributes()` (#61823)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×17
  • Duplicated block (11 lines × 2) src/Illuminate/Cache/CacheManager.php:141 — src/Illuminate/Cache/CacheManager.php:141-151 | src/Illuminate/Log/LogManager.php:230-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Cache/CacheManager.php:141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Illuminate/Collections/Collection.php:1875 — src/Illuminate/Collections/Collection.php:1875-1885 | src/Illuminate/Collections/Traits/EnumeratesValues.php:972-982 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Illuminate/Collections/Collection.php:1871` calls `is_null`, `newInstance`, `array_unique` and `src/Illuminate/Collections/Traits/EnumeratesValues.php:971` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) src/Illuminate/Console/Scheduling/ScheduleListCommand.php:95 — src/Illuminate/Console/Scheduling/ScheduleListCommand.php:95-105 | src/Illuminate/Console/Scheduling/ScheduleListCommand.php:194-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Query/Builder.php:2641 — src/Illuminate/Database/Query/Builder.php:2641-2651 | src/Illuminate/Database/Query/Builder.php:2678-2688 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Query/Builder.php:4515 — src/Illuminate/Database/Query/Builder.php:4515-4525 | src/Illuminate/Database/Query/Builder.php:4557-4567 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:489 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:489-499 | src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:358-368 — before extracting anything, compare `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:489` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:985 — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:985-995 | src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1092-1102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) src/Illuminate/Foundation/Console/ComponentMakeCommand.php:66 — src/Illuminate/Foundation/Console/ComponentMakeCommand.php:66-76 | src/Illuminate/Foundation/Console/NotificationMakeCommand.php:75-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Console/ComponentMakeCommand.php:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) src/Illuminate/Mail/Transport/CloudflareTransport.php:110 — src/Illuminate/Mail/Transport/CloudflareTransport.php:110-120 | src/Illuminate/Mail/Transport/ResendTransport.php:61-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) src/Illuminate/Mail/Transport/SesTransport.php:56 — src/Illuminate/Mail/Transport/SesTransport.php:56-66 | src/Illuminate/Mail/Transport/SesV2Transport.php:60-70 — before extracting anything, compare `src/Illuminate/Mail/Transport/SesTransport.php` and `src/Illuminate/Mail/Transport/SesV2Transport.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Mail/Transport/SesTransport.php:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Illuminate/Mail/Transport/SesV2Transport.php:59` calls `tenantName` and `src/Illuminate/Mail/Transport/SesTransport.php:55` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) src/Illuminate/Broadcasting/Broadcasters/AblyBroadcaster.php:45 — src/Illuminate/Broadcasting/Broadcasters/AblyBroadcaster.php:45-55 | src/Illuminate/Broadcasting/Broadcasters/PusherBroadcaster.php:84-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Eloquent/Builder.php:717 — src/Illuminate/Database/Eloquent/Builder.php:717-727 | src/Illuminate/Database/Query/Builder.php:3557-3567 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:178 — src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:178-188 | src/Illuminate/Database/Query/Grammars/SqlServerGrammar.php:119-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1223 — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1223-1233 | src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:1096-1106 — before extracting anything, compare `src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php` and `src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1245 — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1245-1255 | src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:1118-1128 — before extracting anything, compare `src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php` and `src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/Illuminate/Process/FakeProcessResult.php:180 — src/Illuminate/Process/FakeProcessResult.php:180-190 | src/Illuminate/Process/ProcessResult.php:128-138 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:137 — src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php:137-147 | src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php:150-160 — before extracting anything, compare `src/Illuminate/Queue/Failed/DatabaseFailedJobProvider.php` and `src/Illuminate/Queue/Failed/DatabaseUuidFailedJobProvider.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×14
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Concerns/BuildsQueries.php:237 — src/Illuminate/Database/Concerns/BuildsQueries.php:237-243 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1170-1176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Builder.php:470 — src/Illuminate/Database/Eloquent/Builder.php:470-476 | src/Illuminate/Database/Eloquent/Builder.php:491-497 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) src/Illuminate/Foundation/Console/LangPublishCommand.php:49 — src/Illuminate/Foundation/Console/LangPublishCommand.php:49-55 | src/Illuminate/Foundation/Console/StubPublishCommand.php:102-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Console/LangPublishCommand.php:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Relations/HasOne.php:53 — src/Illuminate/Database/Eloquent/Relations/HasOne.php:53-59 | src/Illuminate/Database/Eloquent/Relations/MorphOne.php:53-59 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/HasOne.php` and `src/Illuminate/Database/Eloquent/Relations/MorphOne.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:710 — src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:710-716 | src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php:472-478 — before extracting anything, compare `src/Illuminate/Database/Query/Grammars/PostgresGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/Illuminate/Foundation/Console/ChannelListCommand.php:120 — src/Illuminate/Foundation/Console/ChannelListCommand.php:120-126 | src/Illuminate/Foundation/Console/RouteListCommand.php:520-526 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) src/Illuminate/Foundation/Console/TestMakeCommand.php:138 — src/Illuminate/Foundation/Console/TestMakeCommand.php:138-144 | src/Illuminate/Foundation/Console/ViewMakeCommand.php:238-244 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Console/TestMakeCommand.php:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php:25 — src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php:25-31 | src/Illuminate/Foundation/Http/Middleware/TrimStrings.php:45-51 — before extracting anything, compare `src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php` and `src/Illuminate/Foundation/Http/Middleware/TrimStrings.php` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) src/Illuminate/Notifications/NotificationServiceProvider.php:18 — src/Illuminate/Notifications/NotificationServiceProvider.php:18-24 | src/Illuminate/Pagination/PaginationServiceProvider.php:16-22 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) src/Illuminate/Console/Application.php:286 — src/Illuminate/Console/Application.php:286-292 | src/Illuminate/Testing/Fluent/Concerns/Has.php:173-179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/DetectsConcurrencyErrors.php:19 — src/Illuminate/Database/DetectsConcurrencyErrors.php:19-25 | src/Illuminate/Database/DetectsLostConnections.php:19-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Builder.php:2234 — src/Illuminate/Database/Eloquent/Builder.php:2234-2240 | src/Illuminate/Validation/Concerns/FormatsMessages.php:541-550 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) src/Illuminate/Database/Eloquent/Model.php:2102 — src/Illuminate/Database/Eloquent/Model.php:2102-2108 | src/Illuminate/Http/Resources/Json/JsonResource.php:188-194 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/Illuminate/Testing/TestComponent.php:112 — src/Illuminate/Testing/TestComponent.php:112-118 | src/Illuminate/Testing/TestView.php:189-195 — before extracting anything, compare `src/Illuminate/Testing/TestComponent.php` and `src/Illuminate/Testing/TestView.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D35 · Change Coupling · Change coupling · ×9
  • Change coupling: ShowCommand.php ↔ TableCommand.php src/Illuminate/Database/Console/ShowCommand.php:1 — `src/Illuminate/Database/Console/ShowCommand.php` and `src/Illuminate/Database/Console/TableCommand.php` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `4a302604` [13.x] Add Postgres transaction pooler support (#60425); `f0de069d` [11.x] Enhance DB inspection commands (#52501); `bee4fd6e` [10.x] Clean up DBAL deprecations (#45289) — run `git show` on any of them.
  • Change coupling: EnvironmentDecryptCommand.php ↔ EnvironmentEncryptCommand.php src/Illuminate/Foundation/Console/EnvironmentDecryptCommand.php:1 — `src/Illuminate/Foundation/Console/EnvironmentDecryptCommand.php` and `src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `8e3b7dfc` Remove unnecessary dirname calls. (#58984); `e624c2bd` [12.x] Add --readable flag to env:encrypt for visible key names (#58262); `6e951b73` feat: interactive env:encrypt & env:decrypt (#53081) — run `git show` on any of them.
  • Change coupling: MySqlGrammar.php ↔ SQLiteGrammar.php src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:1 — `src/Illuminate/Database/Query/Grammars/MySqlGrammar.php` and `src/Illuminate/Database/Query/Grammars/SQLiteGrammar.php` change together 61% of the time (11 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `8d8465a2` [12.x] Fix/cross database null safe equals (#58962); `1f9aa247` fix grammar; `1dcf0b38` Merge commit from fork — run `git show` on any of them.
  • Change coupling: BelongsToMany.php ↔ HasOneOrMany.php src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1 — `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php` change together 56% of the time (18 of the 32 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 18 shared commits counted here, the most recent 3 are `7778ecf1` Fix incrementOrCreate extra attributes on create (#61878); `41bca847` Fix incrementOrCreate on relations (#61849); `10539d46` [13.x] Allow closure values in updateOrCreate and firstOrNew (#59647) — run `git show` on any of them.
  • Change coupling: BelongsToMany.php ↔ HasManyThrough.php src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1 — `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasManyThrough.php` change together 54% of the time (14 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `535733e1` StyleCI fixes; `f993b9c5` Fix return types of `firstWhere` and `first` of `BelongsToMany` and `…; `94f0192f` [11.x] `afterQuery` hook (#50587) — run `git show` on any of them.
  • Change coupling: DatabaseStore.php ↔ FileStore.php src/Illuminate/Cache/DatabaseStore.php:1 — `src/Illuminate/Cache/DatabaseStore.php` and `src/Illuminate/Cache/FileStore.php` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8f6c56bd` [13.x] Extract flexible cache created-key prefix into a named constan…; `fb71d816` remove compact (#60234); `cb7b49ec` [13.x] Add `flushLocks()` support to Cache stores (#58907) — run `git show` on any of them.
  • Change coupling: SesTransport.php ↔ SesV2Transport.php src/Illuminate/Mail/Transport/SesTransport.php:1 — `src/Illuminate/Mail/Transport/SesTransport.php` and `src/Illuminate/Mail/Transport/SesV2Transport.php` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c9f4de58` Revert "[13.x] Add if-related rector rules (#60930)" (#61027); `0754bff2` [13.x] Add if-related rector rules (#60930); `b2d69918` [11.x] prefer `new Collection()` over `collect()` (#53563) — run `git show` on any of them.
  • Change coupling: ManagesTransactions.php ↔ DatabaseTransactionsManager.php src/Illuminate/Database/Concerns/ManagesTransactions.php:1 — `src/Illuminate/Database/Concerns/ManagesTransactions.php` and `src/Illuminate/Database/DatabaseTransactionsManager.php` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `0b475bbe` Better transaction manager object design (#49103); `2d2d82b3` [10.x] Only stage committed transactions (#49093); `95e924d8` [10.x] Fix how nested transaction callbacks are handled (#48859) — run `git show` on any of them.
  • Change coupling: HasUlids.php ↔ Model.php src/Illuminate/Database/Eloquent/Concerns/HasUlids.php:1 — `src/Illuminate/Database/Eloquent/Concerns/HasUlids.php` and `src/Illuminate/Database/Eloquent/Model.php` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `5e1e3289` [11.x] Use contracts instead of concrete type for (#51425); `9d1d397d` [11.x] Fix return type hint of resolveRouteBindingQuery (#51392); `664c5d63` [10.x] Add Support for SaveQuietly and Upsert with UUID/ULID Primary … — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×8
  • Duplicated block (8 lines × 2) src/Illuminate/Bus/ChainedBatch.php:124 — src/Illuminate/Bus/ChainedBatch.php:124-131 | src/Illuminate/Bus/Queueable.php:341-348 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:400 — src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:400-407 | src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:419-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) src/Illuminate/Foundation/Testing/Concerns/InteractsWithDatabase.php:170 — src/Illuminate/Foundation/Testing/Concerns/InteractsWithDatabase.php:170-177 | src/Illuminate/Foundation/Testing/Concerns/InteractsWithDatabase.php:218-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Testing/Concerns/InteractsWithDatabase.php:170` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) src/Illuminate/Pagination/AbstractCursorPaginator.php:115 — src/Illuminate/Pagination/AbstractCursorPaginator.php:115-122 | src/Illuminate/Pagination/AbstractPaginator.php:193-200 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) src/Illuminate/Process/PendingProcess.php:418 — src/Illuminate/Process/PendingProcess.php:418-425 | src/Illuminate/Process/PendingProcess.php:427-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) src/Illuminate/View/Compilers/Concerns/CompilesStacks.php:39 — src/Illuminate/View/Compilers/Concerns/CompilesStacks.php:39-46 | src/Illuminate/View/Compilers/Concerns/CompilesStacks.php:88-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) src/Illuminate/Routing/PendingResourceRegistration.php:221 — src/Illuminate/Routing/PendingResourceRegistration.php:221-228 | src/Illuminate/Routing/PendingSingletonResourceRegistration.php:245-252 — before extracting anything, compare `src/Illuminate/Routing/PendingResourceRegistration.php` and `src/Illuminate/Routing/PendingSingletonResourceRegistration.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1051 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1051-1058 | src/Illuminate/Database/Eloquent/Relations/MorphToMany.php:183-191 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×7
  • Duplicated block (15 lines × 2) src/Illuminate/Database/Eloquent/Casts/AsCollection.php:50 — src/Illuminate/Database/Eloquent/Casts/AsCollection.php:50-64 | src/Illuminate/Database/Eloquent/Casts/AsEncryptedCollection.php:45-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Casts/AsCollection.php:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) src/Illuminate/Foundation/Console/MailMakeCommand.php:83 — src/Illuminate/Foundation/Console/MailMakeCommand.php:83-97 | src/Illuminate/Foundation/Console/MailMakeCommand.php:111-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) src/Illuminate/Redis/Connectors/PhpRedisConnector.php:95 — src/Illuminate/Redis/Connectors/PhpRedisConnector.php:95-109 | src/Illuminate/Redis/Connectors/PhpRedisConnector.php:248-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) src/Illuminate/Redis/Connectors/PhpRedisConnector.php:139 — src/Illuminate/Redis/Connectors/PhpRedisConnector.php:139-153 | src/Illuminate/Redis/Connectors/PhpRedisConnector.php:232-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) src/Illuminate/Routing/PendingResourceRegistration.php:180 — src/Illuminate/Routing/PendingResourceRegistration.php:180-194 | src/Illuminate/Routing/PendingSingletonResourceRegistration.php:204-218 — before extracting anything, compare `src/Illuminate/Routing/PendingResourceRegistration.php` and `src/Illuminate/Routing/PendingSingletonResourceRegistration.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (15 lines × 2) src/Illuminate/Testing/Constraints/NotSoftDeletedInDatabase.php:88 — src/Illuminate/Testing/Constraints/NotSoftDeletedInDatabase.php:88-102 | src/Illuminate/Testing/Constraints/SoftDeletedInDatabase.php:90-104 — before extracting anything, compare `src/Illuminate/Testing/Constraints/NotSoftDeletedInDatabase.php` and `src/Illuminate/Testing/Constraints/SoftDeletedInDatabase.php` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (15 lines × 2) src/Illuminate/Testing/TestResponse.php:1207 — src/Illuminate/Testing/TestResponse.php:1207-1221 | src/Illuminate/Testing/TestResponse.php:1474-1488 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Illuminate/Testing/TestResponse.php:1205` calls `get` and `src/Illuminate/Testing/TestResponse.php:1472` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×7
  • Duplicated block (13 lines × 2) src/Illuminate/Bus/DatabaseBatchRepository.php:243 — src/Illuminate/Bus/DatabaseBatchRepository.php:243-255 | src/Illuminate/Bus/DatabaseBatchRepository.php:289-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) src/Illuminate/Container/Util.php:62 — src/Illuminate/Container/Util.php:62-74 | src/Illuminate/Reflection/Reflector.php:157-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) src/Illuminate/Database/Console/ShowCommand.php:209 — src/Illuminate/Database/Console/ShowCommand.php:209-221 | src/Illuminate/Database/Console/ShowCommand.php:225-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Console/ShowCommand.php:209` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Illuminate/Foundation/Testing/DatabaseTransactions.php:23 — src/Illuminate/Foundation/Testing/DatabaseTransactions.php:23-35 | src/Illuminate/Foundation/Testing/RefreshDatabase.php:144-156 — before extracting anything, compare `src/Illuminate/Foundation/Testing/DatabaseTransactions.php` and `src/Illuminate/Foundation/Testing/RefreshDatabase.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Testing/DatabaseTransactions.php:23` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) src/Illuminate/Redis/Connections/PhpRedisConnection.php:482 — src/Illuminate/Redis/Connections/PhpRedisConnection.php:482-494 | src/Illuminate/Redis/Connections/PhpRedisConnection.php:507-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (13 lines × 2) src/Illuminate/Testing/Fluent/Concerns/Matching.php:29 — src/Illuminate/Testing/Fluent/Concerns/Matching.php:29-41 | src/Illuminate/Testing/Fluent/Concerns/Matching.php:67-79 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Testing/Fluent/Concerns/Matching.php:29` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (13 lines × 2) src/Illuminate/Foundation/Console/EnumMakeCommand.php:112 — src/Illuminate/Foundation/Console/EnumMakeCommand.php:112-124 | src/Illuminate/Foundation/Console/MailMakeCommand.php:230-242 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D15 · Churn × Complexity Hotspots · Hotspot · ×6
  • Hotspot: src/Illuminate/Database/Eloquent/Model.php src/Illuminate/Database/Eloquent/Model.php:445 — src/Illuminate/Database/Eloquent/Model.php changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Model.initializeModelAttributes at line 445. 2 of those changes were fix/bug commits, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Eloquent/Model.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Illuminate/Http/Client/PendingRequest.php src/Illuminate/Http/Client/PendingRequest.php:1056 — src/Illuminate/Http/Client/PendingRequest.php changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in PendingRequest.send at line 1056. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Http/Client/PendingRequest.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Illuminate/Queue/SqsQueue.php src/Illuminate/Queue/SqsQueue.php:581 — src/Illuminate/Queue/SqsQueue.php changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in SqsQueue.getQueueableOptions at line 581. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Queue/SqsQueue.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Illuminate/Image/Drivers/InterventionDriver.php src/Illuminate/Image/Drivers/InterventionDriver.php:80 — src/Illuminate/Image/Drivers/InterventionDriver.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in InterventionDriver.process at line 80. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Image/Drivers/InterventionDriver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Illuminate/Events/Dispatcher.php src/Illuminate/Events/Dispatcher.php:661 — src/Illuminate/Events/Dispatcher.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Dispatcher.queueHandler at line 661. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Events/Dispatcher.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: src/Illuminate/Database/Connectors/SqlServerConnector.php src/Illuminate/Database/Connectors/SqlServerConnector.php:126 — src/Illuminate/Database/Connectors/SqlServerConnector.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SqlServerConnector.getSqlSrvDsn at line 126. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 14:45:07 -07:00' --until='2026-10-22 14:45:07 -07:00' --full-history --no-merges -- src/Illuminate/Database/Connectors/SqlServerConnector.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) src/Illuminate/Bus/Batch.php:125 — src/Illuminate/Bus/Batch.php:125-134 | src/Illuminate/Support/Testing/Fakes/BatchFake.php:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) src/Illuminate/Collections/LazyCollection.php:953 — src/Illuminate/Collections/LazyCollection.php:953-962 | src/Illuminate/Collections/LazyCollection.php:988-997 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Collections/LazyCollection.php:953` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Illuminate/Database/Eloquent/Factories/Factory.php:292 — src/Illuminate/Database/Eloquent/Factories/Factory.php:292-301 | src/Illuminate/Database/Eloquent/Factories/Factory.php:471-480 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Factories/Factory.php:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `int|iterable|null $records =` in one and `iterable|int|null $records =` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) src/Illuminate/Routing/Route.php:1206 — src/Illuminate/Routing/Route.php:1206-1215 | src/Illuminate/Routing/Route.php:1271-1280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Routing/Route.php:1206` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:880 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:880-889 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:903-912 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Concerns/ValidatesAttributes.php:880` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1309 — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1309-1318 | src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:1140-1149 — before extracting anything, compare `src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php` and `src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D5 · Coupling · Off the main sequence · ×6
  • Off the main sequence: illuminate/conditionable — illuminate/conditionable: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
  • Off the main sequence: illuminate/macroable — illuminate/macroable: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
  • Off the main sequence: illuminate/container — illuminate/container: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: illuminate/reflection — illuminate/reflection: abstractness 0.00, instability 0.18, distance 0.82 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: illuminate/support — illuminate/support: abstractness 0.05, instability 0.15, distance 0.80 — zone of pain — concrete and depended on by 28 project(s), so it's rigid to change.
  • Off the main sequence: illuminate/collections — illuminate/collections: abstractness 0.11, instability 0.11, distance 0.78 — zone of pain — concrete and depended on by 25 project(s), so it's rigid to change.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×5
  • Duplicated block (12 lines × 2) src/Illuminate/Broadcasting/BroadcastManager.php:83 — src/Illuminate/Broadcasting/BroadcastManager.php:83-94 | src/Illuminate/Broadcasting/BroadcastManager.php:105-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Broadcasting/BroadcastManager.php:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Illuminate/Queue/Console/PauseCommand.php:48 — src/Illuminate/Queue/Console/PauseCommand.php:48-59 | src/Illuminate/Queue/Console/ResumeCommand.php:48-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Queue/Console/PauseCommand.php:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) src/Illuminate/Foundation/Console/ObserverMakeCommand.php:145 — src/Illuminate/Foundation/Console/ObserverMakeCommand.php:145-156 | src/Illuminate/Foundation/Console/PolicyMakeCommand.php:204-215 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) src/Illuminate/Foundation/Console/Kernel.php:254 — src/Illuminate/Foundation/Console/Kernel.php:254-265 | src/Illuminate/Foundation/Http/Kernel.php:274-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) src/Illuminate/Testing/TestResponse.php:1143 — src/Illuminate/Testing/TestResponse.php:1143-1154 | src/Illuminate/Testing/TestResponse.php:1567-1578 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark src/Illuminate/Foundation/Exceptions/views/layout.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/Illuminate/Foundation/resources/exceptions/renderer/components/layout.blade.php:3 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/Illuminate/Foundation/resources/health-up.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark src/Illuminate/Mail/resources/views/html/layout.blade.php:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D3 · God Classes · MethodTooLong · ×4
  • MethodTooLong: Builder.test types/Database/Eloquent/Builder.php:16 — MethodTooLong — test runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MessageSelector.getPluralIndex src/Illuminate/Translation/MessageSelector.php:110 — MethodTooLong — getPluralIndex runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Vite.__invoke src/Illuminate/Foundation/Vite.php:384 — MethodTooLong — __invoke runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Relations.test types/Database/Eloquent/Relations.php:21 — MethodTooLong — test runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D31 · IaC & Container Security · Medium IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×4
  • Duplicated block (16 lines × 2) src/Illuminate/Foundation/Exceptions/Renderer/Mappers/BladeMapper.php:233 — src/Illuminate/Foundation/Exceptions/Renderer/Mappers/BladeMapper.php:233-248 | src/Illuminate/Foundation/Exceptions/Renderer/Mappers/BladeMapper.php:259-274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (16 lines × 2) src/Illuminate/Queue/Middleware/ThrottlesExceptions.php:122 — src/Illuminate/Queue/Middleware/ThrottlesExceptions.php:122-137 | src/Illuminate/Queue/Middleware/ThrottlesExceptionsWithRedis.php:63-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Queue/Middleware/ThrottlesExceptions.php:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) src/Illuminate/Support/Composer.php:66 — src/Illuminate/Support/Composer.php:66-81 | src/Illuminate/Support/Composer.php:95-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) src/Illuminate/Foundation/Console/CastMakeCommand.php:42 — src/Illuminate/Foundation/Console/CastMakeCommand.php:42-68 | src/Illuminate/Foundation/Console/ClassMakeCommand.php:42-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Console/CastMakeCommand.php:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×4
  • Duplicated block (5 lines × 3) src/Illuminate/Cache/ArrayStore.php:320 — src/Illuminate/Cache/ArrayStore.php:320-324 | src/Illuminate/Cache/FileStore.php:444-448 | src/Illuminate/Cache/StorageStore.php:239-243 — before extracting anything, compare `src/Illuminate/Cache/FileStore.php` and `src/Illuminate/Cache/StorageStore.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 3) src/Illuminate/Database/Query/Grammars/Grammar.php:1005 — src/Illuminate/Database/Query/Grammars/Grammar.php:1005-1009 | src/Illuminate/Database/Query/Grammars/PostgresGrammar.php:362-366 | src/Illuminate/Database/Query/Grammars/SqlServerGrammar.php:287-291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) src/Illuminate/Foundation/Console/EnumMakeCommand.php:75 — src/Illuminate/Foundation/Console/EnumMakeCommand.php:75-79 | src/Illuminate/Foundation/Console/InterfaceMakeCommand.php:52-56 | src/Illuminate/Foundation/Console/TraitMakeCommand.php:65-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (5 lines × 3) src/Illuminate/Filesystem/FilesystemAdapter.php:1227 — src/Illuminate/Filesystem/FilesystemAdapter.php:1227-1231 | src/Illuminate/Testing/TestComponent.php:220-224 | src/Illuminate/Testing/TestResponse.php:2087-2091 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×4
  • Outbound HTTP without resilience src/Illuminate/Broadcasting/Mercure/CreatesMercureDrivers.php:91 — `HttpClient::create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience src/Illuminate/Mail/MailManager.php:500 — `HttpClient::create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience src/Illuminate/Mail/Transport/CloudflareTransport.php:35 — `HttpClient::create(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience src/Illuminate/Mail/Transport/CloudflareTransport.php:46 — `->request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC4 · Keyboard semantics · Anchor without href · ×3
  • Anchor without href src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:5 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:14 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href src/Illuminate/Pagination/resources/views/semantic-ui.blade.php:33 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×3
  • Duplicated block (21 lines × 2) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:891 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:891-911 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:487-507 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) src/Illuminate/Validation/Rules/Contains.php:26 — src/Illuminate/Validation/Rules/Contains.php:26-46 | src/Illuminate/Validation/Rules/DoesntContain.php:26-46 — before extracting anything, compare `src/Illuminate/Validation/Rules/Contains.php` and `src/Illuminate/Validation/Rules/DoesntContain.php` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Rules/Contains.php:26` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (21 lines × 2) src/Illuminate/Validation/Rules/In.php:33 — src/Illuminate/Validation/Rules/In.php:33-55 | src/Illuminate/Validation/Rules/NotIn.php:33-53 — before extracting anything, compare `src/Illuminate/Validation/Rules/In.php` and `src/Illuminate/Validation/Rules/NotIn.php` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Rules/In.php:33` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×3
  • Duplicated block (17 lines × 2) src/Illuminate/Database/Schema/Grammars/Grammar.php:278 — src/Illuminate/Database/Schema/Grammars/Grammar.php:278-294 | src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php:270-286 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Schema/Grammars/Grammar.php:278` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (17 lines × 2) src/Illuminate/Foundation/Vite.php:422 — src/Illuminate/Foundation/Vite.php:422-438 | src/Illuminate/Foundation/Vite.php:448-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Vite.php:422` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:307 — src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:307-323 | src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:340-356 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:510 — src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:510-518 | src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:553-561 | src/Illuminate/Database/Query/Grammars/MySqlGrammar.php:580-588 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 3) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:856 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:856-864 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:879-887 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:902-910 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Concerns/ValidatesAttributes.php:856` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 3) src/Illuminate/Validation/Rules/Email.php:72 — src/Illuminate/Validation/Rules/Email.php:72-80 | src/Illuminate/Validation/Rules/File.php:101-109 | src/Illuminate/Validation/Rules/Password.php:150-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) src/Illuminate/Foundation/Console/OptimizeClearCommand.php:35 — src/Illuminate/Foundation/Console/OptimizeClearCommand.php:35-41 | src/Illuminate/Foundation/Console/OptimizeCommand.php:35-41 | src/Illuminate/Foundation/Console/ReloadCommand.php:35-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (7 lines × 3) types/Database/Eloquent/Builder.php:192 — types/Database/Eloquent/Builder.php:192-198 | types/Database/Eloquent/Builder.php:207-213 | types/Database/Eloquent/Builder.php:222-228 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 3) src/Illuminate/Database/Concerns/BuildsQueries.php:115 — src/Illuminate/Database/Concerns/BuildsQueries.php:115-121 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1213-1219 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:711-717 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php:660 — src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php:660-665 | src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php:706-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php:660` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/Illuminate/Queue/DatabaseQueue.php:197 — src/Illuminate/Queue/DatabaseQueue.php:197-202 | src/Illuminate/Queue/DatabaseQueue.php:213-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) src/Illuminate/Support/Testing/Fakes/NotificationFake.php:257 — src/Illuminate/Support/Testing/Fakes/NotificationFake.php:257-262 | src/Illuminate/Support/Testing/Fakes/QueueFake.php:361-366 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Illuminate/Database/Query/Builder.php:1864 — src/Illuminate/Database/Query/Builder.php:1864-1881 | src/Illuminate/Database/Query/Builder.php:1912-1929 | src/Illuminate/Database/Query/Builder.php:1960-1981 | src/Illuminate/Database/Query/Builder.php:2012-2033 | src/Illuminate/Database/Query/Builder.php:2064-2081 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) src/Illuminate/Validation/Rules/DeclinedIf.php:30 — src/Illuminate/Validation/Rules/DeclinedIf.php:30-37 | src/Illuminate/Validation/Rules/MissingIf.php:30-37 | src/Illuminate/Validation/Rules/MissingUnless.php:30-37 | src/Illuminate/Validation/Rules/PresentIf.php:30-37 | src/Illuminate/Validation/Rules/PresentUnless.php:30-37 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:858 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:858-872 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:891-911 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:454-468 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:487-507 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/Illuminate/Queue/BeanstalkdQueue.php:310 — src/Illuminate/Queue/BeanstalkdQueue.php:310-318 | src/Illuminate/Queue/FailoverQueue.php:241-249 | src/Illuminate/Queue/RedisQueue.php:352-372 | src/Illuminate/Support/Testing/Fakes/QueueFake.php:842-850 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) types/Database/Eloquent/Builder.php:164 — types/Database/Eloquent/Builder.php:164-186 | types/Database/Query/Builder.php:40-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (23 lines × 2) src/Illuminate/Validation/Rules/RequiredIf.php:27 — src/Illuminate/Validation/Rules/RequiredIf.php:27-49 | src/Illuminate/Validation/Rules/RequiredUnless.php:27-49 — before extracting anything, compare `src/Illuminate/Validation/Rules/RequiredIf.php` and `src/Illuminate/Validation/Rules/RequiredUnless.php` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Rules/RequiredIf.php:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) src/Illuminate/Database/Eloquent/Model.php:1756 — src/Illuminate/Database/Eloquent/Model.php:1756-1775 | src/Illuminate/Database/Eloquent/SoftDeletes.php:86-105 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (20 lines × 2) src/Illuminate/Database/Query/Builder.php:1962 — src/Illuminate/Database/Query/Builder.php:1962-1981 | src/Illuminate/Database/Query/Builder.php:2014-2033 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Query/Builder.php:1962` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) src/Illuminate/Cache/Limiters/ConcurrencyLimiter.php:69 — src/Illuminate/Cache/Limiters/ConcurrencyLimiter.php:69-82 | src/Illuminate/Redis/Limiters/ConcurrencyLimiter.php:78-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Cache/Limiters/ConcurrencyLimiter.php:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) src/Illuminate/Database/Eloquent/Builder.php:1246 — src/Illuminate/Database/Eloquent/Builder.php:1246-1259 | src/Illuminate/Database/Query/Builder.php:3745-3758 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Builder.php:1246` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:307 — src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:307-317 | src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:340-350 | src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:371-381 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:320` calls `value` and `src/Illuminate/Http/Resources/ConditionallyLoadsAttributes.php:383` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 3) src/Illuminate/Database/Eloquent/Builder.php:843 — src/Illuminate/Database/Eloquent/Builder.php:843-853 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:969-979 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:375-385 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) src/Illuminate/Queue/BeanstalkdQueue.php:311 — src/Illuminate/Queue/BeanstalkdQueue.php:311-318 | src/Illuminate/Queue/FailoverQueue.php:242-249 | src/Illuminate/Queue/RedisQueue.php:356-363 | src/Illuminate/Support/Testing/Fakes/QueueFake.php:843-850 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Queue/BeanstalkdQueue.php:311` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Illuminate/Queue/RedisQueue.php:352` calls `getConnection`, `use` and `src/Illuminate/Queue/BeanstalkdQueue.php:309` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 4) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1321 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1321-1328 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1368-1375 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1415-1422 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1462-1469 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) src/Illuminate/Foundation/Console/OptimizeClearCommand.php:44 — src/Illuminate/Foundation/Console/OptimizeClearCommand.php:44-51 | src/Illuminate/Foundation/Console/OptimizeCommand.php:44-51 | src/Illuminate/Foundation/Console/ReloadCommand.php:44-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
  • Duplicated block (8 lines × 3) src/Illuminate/Support/Testing/Fakes/BusFake.php:270 — src/Illuminate/Support/Testing/Fakes/BusFake.php:270-277 | src/Illuminate/Support/Testing/Fakes/BusFake.php:339-346 | src/Illuminate/Support/Testing/Fakes/EventFake.php:191-198 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×1
  • Animation without a prefers-reduced-motion guard src/Illuminate/Foundation/resources/health-up.blade.php:27 — <span> moves — its `animate-ping` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 61 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · MessageSelector.getPluralIndex (cyclomatic 335) · ×1
  • MessageSelector.getPluralIndex (cyclomatic 335) src/Illuminate/Translation/MessageSelector.php:110 — MessageSelector.getPluralIndex has cyclomatic complexity 335 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · RouteUrlGenerator.formatParameters (cyclomatic 29) · ×1
  • RouteUrlGenerator.formatParameters (cyclomatic 29) src/Illuminate/Routing/RouteUrlGenerator.php:184 — RouteUrlGenerator.formatParameters has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · EnvironmentEncryptCommand.handle (cyclomatic 26) · ×1
  • EnvironmentEncryptCommand.handle (cyclomatic 26) src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php:63 — EnvironmentEncryptCommand.handle has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · InterventionDriver.process (cyclomatic 26) · ×1
  • InterventionDriver.process (cyclomatic 26) src/Illuminate/Image/Drivers/InterventionDriver.php:80 — InterventionDriver.process has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · HasAttributes.originalIsEquivalent (cyclomatic 25) · ×1
  • HasAttributes.originalIsEquivalent (cyclomatic 25) src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php:2389 — HasAttributes.originalIsEquivalent has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: HasAttributes.castAttribute (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · BlueprintState.update (cyclomatic 24) · ×1
  • BlueprintState.update (cyclomatic 24) src/Illuminate/Database/Schema/BlueprintState.php:154 — BlueprintState.update has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · Batch.send (cyclomatic 23) · ×1
  • Batch.send (cyclomatic 23) src/Illuminate/Http/Client/Batch.php:265 — Batch.send has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RouteListCommand.filterRoute (cyclomatic 22) · ×1
  • RouteListCommand.filterRoute (cyclomatic 22) src/Illuminate/Foundation/Console/RouteListCommand.php:319 — RouteListCommand.filterRoute has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · PendingRequest.send (cyclomatic 22) · ×1
  • PendingRequest.send (cyclomatic 22) src/Illuminate/Http/Client/PendingRequest.php:1056 — PendingRequest.send has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PhpRedisConnector.createClient (cyclomatic 22) · ×1
  • PhpRedisConnector.createClient (cyclomatic 22) src/Illuminate/Redis/Connectors/PhpRedisConnector.php:82 — PhpRedisConnector.createClient has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Serializer.serialize (cyclomatic 20) · ×1
  • Serializer.serialize (cyclomatic 20) src/Illuminate/JsonSchema/Serializer.php:23 — Serializer.serialize has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ShowCommand.displayForCli (cyclomatic 19) · ×1
  • ShowCommand.displayForCli (cyclomatic 19) src/Illuminate/Database/Console/ShowCommand.php:159 — ShowCommand.displayForCli has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PendingRequest.handlePromiseResponse (cyclomatic 19) · ×1
  • PendingRequest.handlePromiseResponse (cyclomatic 19) src/Illuminate/Http/Client/PendingRequest.php:1310 — PendingRequest.handlePromiseResponse has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Password.passes (cyclomatic 19) · ×1
  • Password.passes (cyclomatic 19) src/Illuminate/Validation/Rules/Password.php:336 — Password.passes has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · CronExpressionTimezoneConverter.shiftDaysOfMonth (cyclomatic 18) · ×1
  • CronExpressionTimezoneConverter.shiftDaysOfMonth (cyclomatic 18) src/Illuminate/Console/Scheduling/CronExpressionTimezoneConverter.php:176 — CronExpressionTimezoneConverter.shiftDaysOfMonth has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SqlServerConnector.getSqlSrvDsn (cyclomatic 18) · ×1
  • SqlServerConnector.getSqlSrvDsn (cyclomatic 18) src/Illuminate/Database/Connectors/SqlServerConnector.php:126 — SqlServerConnector.getSqlSrvDsn has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Builder.where (cyclomatic 18) · ×1
  • Builder.where (cyclomatic 18) src/Illuminate/Database/Query/Builder.php:931 — Builder.where has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PhpRedisClusterConnection.scan (cyclomatic 18) · ×1
  • PhpRedisClusterConnection.scan (cyclomatic 18) src/Illuminate/Redis/Connections/PhpRedisClusterConnection.php:26 — PhpRedisClusterConnection.scan has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · HasAttributes.addCastAttributesToArray (cyclomatic 17) · ×1
  • HasAttributes.addCastAttributesToArray (cyclomatic 17) src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php:310 — HasAttributes.addCastAttributesToArray has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: HasAttributes.castAttribute (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · Model.initializeModelAttributes (cyclomatic 17) · ×1
  • Model.initializeModelAttributes (cyclomatic 17) src/Illuminate/Database/Eloquent/Model.php:445 — Model.initializeModelAttributes has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Dispatcher.queueHandler (cyclomatic 17) · ×1
  • Dispatcher.queueHandler (cyclomatic 17) src/Illuminate/Events/Dispatcher.php:661 — Dispatcher.queueHandler has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ApplicationBuilder.buildRoutingCallback (cyclomatic 17) · ×1
  • ApplicationBuilder.buildRoutingCallback (cyclomatic 17) src/Illuminate/Foundation/Configuration/ApplicationBuilder.php:200 — ApplicationBuilder.buildRoutingCallback has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NotificationSender.queueNotification (cyclomatic 16) · ×1
  • NotificationSender.queueNotification (cyclomatic 16) src/Illuminate/Notifications/NotificationSender.php:225 — NotificationSender.queueNotification has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PhpRedisConnector.createRedisClusterInstance (cyclomatic 16) · ×1
  • PhpRedisConnector.createRedisClusterInstance (cyclomatic 16) src/Illuminate/Redis/Connectors/PhpRedisConnector.php:199 — PhpRedisConnector.createRedisClusterInstance has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · MessageSelector.getPluralIndex (cognitive 86) · ×1
  • MessageSelector.getPluralIndex (cognitive 86) src/Illuminate/Translation/MessageSelector.php:110 — MessageSelector.getPluralIndex has cognitive complexity 86 (threshold 15). Drivers by points: ternaries 31 (62 pts), boolean chains 22, if/else 1, match/switch 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RouteUrlGenerator.formatParameters (cognitive 47) · ×1
  • RouteUrlGenerator.formatParameters (cognitive 47) src/Illuminate/Routing/RouteUrlGenerator.php:184 — RouteUrlGenerator.formatParameters has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 6 (8 pts), ternaries 3 (6 pts), boolean chains 5 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NotificationSender.queueNotification (cognitive 42) · ×1
  • NotificationSender.queueNotification (cognitive 42) src/Illuminate/Notifications/NotificationSender.php:225 — NotificationSender.queueNotification has cognitive complexity 42 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 6 (18 pts), loops 2 (3 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CronExpressionTimezoneConverter.shiftDaysOfMonth (cognitive 38) · ×1
  • CronExpressionTimezoneConverter.shiftDaysOfMonth (cognitive 38) src/Illuminate/Console/Scheduling/CronExpressionTimezoneConverter.php:176 — CronExpressionTimezoneConverter.shiftDaysOfMonth has cognitive complexity 38 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 5 (10 pts), ternaries 4 (10 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Batch.send (cognitive 37) · ×1
  • Batch.send (cognitive 37) src/Illuminate/Http/Client/Batch.php:265 — Batch.send has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 8, ternaries 2 (6 pts), loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShowCommand.displayForCli (cognitive 31) · ×1
  • ShowCommand.displayForCli (cognitive 31) src/Illuminate/Database/Console/ShowCommand.php:159 — ShowCommand.displayForCli has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 10 (20 pts), if/else 6 (9 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationBuilder.buildRoutingCallback (cognitive 30) · ×1
  • ApplicationBuilder.buildRoutingCallback (cognitive 30) src/Illuminate/Foundation/Configuration/ApplicationBuilder.php:200 — ApplicationBuilder.buildRoutingCallback has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 3 (7 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueriesRelationships.withAggregate (cognitive 29) · ×1
  • QueriesRelationships.withAggregate (cognitive 29) src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php:864 — QueriesRelationships.withAggregate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 4 (11 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScheduleRunCommand.repeatEvents (cognitive 28) · ×1
  • ScheduleRunCommand.repeatEvents (cognitive 28) src/Illuminate/Console/Scheduling/ScheduleRunCommand.php:239 — ScheduleRunCommand.repeatEvents has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PhpRedisClusterConnection.scan (cognitive 28) · ×1
  • PhpRedisClusterConnection.scan (cognitive 28) src/Illuminate/Redis/Connections/PhpRedisClusterConnection.php:26 — PhpRedisClusterConnection.scan has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FormatsMessages.getFromLocalArray (cognitive 27) · ×1
  • FormatsMessages.getFromLocalArray (cognitive 27) src/Illuminate/Validation/Concerns/FormatsMessages.php:100 — FormatsMessages.getFromLocalArray has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EnvironmentEncryptCommand.handle (cognitive 26) · ×1
  • EnvironmentEncryptCommand.handle (cognitive 26) src/Illuminate/Foundation/Console/EnvironmentEncryptCommand.php:63 — EnvironmentEncryptCommand.handle has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, ternaries 5, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Collection.sortByMany (cognitive 25) · ×1
  • Collection.sortByMany (cognitive 25) src/Illuminate/Collections/Collection.php:1650 — Collection.sortByMany has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), match/switch 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HasAttributes.addCastAttributesToArray (cognitive 25) · ×1
  • HasAttributes.addCastAttributesToArray (cognitive 25) src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php:310 — HasAttributes.addCastAttributesToArray has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 7, ternaries 1 (3 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RouteListCommand.filterRoute (cognitive 24) · ×1
  • RouteListCommand.filterRoute (cognitive 24) src/Illuminate/Foundation/Console/RouteListCommand.php:319 — RouteListCommand.filterRoute has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 17, if/else 3 (5 pts), loops 1 (2 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · PreventRequestsDuringMaintenance.handle (cognitive 24) · ×1
  • PreventRequestsDuringMaintenance.handle (cognitive 24) src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php:59 — PreventRequestsDuringMaintenance.handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PhpRedisConnector.createClient (cognitive 24) · ×1
  • PhpRedisConnector.createClient (cognitive 24) src/Illuminate/Redis/Connectors/PhpRedisConnector.php:82 — PhpRedisConnector.createClient has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Blueprint.addFluentIndexes (cognitive 23) · ×1
  • Blueprint.addFluentIndexes (cognitive 23) src/Illuminate/Database/Schema/Blueprint.php:216 — Blueprint.addFluentIndexes has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 2 (8 pts), boolean chains 6, if/else 2 (6 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResendTransport.doSend (cognitive 23) · ×1
  • ResendTransport.doSend (cognitive 23) src/Illuminate/Mail/Transport/ResendTransport.php:55 — ResendTransport.doSend has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConfiguresPrompts.promptUntilValid (cognitive 22) · ×1
  • ConfiguresPrompts.promptUntilValid (cognitive 22) src/Illuminate/Console/Concerns/ConfiguresPrompts.php:138 — ConfiguresPrompts.promptUntilValid has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BuildsQueries.paginateUsingCursor (cognitive 22) · ×1
  • BuildsQueries.paginateUsingCursor (cognitive 22) src/Illuminate/Database/Concerns/BuildsQueries.php:483 — BuildsQueries.paginateUsingCursor has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 5 (8 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BlueprintState.update (cognitive 22) · ×1
  • BlueprintState.update (cognitive 22) src/Illuminate/Database/Schema/BlueprintState.php:154 — BlueprintState.update has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 5 (10 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Deserializer.normalizeUnions (cognitive 22) · ×1
  • Deserializer.normalizeUnions (cognitive 22) src/Illuminate/JsonSchema/Deserializer.php:472 — Deserializer.normalizeUnions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PendingRequest.send (cognitive 21) · ×1
  • PendingRequest.send (cognitive 21) src/Illuminate/Http/Client/PendingRequest.php:1056 — PendingRequest.send has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 4, error handling 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Serializer.serialize (cognitive 21) · ×1
  • Serializer.serialize (cognitive 21) src/Illuminate/JsonSchema/Serializer.php:23 — Serializer.serialize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Worker.daemon (cognitive 21) · ×1
  • Worker.daemon (cognitive 21) src/Illuminate/Queue/Worker.php:240 — Worker.daemon has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EventFake.assertListening (cognitive 21) · ×1
  • EventFake.assertListening (cognitive 21) src/Illuminate/Support/Testing/Fakes/EventFake.php:85 — EventFake.assertListening has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 1 (5 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CronExpressionTimezoneConverter.expand (cognitive 20) · ×1
  • CronExpressionTimezoneConverter.expand (cognitive 20) src/Illuminate/Console/Scheduling/CronExpressionTimezoneConverter.php:294 — CronExpressionTimezoneConverter.expand has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BroadcastingInstallCommand.handle (cognitive 20) · ×1
  • BroadcastingInstallCommand.handle (cognitive 20) src/Illuminate/Foundation/Console/BroadcastingInstallCommand.php:81 — BroadcastingInstallCommand.handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PendingRequest.handlePromiseResponse (cognitive 20) · ×1
  • PendingRequest.handlePromiseResponse (cognitive 20) src/Illuminate/Http/Client/PendingRequest.php:1310 — PendingRequest.handlePromiseResponse has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 7, if/else 5, ternaries 4 (5 pts), error handling 2 (3 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ImplicitRouteBinding.resolveForRoute (cognitive 20) · ×1
  • ImplicitRouteBinding.resolveForRoute (cognitive 20) src/Illuminate/Routing/ImplicitRouteBinding.php:23 — ImplicitRouteBinding.resolveForRoute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MercureBroadcaster.auth (cognitive 19) · ×1
  • MercureBroadcaster.auth (cognitive 19) src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php:89 — MercureBroadcaster.auth has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BuildsQueries.orderedLazyById (cognitive 19) · ×1
  • BuildsQueries.orderedLazyById (cognitive 19) src/Illuminate/Database/Concerns/BuildsQueries.php:342 — BuildsQueries.orderedLazyById has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Builder.where (cognitive 19) · ×1
  • Builder.where (cognitive 19) src/Illuminate/Database/Query/Builder.php:931 — Builder.where has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Dispatcher.propagateListenerOptions (cognitive 19) · ×1
  • Dispatcher.propagateListenerOptions (cognitive 19) src/Illuminate/Events/Dispatcher.php:747 — Dispatcher.propagateListenerOptions has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11 (15 pts), if/else 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Env.addVariableToEnvContents (cognitive 19) · ×1
  • Env.addVariableToEnvContents (cognitive 19) src/Illuminate/Support/Env.php:185 — Env.addVariableToEnvContents has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BuildsQueries.orderedChunkById (cognitive 18) · ×1
  • BuildsQueries.orderedChunkById (cognitive 18) src/Illuminate/Database/Concerns/BuildsQueries.php:164 — BuildsQueries.orderedChunkById has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Model.initializeModelAttributes (cognitive 18) · ×1
  • Model.initializeModelAttributes (cognitive 18) src/Illuminate/Database/Eloquent/Model.php:445 — Model.initializeModelAttributes has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · PostgresGrammar.compileUnique (cognitive 18) · ×1
  • PostgresGrammar.compileUnique (cognitive 18) src/Illuminate/Database/Schema/Grammars/PostgresGrammar.php:333 — PostgresGrammar.compileUnique has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 5, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Dispatcher.queueHandler (cognitive 18) · ×1
  • Dispatcher.queueHandler (cognitive 18) src/Illuminate/Events/Dispatcher.php:661 — Dispatcher.queueHandler has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 5 (6 pts), boolean chains 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · Kernel.addToMiddlewarePriorityRelative (cognitive 18) · ×1
  • Kernel.addToMiddlewarePriorityRelative (cognitive 18) src/Illuminate/Foundation/Http/Kernel.php:485 — Kernel.addToMiddlewarePriorityRelative has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RateLimitedWithRedis.handleJob (cognitive 18) · ×1
  • RateLimitedWithRedis.handleJob (cognitive 18) src/Illuminate/Queue/Middleware/RateLimitedWithRedis.php:48 — RateLimitedWithRedis.handleJob has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 2 (4 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PacksPhpRedisValues.pack (cognitive 18) · ×1
  • PacksPhpRedisValues.pack (cognitive 18) src/Illuminate/Redis/Connections/PacksPhpRedisValues.php:41 — PacksPhpRedisValues.pack has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Password.passes (cognitive 18) · ×1
  • Password.passes (cognitive 18) src/Illuminate/Validation/Rules/Password.php:336 — Password.passes has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 9. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · Validator.passes (cognitive 18) · ×1
  • Validator.passes (cognitive 18) src/Illuminate/Validation/Validator.php:467 — Validator.passes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MercureBroadcaster.broadcast (cognitive 17) · ×1
  • MercureBroadcaster.broadcast (cognitive 17) src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php:206 — MercureBroadcaster.broadcast has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3, loops 3, boolean chains 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RedisTagSet.entries (cognitive 17) · ×1
  • RedisTagSet.entries (cognitive 17) src/Illuminate/Cache/RedisTagSet.php:40 — RedisTagSet.entries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Collection.groupBy (cognitive 17) · ×1
  • Collection.groupBy (cognitive 17) src/Illuminate/Collections/Collection.php:540 — Collection.groupBy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (3 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConfiguresPooledConnections.ensurePooledPostgresIsProperlyConfigured (cognitive 17) · ×1
  • ConfiguresPooledConnections.ensurePooledPostgresIsProperlyConfigured (cognitive 17) src/Illuminate/Database/Connectors/Concerns/ConfiguresPooledConnections.php:57 — ConfiguresPooledConnections.ensurePooledPostgresIsProperlyConfigured has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlServerConnector.getSqlSrvDsn (cognitive 17) · ×1
  • SqlServerConnector.getSqlSrvDsn (cognitive 17) src/Illuminate/Database/Connectors/SqlServerConnector.php:126 — SqlServerConnector.getSqlSrvDsn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Model.resolveClassAttribute (cognitive 17) · ×1
  • Model.resolveClassAttribute (cognitive 17) src/Illuminate/Database/Eloquent/Model.php:2759 — Model.resolveClassAttribute has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 2 (7 pts), if/else 3 (6 pts), loops 2 (3 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CanBeOneOfMany.ofMany (cognitive 17) · ×1
  • CanBeOneOfMany.ofMany (cognitive 17) src/Illuminate/Database/Eloquent/Relations/Concerns/CanBeOneOfMany.php:77 — CanBeOneOfMany.ofMany has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2, boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResolvesDumpSource.resolveDumpSource (cognitive 17) · ×1
  • ResolvesDumpSource.resolveDumpSource (cognitive 17) src/Illuminate/Foundation/Concerns/ResolvesDumpSource.php:63 — ResolvesDumpSource.resolveDumpSource has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PendingRequest.normalizeMultipartOption (cognitive 17) · ×1
  • PendingRequest.normalizeMultipartOption (cognitive 17) src/Illuminate/Http/Client/PendingRequest.php:1578 — PendingRequest.normalizeMultipartOption has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Str.substrReplace (cognitive 17) · ×1
  • Str.substrReplace (cognitive 17) src/Illuminate/Support/Str.php:1906 — Str.substrReplace has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 3, boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BusFake.assertDispatchedWithChainOfObjects (cognitive 17) · ×1
  • BusFake.assertDispatchedWithChainOfObjects (cognitive 17) src/Illuminate/Support/Testing/Fakes/BusFake.php:446 — BusFake.assertDispatchedWithChainOfObjects has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QueueFake.push (cognitive 17) · ×1
  • QueueFake.push (cognitive 17) src/Illuminate/Support/Testing/Fakes/QueueFake.php:655 — QueueFake.push has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (6 pts), boolean chains 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ValidationRuleParser.explodeWildcardRules (cognitive 17) · ×1
  • ValidationRuleParser.explodeWildcardRules (cognitive 17) src/Illuminate/Validation/ValidationRuleParser.php:161 — ValidationRuleParser.explodeWildcardRules has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 3 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · RedisStore.currentTags (cognitive 16) · ×1
  • RedisStore.currentTags (cognitive 16) src/Illuminate/Cache/RedisStore.php:352 — RedisStore.currentTags has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 3, loops 2 (3 pts), match/switch 2, ternaries 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LazyCollection.select (cognitive 16) · ×1
  • LazyCollection.select (cognitive 16) src/Illuminate/Collections/LazyCollection.php:986 — LazyCollection.select has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScheduleRunCommand.handle (cognitive 16) · ×1
  • ScheduleRunCommand.handle (cognitive 16) src/Illuminate/Console/Scheduling/ScheduleRunCommand.php:106 — ScheduleRunCommand.handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Vite.__invoke (cognitive 16) · ×1
  • Vite.__invoke (cognitive 16) src/Illuminate/Foundation/Vite.php:384 — Vite.__invoke has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 3, boolean chains 2, ternaries 2, match/switch 1 (nesting depth added 4). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · PendingRequest.pool (cognitive 16) · ×1
  • PendingRequest.pool (cognitive 16) src/Illuminate/Http/Client/PendingRequest.php:986 — PendingRequest.pool has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (5 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ResponseFactory.eventStream (cognitive 16) · ×1
  • ResponseFactory.eventStream (cognitive 16) src/Illuminate/Routing/ResponseFactory.php:146 — ResponseFactory.eventStream has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Str.apa (cognitive 16) · ×1
  • Str.apa (cognitive 16) src/Illuminate/Support/Str.php:1597 — Str.apa has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NotificationFake.sendNow (cognitive 16) · ×1
  • NotificationFake.sendNow (cognitive 16) src/Illuminate/Support/Testing/Fakes/NotificationFake.php:332 — NotificationFake.sendNow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Validator.validateUsingCustomRule (cognitive 16) · ×1
  • Validator.validateUsingCustomRule (cognitive 16) src/Illuminate/Validation/Validator.php:955 — Validator.validateUsingCustomRule has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 4 (5 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BladeCompiler.compileStatements (cognitive 16) · ×1
  • BladeCompiler.compileStatements (cognitive 16) src/Illuminate/View/Compilers/BladeCompiler.php:549 — BladeCompiler.compileStatements has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (6 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D22 · Internal API Consistency · Duplicate intent · ×1
  • Duplicate intent: Both methods appear to convert the exception into an HTTP response. In Laravel, `toResponse()` is the standard PSR-15/exception handling contract method, while `response()` is a legacy or convenience alias. Having both creates confusion about which entry point to use. — Deprecate `response()` in favor of `toResponse()` to align with standard exception handling contracts, or ensure `response()` strictly delegates to `toResponse()` with clear documentation. (signatures: AuthorizationException.response() | AuthorizationException.toResponse())
D22 · Internal API Consistency · Inconsistent naming for status mutation · ×1
  • Inconsistent naming for status mutation: `AuthorizationException` uses `withStatus` (immutable-style builder pattern), while `Response` also uses `withStatus`. However, `AuthorizationException` also has `asNotFound()` which is a specific case of setting a status. While not strictly duplicate, the mix of `withStatus` (generic) and `asNotFound` (specific) on the Exception, versus `denyWithStatus` and `denyAsNotFound` on the Response, creates a slight asymmetry in how status codes are applied across the authorization domain. — Ensure that if `withStatus` is the primary builder method, specific helpers like `asNotFound` are clearly documented as syntactic sugar. The current API is acceptable but could be tighter by standardizing on `withStatus` for all status changes and removing `asNotFound` if it doesn't add significant value over `withStatus(404)`. (signatures: AuthorizationException.withStatus(status) | Response.withStatus(status))
D22 · Internal API Consistency · Inconsistent error handling patterns · ×1
  • Inconsistent error handling patterns: `Gate.authorize()` throws an exception (specifically `AuthorizationException`) on failure, whereas `HandlesAuthorization` traits provide methods like `denyWithStatus` and `denyAsNotFound` that likely throw or return specific responses. The naming `denyWithStatus` implies a return value or a specific exception construction, while `authorize` implies a void return on success and exception on failure. This mixes exception-throwing and potentially return-value-based APIs. — Standardize on exception throwing for authorization failures. If `denyWithStatus` is intended to throw, rename it to `throwAuthorizationExceptionWithStatus` or similar to clarify intent, or ensure `authorize` is the single entry point for all authorization checks that fail. (signatures: Gate.authorize(ability, arguments) | HandlesAuthorization.denyWithStatus(status, message, code) | HandlesAuthorization.denyAsNotFound(message, code))
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling clique · ×1
  • Change coupling clique: BeanstalkdQueue.php, DatabaseQueue.php, RedisQueue.php, SqsQueue.php src/Illuminate/Queue/BeanstalkdQueue.php — 4 files — `src/Illuminate/Queue/BeanstalkdQueue.php`, `src/Illuminate/Queue/DatabaseQueue.php`, `src/Illuminate/Queue/RedisQueue.php`, `src/Illuminate/Queue/SqsQueue.php` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (4 members, 19 shared lines) · ×1
  • Near-duplicate member family (4 members, 19 shared lines) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1321 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1321-1355 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1368-1402 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1415-1449 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1462-1496 — These 4 members are variants of one another: a block of 19 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) src/Illuminate/Bus/BusServiceProvider.php:47 — src/Illuminate/Bus/BusServiceProvider.php:47-88 | src/Illuminate/Cache/CacheManager.php:251-267 | src/Illuminate/Filesystem/FilesystemManager.php:333-361 | src/Illuminate/Mail/MailManager.php:303-311 | src/Illuminate/Queue/Connectors/SqsConnector.php:64-78 | src/Illuminate/Queue/QueueServiceProvider.php:375-393 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (28–32 lines × 2) · ×1
  • Duplicated block (28–32 lines × 2) src/Illuminate/Mail/Transport/SesTransport.php:68 — src/Illuminate/Mail/Transport/SesTransport.php:68-95 | src/Illuminate/Mail/Transport/SesV2Transport.php:72-103 — before extracting anything, compare `src/Illuminate/Mail/Transport/SesTransport.php` and `src/Illuminate/Mail/Transport/SesV2Transport.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Mail/Transport/SesTransport.php:68` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (24–31 lines × 2) · ×1
  • Duplicated block (24–31 lines × 2) src/Illuminate/Cache/FileStore.php:403 — src/Illuminate/Cache/FileStore.php:403-433 | src/Illuminate/Cache/StorageStore.php:205-228 — before extracting anything, compare `src/Illuminate/Cache/FileStore.php` and `src/Illuminate/Cache/StorageStore.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Cache/FileStore.php:403` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) src/Illuminate/Bus/DynamoBatchRepository.php:234 — src/Illuminate/Bus/DynamoBatchRepository.php:234-260 | src/Illuminate/Bus/DynamoBatchRepository.php:272-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) src/Illuminate/Database/Eloquent/Casts/AsEnumArrayObject.php:24 — src/Illuminate/Database/Eloquent/Casts/AsEnumArrayObject.php:24-45 | src/Illuminate/Database/Eloquent/Casts/AsEnumCollection.php:24-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Casts/AsEnumArrayObject.php:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) src/Illuminate/Database/Console/Migrations/FreshCommand.php:96 — src/Illuminate/Database/Console/Migrations/FreshCommand.php:96-115 | src/Illuminate/Database/Console/Migrations/RefreshCommand.php:70-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) src/Illuminate/Routing/ResourceRegistrar.php:101 — src/Illuminate/Routing/ResourceRegistrar.php:101-119 | src/Illuminate/Routing/ResourceRegistrar.php:169-188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Routing/ResourceRegistrar.php:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Illuminate/Routing/PendingResourceRegistration.php:151 — src/Illuminate/Routing/PendingResourceRegistration.php:151-168 | src/Illuminate/Routing/PendingSingletonResourceRegistration.php:175-192 — before extracting anything, compare `src/Illuminate/Routing/PendingResourceRegistration.php` and `src/Illuminate/Routing/PendingSingletonResourceRegistration.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) src/Illuminate/Database/Query/Builder.php:1864 — src/Illuminate/Database/Query/Builder.php:1864-1879 | src/Illuminate/Database/Query/Builder.php:1912-1927 | src/Illuminate/Database/Query/Builder.php:1960-1975 | src/Illuminate/Database/Query/Builder.php:2012-2027 | src/Illuminate/Database/Query/Builder.php:2064-2079 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Illuminate/Database/Query/Builder.php:2030` calls `sprintf` and `src/Illuminate/Database/Query/Builder.php:1881` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13–15 lines × 3) · ×1
  • Duplicated block (13–15 lines × 3) src/Illuminate/Bus/BusServiceProvider.php:66 — src/Illuminate/Bus/BusServiceProvider.php:66-78 | src/Illuminate/Cache/CacheManager.php:251-265 | src/Illuminate/Queue/QueueServiceProvider.php:375-387 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (12–15 lines × 2) · ×1
  • Duplicated block (12–15 lines × 2) src/Illuminate/Database/Connection.php:433 — src/Illuminate/Database/Connection.php:433-447 | src/Illuminate/Database/Connection.php:464-475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Connection.php:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) src/Illuminate/Database/Eloquent/Relations/Concerns/AsPivot.php:323 — src/Illuminate/Database/Eloquent/Relations/Concerns/AsPivot.php:323-335 | src/Illuminate/Database/Eloquent/Relations/MorphPivot.php:166-179 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Eloquent/Relations/Concerns/AsPivot.php:323` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:858 — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:858-870 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:897-909 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:454-466 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:493-505 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11–13 lines × 3) · ×1
  • Duplicated block (11–13 lines × 3) src/Illuminate/Database/Connectors/SqlServerConnector.php:144 — src/Illuminate/Database/Connectors/SqlServerConnector.php:144-154 | src/Illuminate/Database/Connectors/SqlServerConnector.php:160-170 | src/Illuminate/Routing/ResourceRegistrar.php:643-655 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Routing/ResourceRegistrar.php:643` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Illuminate/Database/Connectors/SqlServerConnector.php:156` calls `isset` and `src/Illuminate/Database/Connectors/SqlServerConnector.php:172` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) src/Illuminate/Database/Eloquent/Relations/Concerns/AsPivot.php:300 — src/Illuminate/Database/Eloquent/Relations/Concerns/AsPivot.php:300-311 | src/Illuminate/Database/Eloquent/Relations/MorphPivot.php:142-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1330 — src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1330-1340 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1377-1387 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1424-1434 | src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1471-1481 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1330` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) src/Illuminate/Database/Concerns/BuildsQueries.php:522 — src/Illuminate/Database/Concerns/BuildsQueries.php:522-530 | src/Illuminate/Database/Concerns/BuildsQueries.php:536-545 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Database/Concerns/BuildsQueries.php:522` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (5–8 lines × 6) · ×1
  • Duplicated block (5–8 lines × 6) src/Illuminate/Bus/BusServiceProvider.php:73 — src/Illuminate/Bus/BusServiceProvider.php:73-78 | src/Illuminate/Cache/CacheManager.php:258-265 | src/Illuminate/Filesystem/FilesystemManager.php:354-359 | src/Illuminate/Mail/MailManager.php:304-309 | src/Illuminate/Queue/Connectors/SqsConnector.php:67-71 | src/Illuminate/Queue/QueueServiceProvider.php:382-387 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Bus/BusServiceProvider.php:73` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) src/Illuminate/Validation/Rules/DeclinedIf.php:30 — src/Illuminate/Validation/Rules/DeclinedIf.php:30-37 | src/Illuminate/Validation/Rules/MissingIf.php:30-37 | src/Illuminate/Validation/Rules/MissingUnless.php:30-37 | src/Illuminate/Validation/Rules/PresentIf.php:30-37 | src/Illuminate/Validation/Rules/PresentUnless.php:30-37 — before extracting anything, compare `src/Illuminate/Validation/Rules/DeclinedIf.php` and `src/Illuminate/Validation/Rules/MissingIf.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 4) · ×1
  • Duplicated block (25 lines × 4) src/Illuminate/Foundation/Console/EventMakeCommand.php:42 — src/Illuminate/Foundation/Console/EventMakeCommand.php:42-77 | src/Illuminate/Foundation/Console/JobMiddlewareMakeCommand.php:44-68 | src/Illuminate/Foundation/Console/RequestMakeCommand.php:41-65 | src/Illuminate/Routing/Console/MiddlewareMakeCommand.php:42-66 — before extracting anything, compare `src/Illuminate/Foundation/Console/EventMakeCommand.php` and `src/Illuminate/Foundation/Console/RequestMakeCommand.php` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Foundation/Console/EventMakeCommand.php:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) src/Illuminate/JsonSchema/Types/IntegerType.php:27 — src/Illuminate/JsonSchema/Types/IntegerType.php:27-59 | src/Illuminate/JsonSchema/Types/NumberType.php:27-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/JsonSchema/Types/IntegerType.php:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) src/Illuminate/Queue/Console/FailedTableCommand.php:41 — src/Illuminate/Queue/Console/FailedTableCommand.php:41-69 | src/Illuminate/Queue/Console/TableCommand.php:41-69 — before extracting anything, compare `src/Illuminate/Queue/Console/FailedTableCommand.php` and `src/Illuminate/Queue/Console/TableCommand.php` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Queue/Console/FailedTableCommand.php:41` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (19 lines × 4) · ×1
  • Duplicated block (19 lines × 4) src/Illuminate/Validation/Rules/ExcludeIf.php:27 — src/Illuminate/Validation/Rules/ExcludeIf.php:27-45 | src/Illuminate/Validation/Rules/ExcludeUnless.php:27-45 | src/Illuminate/Validation/Rules/ProhibitedIf.php:27-45 | src/Illuminate/Validation/Rules/ProhibitedUnless.php:27-45 — before extracting anything, compare `src/Illuminate/Validation/Rules/ExcludeIf.php` and `src/Illuminate/Validation/Rules/ExcludeUnless.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Illuminate/Validation/Rules/ExcludeIf.php:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) src/Illuminate/Auth/AuthManager.php:279 — src/Illuminate/Auth/AuthManager.php:279-287 | src/Illuminate/Broadcasting/BroadcastManager.php:516-524 | src/Illuminate/Cache/CacheManager.php:556-564 | src/Illuminate/Filesystem/FilesystemManager.php:521-529 | src/Illuminate/Log/LogManager.php:639-647 | src/Illuminate/Redis/RedisManager.php:267-275 | src/Illuminate/Support/Manager.php:133-141 | src/Illuminate/Support/MultipleInstanceManager.php:204-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 8 times. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) src/Illuminate/Database/Eloquent/Builder.php:808 — src/Illuminate/Database/Eloquent/Builder.php:808-812 | src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:777-781 | src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php:319-323 | src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php:313-317 — before extracting anything, compare `src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php` and `src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) src/Illuminate/Mail/Mailable.php:975 — src/Illuminate/Mail/Mailable.php:975-981 | src/Illuminate/Mail/Mailable.php:1225-1231 | src/Illuminate/Mail/Mailables/Content.php:149-155 | src/Illuminate/View/View.php:252-258 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) src/Illuminate/Support/Testing/Fakes/EventFake.php:170 — src/Illuminate/Support/Testing/Fakes/EventFake.php:170-179 | src/Illuminate/Support/Testing/Fakes/MailFake.php:108-117 | src/Illuminate/Support/Testing/Fakes/MailFake.php:242-251 | src/Illuminate/Support/Testing/Fakes/QueueFake.php:170-179 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
D5 · Coupling · Unstable project illuminate/broadcasting · ×1
  • Unstable project illuminate/broadcasting — illuminate/broadcasting has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project illuminate/database · ×1
  • Unstable project illuminate/database — illuminate/database has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project illuminate/events · ×1
  • Unstable project illuminate/events — illuminate/events has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project illuminate/mail · ×1
  • Unstable project illuminate/mail — illuminate/mail has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project illuminate/process · ×1
  • Unstable project illuminate/process — illuminate/process has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project illuminate/translation · ×1
  • Unstable project illuminate/translation — illuminate/translation has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project illuminate/view · ×1
  • Unstable project illuminate/view — illuminate/view has instability 0.90 with 1 dependents.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 794 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
X19 · Unrestored process-global state · Process-global state is restored only on the happy path · ×1
  • Process-global state is restored only on the happy path src/Illuminate/Foundation/Console/DevCommand.php:148 — `runViaConcurrently` changes state that belongs to the whole PROCESS and changes it back at the end of the same body — the `COLUMNS` environment variable (changed at line 157, reset at line 183) — which says the change was meant to last no longer than this call. But the restore is an ordinary statement on the straight-line path, not a `finally`, so it is skipped by any exception thrown in between: PHP then keeps the overwritten value for the rest of the request — and in a CLI command, a queue worker or a long-running server (Octane, Swoole, RoadRunner, FrankenPHP) for the rest of the process's life — and every later relative path, child-process launch, date, number format, XML parse or error report in ANY class reads it. That failure is silent and remote from its cause: the function that breaks is not the function that moved the value. The durable fix is not to widen the restore but to stop mutating the global: pass the value to the operation that needs it — `cwd` and `env` to Symfony `Process` (`new Process($command, $cwd, $env)`) or `proc_open($command, $spec, $pipes, $cwd, $env)`, absolute paths instead of `chdir`, an explicit `DateTimeZone` or locale to `DateTimeImmutable`/`IntlDateFormatter`/`NumberFormatter`, an explicit encoding to the `mb_*` call, `LIBXML_NOERROR`/`libxml_get_errors` handling in one place. Where the global genuinely must move, wrap it `try`/`finally` so the restore runs on every path.
Minor — 96 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×52
  • Orphaned file src/Illuminate/Foundation/Http/Middleware/PreventRequestForgery.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Routing/Redirector.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Redis/Connections/PacksPhpRedisValues.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Cache/MemcachedStore.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/MigrationServiceProvider.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Foundation/Testing/DatabaseTruncation.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Contracts/Container/Container.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Testing/Fluent/Concerns/Has.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Contracts/Routing/ResponseFactory.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Foundation/AliasLoader.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Capsule/Manager.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Query/Processors/PostgresProcessor.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Foundation/Console/EnvironmentDecryptCommand.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Contracts/Filesystem/Filesystem.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/View/Compilers/Concerns/CompilesLoops.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Cache/SessionStore.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Queue/Capsule/Manager.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Eloquent/Relations/Concerns/SupportsInverseRelations.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Testing/Fluent/AssertableJson.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Pagination/resources/views/bootstrap-5.blade.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Contracts/Session/Session.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Query/Processors/SqlServerProcessor.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Console/MonitorCommand.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Foundation/Auth/Access/AuthorizesRequests.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Illuminate/Database/Query/JoinClause.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 27 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate src/Illuminate/Notifications/NotificationSender.php:311 — `! $notifiables instanceof Collection && ! is_array($notifiables)` appears character-identically in 2 files — src/Illuminate/Notifications/NotificationSender.php, src/Illuminate/Support/Testing/Fakes/NotificationFake.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Container/Util.php:58 — `! $type instanceof ReflectionNamedType || $type` appears character-identically in 2 files — src/Illuminate/Container/Util.php, src/Illuminate/Reflection/Reflector.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Bus/BusServiceProvider.php:72 — `! empty($config['key']) && ! empty($config['secret'])` appears character-identically in 6 files — src/Illuminate/Bus/BusServiceProvider.php, src/Illuminate/Cache/CacheManager.php, src/Illuminate/Filesystem/FilesystemManager.php, src/Illuminate/Mail/MailManager.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php:336 — `! empty($values) && ! is_array(array_first($values))` appears character-identically in 2 files — src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php, src/Illuminate/Database/Eloquent/Relations/MorphOneOrMany.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Schema/BlueprintState.php:81 — `! is_null($column['generation']) && $column['generation']['type'] === 'stored'` appears character-identically in 2 files — src/Illuminate/Database/Schema/BlueprintState.php, src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Schema/BlueprintState.php:78 — `! is_null($column['generation']) && $column['generation']['type'] === 'virtual'` appears character-identically in 2 files — src/Illuminate/Database/Schema/BlueprintState.php, src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:198 — `! str_contains($table, '\\') || ! class_exists($table)` appears character-identically in 2 files — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php, src/Illuminate/Validation/Rules/DatabaseRule.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Concerns/HasTimestamps.php:253 — `$class === $ignoredClass || is_subclass_of($class, $ignoredClass)` appears character-identically in 2 files — src/Illuminate/Database/Eloquent/Concerns/HasTimestamps.php, src/Illuminate/Database/Eloquent/Model.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Builder.php:382 — `$column instanceof Closure && is_null($operator)` appears character-identically in 2 files — src/Illuminate/Database/Eloquent/Builder.php, src/Illuminate/Database/Query/Builder.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Validation/Rules/ExcludeIf.php:27 — `$condition instanceof Closure || is_bool($condition)` appears character-identically in 6 files — src/Illuminate/Validation/Rules/ExcludeIf.php, src/Illuminate/Validation/Rules/ExcludeUnless.php, src/Illuminate/Validation/Rules/ProhibitedIf.php, src/Illuminate/Validation/Rules/ProhibitedUnless.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Cache/RedisStore.php:364 — `$connection instanceof PhpRedisConnection && version_compare(phpversion('redis'), '6.1.0', '>=')` appears character-identically in 2 files — src/Illuminate/Cache/RedisStore.php, src/Illuminate/Cache/RedisTagSet.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Cache/ArrayStore.php:95 — `$expiresAt !== 0 && (Carbon::now()->getPreciseTimestamp(3) / 1000) >= $expiresAt` appears character-identically in 2 files — src/Illuminate/Cache/ArrayStore.php, src/Illuminate/Cache/SessionStore.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php:1674 — `$grammar instanceof MySqlGrammar && $grammar` appears character-identically in 2 files — src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php, src/Illuminate/Database/Eloquent/Relations/HasOneOrManyThrough.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Queue/Queue.php:440 — `$job instanceof ShouldBeUnique || ($job instanceof CallQueuedListener && $job->shouldBeUnique())` appears character-identically in 2 files — src/Illuminate/Queue/Queue.php, src/Illuminate/Support/Testing/Fakes/QueueFake.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Eloquent/Collection.php:522 — `$key !== null && isset($dictionary[$key])` appears character-identically in 5 files — src/Illuminate/Database/Eloquent/Collection.php, src/Illuminate/Database/Eloquent/Relations/BelongsToMany.php, src/Illuminate/Database/Eloquent/Relations/HasManyThrough.php, src/Illuminate/Database/Eloquent/Relations/HasOneOrMany.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Routing/Route.php:905 — `$name instanceof BackedEnum && ! is_string($name = $name->value)` appears character-identically in 2 files — src/Illuminate/Routing/Route.php, src/Illuminate/Routing/UrlGenerator.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Console/CacheCommandMutex.php:139 — `$store instanceof LockProvider && ! $store instanceof DynamoDbStore` appears character-identically in 3 files — src/Illuminate/Console/CacheCommandMutex.php, src/Illuminate/Console/Scheduling/CacheEventMutex.php, src/Illuminate/Console/Scheduling/CacheSchedulingMutex.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Validation/Concerns/ValidatesAttributes.php:1718 — `$value instanceof UploadedFile && ! $value` appears character-identically in 2 files — src/Illuminate/Validation/Concerns/ValidatesAttributes.php, src/Illuminate/Validation/Validator.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Testing/Constraints/SeeInHtml.php:80 — `$valuePosition === false || $valuePosition < $position` appears character-identically in 2 files — src/Illuminate/Testing/Constraints/SeeInHtml.php, src/Illuminate/Testing/Constraints/SeeInOrder.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Foundation/Console/LangPublishCommand.php:49 — `(! $this->option('existing') && (! file_exists($to) || $this->option('force'))) || ($this->option('existing') && file_exists($to))` appears character-identically in 2 files — src/Illuminate/Foundation/Console/LangPublishCommand.php, src/Illuminate/Foundation/Console/StubPublishCommand.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Collections/Arr.php:789 — `Arr::accessible($item) && Arr::exists($item, $key)` appears character-identically in 2 files — src/Illuminate/Collections/Arr.php, src/Illuminate/Collections/LazyCollection.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Routing/Middleware/ThrottleRequests.php:171 — `afterCallback && ($limit->afterCallback)($response)` appears character-identically in 2 files — src/Illuminate/Routing/Middleware/ThrottleRequests.php, src/Illuminate/Routing/Middleware/ThrottleRequestsWithRedis.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Broadcasting/Broadcasters/AblyBroadcaster.php:47 — `empty($request->channel_name) || ($this->isGuardedChannel($request->channel_name) && ! $this->retrieveUser($request, $channelName))` appears character-identically in 3 files — src/Illuminate/Broadcasting/Broadcasters/AblyBroadcaster.php, src/Illuminate/Broadcasting/Broadcasters/PusherBroadcaster.php, src/Illuminate/Broadcasting/Broadcasters/RedisBroadcaster.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php:1372 — `in_array($column->type, $this->serials) && $column` appears character-identically in 2 files — src/Illuminate/Database/Schema/Grammars/MySqlGrammar.php, src/Illuminate/Database/Schema/Grammars/SQLiteGrammar.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Illuminate/Foundation/Console/ListenerMakeCommand.php:133 — `isReservedName($this->getNameInput()) || $this` appears character-identically in 5 files — src/Illuminate/Foundation/Console/ListenerMakeCommand.php, src/Illuminate/Foundation/Console/ModelMakeCommand.php, src/Illuminate/Foundation/Console/ObserverMakeCommand.php, src/Illuminate/Foundation/Console/PolicyMakeCommand.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X7 · Silent fallback defaults · Silent fallback default in catch · ×6
  • Silent fallback default in catch src/Illuminate/Bus/DatabaseBatchRepository.php:357 — `unserialize` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch src/Illuminate/Database/Eloquent/Factories/Factory.php:1112 — `appNamespace` swallows every exception into `return 'App\\'` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch src/Illuminate/Foundation/Cloud/ExceptionReporter.php:280 — `executionDetails` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch src/Illuminate/Foundation/Console/DownCommand.php:111 — `excludedPaths` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch src/Illuminate/Foundation/Exceptions/Handler.php:678 — `context` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
  • Silent fallback default in catch src/Illuminate/Log/Formatters/JsonFormatter.php:52 — `getExceptionContext` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
D16 · Bus Factor · Off-boarding risk · ×2
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: src/Illuminate/Foundation/Application.php, src/Illuminate/Support/Facades/Schedule.php, src/Illuminate/Support/Facades/Exceptions.php, src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php, src/Illuminate/Validation/ValidationData.php. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: src/Illuminate/Session/CookieSessionHandler.php, src/Illuminate/Redis/Connections/PredisConnection.php, src/Illuminate/Session/ArraySessionHandler.php, src/Illuminate/Session/FileSessionHandler.php. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 19 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (32 single-owned of 698 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 698 of the 1758 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)) (+13 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/Illuminate/Queue/BeanstalkdQueue.php, src/Illuminate/Queue/NullQueue.php, src/Illuminate/Database/Connectors/SqlServerConnector.php, src/Illuminate/Support/Traits/ParsesSqlServerConfigurationUrls.php, rector.php, src/Illuminate/Foundation/Console/ChannelListCommand.php, src/Illuminate/Database/Eloquent/Relations/MorphOne.php, src/Illuminate/Process/ProcessResult.php (+15 more).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 5 of 38 project(s) overshoot their size bounds, lowering Project Cohesion to 7.4/10. The most over is `src/Illuminate/Database` (52843 LoC, 254 module-visible types across 25 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 52 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: src/Illuminate/Routing/Redirector.php, src/Illuminate/Redis/Connections/PacksPhpRedisValues.php, src/Illuminate/Cache/MemcachedStore.php, src/Illuminate/Database/MigrationServiceProvider.php, src/Illuminate/Foundation/Testing/DatabaseTruncation.php, src/Illuminate/Contracts/Container/Container.php, src/Illuminate/Testing/Fluent/Concerns/Has.php, src/Illuminate/Contracts/Routing/ResponseFactory.php (and 44 more) (54 orphaned of 699 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 699 of the 1758 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
X5 · Nullable reference types · PHP static analysis does not check null everywhere · ×1
  • PHP static analysis does not check null everywhere — 1/2 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
Minor — 13 finding(s)
D10 · Test Quality · Skipped (documented) · ×12
  • Skipped (documented): testNetworkExceptionIsConvertedToConnectionException tests/Http/HttpClientTest.php:5260 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testNetworkExceptionInPoolIsConsideredConnectionException tests/Http/HttpClientTest.php:5281 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testImagePng tests/Http/HttpTestingFileFactoryTest.php:16 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testImageJpeg tests/Http/HttpTestingFileFactoryTest.php:31 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testImageGif tests/Http/HttpTestingFileFactoryTest.php:51 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testImageWebp tests/Http/HttpTestingFileFactoryTest.php:65 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testImageWbmp tests/Http/HttpTestingFileFactoryTest.php:79 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testCallingCreateWithoutGDLoadedThrowsAnException tests/Http/HttpTestingFileFactoryTest.php:117 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): test_extension_returns_avif_for_avif tests/Image/ImageTest.php:272 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): test_extension_returns_jxl_for_jxl tests/Image/ImageTest.php:289 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testItPersistsConnection tests/Redis/RedisConnectionTest.php:574 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
  • Skipped (documented): testMemoizationOnSameLine tests/Support/OnceTest.php:294 — Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
D10 · Test Quality · No assertions (declared) · ×1
  • No assertions (declared): test_it_can_resolve_the_implicit_model_route_bindings_for_the_given_route tests/Routing/ImplicitRouteBindingTest.php:109 — This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d98eb9ec15e0439da45a7e644e1a67fa/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d98eb9ec15e0439da45a7e644e1a67fa/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .21artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .4artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 75 file(s) — `src/Illuminate/Auth/Passwords/CacheTokenRepository.php`, `src/Illuminate/Auth/Passwords/DatabaseTokenRepository.php`, `src/Illuminate/Auth/SessionGuard.php`, `src/Illuminate/Broadcasting/Broadcasters/MercureBroadcaster.php`, `src/Illuminate/Broadcasting/Mercure/ChannelEncrypter.php`, … (+70 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a16768-2636-7cba-a3eb-1afffff14a99 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 17 · Warnings: 798 · Recommendations: 96 · Info: 13 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 06:17 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md