Public report of filamentphp/filament, 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 reportMeasured 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, 03:03 UTC · Survey ID cd_20a1db21362c4e9d84b887c07fd09ad3
filamentphp/filament
Measured 23 October 2026, 02:33 UTC, at code version f1033d8
Regression: 1 dimension 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 scoreWeak
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.
A large codebase: 289,216 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Code Health, 37
Findings by how serious they are
23 critical1388 serious94 minor
18 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, 02:33 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 ▸
74of 77 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.
1479of 1505 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
77dimensions across 7 lenses, read from 289,216 lines of product code in 17 projects.
filamentphp/filament scores 48 out of 100 and is rated Weak, while six of its seven lenses score higher still: Architecture at 78, Security and Compliance and Performance at 60, Accessibility at 58 and Maturity at 56, all rated Adequate, and Production Readiness at 71, rated Strong.
The score is lower than those six because the weakest lens counts most, and here that is Code Health, which scores 37 and is rated Weak. Its Type Safety dimension scores 0 out of 10, and until that reaches 4, Code Health can't be rated higher than Adequate. The first actions are to adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up and to 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, and if Code Health rose to 70, the score would rise from 48 to about 58.
23 findings are critical: 12 in Secrets (history), nine in Change Coupling, one in ARIA correctness and one in Static Analysis (SAST).
Watchdog couldn't measure 15 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 289,216 lines, which would take an estimated 2.6 person-years, around €380,000, to rebuild.
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 forThe 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.
If Code Health rose from 37 to 70, the lowest score rated Strong, the score would rise from 48 to about 58.
Code composition: what the lines of code are
Product code 70%Tests 30%
New since the last survey: 251 findings
These 251 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · ClassTooLong: Repeater packages/forms/src/Components/Repeater.php
God Classes · FunctionTooLong: reordering.reordering packages/forms/resources/js/utilities/reordering.js
God Classes · ClassTooLong: Builder packages/forms/src/Components/Builder.php
God Classes · MethodTooLong: Builder.toEmbeddedHtml packages/forms/src/Components/Builder.php
God Classes · FunctionTooLong: notification.notificationComponent packages/notifications/resources/js/components/notification.js
God Classes · MethodTooLong: Repeater.toEmbeddedHtml packages/forms/src/Components/Repeater.php
God Classes · FunctionTooLong: global-search.default packages/panels/resources/js/components/global-search.js
God Classes · MethodTooLong: Repeater.toTableEmbeddedHtml packages/forms/src/Components/Repeater.php
God Classes · MethodTooLong: Builder.generateBlockPickerHtml packages/forms/src/Components/Builder.php
God Classes · FunctionTooLong: reordering.reordering.init packages/forms/resources/js/utilities/reordering.js
God Classes · FileTooLong: components/rich-editor.js packages/forms/resources/js/components/rich-editor.js
God Classes · FunctionTooLong: editable-table-column.editableTableColumn packages/tables/resources/js/utilities/editable-table-column.js
God Classes · FileTooLong: components/tabs.js packages/schemas/resources/js/components/tabs.js
God Classes · FileTooLong: components/date-time-picker.js packages/forms/resources/js/components/date-time-picker.js
God Classes · MethodTooLong: Repeater.toSimpleEmbeddedHtml packages/forms/src/Components/Repeater.php
God Classes · FunctionTooLong: select.selectFormComponent packages/forms/resources/js/components/select.js
God Classes · MethodTooLong: Select.constructor packages/support/resources/js/utilities/select.js
God Classes · FunctionTooLong: code-editor.codeEditorFormComponent packages/forms/resources/js/components/code-editor.js
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: 119 findings
These 119 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.
€130,000 to €630,000, for 2,102 to 6,668 hours of work, about 2.6 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, 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.7 at a score of 48. 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.
Size
Large: 289,216 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
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 6 points · Medium effort · Type Safety
2
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.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
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 €380,000 to build again, about 2.6 person-years of work. Its weakest lens is Code Health, at 37 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. 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 6.6 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 8% on every change. The history of the code shows how much it changes: about 170,254 lines over the last 90 days, which is about 690,475 lines a year. At that pace, the extra work comes to an estimated 60.9 to 365.5 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.
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.
347 modules, with 477 dependencies between them. 6 loops run through 28 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 307 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.
Filament.Actions.Exports.Models uses Filament.Actions.Exports, so a change to Filament.Actions.Exports can break Filament.Actions.Exports.Models, while a change to Filament.Actions.Exports.Models can't break Filament.Actions.Exports.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→20 Filament.Actions.Imports.Models uses Filament.Actions.Importspart of a loop✕
Connections
1 pair of types, where a type in Filament.Actions.Imports.Models uses a type in Filament.Actions.Imports.
Filament.Actions.Imports.Models uses Filament.Actions.Imports, so a change to Filament.Actions.Imports can break Filament.Actions.Imports.Models, while a change to Filament.Actions.Imports.Models can't break Filament.Actions.Imports.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Support.Commands.FileGenerators uses Filament.Support.Commands.FileGenerators.Contracts, so a change to Filament.Support.Commands.FileGenerators.Contracts can break Filament.Support.Commands.FileGenerators, while a change to Filament.Support.Commands.FileGenerators can't break Filament.Support.Commands.FileGenerators.Contracts.
Position
Below the diagonal: Filament.Support.Commands.FileGenerators uses a module listed above it, which is the healthy direction.
8→11 Filament.Support.Components.Contracts uses Filament.Support.Componentspart of a loop✕
Connections
1 pair of types, where a type in Filament.Support.Components.Contracts uses a type in Filament.Support.Components.
Filament.Support.Components.Contracts uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Support.Components.Contracts, while a change to Filament.Support.Components.Contracts can't break Filament.Support.Components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Support.Contracts uses Filament.Support.Enums, so a change to Filament.Support.Enums can break Filament.Support.Contracts, while a change to Filament.Support.Contracts can't break Filament.Support.Enums.
Position
Below the diagonal: Filament.Support.Contracts uses a module listed above it, which is the healthy direction.
Filament.Schemas.Contracts uses Filament.Support.Contracts, so a change to Filament.Support.Contracts can break Filament.Schemas.Contracts, while a change to Filament.Schemas.Contracts can't break Filament.Support.Contracts.
Position
Below the diagonal: Filament.Schemas.Contracts uses a module listed above it, which is the healthy direction.
10→15 Filament.Schemas.Contracts uses Filament.Schemaspart of a loop✕
Connections
1 pair of types, where a type in Filament.Schemas.Contracts uses a type in Filament.Schemas.
Filament.Schemas.Contracts uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Schemas.Contracts, while a change to Filament.Schemas.Contracts can't break Filament.Schemas.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Support.Components uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Support.Components, while a change to Filament.Support.Components can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Support.Components uses a module listed above it, which is the healthy direction.
Filament.Forms.Components.RichEditor uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Forms.Components.RichEditor, while a change to Filament.Forms.Components.RichEditor can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Forms.Components.RichEditor uses a module listed above it, which is the healthy direction.
Filament.Forms.Components.RichEditor uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Forms.Components.RichEditor, while a change to Filament.Forms.Components.RichEditor can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Forms.Components.RichEditor uses a module listed above it, which is the healthy direction.
12→19 Filament.Forms.Components.RichEditor uses Filament.Forms.Componentspart of a loop✕
Connections
2 pairs of types, where a type in Filament.Forms.Components.RichEditor uses a type in Filament.Forms.Components.
Filament.Forms.Components.RichEditor uses Filament.Forms.Components, so a change to Filament.Forms.Components can break Filament.Forms.Components.RichEditor, while a change to Filament.Forms.Components.RichEditor can't break Filament.Forms.Components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→23 Filament.Forms.Components.RichEditor uses Filament.Actionspart of a loop✕
Connections
1 pair of types, where a type in Filament.Forms.Components.RichEditor uses a type in Filament.Actions.
Filament.Forms.Components.RichEditor uses Filament.Actions, so a change to Filament.Actions can break Filament.Forms.Components.RichEditor, while a change to Filament.Forms.Components.RichEditor can't break Filament.Actions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Notifications uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Notifications, while a change to Filament.Notifications can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Notifications uses a module listed above it, which is the healthy direction.
Filament.Notifications uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Notifications, while a change to Filament.Notifications can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Notifications uses a module listed above it, which is the healthy direction.
Filament.QueryBuilder.Constraints uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.QueryBuilder.Constraints, while a change to Filament.QueryBuilder.Constraints can't break Filament.Support.Components.
Position
Below the diagonal: Filament.QueryBuilder.Constraints uses a module listed above it, which is the healthy direction.
Filament.Schemas uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Schemas, while a change to Filament.Schemas can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Schemas uses a module listed above it, which is the healthy direction.
Filament.Schemas uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break Filament.Schemas, while a change to Filament.Schemas can't break Filament.Schemas.Contracts.
Position
Below the diagonal: Filament.Schemas uses a module listed above it, which is the healthy direction.
Filament.Schemas uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Schemas, while a change to Filament.Schemas can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Schemas uses a module listed above it, which is the healthy direction.
Filament.Actions.Exports uses Filament.Actions.Exports.Models, so a change to Filament.Actions.Exports.Models can break Filament.Actions.Exports, while a change to Filament.Actions.Exports can't break Filament.Actions.Exports.Models.
Position
Below the diagonal: Filament.Actions.Exports uses a module listed above it, which is the healthy direction.
Filament.Actions.Exports uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Actions.Exports, while a change to Filament.Actions.Exports can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Actions.Exports uses a module listed above it, which is the healthy direction.
Filament.Actions.Exports uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Actions.Exports, while a change to Filament.Actions.Exports can't break Filament.Notifications.
Position
Below the diagonal: Filament.Actions.Exports uses a module listed above it, which is the healthy direction.
16→22 Filament.Actions.Exports uses Filament.Actions.Testingpart of a loop✕
Connections
1 pair of types, where a type in Filament.Actions.Exports uses a type in Filament.Actions.Testing.
Filament.Actions.Exports uses Filament.Actions.Testing, so a change to Filament.Actions.Testing can break Filament.Actions.Exports, while a change to Filament.Actions.Exports can't break Filament.Actions.Testing.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.QueryBuilder.Constraints.Operators uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.QueryBuilder.Constraints.Operators, while a change to Filament.QueryBuilder.Constraints.Operators can't break Filament.Support.Components.
Position
Below the diagonal: Filament.QueryBuilder.Constraints.Operators uses a module listed above it, which is the healthy direction.
Filament.QueryBuilder.Constraints.Operators uses Filament.QueryBuilder.Constraints, so a change to Filament.QueryBuilder.Constraints can break Filament.QueryBuilder.Constraints.Operators, while a change to Filament.QueryBuilder.Constraints.Operators can't break Filament.QueryBuilder.Constraints.
Position
Below the diagonal: Filament.QueryBuilder.Constraints.Operators uses a module listed above it, which is the healthy direction.
Filament.Schemas.Components uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Schemas.Components, while a change to Filament.Schemas.Components can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Schemas.Components uses a module listed above it, which is the healthy direction.
Filament.Schemas.Components uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Schemas.Components, while a change to Filament.Schemas.Components can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Schemas.Components uses a module listed above it, which is the healthy direction.
Filament.Schemas.Components uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Schemas.Components, while a change to Filament.Schemas.Components can't break Filament.Schemas.
Position
Below the diagonal: Filament.Schemas.Components uses a module listed above it, which is the healthy direction.
18→23 Filament.Schemas.Components uses Filament.Actionspart of a loop✕
Connections
1 pair of types, where a type in Filament.Schemas.Components uses a type in Filament.Actions.
Filament.Schemas.Components uses Filament.Actions, so a change to Filament.Actions can break Filament.Schemas.Components, while a change to Filament.Schemas.Components can't break Filament.Actions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Forms.Components uses Filament.Support.Enums, so a change to Filament.Support.Enums can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Support.Enums.
Position
Below the diagonal: Filament.Forms.Components uses a module listed above it, which is the healthy direction.
Filament.Forms.Components uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Forms.Components uses a module listed above it, which is the healthy direction.
Filament.Forms.Components uses Filament.Forms.Components.RichEditor, so a change to Filament.Forms.Components.RichEditor can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Forms.Components.RichEditor.
Position
Below the diagonal: Filament.Forms.Components uses a module listed above it, which is the healthy direction.
Filament.Forms.Components uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Schemas.
Position
Below the diagonal: Filament.Forms.Components uses a module listed above it, which is the healthy direction.
Filament.Forms.Components uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Forms.Components uses a module listed above it, which is the healthy direction.
19→23 Filament.Forms.Components uses Filament.Actionspart of a loop✕
Connections
6 pairs of types, where a type in Filament.Forms.Components uses a type in Filament.Actions.
Filament.Forms.Components uses Filament.Actions, so a change to Filament.Actions can break Filament.Forms.Components, while a change to Filament.Forms.Components can't break Filament.Actions.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Actions.Imports uses Filament.Actions.Imports.Models, so a change to Filament.Actions.Imports.Models can break Filament.Actions.Imports, while a change to Filament.Actions.Imports can't break Filament.Actions.Imports.Models.
Position
Below the diagonal: Filament.Actions.Imports uses a module listed above it, which is the healthy direction.
Filament.Actions.Imports uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Actions.Imports, while a change to Filament.Actions.Imports can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Actions.Imports uses a module listed above it, which is the healthy direction.
Filament.Actions.Imports uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Actions.Imports, while a change to Filament.Actions.Imports can't break Filament.Notifications.
Position
Below the diagonal: Filament.Actions.Imports uses a module listed above it, which is the healthy direction.
Filament.Actions.Imports uses Filament.Forms.Components, so a change to Filament.Forms.Components can break Filament.Actions.Imports, while a change to Filament.Actions.Imports can't break Filament.Forms.Components.
Position
Below the diagonal: Filament.Actions.Imports uses a module listed above it, which is the healthy direction.
20→22 Filament.Actions.Imports uses Filament.Actions.Testingpart of a loop✕
Connections
1 pair of types, where a type in Filament.Actions.Imports uses a type in Filament.Actions.Testing.
Filament.Actions.Imports uses Filament.Actions.Testing, so a change to Filament.Actions.Testing can break Filament.Actions.Imports, while a change to Filament.Actions.Imports can't break Filament.Actions.Testing.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Tables.Filters uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Tables.Filters, while a change to Filament.Tables.Filters can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Tables.Filters uses a module listed above it, which is the healthy direction.
Filament.Tables.Filters uses Filament.QueryBuilder.Constraints, so a change to Filament.QueryBuilder.Constraints can break Filament.Tables.Filters, while a change to Filament.Tables.Filters can't break Filament.QueryBuilder.Constraints.
Position
Below the diagonal: Filament.Tables.Filters uses a module listed above it, which is the healthy direction.
Filament.Tables.Filters uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Tables.Filters, while a change to Filament.Tables.Filters can't break Filament.Schemas.
Position
Below the diagonal: Filament.Tables.Filters uses a module listed above it, which is the healthy direction.
Filament.Tables.Filters uses Filament.Forms.Components, so a change to Filament.Forms.Components can break Filament.Tables.Filters, while a change to Filament.Tables.Filters can't break Filament.Forms.Components.
Position
Below the diagonal: Filament.Tables.Filters uses a module listed above it, which is the healthy direction.
Filament.Actions.Testing uses Filament.Actions.Exports.Models, so a change to Filament.Actions.Exports.Models can break Filament.Actions.Testing, while a change to Filament.Actions.Testing can't break Filament.Actions.Exports.Models.
Position
Below the diagonal: Filament.Actions.Testing uses a module listed above it, which is the healthy direction.
Filament.Actions.Testing uses Filament.Actions.Imports.Models, so a change to Filament.Actions.Imports.Models can break Filament.Actions.Testing, while a change to Filament.Actions.Testing can't break Filament.Actions.Imports.Models.
Position
Below the diagonal: Filament.Actions.Testing uses a module listed above it, which is the healthy direction.
Filament.Actions.Testing uses Filament.Actions.Exports, so a change to Filament.Actions.Exports can break Filament.Actions.Testing, while a change to Filament.Actions.Testing can't break Filament.Actions.Exports.
Position
Below the diagonal: Filament.Actions.Testing uses a module listed above it, which is the healthy direction.
Filament.Actions.Testing uses Filament.Actions.Imports, so a change to Filament.Actions.Imports can break Filament.Actions.Testing, while a change to Filament.Actions.Testing can't break Filament.Actions.Imports.
Position
Below the diagonal: Filament.Actions.Testing uses a module listed above it, which is the healthy direction.
Filament.Actions uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Actions, while a change to Filament.Actions can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Actions uses a module listed above it, which is the healthy direction.
Filament.Actions uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Actions, while a change to Filament.Actions can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Actions uses a module listed above it, which is the healthy direction.
Filament.Actions uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Actions, while a change to Filament.Actions can't break Filament.Schemas.
Position
Below the diagonal: Filament.Actions uses a module listed above it, which is the healthy direction.
Filament.Actions uses Filament.Forms.Components, so a change to Filament.Forms.Components can break Filament.Actions, while a change to Filament.Actions can't break Filament.Forms.Components.
Position
Below the diagonal: Filament.Actions uses a module listed above it, which is the healthy direction.
Filament.Actions uses Filament.Actions.Testing, so a change to Filament.Actions.Testing can break Filament.Actions, while a change to Filament.Actions can't break Filament.Actions.Testing.
Position
Below the diagonal: Filament.Actions uses a module listed above it, which is the healthy direction.
Filament.Actions.Contracts uses Filament.Actions, so a change to Filament.Actions can break Filament.Actions.Contracts, while a change to Filament.Actions.Contracts can't break Filament.Actions.
Position
Below the diagonal: Filament.Actions.Contracts uses a module listed above it, which is the healthy direction.
Filament.Tables.Contracts uses Filament.Support.Contracts, so a change to Filament.Support.Contracts can break Filament.Tables.Contracts, while a change to Filament.Tables.Contracts can't break Filament.Support.Contracts.
Position
Below the diagonal: Filament.Tables.Contracts uses a module listed above it, which is the healthy direction.
Filament.Tables.Contracts uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Tables.Contracts, while a change to Filament.Tables.Contracts can't break Filament.Schemas.
Position
Below the diagonal: Filament.Tables.Contracts uses a module listed above it, which is the healthy direction.
Filament.Tables.Contracts uses Filament.Tables.Filters, so a change to Filament.Tables.Filters can break Filament.Tables.Contracts, while a change to Filament.Tables.Contracts can't break Filament.Tables.Filters.
Position
Below the diagonal: Filament.Tables.Contracts uses a module listed above it, which is the healthy direction.
Filament.Tables.Contracts uses Filament.Actions, so a change to Filament.Actions can break Filament.Tables.Contracts, while a change to Filament.Tables.Contracts can't break Filament.Actions.
Position
Below the diagonal: Filament.Tables.Contracts uses a module listed above it, which is the healthy direction.
25→27 Filament.Tables.Contracts uses Filament.Tablespart of a loop✕
Connections
1 pair of types, where a type in Filament.Tables.Contracts uses a type in Filament.Tables.
Filament.Tables.Contracts uses Filament.Tables, so a change to Filament.Tables can break Filament.Tables.Contracts, while a change to Filament.Tables.Contracts can't break Filament.Tables.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Pages uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break Filament.Pages, while a change to Filament.Pages can't break Filament.Schemas.Contracts.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Pages, while a change to Filament.Pages can't break Filament.Notifications.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Pages, while a change to Filament.Pages can't break Filament.Schemas.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Pages, while a change to Filament.Pages can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages uses Filament.Actions, so a change to Filament.Actions can break Filament.Pages, while a change to Filament.Pages can't break Filament.Actions.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break Filament.Pages, while a change to Filament.Pages can't break Filament.Actions.Contracts.
Position
Below the diagonal: Filament.Pages uses a module listed above it, which is the healthy direction.
Filament.Tables uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break Filament.Tables, while a change to Filament.Tables can't break Filament.Schemas.Contracts.
Position
Below the diagonal: Filament.Tables uses a module listed above it, which is the healthy direction.
Filament.Tables uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Tables, while a change to Filament.Tables can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Tables uses a module listed above it, which is the healthy direction.
Filament.Tables uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break Filament.Tables, while a change to Filament.Tables can't break Filament.Actions.Contracts.
Position
Below the diagonal: Filament.Tables uses a module listed above it, which is the healthy direction.
Filament.Tables uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break Filament.Tables, while a change to Filament.Tables can't break Filament.Tables.Contracts.
Position
Below the diagonal: Filament.Tables uses a module listed above it, which is the healthy direction.
App.Livewire uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break App.Livewire, while a change to App.Livewire can't break Filament.Schemas.Contracts.
Position
Below the diagonal: App.Livewire uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in App.Livewire uses a type in Filament.Schemas.
The types involved
App.Livewire.PrimesDemo → Filament.Schemas.Schema
Direction
App.Livewire uses Filament.Schemas, so a change to Filament.Schemas can break App.Livewire, while a change to App.Livewire can't break Filament.Schemas.
Position
Below the diagonal: App.Livewire uses a module listed above it, which is the healthy direction.
App.Livewire uses Filament.Actions, so a change to Filament.Actions can break App.Livewire, while a change to App.Livewire can't break Filament.Actions.
Position
Below the diagonal: App.Livewire uses a module listed above it, which is the healthy direction.
App.Livewire uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break App.Livewire, while a change to App.Livewire can't break Filament.Actions.Contracts.
Position
Below the diagonal: App.Livewire uses a module listed above it, which is the healthy direction.
App.Livewire uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break App.Livewire, while a change to App.Livewire can't break Filament.Tables.Contracts.
Position
Below the diagonal: App.Livewire uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Support.Enums, so a change to Filament.Support.Enums can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Support.Enums.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Actions.Exports.Models, so a change to Filament.Actions.Exports.Models can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Actions.Exports.Models.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Schemas.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Actions.Testing, so a change to Filament.Actions.Testing can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Actions.Testing.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Actions, so a change to Filament.Actions can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Actions.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Actions.Contracts.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Actions.Concerns uses Filament.Tables, so a change to Filament.Tables can break Filament.Actions.Concerns, while a change to Filament.Actions.Concerns can't break Filament.Tables.
Position
Below the diagonal: Filament.Actions.Concerns uses a module listed above it, which is the healthy direction.
Filament.Resources uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Resources, while a change to Filament.Resources can't break Filament.Schemas.
Position
Below the diagonal: Filament.Resources uses a module listed above it, which is the healthy direction.
Filament.Resources uses Filament.Tables, so a change to Filament.Tables can break Filament.Resources, while a change to Filament.Resources can't break Filament.Tables.
Position
Below the diagonal: Filament.Resources uses a module listed above it, which is the healthy direction.
30→34 Filament.Resources uses Filamentpart of a loop✕
Connections
1 pair of types, where a type in Filament.Resources uses a type in Filament.
The types involved
Filament.Resources.Resource → Filament.Panel
Direction
Filament.Resources uses Filament, so a change to Filament can break Filament.Resources, while a change to Filament.Resources can't break Filament.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Filament.Resources.RelationManagers uses Filament.Support.Enums, so a change to Filament.Support.Enums can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Support.Enums.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Schemas.Contracts.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Schemas.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Actions, so a change to Filament.Actions can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Actions.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Actions.Contracts.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Tables.Contracts.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Resources.RelationManagers uses Filament.Tables, so a change to Filament.Tables can break Filament.Resources.RelationManagers, while a change to Filament.Resources.RelationManagers can't break Filament.Tables.
Position
Below the diagonal: Filament.Resources.RelationManagers uses a module listed above it, which is the healthy direction.
Filament.Tables.Columns uses Filament.Support.Components.Contracts, so a change to Filament.Support.Components.Contracts can break Filament.Tables.Columns, while a change to Filament.Tables.Columns can't break Filament.Support.Components.Contracts.
Position
Below the diagonal: Filament.Tables.Columns uses a module listed above it, which is the healthy direction.
Filament.Tables.Columns uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament.Tables.Columns, while a change to Filament.Tables.Columns can't break Filament.Support.Components.
Position
Below the diagonal: Filament.Tables.Columns uses a module listed above it, which is the healthy direction.
Filament.Tables.Columns uses Filament.Tables, so a change to Filament.Tables can break Filament.Tables.Columns, while a change to Filament.Tables.Columns can't break Filament.Tables.
Position
Below the diagonal: Filament.Tables.Columns uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Schemas.Contracts, so a change to Filament.Schemas.Contracts can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Schemas.Contracts.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Schemas.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Actions.Contracts, so a change to Filament.Actions.Contracts can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Actions.Contracts.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Tables.Contracts.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament.Widgets uses Filament.Tables, so a change to Filament.Tables can break Filament.Widgets, while a change to Filament.Widgets can't break Filament.Tables.
Position
Below the diagonal: Filament.Widgets uses a module listed above it, which is the healthy direction.
Filament uses Filament.Pages.Enums, so a change to Filament.Pages.Enums can break Filament, while a change to Filament can't break Filament.Pages.Enums.
Position
Below the diagonal: Filament uses a module listed above it, which is the healthy direction.
Filament uses Filament.Support.Components, so a change to Filament.Support.Components can break Filament, while a change to Filament can't break Filament.Support.Components.
Position
Below the diagonal: Filament uses a module listed above it, which is the healthy direction.
Filament.Panel.Concerns uses Filament.Pages.Enums, so a change to Filament.Pages.Enums can break Filament.Panel.Concerns, while a change to Filament.Panel.Concerns can't break Filament.Pages.Enums.
Position
Below the diagonal: Filament.Panel.Concerns uses a module listed above it, which is the healthy direction.
Filament.Panel.Concerns uses Filament.Actions, so a change to Filament.Actions can break Filament.Panel.Concerns, while a change to Filament.Panel.Concerns can't break Filament.Actions.
Position
Below the diagonal: Filament.Panel.Concerns uses a module listed above it, which is the healthy direction.
Filament.Panel.Concerns uses Filament.Pages, so a change to Filament.Pages can break Filament.Panel.Concerns, while a change to Filament.Panel.Concerns can't break Filament.Pages.
Position
Below the diagonal: Filament.Panel.Concerns uses a module listed above it, which is the healthy direction.
Filament.Panel.Concerns uses Filament.Resources, so a change to Filament.Resources can break Filament.Panel.Concerns, while a change to Filament.Panel.Concerns can't break Filament.Resources.
Position
Below the diagonal: Filament.Panel.Concerns uses a module listed above it, which is the healthy direction.
Filament.Tables.Table.Concerns uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Tables.Table.Concerns, while a change to Filament.Tables.Table.Concerns can't break Filament.Schemas.
Position
Below the diagonal: Filament.Tables.Table.Concerns uses a module listed above it, which is the healthy direction.
Filament.Tables.Table.Concerns uses Filament.Tables.Filters, so a change to Filament.Tables.Filters can break Filament.Tables.Table.Concerns, while a change to Filament.Tables.Table.Concerns can't break Filament.Tables.Filters.
Position
Below the diagonal: Filament.Tables.Table.Concerns uses a module listed above it, which is the healthy direction.
Filament.Tables.Table.Concerns uses Filament.Actions, so a change to Filament.Actions can break Filament.Tables.Table.Concerns, while a change to Filament.Tables.Table.Concerns can't break Filament.Actions.
Position
Below the diagonal: Filament.Tables.Table.Concerns uses a module listed above it, which is the healthy direction.
Filament.Tables.Table.Concerns uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break Filament.Tables.Table.Concerns, while a change to Filament.Tables.Table.Concerns can't break Filament.Tables.Contracts.
Position
Below the diagonal: Filament.Tables.Table.Concerns uses a module listed above it, which is the healthy direction.
Filament.Tables.Table.Concerns uses Filament.Tables.Columns, so a change to Filament.Tables.Columns can break Filament.Tables.Table.Concerns, while a change to Filament.Tables.Table.Concerns can't break Filament.Tables.Columns.
Position
Below the diagonal: Filament.Tables.Table.Concerns uses a module listed above it, which is the healthy direction.
Filament.Auth.Pages uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Auth.Pages, while a change to Filament.Auth.Pages can't break Filament.Notifications.
Position
Below the diagonal: Filament.Auth.Pages uses a module listed above it, which is the healthy direction.
Filament.Auth.Pages uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Auth.Pages, while a change to Filament.Auth.Pages can't break Filament.Schemas.
Position
Below the diagonal: Filament.Auth.Pages uses a module listed above it, which is the healthy direction.
Filament.Auth.Pages uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Auth.Pages, while a change to Filament.Auth.Pages can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Auth.Pages uses a module listed above it, which is the healthy direction.
Filament.Auth.Pages uses Filament.Actions, so a change to Filament.Actions can break Filament.Auth.Pages, while a change to Filament.Auth.Pages can't break Filament.Actions.
Position
Below the diagonal: Filament.Auth.Pages uses a module listed above it, which is the healthy direction.
Filament.Auth.Pages uses Filament.Pages, so a change to Filament.Pages can break Filament.Auth.Pages, while a change to Filament.Auth.Pages can't break Filament.Pages.
Position
Below the diagonal: Filament.Auth.Pages uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.Notifications.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.Schemas.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament.Actions, so a change to Filament.Actions can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.Actions.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament.Pages, so a change to Filament.Pages can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.Pages.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Pages.Tenancy uses Filament, so a change to Filament can break Filament.Pages.Tenancy, while a change to Filament.Pages.Tenancy can't break Filament.
Position
Below the diagonal: Filament.Pages.Tenancy uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Pages.Enums, so a change to Filament.Pages.Enums can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Pages.Enums.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Notifications, so a change to Filament.Notifications can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Notifications.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Schemas, so a change to Filament.Schemas can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Schemas.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Schemas.Components, so a change to Filament.Schemas.Components can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Schemas.Components.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Actions, so a change to Filament.Actions can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Actions.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Tables.Contracts, so a change to Filament.Tables.Contracts can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Tables.Contracts.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Pages, so a change to Filament.Pages can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Pages.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament.Tables, so a change to Filament.Tables can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.Tables.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
Filament.Resources.Pages uses Filament, so a change to Filament can break Filament.Resources.Pages, while a change to Filament.Resources.Pages can't break Filament.
Position
Below the diagonal: Filament.Resources.Pages uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 37% · Weak · gated by R1, X5 ·
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 category
Findings
Severity
A07:2025 — Authentication Failures
13
High / Critical
A03:2025 — Software Supply Chain Failures
4
Medium
A05:2025 — Injection
2
High / Critical
Roadmap
Begin by establishing type safety in the frontend by adopting TypeScript and raising PHPStan to its strictest level to enforce nullable reference types, ensuring all identified nullness errors are actively resolved rather than silenced. Next, implement cancellation propagation by threading AbortSignals through async functions to ensure work stops when callers give up. Finally, improve architectural clarity by documenting significant design decisions in a dedicated ADR folder to capture context and consequences for future reference.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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.
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.
Reconcile the README with reality: docs/02-getting-started.md links to `introduction/installation#installing-the-panel-builder`, but `docs/introduction/installation` does not exist; docs/02-getting-started.md links to `components`, but `docs/components` does not exist; docs/02-getting-started.md links to `resources`, but `docs/resources` does not exist; docs/02-getting-started.md links to `widgets`, but `docs/widgets` does not exist; docs/02-getting-started.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist.
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 — 23
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 — 1388
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 — 94
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 18
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. 74 of 77 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 — 77 dimensions across the health lenses
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
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, 1479 of 1505 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.)
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.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — docs-assets/screenshots/ (puppeteer) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and 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, .js) 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.
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.
D22 Internal API Consistency — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (composer.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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. `docs-assets/app/app/Support/DemoData.php`, `packages/actions/src/Concerns/InteractsWithActions.php`, `packages/actions/src/CreateAction.php`, `packages/actions/src/EditAction.php`, `packages/actions/src/Exports/Concerns/CanFormatState.php`, … (+65 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.
D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC1 Text alternatives — 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 renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC2 Forms & labels — 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 renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC3 Page structure — 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 renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC4 Keyboard semantics — 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 repository renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC5 ARIA correctness — 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 renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — 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 renders user interface from a TEMPLATE LANGUAGE — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — and the accessibility cards on this run were measured over the 110 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
AC6 Visual & motion safety — 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
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 Symfony DependencyInjection, 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.
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 this repository's , PHP is most of its product and 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 this repository's , PHP is most of its product and 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.
M4 Documentation accuracy — 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. 498 further occurrence(s) are not listed individually; the score already reflects all 538.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. The JavaScript/TypeScript, PHP source it reads makes no outbound call, and the rest of this repository's production source is , which it does not read yet — the calls may well be there — a gap in this analyzer's language reach, not a finding about the code.
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.
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.
X4 Structured logging — 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, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, 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: 16 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
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.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED 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.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
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.
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.
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.
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.
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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): D19, D21, 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.
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.
210 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was dropdown.default at 106. A further 8 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 IsAfterOperator.resolveRelativeDate at 31 — they are counted neither in the figure above nor in this dimension's score. 4 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: packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php (IsAfterOperator.resolveRelativeDate at 31), packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php (IsBeforeOperator.resolveRelativeDate at 31), docs-assets/app/app/Livewire/Infolists/Entries/IconSchema.php (IconSchema.schema at 16), packages/support/src/Colors/ColorManager.php (ColorManager.getComponentClasses at 16). 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.
+ 180 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 15 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with dropdown.default (cyclomatic 106), (anonymous) (cyclomatic 84), table.default (cyclomatic 79). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 15 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
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.
+ 243 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 120 down to 120 or less in Cognitive Complexity — start with dateTimePickerFormComponent (cognitive 181), Builder.toEmbeddedHtml (cognitive 142), toggleCodeBlock (cognitive 140). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 5.0 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
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.
Do you agree with this assessment?
D3 · God Classes8.0 / 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.
Resolve the 56 TooManyMethods finding(s) in God Classes — start with HasState.php (2), Page.php (2), CanFormatState.php (2). — One of this dimension's main actionable groups (56 warning-level).
Resolve the 39 MethodTooLong finding(s) in God Classes — start with Repeater.php (3), Builder.php (2), Field.php (2). — One of this dimension's main actionable groups (39 warning-level).
Resolve the 36 FunctionTooLong finding(s) in God Classes — start with REDACTED (3), rich-editor.js (2), file-upload.js (2). — One of this dimension's main actionable groups (36 warning-level).
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.
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.
415 duplicated block group(s) detected. A further 38 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 29 of the 453 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.
+ 169 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 20 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with HasAffixes.php (2), IconEntry.php (2), AssociateAction.php. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 20 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with IsAfterOperator.php (2), XlsxExportContentGenerator.php, Builder.php. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 19 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Builder.php (2), ActionGroup.php, DateTimePicker.php. — One of this dimension's main actionable groups (19 warning-level).
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.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 1 serious finding✓ 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.
17 production modules (Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: filament/support
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
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.
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.
Resolve the 68 Low cohesion finding(s) in Cohesion (LCOM4) — start with Component.php (3), TableColumn.php (2), Table.php. — One of this dimension's main actionable groups (68 warning-level).
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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
2 outdated direct production npm dependency(ies) of 3 graded, 0 pinning defect(s), across 3 package.json (3 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated (npm): pixelmatch · ×2
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 3 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 3 production dependency(ies) this repository's committed lockfile resolves, across 3 product package.json manifest(s). Its 98 `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.
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.
Top hotspots: packages/forms/src/Components/Builder.php (15×65=975); packages/support/resources/js/components/dropdown.js (7×106=742); packages/forms/resources/js/components/file-upload.js (10×64=640) Repeated repair below the complexity floor: packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php (5 of 8 changes were fixes); packages/forms/src/Components/ColorPicker.php (5 of 7 changes were fixes); packages/actions/src/Imports/ImportColumn.php (5 of 6 changes were fixes)
Resolve the 54 Hotspot finding(s) in Churn × Complexity Hotspots — start with CanFormatState.php (2), Builder.php, dropdown.js. — One of this dimension's main actionable groups (54 warning-level).
Resolve the 14 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.js (3), AppAuthentication.php, ColorPicker.php. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.8 / 10Strong✓ 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.
60 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php. Counted over 522 of the 1496 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 deducted task-comment markers across 289216 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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The Filament repository is well documented: a root README with an impressive banner and a clear 'Build apps & admin panels fast' hook plus links to Laravel v11+, Livewire v3, PHP 8.2+; the packages/spatie-* directories each have focused READMEs for their own plugins (Google Fonts, Media Library, Settings, Tags) that document installation, usage examples, and internal Spatie integration; a dedicated docs/02-getting-started.md covers getting started with panel configuration, resources, widgets, and deployment steps; the upgrade guide is thorough. The visible content is complete and well-structured for its scope. This repository's documentation is comprehensive and well-structured: the README for each directory (e.g. docs/01-introduction) gives an overview of what the project does and how to use its contents, with installation, usage, contribution guidance, and license in place for every root-level document. The architecture/design docs are also fully present and detailed, covering SDUI concepts, Laravel Boost integration, OPcache optimization, versioning policy, resource creation, editing, and more. All visible documents are well-organized by heading outline; the only unshown section is a clip marker, so no sections were omitted from the outline as missing. This Filament project's documentation is comprehensive and well-structured: it contains 5 README files (each covering a specific feature like viewing/creating resources with a View page, soft-deletes, nested resources, singular pages, and global search) plus architecture/design docs at 161 documents. Each document has an overview section stating what the project does for its readers, and every visible file is complete within its body (no clipped sections). The documentation is clear, focused on a single topic per file, and well-organized with headings; it lacks no standard guidance for contributors or license but is not required by the repository's scope.
Documentation: contradicts the code · ×3docs/01-introduction/05-version-support-policy.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. 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.
7 of 17 build units (Composer, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
12 finding(s): 0 critical, 12 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 11 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
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.
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).
2 finding(s): 0 critical, 1 high, 1 medium, 0 low. semgrep hit a parse error in 70 file(s) — `docs-assets/app/app/Support/DemoData.php` (line 18, line 69), `packages/actions/src/Concerns/InteractsWithActions.php` (line 538, line 593), `packages/actions/src/CreateAction.php` (line 68), `packages/actions/src/EditAction.php` (line 45, line 82), `packages/actions/src/Exports/Concerns/CanFormatState.php` (line 116), … (+65 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
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
8 of 522 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php. Counted over 522 of the 1496 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with EditRecord.php, CreateRecord.php, ImageEntry.php. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 24 Change coupling finding(s) in Change Coupling — start with RequestPasswordReset.php (2), CheckboxColumn.php (2), SpatieMediaLibraryImageEntry.php. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 5 Change-coupling hub finding(s) in Change Coupling — start with EditRecord.php, EditTenantProfile.php, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
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.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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.
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>. (×3) — docs-assets/app/resources/views/components/layouts/app.blade.php:2, packages/panels/resources/views/components/layout/base.blade.php:14, packages/support/stubs/scaffolding/resources/views/components/layouts/app.blade.php:2
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.
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.
aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable. — packages/support/resources/views/components/pagination/item.blade.php:24
What to do
Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
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.
`.fi-wi-stats-overview-stat` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/widgets/resources/css/stats-overview-widget.css:2
`.fi-ta-header-cell .fi-ta-header-cell-sort-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/tables/resources/css/header-cell.css:126
`.fi-ta-color > .fi-ta-color-item.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/tables/resources/css/columns/color.css:73
`.fi-ta-text-item > .fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/tables/resources/css/columns/text.css:200
`.fi-badge .fi-badge-delete-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/badge.css:62
`.fi-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/button.css:3
`.fi-icon-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/icon-button.css:2
`.fi-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/link.css:2
`.fi-modal > .fi-modal-window-ctn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/modal.css:135
`.fi-modal > .fi-modal-window-ctn > .fi-modal-window` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/modal.css:170
`.fi-modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/modal.css:2
`.fi-pagination .fi-pagination-item-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/pagination.css:67
`.fi-tabs-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/tabs.css:30
`.fi-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/toggle.css:2
`input[type='checkbox'].fi-checkbox-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/checkbox.css:2
`input.fi-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/index.css:2
`.fi-one-time-code-input-ctn > .fi-one-time-code-input-digit` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/one-time-code.css:5
`input[type='radio'].fi-radio-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/radio.css:2
`select.fi-select-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/select.css:2
`.fi-select-input .fi-select-input-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/select.css:33
`.fi-select-input .fi-select-input-value-remove-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/input/select.css:79
`.fi-dropdown-list-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/support/resources/css/components/dropdown/list/item.css:2
`.fi-sc-text.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/schemas/resources/css/components/text.css:3
`.fi-skip-link:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/panels/resources/css/utilities.css:2
`.fi-main` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/panels/resources/css/components/layout.css:61
`.fi-in-code.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/infolists/resources/css/components/code.css:19
`.fi-in-color > .fi-in-color-item.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/infolists/resources/css/components/color.css:31
`.fi-in-text-item > .fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/infolists/resources/css/components/text.css:137
`.fi-fo-builder .fi-fo-builder-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/builder.css:21
`.fi-fo-builder` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/builder.css:2
`.fi-fo-date-time-picker .fi-fo-date-time-picker-calendar` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/date-time-picker.css:65
`.fi-fo-markdown-editor.fi-disabled[style*='--max-height']` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/markdown-editor.css:35
`.fi-fo-repeater .fi-fo-repeater-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/repeater.css:17
`.fi-fo-repeater` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/repeater.css:2
`.fi-fo-rich-editor[style*='--max-height'] .fi-fo-rich-editor-content[role='region']` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/rich-editor.css:160
`.fi-fo-rich-editor .fi-fo-rich-editor-custom-block-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/rich-editor.css:235
`.fi-fo-rich-editor .fi-fo-rich-editor-custom-blocks-search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/rich-editor.css:272
`.fi-fo-rich-editor .tiptap:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/rich-editor.css:283
`.fi-fo-rich-editor.fi-disabled [data-resize-state='true'] [data-resize-wrapper]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/rich-editor.css:497
`.fi-fo-textarea textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — packages/forms/resources/css/components/textarea.css:5
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.
Do you agree with this assessment?
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 110 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.
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.
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.
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.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not only APP_KEY in .env) and encrypt the most sensitive columns (Eloquent 'encrypted' casts, CipherSweet) — partial coverage still leaves gaps.
Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
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.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — Gate abilities and policy classes (Gate::define, a UserPolicy), spatie/laravel-permission roles and permissions, or a Symfony Voter — and consult them where access is checked ($this->authorize, a can: middleware, #[IsGranted]), so the rule set is reviewable and testable on its own.
Do you agree with this assessment?
C4 · Data Retention9.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a documented retention period / data-expiry.
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
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.
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 13 of 18 project(s) that lack one — worth up to 1.4 pts.
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.
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.
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.
docs/02-getting-started.md links to `introduction/installation#installing-the-panel-builder`, but `docs/introduction/installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-getting-started.md:5
docs/02-getting-started.md links to `components`, but `docs/components` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-getting-started.md:8
docs/02-getting-started.md links to `resources`, but `docs/resources` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-getting-started.md:28
docs/02-getting-started.md links to `widgets`, but `docs/widgets` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-getting-started.md:40
docs/02-getting-started.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/02-getting-started.md:48
docs/05-panel-configuration.md links to `resources/overview`, but `docs/resources/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:11
docs/05-panel-configuration.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:11
docs/05-panel-configuration.md links to `widgets/overview`, but `docs/widgets/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:11
docs/05-panel-configuration.md links to `advanced/render-hooks#available-render-hooks`, but `docs/advanced/render-hooks` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:85
docs/05-panel-configuration.md links to `resources/creating-records`, but `docs/resources/creating-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:282
docs/05-panel-configuration.md links to `resources/editing-records`, but `docs/resources/editing-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:282
docs/05-panel-configuration.md links to `advanced/assets`, but `docs/advanced/assets` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:321
docs/05-panel-configuration.md links to `introduction/installation#publishing-configuration`, but `docs/introduction/installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/05-panel-configuration.md:407
docs/13-deployment.md links to `introduction/optimizing-local-development`, but `docs/introduction/optimizing-local-development` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/13-deployment.md:9
docs/13-deployment.md links to `users/overview#authorizing-access-to-the-panel`, but `docs/users/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/13-deployment.md:15
docs/14-upgrade-guide.md links to `styling/overview#creating-a-custom-theme`, but `docs/styling/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/14-upgrade-guide.md:279
docs/14-upgrade-guide.md links to `actions/import#customizing-the-import-job-retries`, but `docs/actions/import` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/14-upgrade-guide.md:558
docs/14-upgrade-guide.md links to `actions/export#customizing-the-export-job-retries`, but `docs/actions/export` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/14-upgrade-guide.md:558
docs/01-introduction/01-overview.md links to `../styling`, but `docs/styling` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/01-overview.md:70
docs/01-introduction/01-overview.md links to `../testing`, but `docs/testing` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/01-overview.md:76
docs/01-introduction/02-installation.md links to `../getting-started`, but `docs/getting-started` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/02-installation.md:51
docs/01-introduction/02-installation.md links to `../components`, but `docs/components` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/02-installation.md:90
docs/01-introduction/02-installation.md links to `../notifications`, but `docs/notifications` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/02-installation.md:113
docs/01-introduction/04-optimizing-local-development.md links to `../deployment`, but `docs/deployment` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/01-introduction/04-optimizing-local-development.md:7
docs/03-resources/01-overview.md links to `deleting-records#handling-soft-deletes`, but `docs/03-resources/deleting-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:77
docs/03-resources/01-overview.md links to `viewing-records`, but `docs/03-resources/viewing-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:81
docs/03-resources/01-overview.md links to `global-search`, but `docs/03-resources/global-search` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:117
docs/03-resources/01-overview.md links to `../forms`, but `docs/forms` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:158
docs/03-resources/01-overview.md links to `../tables`, but `docs/tables` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:258
docs/03-resources/01-overview.md links to `../navigation/overview#rendering-html-in-navigation-item-labels`, but `docs/navigation/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:364
docs/03-resources/01-overview.md links to `../navigation/clusters`, but `docs/navigation/clusters` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:470
docs/03-resources/01-overview.md links to `../navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:470
docs/03-resources/01-overview.md links to `editing-records`, but `docs/03-resources/editing-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:590
docs/03-resources/01-overview.md links to `managing-relationships#relation-pages`, but `docs/03-resources/managing-relationships` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:592
docs/03-resources/01-overview.md links to `../navigation`, but `docs/navigation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/01-overview.md:612
docs/03-resources/02-listing-records.md links to `../styling/icons`, but `docs/styling/icons` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/02-listing-records.md:51
docs/03-resources/02-listing-records.md links to `overview#customizing-the-resource-eloquent-query`, but `docs/03-resources/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/02-listing-records.md:187
docs/03-resources/02-listing-records.md links to `../schemas`, but `docs/schemas` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/02-listing-records.md:202
docs/03-resources/03-creating-records.md links to `../actions/create#customizing-data-before-saving`, but `docs/actions/create` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/03-creating-records.md:20
docs/03-resources/03-creating-records.md links to `../panel-configuration`, but `docs/panel-configuration` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/03-resources/03-creating-records.md:61
What to do
Reconcile the README with reality: docs/02-getting-started.md links to `introduction/installation#installing-the-panel-builder`, but `docs/introduction/installation` does not exist; docs/02-getting-started.md links to `components`, but `docs/components` does not exist; docs/02-getting-started.md links to `resources`, but `docs/resources` does not exist; docs/02-getting-started.md links to `widgets`, but `docs/widgets` does not exist; docs/02-getting-started.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/upgrade`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add OpenTelemetry tracing/metrics (opentelemetry-php) so requests are traceable across the system, not just health-probable.
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
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.readFileSync` in `buildInter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/fonts.js:72
`fs.writeFileSync` in `buildInter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — bin/fonts.js:90, bin/fonts.js:97
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 86 plain JS — the untyped files are packages/actions/resources/js/components/modals.js, packages/actions/resources/js/index.js, packages/forms/resources/js/components/builder.js, packages/forms/resources/js/components/checkbox-list.js, packages/forms/resources/js/components/code-editor.js, packages/forms/resources/js/components/color-picker.js (+80 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
5 duplicated blocks under packages/ have copies in at least two of the sibling directories forms, panels, schemas, support, tables — 1 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/forms/resources/js/components/select.js:25
packages/forms/resources/js/components/rich-editor/extension-mention.js:20 · packages/forms/resources/js/components/rich-editor/extension-merge-tag.js:15 — the two spans are one implementation copied and then locally edited — 636 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/forms/resources/js/components/rich-editor/extension-mention.js:20
packages/forms/resources/js/components/rich-editor/mention-suggestion.js:187 · packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:95 — the two spans are one implementation copied and then locally edited — 314 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/forms/resources/js/components/rich-editor/mention-suggestion.js:187
packages/forms/resources/js/components/rich-editor/extension-grid-column.js:27 · packages/forms/resources/js/components/rich-editor/extension-grid.js:114 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/rich-editor/extension-grid-column.js:27
packages/forms/resources/js/components/rich-editor/mention-suggestion.js:130 · packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:50 — the two spans are one implementation copied and then locally edited — 167 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/forms/resources/js/components/rich-editor/mention-suggestion.js:130
packages/widgets/resources/js/components/chart.js:58 · packages/widgets/resources/js/components/stats-overview/stat/chart.js:35 — the two spans are one implementation copied and then locally edited — 117 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/widgets/resources/js/components/chart.js:58
packages/forms/resources/js/components/rich-editor/extension-custom-block.js:55 · packages/forms/resources/js/components/rich-editor/extension-custom-block.js:90 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/rich-editor/extension-custom-block.js:55
packages/support/resources/js/utilities/select.js:1872 · packages/support/resources/js/utilities/select.js:1892 — 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. — packages/support/resources/js/utilities/select.js:1872
packages/forms/resources/js/components/date-time-picker.js:192 · packages/forms/resources/js/components/date-time-picker.js:214 · packages/forms/resources/js/components/date-time-picker.js:236 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/date-time-picker.js:192
packages/forms/resources/js/components/rich-editor/extension-local-files.js:182 · packages/forms/resources/js/components/rich-editor/extension-local-files.js:229 — 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. — packages/forms/resources/js/components/rich-editor/extension-local-files.js:182
packages/forms/resources/js/components/markdown-editor.js:47 · packages/forms/resources/js/components/markdown-editor.js:68 — 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. — packages/forms/resources/js/components/markdown-editor.js:47
packages/forms/resources/js/components/rich-editor/extension-custom-block.js:176 · packages/forms/resources/js/components/rich-editor/extension-image.js:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/rich-editor/extension-custom-block.js:176
packages/support/resources/js/components/dropdown.js:560 · packages/support/resources/js/components/dropdown.js:640 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/support/resources/js/components/dropdown.js:560
packages/tables/resources/js/components/columns/checkbox.js:3 · packages/tables/resources/js/components/columns/toggle.js:3 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/tables/resources/js/components/columns/checkbox.js:3
packages/forms/resources/js/components/file-upload.js:683 · packages/forms/resources/js/components/file-upload.js:700 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/file-upload.js:683
REDACTED:961 · REDACTED:978 — 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. — REDACTED:961
REDACTED:2360 · REDACTED:2380 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2360
REDACTED:2870 · REDACTED:3009 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2870
packages/forms/resources/js/components/rich-editor.js:777 · packages/forms/resources/js/components/rich-editor.js:811 — 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. — packages/forms/resources/js/components/rich-editor.js:777
packages/schemas/resources/js/components/tabs.js:158 · packages/schemas/resources/js/components/wizard.js:30 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/schemas/resources/js/components/tabs.js:158
packages/support/resources/js/utilities/select.js:1207 · packages/support/resources/js/utilities/select.js:1223 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/support/resources/js/utilities/select.js:1207
packages/tables/resources/js/components/columns/select.js:144 · packages/tables/resources/js/components/columns/text-input.js:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/tables/resources/js/components/columns/select.js:144
REDACTED:2129 · REDACTED:2148 — 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. — REDACTED:2129
packages/tables/resources/js/components/column-manager.js:193 · packages/tables/resources/js/components/column-manager.js:234 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/tables/resources/js/components/column-manager.js:193
packages/schemas/resources/js/index.js:260 · packages/support/resources/js/partials.js:12 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/schemas/resources/js/index.js:260
packages/tables/resources/js/components/column-manager.js:410 · packages/tables/resources/js/components/table.js:802 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/tables/resources/js/components/column-manager.js:410
packages/forms/resources/js/components/date-time-picker.js:392 · packages/forms/resources/js/components/date-time-picker.js:404 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/date-time-picker.js:392
REDACTED:2194 · REDACTED:2225 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2194
packages/support/resources/js/utilities/select.js:1560 · packages/support/resources/js/utilities/select.js:1569 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/support/resources/js/utilities/select.js:1560
packages/forms/resources/js/components/file-upload.js:327 · packages/forms/resources/js/components/rich-editor/extension-local-files.js:36 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/forms/resources/js/components/file-upload.js:327
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
packages/forms/resources/js/components/markdown-editor.js:6 imports codemirror/lib/codemirror, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/forms/resources/js/components/markdown-editor.js:6
packages/notifications/resources/js/components/notification.js:1 imports alpinejs/src/utils/once, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/notifications/resources/js/components/notification.js:1
packages/panels/resources/js/echo.js:2 imports pusher-js/dist/web/pusher, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/panels/resources/js/echo.js:2
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
EasyMDE has cyclomatic complexity 53 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1933
toggleCodeBlock has cyclomatic complexity 42 and cognitive complexity 114; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:501
renderOptions has cyclomatic complexity 37 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:306
render has cyclomatic complexity 35 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:2346
openDropdown has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:1369
handleToolbarKeydown has cyclomatic complexity 31 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/forms/resources/js/components/rich-editor.js:679
handleDropdownKeydown has cyclomatic complexity 30 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:1262
getLabelsForMultipleSelection has cyclomatic complexity 27 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:684
createToolbarButton has cyclomatic complexity 25 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:218
positionOverflow has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/schemas/resources/js/components/tabs.js:449
(anonymous) has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/schemas/resources/js/components/tabs.js:659
createToolbar has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3107
scrollOverflow has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/schemas/resources/js/components/tabs.js:377
keydown has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/panels/resources/js/components/global-search.js:152
handleCalendarKeydown has cyclomatic complexity 20 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/forms/resources/js/components/date-time-picker.js:472
reconcile has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/forms/resources/js/utilities/reordering.js:300
init has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/forms/resources/js/components/file-upload.js:130
createOptionElement has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:507
syncActionModals has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/actions/resources/js/components/modals.js:95
updateOptionLabelInList has cyclomatic complexity 16 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/support/resources/js/utilities/select.js:1187
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files5.3 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 3219 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
packages/support/resources/js/utilities/select.js has 2039 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/support/resources/js/utilities/select.js:1
packages/forms/resources/js/components/file-upload.js has 1001 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/forms/resources/js/components/file-upload.js:1
packages/forms/resources/js/components/rich-editor.js has 933 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/forms/resources/js/components/rich-editor.js:1
packages/schemas/resources/js/components/tabs.js has 822 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/schemas/resources/js/components/tabs.js:1
packages/forms/resources/js/components/date-time-picker.js has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/forms/resources/js/components/date-time-picker.js:1
packages/tables/resources/js/components/table.js has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/tables/resources/js/components/table.js:1
packages/support/resources/js/components/dropdown.js has 579 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/support/resources/js/components/dropdown.js:1
packages/forms/resources/js/components/markdown-editor.js has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/forms/resources/js/components/markdown-editor.js:1
packages/forms/resources/js/utilities/reordering.js has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/forms/resources/js/utilities/reordering.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
87 file(s) (~23324 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
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.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
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.
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.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`load` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/forms/resources/js/components/file-upload.js:301
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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.
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.
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped1.2 / 10Critical✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`options.icon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:318
`newValue` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:1151, REDACTED:1162
`preview_result` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:1229, REDACTED:3377
`save+dd` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:2790
`wordCount(cm.getValue())` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:3265, REDACTED:3268
`cm.lineCount()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:3272, REDACTED:3275
`posLine+':'+posColumn` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:3285
`options.imageTexts.sbInit` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:3298
`extension.options.editCustomBlockButtonIconHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/forms/resources/js/components/rich-editor/extension-custom-block.js:73
`extension.options.deleteCustomBlockButtonIconHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/forms/resources/js/components/rich-editor/extension-custom-block.js:108
`new TextDecoder().decode(Uint8Array.from(atob(node.attrs.preview),(char)=>char.charCodeAt(0),),)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/forms/resources/js/components/rich-editor/extension-custom-block.js:131
`cleanedHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/forms/resources/js/components/rich-editor/extension-local-files.js:368
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/partials.js:47
`toEl.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/partials.js:79
`toEl.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/partials.js:83
`optionLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — packages/support/resources/js/utilities/select.js:546, packages/support/resources/js/utilities/select.js:563
`label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/utilities/select.js:804
`selectedLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/utilities/select.js:983
`newLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/support/resources/js/utilities/select.js:1201
`column.label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — packages/tables/resources/js/components/column-manager.js:257
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
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.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — packages/forms/resources/js/components/markdown-editor.js:220, packages/forms/resources/js/components/rich-editor/extension-mention.js:308, packages/forms/resources/js/components/rich-editor/extension-mention.js:374, …
`catch` 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. — packages/forms/resources/js/components/rich-editor/extension-local-files.js:305
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/forms/resources/js/utilities/reordering.js:295
`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. — packages/support/src/helpers.php:520
`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. — packages/upgrade/src/check-compatibility.php:230
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
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.
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.
0/5 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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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).
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.
Unscored — 1 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.
Not evidenced — 3 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 — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 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.
AC4 Keyboard semantics — AC4 could not be measured here. This repository renders user interface from a template language — 19 Laravel (Blade) template file(s) carrying 351 markup element(s) (e.g. packages/widgets/resources/views/stats-overview-widget/stat.blade.php, packages/tables/resources/views/index.blade.php, packages/tables/resources/views/components/filters.blade.php) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no interactive element from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no interactive element.
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.
D10 Test Quality — ~123932 lines of test source are present (.php, .js) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .php test runner
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.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
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 (docs-assets), 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
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.php), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 70 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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 measured — JavaScript/TypeScript suite
D9 Test Distribution — Test source is present (.php, .js) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 11 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 36 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'.
P7 Outbound HTTP resilience — 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
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 and TypeScript/JavaScript 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.
R4 Test Coverage — the JS/TS workspace (86 production file(s)) has no JavaScript/TypeScript test, but it is 6.4% of this repository's production source and the other 93.6% carries 123,932 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
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.
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.
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. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no 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
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.
X4 Structured logging — 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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — 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.
Boundary-crossing change coupling: EditRecord.php ↔ SettingsPage.php packages/panels/src/Resources/Pages/EditRecord.php:1— `packages/panels/src/Resources/Pages/EditRecord.php` (context panels) and `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php` (context spatie-laravel-settings-plugin) sit in DIFFERENT parts of the tree yet change together 91% of the time (10 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) — 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 `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms; `0c700362` Refactor to pass url to hasSpaMode across codebase — run `git show` on any of them.
Boundary-crossing change coupling: CreateRecord.php ↔ SettingsPage.php packages/panels/src/Resources/Pages/CreateRecord.php:1— `packages/panels/src/Resources/Pages/CreateRecord.php` (context panels) and `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php` (context spatie-laravel-settings-plugin) sit in DIFFERENT parts of the tree yet change together 91% of the time (10 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) — 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 `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms; `0c700362` Refactor to pass url to hasSpaMode across codebase — run `git show` on any of them.
Boundary-crossing change coupling: ImageEntry.php ↔ ImageColumn.php packages/infolists/src/Components/ImageEntry.php:1— `packages/infolists/src/Components/ImageEntry.php` (context infolists) and `packages/tables/src/Columns/ImageColumn.php` (context tables) sit in DIFFERENT parts of the tree yet change together 75% of the time (12 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) — 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 12 shared commits counted here, the most recent 3 are `51c92903` More escaping; `206f50c6` escape; `e1f36a73` security: Escape `ImageColumn` and `ImageEntry` URLs (#19885) — run `git show` on any of them.
Boundary-crossing change coupling: EditTenantProfile.php ↔ SettingsPage.php packages/panels/src/Pages/Tenancy/EditTenantProfile.php:1— `packages/panels/src/Pages/Tenancy/EditTenantProfile.php` (context panels) and `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php` (context spatie-laravel-settings-plugin) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 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) — 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 8 shared commits counted here, the most recent 3 are `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms; `0c700362` Refactor to pass url to hasSpaMode across codebase — run `git show` on any of them.
Boundary-crossing change coupling: RegisterTenant.php ↔ SettingsPage.php packages/panels/src/Pages/Tenancy/RegisterTenant.php:1— `packages/panels/src/Pages/Tenancy/RegisterTenant.php` (context panels) and `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php` (context spatie-laravel-settings-plugin) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 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) — 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 8 shared commits counted here, the most recent 3 are `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms; `0c700362` Refactor to pass url to hasSpaMode across codebase — run `git show` on any of them.
Boundary-crossing change coupling: Entry.php ↔ Form.php packages/infolists/src/Components/Entry.php:1— `packages/infolists/src/Components/Entry.php` (context infolists) and `packages/schemas/src/Components/Form.php` (context schemas) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 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) — 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 6 shared commits counted here, the most recent 3 are `32441507` Fix issues with container keys and relative JS paths; `92628728` remove old decorations; `84aa9fd2` Actions and decorations docs (at that commit the file was still `packages/schema/src/Components/Form.php`) — run `git show` on any of them.
Boundary-crossing change coupling: Field.php ↔ Form.php packages/forms/src/Components/Field.php:1— `packages/forms/src/Components/Field.php` (context forms) and `packages/schemas/src/Components/Form.php` (context schemas) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 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) — 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 6 shared commits counted here, the most recent 3 are `32441507` Fix issues with container keys and relative JS paths; `92628728` remove old decorations; `84aa9fd2` Actions and decorations docs (at that commit the file was still `packages/schema/src/Components/Form.php`) — run `git show` on any of them.
Boundary-crossing change coupling: SpatieMediaLibraryImageColumn.php ↔ SpatieTagsColumn.php packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php:1— `packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php` (context spatie-laravel-media-library-plugin) and `packages/spatie-laravel-tags-plugin/src/Tables/Columns/SpatieTagsColumn.php` (context spatie-laravel-tags-plugin) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 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) — 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 7 shared commits counted here, the most recent 3 are `70dfea32` add missing type variables for eloquent-builder; `2ed4e800` reintroduce state cache; `916af44c` Revert cached state — run `git show` on any of them.
Boundary-crossing change coupling: components.php ↔ table.php packages/forms/resources/lang/ar/components.php:1— `packages/forms/resources/lang/ar/components.php` (context forms) and `packages/tables/resources/lang/ar/table.php` (context tables) sit in DIFFERENT parts of the tree yet 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) — 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 5 shared commits counted here, the most recent 3 are `e4d67d17` translation: improve Arabic translations and fix pluralization rules …; `7f5e7a2b` fix(translation): further improve Arabic translations, pluralization,…; `0c89e161` [4.x]: Add missing Arabic translations across multiple packages (#19188) — run `git show` on any of them.
AC5 · ARIA correctness· aria-hidden on a focusable element · ×1
aria-hidden on a focusable element packages/support/resources/views/components/pagination/item.blade.php:24— aria-hidden="true" hides the element from assistive tech but leaves it keyboard-focusable — a confusing dead stop. Remove aria-hidden or make the element non-focusable.
Low cohesion: Table (LCOM4 76) packages/tables/src/Table.php:10— Table's methods fall into 76 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 76 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: Panel (LCOM4 64) packages/panels/src/Panel.php:14— Panel's methods fall into 64 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 64 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: Action (LCOM4 28) packages/actions/src/Action.php:51— Action's methods fall into 28 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 28 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: MorphToSelect (LCOM4 23) packages/forms/src/Components/MorphToSelect.php:18— MorphToSelect's methods fall into 23 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 23 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: Entry (LCOM4 22) packages/infolists/src/Components/Entry.php:26— Entry's methods fall into 22 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 22 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: Field (LCOM4 21) packages/forms/src/Components/Field.php:31— Field's methods fall into 21 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 21 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: ExportBulkAction (LCOM4 16) packages/actions/src/ExportBulkAction.php:7— ExportBulkAction's methods fall into 16 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 16 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: ExportAction (LCOM4 15) packages/actions/src/ExportAction.php:5— ExportAction's methods fall into 15 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 15 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: FusedGroup (LCOM4 15) packages/schemas/src/Components/FusedGroup.php:28— FusedGroup's methods fall into 15 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 15 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: Tab (LCOM4 15) packages/schemas/src/Components/Tabs/Tab.php:23— Tab's methods fall into 15 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 15 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: CheckboxList (LCOM4 14) packages/forms/src/Components/CheckboxList.php:31— CheckboxList'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: Section (LCOM4 14) packages/schemas/src/Components/Section.php:43— Section'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: Column (LCOM4 14) packages/tables/src/Columns/Column.php:29— Column'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: BaseFileUpload (LCOM4 13) packages/forms/src/Components/BaseFileUpload.php:23— BaseFileUpload'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: NavigationItem (LCOM4 11) packages/panels/src/Navigation/NavigationItem.php:15— NavigationItem'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: Schema (LCOM4 11) packages/schemas/src/Schema.php:26— Schema'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: Builder (LCOM4 10) packages/forms/src/Components/Builder.php:36— Builder'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: SelectConstraint (LCOM4 10) packages/query-builder/src/Constraints/SelectConstraint.php:15— SelectConstraint'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: Actions (LCOM4 10) packages/schemas/src/Components/Actions.php:19— Actions'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: SpatieMediaLibraryFileUpload (LCOM4 10) packages/spatie-laravel-media-library-plugin/src/Forms/Components/SpatieMediaLibraryFileUpload.php:18— SpatieMediaLibraryFileUpload'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: Stat (LCOM4 10) packages/widgets/src/StatsOverviewWidget/Stat.php:17— Stat'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: Callout (LCOM4 9) packages/schemas/src/Components/Callout.php:32— Callout'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: Component (LCOM4 9) packages/schemas/src/Components/Component.php:45— Component'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: Step (LCOM4 9) packages/schemas/src/Components/Wizard/Step.php:16— Step'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: BaseFilter (LCOM4 9) packages/tables/src/Filters/BaseFilter.php:8— BaseFilter'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.
TooManyMethods: FilamentManager packages/panels/src/FilamentManager.php:46— TooManyMethods — 163 methods. The bar is 30 methods; this is 133 over it, 5.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: TablesDemo docs-assets/app/app/Livewire/TablesDemo.php:71— TooManyMethods — 158 methods. The bar is 30 methods; this is 128 over it, 5.27× 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: Repeater packages/forms/src/Components/Repeater.php:36— TooManyMethods — 120 methods. The bar is 30 methods; this is 90 over it, 4.00× 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 packages/forms/src/Components/Builder.php:36— 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: RichEditor packages/forms/src/Components/RichEditor.php:47— 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: Select packages/forms/src/Components/Select.php:51— 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: BaseFileUpload packages/forms/src/Components/BaseFileUpload.php:23— TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.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: CanBeValidated packages/forms/src/Components/Concerns/CanBeValidated.php:23— TooManyMethods — 82 methods. The bar is 30 methods; this is 52 over it, 2.73× 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: HasAuth packages/panels/src/Panel/Concerns/HasAuth.php:24— TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.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: CanOpenModal packages/actions/src/Concerns/CanOpenModal.php:20— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: FileUpload packages/forms/src/Components/FileUpload.php:22— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: HasState packages/schemas/src/Components/Concerns/HasState.php:24— 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.
TooManyMethods: Action packages/actions/src/Action.php:51— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.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: SelectColumn packages/tables/src/Columns/SelectColumn.php:42— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× 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: ImportColumn packages/actions/src/Imports/ImportColumn.php:24— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.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: DateTimePicker packages/forms/src/Components/DateTimePicker.php:28— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.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: Page packages/panels/src/Pages/Page.php:34— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: InteractsWithActions packages/actions/src/Concerns/InteractsWithActions.php:33— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.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: InteractsWithRelationshipTable packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:18— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.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: Slider packages/forms/src/Components/Slider.php:21— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.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: Select packages/support/resources/js/utilities/select.js:20— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.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: RichContentFaker packages/forms/src/Components/RichEditor/RichContentFaker.php:14— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.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: ResourceClassGenerator packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:28— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.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: ActionGroup packages/actions/src/ActionGroup.php:38— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: ImageEntry packages/infolists/src/Components/ImageEntry.php:25— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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.
Hotspot: packages/forms/src/Components/Builder.php packages/forms/src/Components/Builder.php:1653— packages/forms/src/Components/Builder.php changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in Builder.toEmbeddedHtml at line 1653. 7 of those changes were fix/bug commits, 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/Builder.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: packages/support/resources/js/components/dropdown.js packages/support/resources/js/components/dropdown.js:21— packages/support/resources/js/components/dropdown.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 106 in dropdown.default at line 21. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/support/resources/js/components/dropdown.js`: 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: packages/forms/resources/js/components/file-upload.js packages/forms/resources/js/components/file-upload.js:130— packages/forms/resources/js/components/file-upload.js changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in file-upload.fileUploadFormComponent.init at line 130. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/file-upload.js`: 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: packages/forms/resources/js/components/rich-editor.js packages/forms/resources/js/components/rich-editor.js:88— packages/forms/resources/js/components/rich-editor.js changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in rich-editor.richEditorFormComponent.init at line 88. 5 of those changes were fix/bug commits, and the other 6 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/rich-editor.js`: 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: packages/forms/src/Components/Repeater.php packages/forms/src/Components/Repeater.php:1565— packages/forms/src/Components/Repeater.php changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in Repeater.toEmbeddedHtml at line 1565. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/Repeater.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: packages/support/resources/js/utilities/select.js packages/support/resources/js/utilities/select.js:306— packages/support/resources/js/utilities/select.js changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in Select.renderOptions at line 306. 10 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/support/resources/js/utilities/select.js`: 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: packages/forms/src/Components/DateTimePicker.php packages/forms/src/Components/DateTimePicker.php:101— packages/forms/src/Components/DateTimePicker.php changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in DateTimePicker.toEmbeddedHtml at line 101. 9 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/DateTimePicker.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: packages/schemas/src/Components/Tabs.php packages/schemas/src/Components/Tabs.php:284— packages/schemas/src/Components/Tabs.php changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in Tabs.toEmbeddedHtml at line 284. 4 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/schemas/src/Components/Tabs.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: packages/forms/src/Components/RichEditor.php packages/forms/src/Components/RichEditor.php:1693— packages/forms/src/Components/RichEditor.php changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in RichEditor.toEmbeddedHtml at line 1693. 5 of those changes were fix/bug commits, and the other 7 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/RichEditor.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: packages/tables/resources/js/components/table.js packages/tables/resources/js/components/table.js:3— packages/tables/resources/js/components/table.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in table.default at line 3. 3 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/tables/resources/js/components/table.js`: 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: packages/tables/src/Columns/TextColumn.php packages/tables/src/Columns/TextColumn.php:274— packages/tables/src/Columns/TextColumn.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in TextColumn.toEmbeddedHtml at line 274. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/tables/src/Columns/TextColumn.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: packages/schemas/src/Components/Section.php packages/schemas/src/Components/Section.php:264— packages/schemas/src/Components/Section.php changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in Section.toEmbeddedHtml at line 264. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/schemas/src/Components/Section.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: packages/forms/src/Components/Select.php packages/forms/src/Components/Select.php:1867— packages/forms/src/Components/Select.php changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in Select.toEmbeddedHtml at line 1867. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/Select.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: packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php:164— packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in EmailAuthentication.verifyCode at line 164. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.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: packages/forms/src/Components/TextInput.php packages/forms/src/Components/TextInput.php:327— packages/forms/src/Components/TextInput.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in TextInput.toEmbeddedHtml at line 327. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/TextInput.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: packages/forms/resources/js/components/date-time-picker.js packages/forms/resources/js/components/date-time-picker.js:88— packages/forms/resources/js/components/date-time-picker.js changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in date-time-picker.dateTimePickerFormComponent.init at line 88. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/date-time-picker.js`: 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: packages/infolists/src/Components/TextEntry.php packages/infolists/src/Components/TextEntry.php:177— packages/infolists/src/Components/TextEntry.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in TextEntry.toEmbeddedHtml at line 177. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/infolists/src/Components/TextEntry.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: packages/forms/src/Components/Field.php packages/forms/src/Components/Field.php:344— packages/forms/src/Components/Field.php changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in Field.wrapEmbeddedHtml at line 344. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/Field.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: packages/forms/src/Components/ToggleButtons.php packages/forms/src/Components/ToggleButtons.php:93— packages/forms/src/Components/ToggleButtons.php changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in ToggleButtons.toEmbeddedHtml at line 93. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/ToggleButtons.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: packages/schemas/src/Components/FusedGroup.php packages/schemas/src/Components/FusedGroup.php:221— packages/schemas/src/Components/FusedGroup.php changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in FusedGroup.toEmbeddedHtml at line 221. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/schemas/src/Components/FusedGroup.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: packages/support/src/SupportServiceProvider.php packages/support/src/SupportServiceProvider.php:166— packages/support/src/SupportServiceProvider.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in SupportServiceProvider.packageBooted at line 166. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/support/src/SupportServiceProvider.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: packages/actions/resources/js/components/modals.js packages/actions/resources/js/components/modals.js:1— packages/actions/resources/js/components/modals.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in modals.default at line 1. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/actions/resources/js/components/modals.js`: 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: packages/tables/src/Concerns/InteractsWithTable.php packages/tables/src/Concerns/InteractsWithTable.php:49— packages/tables/src/Concerns/InteractsWithTable.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in InteractsWithTable.bootedInteractsWithTable at line 49. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/tables/src/Concerns/InteractsWithTable.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: packages/forms/resources/js/components/markdown-editor.js packages/forms/resources/js/components/markdown-editor.js:121— packages/forms/resources/js/components/markdown-editor.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in markdown-editor.markdownEditorFormComponent.init at line 121. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/markdown-editor.js`: 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: REDACTED REDACTED:2346— REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in EasyMDE.EasyMDE.render at line 2346. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- REDACTED`: 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.
+ 29 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×40
Focus outline removed in CSS without a :focus replacement packages/widgets/resources/css/stats-overview-widget.css:2— `.fi-wi-stats-overview-stat` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/tables/resources/css/header-cell.css:126— `.fi-ta-header-cell .fi-ta-header-cell-sort-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/tables/resources/css/columns/color.css:73— `.fi-ta-color > .fi-ta-color-item.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/tables/resources/css/columns/text.css:200— `.fi-ta-text-item > .fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/badge.css:62— `.fi-badge .fi-badge-delete-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/button.css:3— `.fi-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/icon-button.css:2— `.fi-icon-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/link.css:2— `.fi-link` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/modal.css:135— `.fi-modal > .fi-modal-window-ctn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/modal.css:170— `.fi-modal > .fi-modal-window-ctn > .fi-modal-window` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/modal.css:2— `.fi-modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/pagination.css:67— `.fi-pagination .fi-pagination-item-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/tabs.css:30— `.fi-tabs-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/toggle.css:2— `.fi-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/checkbox.css:2— `input[type='checkbox'].fi-checkbox-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/index.css:2— `input.fi-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/one-time-code.css:5— `.fi-one-time-code-input-ctn > .fi-one-time-code-input-digit` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/radio.css:2— `input[type='radio'].fi-radio-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/select.css:2— `select.fi-select-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/select.css:33— `.fi-select-input .fi-select-input-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/input/select.css:79— `.fi-select-input .fi-select-input-value-remove-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/support/resources/css/components/dropdown/list/item.css:2— `.fi-dropdown-list-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/schemas/resources/css/components/text.css:3— `.fi-sc-text.fi-copyable` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/panels/resources/css/utilities.css:2— `.fi-skip-link:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement packages/panels/resources/css/components/layout.css:61— `.fi-main` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
MethodTooLong: BuilderSchema.schema docs-assets/app/app/Livewire/Forms/Fields/BuilderSchema.php:16— MethodTooLong — schema runs 343 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 243 over it, 3.43× 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: FieldSchema.schema docs-assets/app/app/Livewire/Forms/Fields/FieldSchema.php:31— MethodTooLong — schema runs 306 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 206 over it, 3.06× 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: SliderSchema.schema docs-assets/app/app/Livewire/Forms/Fields/SliderSchema.php:12— MethodTooLong — schema runs 270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 170 over it, 2.70× 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: Builder.toEmbeddedHtml packages/forms/src/Components/Builder.php:1653— MethodTooLong — toEmbeddedHtml runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.64× 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: RepeaterSchema.schema docs-assets/app/app/Livewire/Forms/Fields/RepeaterSchema.php:13— MethodTooLong — schema runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× 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: EntrySchema.schema docs-assets/app/app/Livewire/Infolists/Entries/EntrySchema.php:20— MethodTooLong — schema runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× 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: TextSchema.schema docs-assets/app/app/Livewire/Infolists/Entries/TextSchema.php:15— MethodTooLong — schema runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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: Repeater.toEmbeddedHtml packages/forms/src/Components/Repeater.php:1565— MethodTooLong — toEmbeddedHtml runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× 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: PrimesDemo.primes docs-assets/app/app/Livewire/PrimesDemo.php:28— MethodTooLong — primes runs 205 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 105 over it, 2.05× 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: Repeater.toTableEmbeddedHtml packages/forms/src/Components/Repeater.php:1957— MethodTooLong — toTableEmbeddedHtml runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× 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: RichEditorSchema.schema docs-assets/app/app/Livewire/Forms/Fields/RichEditorSchema.php:20— MethodTooLong — schema runs 201 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× 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: SectionSchema.schema docs-assets/app/app/Livewire/Schemas/Layout/SectionSchema.php:16— MethodTooLong — schema runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: ToggleButtonsSchema.schema docs-assets/app/app/Livewire/Forms/Fields/ToggleButtonsSchema.php:12— MethodTooLong — schema runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: Field.wrapEmbeddedHtml packages/forms/src/Components/Field.php:344— MethodTooLong — wrapEmbeddedHtml runs 188 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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: SupportServiceProvider.packageBooted packages/support/src/SupportServiceProvider.php:166— MethodTooLong — packageBooted runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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: CanExportRecords.setUp packages/actions/src/Concerns/CanExportRecords.php:77— MethodTooLong — setUp 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: Builder.generateBlockPickerHtml packages/forms/src/Components/Builder.php:1432— MethodTooLong — generateBlockPickerHtml runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: TabsSchema.schema docs-assets/app/app/Livewire/Schemas/Layout/TabsSchema.php:17— MethodTooLong — schema runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: SelectSchema.schema docs-assets/app/app/Livewire/Forms/Fields/SelectSchema.php:12— MethodTooLong — schema runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× 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: FusedGroup.toEmbeddedHtml packages/schemas/src/Components/FusedGroup.php:221— MethodTooLong — toEmbeddedHtml runs 167 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 67 over it, 1.67× 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: WizardSchema.schema docs-assets/app/app/Livewire/Schemas/Layout/WizardSchema.php:18— MethodTooLong — schema runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× 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: ImportAction.setUp packages/actions/src/ImportAction.php:81— MethodTooLong — setUp runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× 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: Field.wrapInputHtml packages/forms/src/Components/Field.php:580— MethodTooLong — wrapInputHtml runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: SetUpAppAuthenticationAction.make packages/panels/src/Auth/MultiFactor/App/Actions/SetUpAppAuthenticationAction.php:45— MethodTooLong — make runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: GridSchema.schema docs-assets/app/app/Livewire/Schemas/Layout/GridSchema.php:18— MethodTooLong — schema runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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.
FunctionTooLong: rich-editor.richEditorFormComponent packages/forms/resources/js/components/rich-editor.js:25— FunctionTooLong — richEditorFormComponent runs 710 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 610 over it, 7.10× 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.
FunctionTooLong: file-upload.fileUploadFormComponent packages/forms/resources/js/components/file-upload.js:30— FunctionTooLong — fileUploadFormComponent runs 684 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 584 over it, 6.84× 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.
FunctionTooLong: tabs.tabsSchemaComponent packages/schemas/resources/js/components/tabs.js:10— FunctionTooLong — tabsSchemaComponent runs 654 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 554 over it, 6.54× 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.
FunctionTooLong: date-time-picker.dateTimePickerFormComponent packages/forms/resources/js/components/date-time-picker.js:27— FunctionTooLong — dateTimePickerFormComponent runs 571 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 471 over it, 5.71× 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.
FunctionTooLong: table.default packages/tables/resources/js/components/table.js:3— FunctionTooLong — default runs 420 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 320 over it, 4.20× 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.
FunctionTooLong: dropdown.default packages/support/resources/js/components/dropdown.js:21— FunctionTooLong — default runs 419 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 319 over it, 4.19× 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.
FunctionTooLong: reordering.reordering packages/forms/resources/js/utilities/reordering.js:1— FunctionTooLong — reordering runs 334 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× 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.
FunctionTooLong: rich-editor.richEditorFormComponent.init packages/forms/resources/js/components/rich-editor.js:88— FunctionTooLong — richEditorFormComponent.init runs 308 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 208 over it, 3.08× 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.
FunctionTooLong: file-upload.fileUploadFormComponent.init packages/forms/resources/js/components/file-upload.js:130— FunctionTooLong — fileUploadFormComponent.init runs 301 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 201 over it, 3.01× 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.
FunctionTooLong: chart.chart packages/widgets/resources/js/components/chart.js:26— FunctionTooLong — chart runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× 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.
FunctionTooLong: column-manager.filamentTableColumnManager packages/tables/resources/js/components/column-manager.js:1— FunctionTooLong — filamentTableColumnManager runs 264 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 164 over it, 2.64× 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.
FunctionTooLong: markdown-editor.markdownEditorFormComponent packages/forms/resources/js/components/markdown-editor.js:90— FunctionTooLong — markdownEditorFormComponent runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× 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.
FunctionTooLong: EasyMDE.toggleCodeBlock REDACTED:501— FunctionTooLong — toggleCodeBlock runs 240 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 140 over it, 2.40× 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.
FunctionTooLong: EasyMDE.EasyMDE.render REDACTED:2346— FunctionTooLong — EasyMDE.render runs 237 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× 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.
FunctionTooLong: extension-local-files.LocalFilesPlugin packages/forms/resources/js/components/rich-editor/extension-local-files.js:43— FunctionTooLong — LocalFilesPlugin runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× 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.
FunctionTooLong: notification.notificationComponent packages/notifications/resources/js/components/notification.js:3— FunctionTooLong — notificationComponent runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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.
FunctionTooLong: modals.default packages/actions/resources/js/components/modals.js:1— FunctionTooLong — default runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× 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.
FunctionTooLong: global-search.default packages/panels/resources/js/components/global-search.js:1— FunctionTooLong — default runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× 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.
FunctionTooLong: mention-suggestion.default packages/forms/resources/js/components/rich-editor/mention-suggestion.js:4— FunctionTooLong — default runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× 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.
FunctionTooLong: reordering.reordering.init packages/forms/resources/js/utilities/reordering.js:23— FunctionTooLong — reordering.init runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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.
FunctionTooLong: extensions.default packages/forms/resources/js/components/rich-editor/extensions.js:41— FunctionTooLong — default runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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.
FunctionTooLong: mention-suggestion.default.render packages/forms/resources/js/components/rich-editor/mention-suggestion.js:55— FunctionTooLong — default.render runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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.
FunctionTooLong: editable-table-column.editableTableColumn packages/tables/resources/js/utilities/editable-table-column.js:1— FunctionTooLong — editableTableColumn runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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.
FunctionTooLong: modal.default packages/support/resources/js/components/modal.js:49— FunctionTooLong — default 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.
FunctionTooLong: EasyMDE.EasyMDE REDACTED:1933— FunctionTooLong — EasyMDE 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.
FileTooLong: REDACTED REDACTED— FileTooLong — 2208 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 1708 over it, 4.42× 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: Livewire/TablesDemo.php docs-assets/app/app/Livewire/TablesDemo.php— FileTooLong — 1934 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TablesDemo (71-2733). The bar is 500 significant lines; this is 1434 over it, 3.87× 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: utilities/select.js packages/support/resources/js/utilities/select.js— FileTooLong — 1437 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Select (20-2266). The bar is 500 significant lines; this is 937 over it, 2.87× 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: Components/Repeater.php packages/forms/src/Components/Repeater.php— FileTooLong — 1385 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Repeater (36-2308). The bar is 500 significant lines; this is 885 over it, 2.77× 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: Components/RichEditor.php packages/forms/src/Components/RichEditor.php— FileTooLong — 1275 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 775 over it, 2.55× 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: Components/Builder.php packages/forms/src/Components/Builder.php— FileTooLong — 1193 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: Builder (36-2021). The bar is 500 significant lines; this is 693 over it, 2.39× 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: Components/Select.php packages/forms/src/Components/Select.php— FileTooLong — 1152 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 652 over it, 2.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: components/file-upload.js packages/forms/resources/js/components/file-upload.js— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: fileUploadFormComponent (30-1130). The bar is 500 significant lines; this is 293 over it, 1.59× 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: src/Action.php packages/actions/src/Action.php— FileTooLong — 750 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: Action (51-1218). The bar is 500 significant lines; this is 250 over it, 1.50× 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: Components/Tabs.php packages/schemas/src/Components/Tabs.php— FileTooLong — 730 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 230 over it, 1.46× 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: components/rich-editor.js packages/forms/resources/js/components/rich-editor.js— FileTooLong — 727 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: richEditorFormComponent (25-1088). The bar is 500 significant lines; this is 227 over it, 1.45× 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: Components/FileUpload.php packages/forms/src/Components/FileUpload.php— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 218 over it, 1.44× 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: components/tabs.js packages/schemas/resources/js/components/tabs.js— FileTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: tabsSchemaComponent (10-877). The bar is 500 significant lines; this is 162 over it, 1.32× 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: Icons/Heroicon.php packages/support/src/Icons/Heroicon.php— FileTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: Heroicon (8-671). The bar is 500 significant lines; this is 160 over it, 1.32× 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: components/date-time-picker.js packages/forms/resources/js/components/date-time-picker.js— FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: dateTimePickerFormComponent (27-956). The bar is 500 significant lines; this is 146 over it, 1.29× 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: Columns/SelectColumn.php packages/tables/src/Columns/SelectColumn.php— FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 104 over it, 1.21× 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: Components/BaseFileUpload.php packages/forms/src/Components/BaseFileUpload.php— FileTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: BaseFileUpload (23-1292). The bar is 500 significant lines; this is 97 over it, 1.19× 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: Components/DateTimePicker.php packages/forms/src/Components/DateTimePicker.php— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× 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: Components/ModalTableSelect.php packages/forms/src/Components/ModalTableSelect.php— FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ModalTableSelect (34-997). The bar is 500 significant lines; this is 52 over it, 1.10× 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/HasState.php packages/schemas/src/Components/Concerns/HasState.php— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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: components/table.js packages/tables/resources/js/components/table.js— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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/InteractsWithActions.php packages/actions/src/Concerns/InteractsWithActions.php— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 16 over it, 1.03× 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: Components/Field.php packages/forms/src/Components/Field.php— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: Field (31-795). The bar is 500 significant lines; this is 14 over it, 1.03× 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/CanBeValidated.php packages/forms/src/Components/Concerns/CanBeValidated.php— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 over it, 1.02× 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: RichEditor/RichContentFaker.php packages/forms/src/Components/RichEditor/RichContentFaker.php— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: RichContentFaker (14-968). The bar is 500 significant lines; this is 9 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.
+ 1 more in this group — see findings.md.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×25
Untrusted text written into markup unescaped REDACTED:318— `options.icon` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:1151— `newValue` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:1162— `newValue` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:1229— `preview_result` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:2790— `save+dd` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3265— `wordCount(cm.getValue())` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3268— `wordCount(cm.getValue())` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3272— `cm.lineCount()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3275— `cm.lineCount()` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3285— `posLine+':'+posColumn` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3298— `options.imageTexts.sbInit` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:3377— `preview_result` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/forms/resources/js/components/rich-editor/extension-custom-block.js:73— `extension.options.editCustomBlockButtonIconHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/forms/resources/js/components/rich-editor/extension-custom-block.js:108— `extension.options.deleteCustomBlockButtonIconHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/forms/resources/js/components/rich-editor/extension-custom-block.js:131— `new TextDecoder().decode(Uint8Array.from(atob(node.attrs.preview),(char)=>char.charCodeAt(0),),)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/forms/resources/js/components/rich-editor/extension-local-files.js:368— `cleanedHtml` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/partials.js:47— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/partials.js:79— `toEl.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/partials.js:83— `toEl.outerHTML` is text this program did not author, and it is written into the text of an element through `outerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/utilities/select.js:546— `optionLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/utilities/select.js:563— `optionLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/utilities/select.js:804— `label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/utilities/select.js:983— `selectedLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/support/resources/js/utilities/select.js:1201— `newLabel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped packages/tables/resources/js/components/column-manager.js:257— `column.label` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Change coupling: SpatieMediaLibraryImageEntry.php ↔ SpatieMediaLibraryImageColumn.php packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:1— `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php` and `packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php` change together 100% of the time (10 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 10 shared commits counted here, the most recent 3 are `822f1077` Add configurable temporary URL expiry duration (#19733); `66b22c34` Fix PHPStan; `734aaea9` phpstan — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php:1— `packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php` and `packages/panels/src/Auth/Pages/Register.php` change together 92% of the time (12 of the 13 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 12 shared commits counted here, the most recent 3 are `eaa5ad15` fix: Scope authentication state by guard and user model (#20581); `0c60f39e` Additional sensitive parameters; `f7500b1b` security: Temporary file uploads available on auth pages (#19886) — run `git show` on any of them.
Change coupling: Tab.php ↔ Step.php packages/schemas/src/Components/Tabs/Tab.php:1— `packages/schemas/src/Components/Tabs/Tab.php` and `packages/schemas/src/Components/Wizard/Step.php` change together 80% of the time (8 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 8 shared commits counted here, the most recent 3 are `47779b89` simplify concealed components; `d3d244b9` fix: Support Closure in `columns()` for Wizard Step and Tab (#19177); `3d1d7105` Fix Htmlable icons support (#18515) — run `git show` on any of them.
Change coupling: RequestPasswordReset.php ↔ REDACTED packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:1— `packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php` and `packages/panels/src/Auth/Pages/Register.php` change together 77% of the time (10 of the 13 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 10 shared commits counted here, the most recent 3 are `0c60f39e` Additional sensitive parameters; `f7500b1b` security: Temporary file uploads available on auth pages (#19886); `4e9955d3` Feat/header hide title (#18256) — run `git show` on any of them.
Change coupling: OptionStateCast.php ↔ OptionsArrayStateCast.php packages/schemas/src/Components/StateCasts/OptionStateCast.php:1— `packages/schemas/src/Components/StateCasts/OptionStateCast.php` and `packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php` change together 73% of the time (8 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 8 shared commits counted here, the most recent 3 are `fadf0fd2` Preserve string primary keys in relationship select state; `b5ac9ecf` Allow OptionState to use a Stringable (#20220); `d6b09f6a` fix: improve integer handling in OptionsArrayStateCast and OptionStat… — run `git show` on any of them.
Change coupling: TextInput.php ↔ Textarea.php packages/forms/src/Components/TextInput.php:1— `packages/forms/src/Components/TextInput.php` and `packages/forms/src/Components/Textarea.php` change together 70% of the time (7 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). 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 `01d66f30` fix: associate field helpers, errors, and required states (#20610); `47779b89` simplify concealed components; `44205a1d` fix: Strip characters for numeric input (#19454) — run `git show` on any of them.
Change coupling: Form.php ↔ Section.php packages/schemas/src/Components/Form.php:1— `packages/schemas/src/Components/Form.php` and `packages/schemas/src/Components/Section.php` change together 70% of the time (7 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). 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 `32441507` Fix issues with container keys and relative JS paths; `92628728` remove old decorations; `84aa9fd2` Actions and decorations docs (at that commit the files were still `packages/schema/src/Components/Form.php` and `packages/schema/src/Components/Section.php`) — run `git show` on any of them.
Change coupling: Get.php ↔ Set.php packages/schemas/src/Components/Utilities/Get.php:1— `packages/schemas/src/Components/Utilities/Get.php` and `packages/schemas/src/Components/Utilities/Set.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 `fa1b15aa` fix: Setting repeater in section from section action (#18767); `6772cbbf` fix: Infinite loop when multiple `$get()`s read state from components…; `396c4efd` Improve schema performance, especially in repeaters/builders (#18068) — run `git show` on any of them.
Change coupling: CheckboxColumn.php ↔ TextInputColumn.php packages/tables/src/Columns/CheckboxColumn.php:1— `packages/tables/src/Columns/CheckboxColumn.php` and `packages/tables/src/Columns/TextInputColumn.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 `eaada2f1` fix: restore accessible editable-column save feedback (#20708); `048cde39` fix interactive table column event bubbling and wire:navigate nested …; `ad4c252a` clean up — run `git show` on any of them.
Change coupling: SimpleMethodChangesRector.php ↔ SimplePropertyChangesRector.php packages/upgrade/src/Rector/SimpleMethodChangesRector.php:1— `packages/upgrade/src/Rector/SimpleMethodChangesRector.php` and `packages/upgrade/src/Rector/SimplePropertyChangesRector.php` change together 60% of the time (6 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). 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 `4a5e5660` minor fixes; `b9d4dabd` Convert static config to configureUsing() with functions; `4f2ff50c` Navigation group enums — run `git show` on any of them.
Change coupling: select.js ↔ SelectColumn.php packages/tables/resources/js/components/columns/select.js:1— `packages/tables/resources/js/components/columns/select.js` and `packages/tables/src/Columns/SelectColumn.php` change together 56% of the time (9 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `eaada2f1` fix: restore accessible editable-column save feedback (#20708); `94ac2e05` fix: repair select keyboard focus and accessibility (#20697); `d1673d9f` Fix: Select with searchable and preloaded option empty state #18529 (… — run `git show` on any of them.
Change coupling: ExportCsv.php ↔ ImportCsv.php packages/actions/src/Exports/Jobs/ExportCsv.php:1— `packages/actions/src/Exports/Jobs/ExportCsv.php` and `packages/actions/src/Imports/Jobs/ImportCsv.php` change together 56% of the time (10 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) 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 10 shared commits counted here, the most recent 3 are `9aa3b7df` fix: Clear user after import/export job; `8f341895` [4.x] fix(actions): batch cancel, failed() handler, explicit retry de…; `ca1eca03` Lock rows when updating — run `git show` on any of them.
Change coupling: CheckboxColumn.php ↔ SelectColumn.php packages/tables/src/Columns/CheckboxColumn.php:1— `packages/tables/src/Columns/CheckboxColumn.php` and `packages/tables/src/Columns/SelectColumn.php` change together 55% of the time (6 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 6 shared commits counted here, the most recent 3 are `eaada2f1` fix: restore accessible editable-column save feedback (#20708); `ad4c252a` clean up; `08121af3` Merge — run `git show` on any of them.
Change coupling: TestsActions.php ↔ TestsBulkActions.php packages/tables/src/Testing/TestsActions.php:1— `packages/tables/src/Testing/TestsActions.php` and `packages/tables/src/Testing/TestsBulkActions.php` change together 55% of the time (6 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 6 shared commits counted here, the most recent 3 are `12d02a96` rename assertSchemaSet to assertSchemaStateSet; `49522f4b` replace old methods; `c99b34f4` Replace setActionData() with fillForm() — run `git show` on any of them.
Change coupling: HasActions.php ↔ HasBulkActions.php packages/tables/src/Concerns/HasActions.php:1— `packages/tables/src/Concerns/HasActions.php` and `packages/tables/src/Concerns/HasBulkActions.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 `9a9091c1` Prevent catching exceptions from DB commit side-effects; `72393391` Set form data before calling hook; `00e7c302` Make sure to call before hook when for actions without form — run `git show` on any of them.
Change coupling: Builder.php ↔ Repeater.php packages/forms/src/Components/Builder.php:1— `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` change together 53% of the time (27 of the 51 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 27 shared commits counted here, the most recent 3 are `f1033d8c` fix: preserve field state when required descriptions change (#20799); `abab7820` fix: keep repeater and builder items list when adding items (#20794); `a4d968f7` feat: improve Repeater and Builder reordering accessibility (#20690) — run `git show` on any of them.
Change coupling: EditProfile.php ↔ RegisterTenant.php packages/panels/src/Auth/Pages/EditProfile.php:1— `packages/panels/src/Auth/Pages/EditProfile.php` and `packages/panels/src/Pages/Tenancy/RegisterTenant.php` change together 53% of the time (9 of the 17 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 9 shared commits counted here, the most recent 3 are `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms; `b9f82091` Remove unused calls to `getCurrentOrDefaultPanel()` — run `git show` on any of them.
Change coupling: RegisterTenant.php ↔ CreateRecord.php packages/panels/src/Pages/Tenancy/RegisterTenant.php:1— `packages/panels/src/Pages/Tenancy/RegisterTenant.php` and `packages/panels/src/Resources/Pages/CreateRecord.php` change together 53% of the time (9 of the 17 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 9 shared commits counted here, the most recent 3 are `5b4c8c39` fix: Re-authorize during Livewire hydration (#19841); `9272e5ad` [4.x] Add key to form actions content component for use with testing …; `9adc416f` fix: Default testing schema name on pages with forms — run `git show` on any of them.
Change coupling: CheckboxList.php ↔ TableSelect.php packages/forms/src/Components/CheckboxList.php:1— `packages/forms/src/Components/CheckboxList.php` and `packages/forms/src/Components/TableSelect.php` change together 50% of the time (8 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 8 shared commits counted here, the most recent 3 are `a09c6355` fix(forms): clear cached relation after Select saves, so reload doesn…; `246674ed` task: Extract internal form field closures into methods (#19807); `5b7cdcdf` fix: Repeater n+1 queries (#18831) — run `git show` on any of them.
Change coupling: Exporter.php ↔ Importer.php packages/actions/src/Exports/Exporter.php:1— `packages/actions/src/Exports/Exporter.php` and `packages/actions/src/Imports/Importer.php` change together 50% of the time (7 of the 14 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 7 shared commits counted here, the most recent 3 are `64752012` Simplify import, export and authentication limiter keys; `a094b067` Custom Downloader to allow for people running Laravel Vapor to suppor…; `6bc46098` Modify import completed notification (#19714) — run `git show` on any of them.
Change coupling: RequestPasswordReset.php ↔ ViewRecord.php packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:1— `packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php` and `packages/panels/src/Resources/Pages/ViewRecord.php` change together 50% of the time (7 of the 14 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 7 shared commits counted here, the most recent 3 are `9adc416f` fix: Default testing schema name on pages with forms; `11dd93a6` Styling; `22a74631` Correcting namespaces and file locations — run `git show` on any of them.
Change coupling: Section.php ↔ Step.php packages/schemas/src/Components/Section.php:1— `packages/schemas/src/Components/Section.php` and `packages/schemas/src/Components/Wizard/Step.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 `47779b89` simplify concealed components; `aa039ce2` fix: Inheritable keys in repeaters (#18383); `6ca1c0d3` fix: More predictable key inheritance — run `git show` on any of them.
Change coupling: extension-custom-block.js ↔ RichContentCustomBlock.php packages/forms/resources/js/components/rich-editor/extension-custom-block.js:1— `packages/forms/resources/js/components/rich-editor/extension-custom-block.js` and `packages/forms/src/Components/RichEditor/RichContentCustomBlock.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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `3b521d2e` feature: Styling custom block previews with prose (#19741); `dab25e4b` render custom blocks; `28017495` parse custom blocks in backend — run `git show` on any of them.
Change coupling: SpatieMediaLibraryFileUpload.php ↔ SpatieMediaLibraryImageEntry.php packages/spatie-laravel-media-library-plugin/src/Forms/Components/SpatieMediaLibraryFileUpload.php:1— `packages/spatie-laravel-media-library-plugin/src/Forms/Components/SpatieMediaLibraryFileUpload.php` and `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.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 `822f1077` Add configurable temporary URL expiry duration (#19733); `3f8304c9` Use private visibility for files instead of public by default; `d3e155d2` Fixes for PR — run `git show` on any of them.
Duplicated block (13 lines × 2) packages/actions/src/AssociateAction.php:318— packages/actions/src/AssociateAction.php:318-330 | packages/actions/src/AttachAction.php:327-339 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 `packages/actions/src/AssociateAction.php:318` 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) packages/actions/src/DetachAction.php:30— packages/actions/src/DetachAction.php:30-42 | packages/actions/src/DetachBulkAction.php:34-46 — 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 `packages/actions/src/DetachAction.php:30` 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 (13 lines × 2) packages/actions/src/DissociateAction.php:30— packages/actions/src/DissociateAction.php:30-42 | packages/actions/src/DissociateBulkAction.php:35-47 — 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 `packages/actions/src/DissociateAction.php:30` 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 (13 lines × 2) packages/actions/src/ForceDeleteBulkAction.php:116— packages/actions/src/ForceDeleteBulkAction.php:116-128 | packages/actions/src/RestoreBulkAction.php:120-132 — before extracting anything, compare `packages/actions/src/ForceDeleteBulkAction.php` and `packages/actions/src/RestoreBulkAction.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 `packages/actions/src/ForceDeleteBulkAction.php:116` 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) packages/forms/src/Components/Concerns/HasAffixes.php:182— packages/forms/src/Components/Concerns/HasAffixes.php:182-194 | packages/infolists/src/Components/Concerns/HasAffixes.php:85-97 — before extracting anything, compare `packages/forms/src/Components/Concerns/HasAffixes.php` and `packages/infolists/src/Components/Concerns/HasAffixes.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 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (13 lines × 2) packages/forms/src/Components/Concerns/HasAffixes.php:210— packages/forms/src/Components/Concerns/HasAffixes.php:210-222 | packages/infolists/src/Components/Concerns/HasAffixes.php:113-125 — before extracting anything, compare `packages/forms/src/Components/Concerns/HasAffixes.php` and `packages/infolists/src/Components/Concerns/HasAffixes.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 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (13 lines × 2) packages/infolists/src/Components/IconEntry.php:147— packages/infolists/src/Components/IconEntry.php:147-159 | packages/tables/src/Columns/IconColumn.php:175-187 — before extracting anything, compare `packages/infolists/src/Components/IconEntry.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (13 lines × 2) packages/infolists/src/Components/IconEntry.php:167— packages/infolists/src/Components/IconEntry.php:167-179 | packages/tables/src/Columns/IconColumn.php:195-207 — before extracting anything, compare `packages/infolists/src/Components/IconEntry.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (13 lines × 2) packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:88— packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:88-100 | packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.php:90-102 — before extracting anything, compare `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php` and `packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.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 `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:88` 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 (13 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:225— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:225-237 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:225-237 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 (13 lines × 2) packages/schemas/src/Components/Concerns/HasState.php:897— packages/schemas/src/Components/Concerns/HasState.php:897-909 | packages/schemas/src/Components/Concerns/HasState.php:929-941 — 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) packages/schemas/src/Components/StateCasts/OptionStateCast.php:42— packages/schemas/src/Components/StateCasts/OptionStateCast.php:42-54 | packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:60-72 — 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 `packages/schemas/src/Components/StateCasts/OptionStateCast.php:42` 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 (13 lines × 2) packages/schemas/src/Components/StateCasts/StripCharactersStateCast.php:18— packages/schemas/src/Components/StateCasts/StripCharactersStateCast.php:18-30 | packages/schemas/src/Components/StateCasts/StripCharactersStateCast.php:35-47 — 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) packages/support/src/View/Concerns/CanGenerateButtonHtml.php:143— packages/support/src/View/Concerns/CanGenerateButtonHtml.php:143-155 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:132-144 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` and `packages/support/src/View/Concerns/CanGenerateLinkHtml.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 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 (13 lines × 2) packages/actions/src/Commands/MakeExporterCommand.php:172— packages/actions/src/Commands/MakeExporterCommand.php:172-184 | packages/actions/src/Commands/MakeImporterCommand.php:200-212 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/actions/src/Commands/MakeImporterCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 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 (13 lines × 2) packages/forms/src/Components/Select.php:773— packages/forms/src/Components/Select.php:773-785 | packages/tables/src/Columns/SelectColumn.php:494-506 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) packages/notifications/src/Livewire/DatabaseNotifications.php:167— packages/notifications/src/Livewire/DatabaseNotifications.php:167-179 | packages/notifications/src/Livewire/Notifications.php:98-110 — 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 (13 lines × 2) packages/panels/src/Auth/MultiFactor/App/Concerns/InteractsWithAppAuthentication.php:18— packages/panels/src/Auth/MultiFactor/App/Concerns/InteractsWithAppAuthentication.php:18-30 | packages/panels/src/Auth/MultiFactor/App/Concerns/InteractsWithAppAuthenticationRecovery.php:19-31 — 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 (13 lines × 2) packages/actions/src/Testing/TestsActions.php:417— packages/actions/src/Testing/TestsActions.php:417-429 | packages/actions/src/Testing/TestsActions.php:466-478 — 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 `packages/actions/src/Testing/TestsActions.php:417` 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) packages/forms/src/Testing/TestsForms.php:104— packages/forms/src/Testing/TestsForms.php:104-116 | packages/forms/src/Testing/TestsForms.php:139-151 — 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 `packages/forms/src/Testing/TestsForms.php:104` 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 (5 lines × 2) packages/actions/src/Exports/ContentGenerators/XlsxExportContentGenerator.php:20— packages/actions/src/Exports/ContentGenerators/XlsxExportContentGenerator.php:20-24 | packages/actions/src/Exports/Jobs/CreateXlsxFile.php:66-70 — 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 `packages/actions/src/Exports/ContentGenerators/XlsxExportContentGenerator.php:20` 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) packages/forms/src/Components/Builder.php:1670— packages/forms/src/Components/Builder.php:1670-1674 | packages/forms/src/Components/Repeater.php:1577-1581 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Builder.php:1675` calls `getAction`, `getEditActionName` and `packages/forms/src/Components/Repeater.php:1582` does not — after which the two agree again for 4 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 (5 lines × 2) packages/forms/src/Components/Select.php:162— packages/forms/src/Components/Select.php:162-166 | packages/tables/src/Columns/SelectColumn.php:129-133 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Select.php:162` 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 (5 lines × 2) packages/infolists/src/Components/TextEntry.php:305— packages/infolists/src/Components/TextEntry.php:305-309 | packages/tables/src/Columns/TextColumn.php:405-409 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/panels/src/Auth/MultiFactor/Pages/SetUpRequiredMultiFactorAuthentication.php:58— packages/panels/src/Auth/MultiFactor/Pages/SetUpRequiredMultiFactorAuthentication.php:58-62 | packages/panels/src/Auth/Pages/EditProfile.php:541-545 — 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 `packages/panels/src/Auth/MultiFactor/Pages/SetUpRequiredMultiFactorAuthentication.php:58` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/panels/src/Auth/Pages/EditProfile.php:540` calls `label`, `__` and `packages/panels/src/Auth/MultiFactor/Pages/SetUpRequiredMultiFactorAuthentication.php:57` 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 (5 lines × 2) packages/panels/src/Resources/Pages/CreateRecord.php:125— packages/panels/src/Resources/Pages/CreateRecord.php:125-129 | packages/panels/src/Resources/Pages/EditRecord.php:180-184 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 `packages/panels/src/Resources/Pages/CreateRecord.php:125` 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 (5 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:245— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:245-249 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:245-249 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:245` 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) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:275— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:275-279 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:275-279 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:275` 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 (5 lines × 2) packages/schemas/src/Components/Tabs.php:476— packages/schemas/src/Components/Tabs.php:476-480 | packages/schemas/src/Components/Tabs.php:550-554 — 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 `packages/schemas/src/Components/Tabs.php:476` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/schemas/src/Components/Tabs.php:555` calls `getIcon` and `packages/schemas/src/Components/Tabs.php:481` 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 (5 lines × 2) packages/support/src/View/Components/DropdownComponent/HeaderComponent.php:18— packages/support/src/View/Components/DropdownComponent/HeaderComponent.php:18-22 | packages/widgets/src/View/Components/StatsOverviewWidgetComponent/StatComponent/DescriptionComponent.php:18-22 — before extracting anything, compare `packages/support/src/View/Components/DropdownComponent/HeaderComponent.php` and `packages/widgets/src/View/Components/StatsOverviewWidgetComponent/StatComponent/DescriptionComponent.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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) packages/tables/src/Columns/Summarizers/Summarizer.php:142— packages/tables/src/Columns/Summarizers/Summarizer.php:142-146 | packages/tables/src/Concerns/CanSummarizeRecords.php:103-107 — 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 `packages/tables/src/Columns/Summarizers/Summarizer.php:142` 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 (5 lines × 2) packages/panels/src/Auth/Pages/Login.php:60— packages/panels/src/Auth/Pages/Login.php:60-64 | packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:49-53 — 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) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:121— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:121-125 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:113-117 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) packages/panels/src/Pages/Concerns/HasSubNavigation.php:29— packages/panels/src/Pages/Concerns/HasSubNavigation.php:29-33 | packages/panels/src/Resources/Pages/ListRecords.php:231-235 — 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 (5 lines × 2) packages/panels/src/Pages/Page.php:639— packages/panels/src/Pages/Page.php:639-643 | packages/panels/src/Resources/Resource/Concerns/HasConfiguration.php:26-30 — 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 (5 lines × 2) packages/support/src/Assets/Css.php:31— packages/support/src/Assets/Css.php:31-35 | packages/support/src/Assets/Js.php:164-168 — 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) packages/tables/src/Filters/BaseFilter.php:60— packages/tables/src/Filters/BaseFilter.php:60-64 | packages/tables/src/Grouping/Group.php:512-516 — 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) packages/forms/src/Components/Concerns/CanBeAutocapitalized.php:24— packages/forms/src/Components/Concerns/CanBeAutocapitalized.php:24-28 | packages/forms/src/Components/Concerns/CanBeAutocompleted.php:24-28 — 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) packages/panels/src/Panel/Concerns/HasTenancy.php:494— packages/panels/src/Panel/Concerns/HasTenancy.php:494-498 | packages/panels/src/Panel/Concerns/HasUserMenu.php:204-208 — before extracting anything, compare `packages/panels/src/Panel/Concerns/HasTenancy.php` and `packages/panels/src/Panel/Concerns/HasUserMenu.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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) packages/actions/src/Action.php:256— packages/actions/src/Action.php:256-260 | packages/actions/src/ActionGroup.php:379-383 — 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) packages/actions/src/ActionGroup.php:646— packages/actions/src/ActionGroup.php:646-654 | packages/actions/src/ActionGroup.php:704-712 — 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 (9 lines × 2) packages/forms/src/Components/Builder.php:509— packages/forms/src/Components/Builder.php:509-517 | packages/forms/src/Components/Builder.php:559-567 — 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 `packages/forms/src/Components/Builder.php:509` 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 (9 lines × 2) packages/forms/src/Components/DateTimePicker.php:755— packages/forms/src/Components/DateTimePicker.php:755-763 | packages/forms/src/Components/DateTimePicker.php:770-778 — 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) packages/forms/src/Components/Repeater.php:478— packages/forms/src/Components/Repeater.php:478-486 | packages/forms/src/Components/Repeater.php:524-532 — 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 `packages/forms/src/Components/Repeater.php:478` 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 (9 lines × 2) packages/panels/src/Livewire/Concerns/HasTenantMenu.php:94— packages/panels/src/Livewire/Concerns/HasTenantMenu.php:94-102 | packages/panels/src/Livewire/Concerns/HasUserMenu.php:80-88 — 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 `packages/panels/src/Livewire/Concerns/HasTenantMenu.php:94` 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 (9 lines × 2) packages/schemas/src/Components/Tabs.php:401— packages/schemas/src/Components/Tabs.php:401-409 | packages/schemas/src/Components/Tabs.php:751-759 — 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 (9 lines × 2) packages/support/src/Commands/Concerns/CanAskForResource.php:62— packages/support/src/Commands/Concerns/CanAskForResource.php:62-70 | packages/support/src/Commands/Concerns/HasCluster.php:59-67 — 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 `packages/support/src/Commands/Concerns/CanAskForResource.php:62` 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) packages/tables/src/Filters/QueryBuilder.php:173— packages/tables/src/Filters/QueryBuilder.php:173-181 | packages/tables/src/Filters/QueryBuilder.php:256-264 — 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 `packages/tables/src/Filters/QueryBuilder.php:173` 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) packages/forms/src/Components/Builder.php:1126— packages/forms/src/Components/Builder.php:1126-1134 | packages/forms/src/Components/Repeater.php:965-973 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (9 lines × 2) packages/forms/src/Components/ModalTableSelect.php:896— packages/forms/src/Components/ModalTableSelect.php:896-904 | packages/forms/src/Components/TableSelect.php:470-478 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 322 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) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:150— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:150-158 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:124-132 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) packages/panels/src/Pages/Concerns/HasRoutes.php:63— packages/panels/src/Pages/Concerns/HasRoutes.php:63-71 | packages/panels/src/Resources/Resource/Concerns/HasRoutes.php:170-178 — 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) packages/panels/src/Pages/Concerns/HasSubNavigation.php:38— packages/panels/src/Pages/Concerns/HasSubNavigation.php:38-46 | packages/panels/src/Resources/Resource/Concerns/HasNavigation.php:94-102 — 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) packages/forms/src/Components/Select.php:514— packages/forms/src/Components/Select.php:514-522 | packages/tables/src/Columns/SelectColumn.php:213-221 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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) packages/panels/src/Commands/CacheComponentsCommand.php:18— packages/panels/src/Commands/CacheComponentsCommand.php:18-26 | packages/panels/src/Commands/ClearCachedComponentsCommand.php:18-26 — 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) packages/panels/src/Pages/Page.php:651— packages/panels/src/Pages/Page.php:651-659 | packages/panels/src/Resources/Resource/Concerns/HasConfiguration.php:38-46 — 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) packages/panels/src/Resources/Pages/CreateRecord.php:315— packages/panels/src/Resources/Pages/CreateRecord.php:315-323 | packages/panels/src/Resources/Pages/EditRecord.php:366-374 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (9 lines × 2) packages/query-builder/src/Constraints/BooleanConstraint.php:17— packages/query-builder/src/Constraints/BooleanConstraint.php:17-25 | packages/query-builder/src/Constraints/SelectConstraint.php:42-50 — 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) packages/tables/src/Testing/TestsColumns.php:29— packages/tables/src/Testing/TestsColumns.php:29-37 | packages/tables/src/Testing/TestsColumns.php:51-59 — 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 (14 lines × 2) packages/forms/src/Components/Builder.php:709— packages/forms/src/Components/Builder.php:709-722 | packages/forms/src/Components/Repeater.php:667-680 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (14 lines × 2) packages/forms/src/Components/Builder.php:739— packages/forms/src/Components/Builder.php:739-752 | packages/forms/src/Components/Repeater.php:697-710 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (14 lines × 2) packages/forms/src/Components/Builder.php:1683— packages/forms/src/Components/Builder.php:1683-1696 | packages/forms/src/Components/Repeater.php:1591-1604 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/Repeater.php:1589` calls `hasItemNumbers`, `hasItemHeaders` and `packages/forms/src/Components/Builder.php:1681` 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.
Duplicated block (14 lines × 2) packages/forms/src/Components/Select.php:1209— packages/forms/src/Components/Select.php:1209-1222 | packages/forms/src/Components/Select.php:1280-1293 — 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 `packages/forms/src/Components/Select.php:1209` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Select.php:1295` calls `getResults` and `packages/forms/src/Components/Select.php:1223` does not — after which the two agree again for 4 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 (14 lines × 2) packages/infolists/src/Components/ImageEntry.php:269— packages/infolists/src/Components/ImageEntry.php:269-282 | packages/tables/src/Columns/ImageColumn.php:263-276 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (14 lines × 2) packages/infolists/src/Components/ImageEntry.php:519— packages/infolists/src/Components/ImageEntry.php:519-532 | packages/tables/src/Columns/ImageColumn.php:515-528 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/infolists/src/Components/ImageEntry.php:534` calls `getAlignment` and `packages/tables/src/Columns/ImageColumn.php:530` does not — after which the two agree again for 4 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 (14 lines × 2) packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:41— packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:41-54 | packages/panels/src/Auth/MultiFactor/App/Actions/SetUpAppAuthenticationAction.php:67-80 — 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 `packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:41` 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 (14 lines × 2) packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:26— packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:26-39 | packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.php:27-40 — before extracting anything, compare `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php` and `packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.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. 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 (14 lines × 2) packages/panels/src/Auth/Pages/EditProfile.php:202— packages/panels/src/Auth/Pages/EditProfile.php:202-215 | packages/panels/src/Pages/Tenancy/RegisterTenant.php:94-107 — 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 `packages/panels/src/Auth/Pages/EditProfile.php:202` 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 (14 lines × 2) packages/panels/src/Auth/Pages/EmailVerification/EmailVerificationPrompt.php:46— packages/panels/src/Auth/Pages/EmailVerification/EmailVerificationPrompt.php:46-59 | packages/panels/src/Auth/Pages/Register.php:169-182 — 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 (14 lines × 2) packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php:155— packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php:155-168 | packages/panels/src/Auth/Pages/Register.php:139-152 — before extracting anything, compare `packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php` and `packages/panels/src/Auth/Pages/Register.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) packages/panels/src/Pages/Tenancy/RegisterTenant.php:94— packages/panels/src/Pages/Tenancy/RegisterTenant.php:94-107 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:86-99 — 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 `packages/panels/src/Pages/Tenancy/RegisterTenant.php:94` 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 after the matched lines, `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:101` calls `rememberData`, `getSavedNotification`, `send` and `packages/panels/src/Pages/Tenancy/RegisterTenant.php:109` 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.
Duplicated block (14 lines × 2) packages/panels/src/Resources/Resource/Concerns/BelongsToParent.php:53— packages/panels/src/Resources/Resource/Concerns/BelongsToParent.php:53-66 | packages/panels/src/Resources/Resource/Concerns/BelongsToTenant.php:52-65 — 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 (14 lines × 2) packages/schemas/src/Components/StateCasts/EnumArrayStateCast.php:27— packages/schemas/src/Components/StateCasts/EnumArrayStateCast.php:27-40 | packages/schemas/src/Components/StateCasts/EnumArrayStateCast.php:60-73 — 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 `packages/schemas/src/Components/StateCasts/EnumArrayStateCast.php:27` 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) packages/schemas/src/Concerns/InteractsWithSchemas.php:93— packages/schemas/src/Concerns/InteractsWithSchemas.php:93-106 | packages/tables/src/Concerns/HasColumns.php:100-113 — 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 `packages/schemas/src/Concerns/InteractsWithSchemas.php:93` 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 (14 lines × 2) packages/tables/src/Columns/Column.php:125— packages/tables/src/Columns/Column.php:125-138 | packages/tables/src/Columns/Layout/Component.php:153-166 — 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 (14 lines × 2) packages/actions/src/Commands/MakeExporterCommand.php:100— packages/actions/src/Commands/MakeExporterCommand.php:100-113 | packages/forms/src/Commands/MakeFormCommand.php:97-110 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/forms/src/Commands/MakeFormCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (14 lines × 2) packages/forms/src/Testing/TestsForms.php:382— packages/forms/src/Testing/TestsForms.php:382-395 | packages/forms/src/Testing/TestsForms.php:419-432 — 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 `packages/forms/src/Testing/TestsForms.php:382` 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 (11 lines × 2) packages/actions/src/AssociateAction.php:52— packages/actions/src/AssociateAction.php:52-62 | packages/actions/src/AttachAction.php:68-78 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 `packages/actions/src/AssociateAction.php:52` 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 (11 lines × 2) packages/actions/src/Exports/ExportColumn.php:123— packages/actions/src/Exports/ExportColumn.php:123-133 | packages/tables/src/Columns/Concerns/InteractsWithTableQuery.php:22-32 — 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 `packages/actions/src/Exports/ExportColumn.php:123` 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) packages/actions/src/Exports/ExportColumn.php:146— packages/actions/src/Exports/ExportColumn.php:146-156 | packages/tables/src/Columns/Concerns/InteractsWithTableQuery.php:45-55 — 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) packages/forms/src/Components/Builder.php:229— packages/forms/src/Components/Builder.php:229-245 | packages/forms/src/Components/Repeater.php:223-233 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (11 lines × 2) packages/forms/src/Components/Builder.php:2005— packages/forms/src/Components/Builder.php:2005-2015 | packages/forms/src/Components/Repeater.php:2292-2302 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:2005` 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 (11 lines × 2) packages/panels/src/Livewire/Concerns/HasTenantMenu.php:73— packages/panels/src/Livewire/Concerns/HasTenantMenu.php:73-83 | packages/panels/src/Livewire/Concerns/HasUserMenu.php:63-73 — 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) packages/panels/src/Pages/Dashboard/Concerns/HasFilters.php:59— packages/panels/src/Pages/Dashboard/Concerns/HasFilters.php:59-69 | packages/tables/src/Concerns/InteractsWithTable.php:317-327 — 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 (11 lines × 2) packages/panels/src/Panel/Concerns/HasTenancy.php:454— packages/panels/src/Panel/Concerns/HasTenancy.php:454-464 | packages/panels/src/Panel/Concerns/HasUserMenu.php:126-136 — before extracting anything, compare `packages/panels/src/Panel/Concerns/HasTenancy.php` and `packages/panels/src/Panel/Concerns/HasUserMenu.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 `packages/panels/src/Panel/Concerns/HasTenancy.php:454` 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 (11 lines × 2) packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:285— packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:285-295 | packages/tables/src/Filters/Concerns/HasRelationship.php:107-117 — 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 `packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:285` 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) packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:343— packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:343-353 | packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:380-390 — 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 `packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:343` 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 (11 lines × 2) packages/upgrade/src/Rector/SimpleMethodChangesRector.php:188— packages/upgrade/src/Rector/SimpleMethodChangesRector.php:188-198 | packages/upgrade/src/Rector/SimplePropertyChangesRector.php:177-187 — 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 `packages/upgrade/src/Rector/SimpleMethodChangesRector.php:188` 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) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:87— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:87-97 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:89-99 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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 (11 lines × 2) packages/infolists/src/Components/ImageEntry.php:440— packages/infolists/src/Components/ImageEntry.php:440-450 | packages/tables/src/Columns/ImageColumn.php:433-443 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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) packages/schemas/src/Components/Text.php:110— packages/schemas/src/Components/Text.php:110-120 | packages/schemas/src/Components/UnorderedList.php:54-64 — 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) packages/support/src/Concerns/HasIconPosition.php:21— packages/support/src/Concerns/HasIconPosition.php:21-31 | packages/tables/src/Columns/Concerns/HasIcon.php:89-99 — 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) packages/forms/src/Components/BaseFileUpload.php:1059— packages/forms/src/Components/BaseFileUpload.php:1059-1069 | packages/forms/src/Components/RichEditor.php:609-619 — 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) packages/forms/src/Testing/TestsForms.php:194— packages/forms/src/Testing/TestsForms.php:194-204 | packages/forms/src/Testing/TestsForms.php:231-241 — 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) packages/tables/src/Testing/TestsFilters.php:114— packages/tables/src/Testing/TestsFilters.php:114-124 | packages/tables/src/Testing/TestsFilters.php:135-145 — 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 `packages/tables/src/Testing/TestsFilters.php:114` 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 (7 lines × 2) packages/infolists/src/Components/Concerns/CanFormatState.php:228— packages/infolists/src/Components/Concerns/CanFormatState.php:228-234 | packages/tables/src/Columns/Concerns/CanFormatState.php:228-234 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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) packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:205— packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:205-211 | packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:232-238 — 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) packages/panels/src/Resources/Pages/ManageRelatedRecords.php:126— packages/panels/src/Resources/Pages/ManageRelatedRecords.php:126-132 | packages/panels/src/Resources/RelationManagers/RelationManager.php:297-303 — 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) packages/schemas/src/Components/Actions.php:188— packages/schemas/src/Components/Actions.php:188-194 | packages/schemas/src/Components/Flex.php:54-60 — 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 (7 lines × 2) packages/schemas/src/Components/EmptyState.php:90— packages/schemas/src/Components/EmptyState.php:90-96 | packages/schemas/src/Components/Section.php:274-280 — 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 (7 lines × 2) packages/tables/src/Concerns/HasBulkActions.php:116— packages/tables/src/Concerns/HasBulkActions.php:116-122 | packages/tables/src/Concerns/HasBulkActions.php:196-203 — 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 `packages/tables/src/Concerns/HasBulkActions.php:116` 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 (7 lines × 2) docs-assets/app/app/Filament/Clusters/Settings/SettingsCluster.php:18— docs-assets/app/app/Filament/Clusters/Settings/SettingsCluster.php:18-24 | docs-assets/app/app/Filament/Resources/UserResource.php:25-31 — 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) packages/forms/src/Components/Builder.php:289— packages/forms/src/Components/Builder.php:289-295 | packages/forms/src/Components/Repeater.php:265-271 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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) packages/forms/src/Components/Builder.php:1407— packages/forms/src/Components/Builder.php:1407-1413 | packages/forms/src/Components/Repeater.php:2240-2246 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (7 lines × 2) packages/forms/src/Components/Concerns/CanBeValidated.php:795— packages/forms/src/Components/Concerns/CanBeValidated.php:795-801 | packages/tables/src/Columns/Concerns/CanBeValidated.php:94-100 — 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) packages/forms/src/Components/Field.php:232— packages/forms/src/Components/Field.php:232-238 | packages/infolists/src/Components/Entry.php:217-223 — 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) packages/panels/src/Resources/Pages/CreateRecord.php:260— packages/panels/src/Resources/Pages/CreateRecord.php:260-266 | packages/panels/src/Resources/Pages/EditRecord.php:331-337 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (7 lines × 2) packages/actions/src/Imports/ImportColumn.php:735— packages/actions/src/Imports/ImportColumn.php:735-741 | packages/schemas/src/Components/Concerns/EntanglesStateWithSingularRelationship.php:232-238 — 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) packages/forms/src/Components/BaseFileUpload.php:587— packages/forms/src/Components/BaseFileUpload.php:587-593 | packages/forms/src/Components/Concerns/HasFileAttachments.php:283-289 — 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) packages/panels/src/Resources/Pages/Concerns/InteractsWithParentRecord.php:180— packages/panels/src/Resources/Pages/Concerns/InteractsWithParentRecord.php:180-186 | packages/panels/src/Resources/Pages/Concerns/InteractsWithRecord.php:54-60 — 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 (7 lines × 2) packages/support/src/Concerns/HasAlignment.php:56— packages/support/src/Concerns/HasAlignment.php:56-62 | packages/support/src/Concerns/HasVerticalAlignment.php:36-42 — 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.
ClassTooLong: TablesDemo docs-assets/app/app/Livewire/TablesDemo.php:71— ClassTooLong — 1867 significant lines (blank, comment-only and punctuation-only lines excluded), 158 methods. The bar is 400 significant lines; this is 1467 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.
ClassTooLong: Select packages/support/resources/js/utilities/select.js:20— ClassTooLong — 1367 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 967 over it, 3.42× 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: Repeater packages/forms/src/Components/Repeater.php:36— ClassTooLong — 1354 significant lines (blank, comment-only and punctuation-only lines excluded), 120 methods. The bar is 400 significant lines; this is 954 over it, 3.39× 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 packages/forms/src/Components/Builder.php:36— ClassTooLong — 1162 significant lines (blank, comment-only and punctuation-only lines excluded), 113 methods. The bar is 400 significant lines; this is 762 over it, 2.91× 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: Action packages/actions/src/Action.php:51— ClassTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The bar is 400 significant lines; this is 304 over it, 1.76× 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: Heroicon packages/support/src/Icons/Heroicon.php:8— ClassTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 256 over it, 1.64× 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: BaseFileUpload packages/forms/src/Components/BaseFileUpload.php:23— ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 178 over it, 1.45× 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: ModalTableSelect packages/forms/src/Components/ModalTableSelect.php:34— ClassTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 122 over it, 1.31× 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: Color packages/support/src/Colors/Color.php:7— ClassTooLong — 503 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 103 over it, 1.26× 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: RichContentFaker packages/forms/src/Components/RichEditor/RichContentFaker.php:14— ClassTooLong — 499 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 99 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: Field packages/forms/src/Components/Field.php:31— ClassTooLong — 488 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 88 over it, 1.22× 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: MakeResourceCommand packages/panels/src/Commands/MakeResourceCommand.php:39— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 50 over it, 1.13× 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: ActionGroup packages/actions/src/ActionGroup.php:38— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 46 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: FilamentManager packages/panels/src/FilamentManager.php:46— ClassTooLong — 417 significant lines (blank, comment-only and punctuation-only lines excluded), 163 methods. The bar is 400 significant lines; this is 17 over it, 1.04× 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: MakePageCommand packages/panels/src/Commands/MakePageCommand.php:53— ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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.
Repeated repair: packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php:176— packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php changed 8 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 10 (its worst body is AppAuthentication.verifyCode at line 176), 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: prevent double encoding of app authentication QR codes”; “fix: Scope authentication state by guard and user model (#20581)”; “fix(panels): correctly track accepted TOTP periods”; “fix: Cache used MFA codes using hash of secret rather than secret and code (#20335)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/src/Auth/MultiFactor/App/AppAuthentication.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: packages/forms/src/Components/ColorPicker.php packages/forms/src/Components/ColorPicker.php:64— packages/forms/src/Components/ColorPicker.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 13 (its worst body is ColorPicker.toEmbeddedHtml at line 64), 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 color picker dialog accessibility”; “fix: associate other fields with helper text and errors (#20700)”; “fix: make disabled and read-only form fields consistent (#20694)”; “fix: improve notification and dropdown interactions”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/ColorPicker.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: packages/actions/src/Imports/ImportColumn.php packages/actions/src/Imports/ImportColumn.php:512— packages/actions/src/Imports/ImportColumn.php changed 6 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 ImportColumn.resolveRelatedRecords at line 512), 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 SQL Server compatibility across queries and test fixtures”; “Fix SQL Server relationship coverage queries in imports”; “Fix missing relationship values in imports”; “fix: accept repeated relationship lookup keys during import”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/actions/src/Imports/ImportColumn.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: packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:28— packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.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 12 (its worst body is DisableAppAuthenticationAction.make at line 28), 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: Scope authentication state by guard and user model (#20581)”; “fix: secure multi-factor authentication actions (#20522)”; “fix: Cache used MFA codes using hash of secret rather than secret and code (#20335)”; “fix: MFA recovery code autocomplete (#20294)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.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: packages/support/resources/js/index.js packages/support/resources/js/index.js:20— packages/support/resources/js/index.js 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 2 (its worst body is index.document.addEventListener("alpine:init") at line 20), 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: preserve cloak state during Livewire updates”; “fix: improve standalone copy accessibility and feedback (#20695)”; “Fix activation of ARIA-disabled buttons while preserving focus”; “fix: improve notification and dropdown interactions”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/support/resources/js/index.js`: 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: packages/forms/resources/js/components/file-upload/filepond-plugin-media-preview.js packages/forms/resources/js/components/file-upload/filepond-plugin-media-preview.js:289— packages/forms/resources/js/components/file-upload/filepond-plugin-media-preview.js changed 4 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 14 (its worst body is filepond-plugin-media-preview.plugin 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: “Fix: avoid forced style recalculation when initializing single-trigger dropdowns (#20774)”; “fix: reuse audio preview playback listener during dragging”; “fix: clean up JavaScript resources on destruction”; “fix: correct FileUpload audio preview interactions (#20511)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/file-upload/filepond-plugin-media-preview.js`: 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: packages/forms/src/Components/TagsInput.php packages/forms/src/Components/TagsInput.php:224— packages/forms/src/Components/TagsInput.php changed 4 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 14 (its worst body is TagsInput.toEmbeddedHtml at line 224), 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: associate other fields with helper text and errors (#20700)”; “fix: make disabled and read-only form fields consistent (#20694)”; “fix: remove blank separated tags during hydration (#20604)”; “fix”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/src/Components/TagsInput.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: packages/panels/resources/js/index.js packages/panels/resources/js/index.js:15— packages/panels/resources/js/index.js 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 1 (its worst body is index.document.addEventListener("alpine:init") at line 15), 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: improve responsive sidebar keyboard accessibility (#20756)”; “fix: ignore diacritics when searching (#20704)”; “fix: SPA mode resource create page back button cache (#20297)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/resources/js/index.js`: 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: packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php:33— packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.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 3 (its worst body is RegenerateAppAuthenticationRecoveryCodesAction.make at line 33), 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: Scope authentication state by guard and user model (#20581)”; “fix: secure multi-factor authentication actions (#20522)”; “fix: Cache used MFA codes using hash of secret rather than secret and code (#20335)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.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: packages/notifications/resources/js/index.js packages/notifications/resources/js/index.js:16— packages/notifications/resources/js/index.js 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 1 (its worst body is index.document.addEventListener("alpine:init") at line 16), 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: keep Livewire notifications in their originating tab (#20788)”; “fix: prevent transient notifications replaying after concurrent requests (#20726)”; “fix: clean up broadcast notification listeners (#20687)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/notifications/resources/js/index.js`: 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: packages/tables/src/Columns/Concerns/CanUpdateState.php packages/tables/src/Columns/Concerns/CanUpdateState.php:57— packages/tables/src/Columns/Concerns/CanUpdateState.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 CanUpdateState.updateState at line 57), 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: restore accessible editable-column save feedback (#20708)”; “Fix constrained eager loads in editable column callbacks”; “fix: preserve editable column update contract”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/tables/src/Columns/Concerns/CanUpdateState.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: packages/forms/resources/js/components/select.js packages/forms/resources/js/components/select.js:56— packages/forms/resources/js/components/select.js 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 4 (its worst body is select.selectFormComponent.init at line 56), 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: repair select keyboard focus and accessibility (#20697)”; “[3.x] Fix select refresh listener memory leak (#20650)”; “fix”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/forms/resources/js/components/select.js`: 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: packages/panels/src/Panel.php packages/panels/src/Panel.php:87— packages/panels/src/Panel.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 Panel.boot at line 87), 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: restore tenant context for queued imports (#20758)”; “fix: use resource registration getters”; “fix: register tenancy for configurable resources (#20388)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/panels/src/Panel.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: packages/notifications/src/Notification.php packages/notifications/src/Notification.php:354— packages/notifications/src/Notification.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 13 (its worst body is Notification.toEmbeddedHtml at line 354), 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: prevent transient notifications replaying after concurrent requests (#20726)”; “fix: improve notification and dropdown interactions”; “fix: preserve icon rendering configuration (#20605)”. 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 10:20:33 +01:00' --until='2026-10-22 10:20:33 +01:00' --full-history --no-merges -- packages/notifications/src/Notification.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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×14
Members sharing a duplicated core (4 members, 50+ identical tokens) packages/actions/src/SelectAction.php:50— packages/actions/src/SelectAction.php:50-75 | packages/forms/src/Components/Concerns/HasOptions.php:36-61 | packages/query-builder/src/Constraints/SelectConstraint.php:128-153 | packages/tables/src/Filters/Concerns/HasOptions.php:38-63 — 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) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:48— packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:48-249 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:34-199 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:151-273 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:53-228 — 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) packages/forms/src/Commands/MakeFieldCommand.php:121— packages/forms/src/Commands/MakeFieldCommand.php:121-147 | packages/infolists/src/Commands/MakeEntryCommand.php:121-147 | packages/schemas/src/Commands/MakeComponentCommand.php:137-163 | packages/tables/src/Commands/MakeColumnCommand.php:134-164 — 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) packages/forms/src/Components/CheckboxList.php:346— packages/forms/src/Components/CheckboxList.php:346-383 | packages/forms/src/Components/ModalTableSelect.php:586-688 | packages/forms/src/Components/Select.php:1343-1445 | packages/forms/src/Components/TableSelect.php:248-329 — 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) packages/forms/src/Components/ColorPicker.php:66— packages/forms/src/Components/ColorPicker.php:66-199 | packages/forms/src/Components/DateTimePicker.php:103-367 | packages/forms/src/Components/Select.php:1869-2086 | packages/forms/src/Components/TextInput.php:329-427 — 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) packages/forms/src/Components/Concerns/CanBeValidated.php:99— packages/forms/src/Components/Concerns/CanBeValidated.php:99-113 | packages/forms/src/Components/Concerns/CanBeValidated.php:121-135 | packages/forms/src/Components/Concerns/CanBeValidated.php:143-157 | packages/forms/src/Components/Concerns/CanBeValidated.php:443-457 — 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) packages/forms/src/Components/Field.php:243— packages/forms/src/Components/Field.php:243-266 | packages/infolists/src/Components/Entry.php:228-249 | packages/schemas/src/Components/Actions.php:148-165 | packages/schemas/src/Components/FusedGroup.php:197-218 — 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) packages/forms/src/Components/Field.php:352— packages/forms/src/Components/Field.php:352-574 | packages/schemas/src/Components/Actions.php:182-264 | packages/schemas/src/Components/FusedGroup.php:225-443 | packages/schemas/src/Components/Section.php:266-486 — 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) packages/infolists/src/Components/Concerns/CanFormatState.php:125— packages/infolists/src/Components/Concerns/CanFormatState.php:125-137 | packages/infolists/src/Components/Concerns/CanFormatState.php:175-185 | packages/tables/src/Columns/Concerns/CanFormatState.php:125-137 | packages/tables/src/Columns/Concerns/CanFormatState.php:175-185 — 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) packages/infolists/src/Components/Concerns/HasColor.php:32— packages/infolists/src/Components/Concerns/HasColor.php:32-56 | packages/infolists/src/Components/Concerns/HasIcon.php:31-55 | packages/tables/src/Columns/Concerns/HasColor.php:32-56 | packages/tables/src/Columns/Concerns/HasIcon.php:31-55 — 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) packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:268— packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:268-291 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceFormSchemaClassGenerator.php:72-95 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceInfolistSchemaClassGenerator.php:71-94 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceTableClassGenerator.php:77-100 — 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) packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php:63— packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php:63-103 | packages/query-builder/src/Constraints/TextConstraint/Operators/EndsWithOperator.php:63-103 | packages/query-builder/src/Constraints/TextConstraint/Operators/EqualsOperator.php:63-103 | packages/query-builder/src/Constraints/TextConstraint/Operators/StartsWithOperator.php:63-103 — 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) packages/tables/src/Columns/Layout/Grid.php:62— packages/tables/src/Columns/Layout/Grid.php:62-88 | packages/tables/src/Columns/Layout/Panel.php:32-47 | packages/tables/src/Columns/Layout/Split.php:35-53 | packages/tables/src/Columns/Layout/Stack.php:38-68 — 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) packages/schemas/src/Testing/TestsSchemas.php:89— packages/schemas/src/Testing/TestsSchemas.php:89-113 | packages/schemas/src/Testing/TestsSchemas.php:118-142 | packages/schemas/src/Testing/TestsSchemas.php:208-232 | packages/schemas/src/Testing/TestsSchemas.php:237-261 — 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.
Duplicated block (15 lines × 2) packages/actions/src/Testing/ExportFake.php:45— packages/actions/src/Testing/ExportFake.php:45-59 | packages/actions/src/Testing/ExportFake.php:90-104 — 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 `packages/actions/src/Testing/ExportFake.php:45` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/actions/src/Testing/ExportFake.php:106` calls `fail` and `packages/actions/src/Testing/ExportFake.php:61` 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.
Duplicated block (15 lines × 2) packages/forms/src/Components/Repeater.php:1622— packages/forms/src/Components/Repeater.php:1622-1638 | packages/forms/src/Components/Repeater.php:1846-1860 — 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 `packages/forms/src/Components/Repeater.php:1622` 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 (15 lines × 2) packages/panels/src/Navigation/NavigationManager.php:75— packages/panels/src/Navigation/NavigationManager.php:75-89 | packages/panels/src/Pages/Concerns/HasSubNavigation.php:142-156 — 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 `packages/panels/src/Navigation/NavigationManager.php:75` 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 (15 lines × 2) packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:129— packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:129-143 | packages/tables/src/Filters/SelectFilter.php:377-391 — 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 (15 lines × 2) packages/support/src/Concerns/HasCellState.php:417— packages/support/src/Concerns/HasCellState.php:417-431 | packages/support/src/Concerns/HasCellState.php:456-470 — 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) packages/panels/src/Panel/Concerns/HasTenancy.php:103— packages/panels/src/Panel/Concerns/HasTenancy.php:103-117 | packages/panels/src/Panel/Concerns/HasUserMenu.php:74-88 — before extracting anything, compare `packages/panels/src/Panel/Concerns/HasTenancy.php` and `packages/panels/src/Panel/Concerns/HasUserMenu.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 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 (15 lines × 2) packages/actions/src/Commands/MakeImporterCommand.php:106— packages/actions/src/Commands/MakeImporterCommand.php:106-120 | packages/tables/src/Commands/MakeTableCommand.php:105-119 — before extracting anything, compare `packages/actions/src/Commands/MakeImporterCommand.php` and `packages/tables/src/Commands/MakeTableCommand.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (15 lines × 2) packages/forms/src/Components/Select.php:720— packages/forms/src/Components/Select.php:720-734 | packages/tables/src/Columns/SelectColumn.php:461-475 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) packages/schemas/src/Testing/TestsSchemas.php:26— packages/schemas/src/Testing/TestsSchemas.php:26-40 | packages/schemas/src/Testing/TestsSchemas.php:62-76 — 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) packages/schemas/src/Testing/TestsSchemas.php:266— packages/schemas/src/Testing/TestsSchemas.php:266-280 | packages/schemas/src/Testing/TestsSchemas.php:293-307 — 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 `packages/schemas/src/Testing/TestsSchemas.php:266` 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 (15 lines × 2) packages/tables/src/Testing/TestsColumns.php:96— packages/tables/src/Testing/TestsColumns.php:96-110 | packages/tables/src/Testing/TestsColumns.php:134-148 — 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 `packages/tables/src/Testing/TestsColumns.php:96` 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 (15 lines × 2) packages/tables/src/Testing/TestsSummaries.php:21— packages/tables/src/Testing/TestsSummaries.php:21-35 | packages/tables/src/Testing/TestsSummaries.php:55-69 — 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 `packages/tables/src/Testing/TestsSummaries.php:21` 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) packages/actions/src/ActionGroup.php:346— packages/actions/src/ActionGroup.php:346-355 | packages/notifications/src/Notification.php:114-123 — 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 `packages/actions/src/ActionGroup.php:346` 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 (10 lines × 2) packages/actions/src/AssociateAction.php:286— packages/actions/src/AssociateAction.php:286-295 | packages/actions/src/AttachAction.php:293-302 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 `packages/actions/src/AssociateAction.php:286` 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) packages/actions/src/AssociateAction.php:346— packages/actions/src/AssociateAction.php:346-355 | packages/actions/src/AttachAction.php:355-364 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 (10 lines × 2) packages/actions/src/AttachAction.php:228— packages/actions/src/AttachAction.php:228-237 | packages/actions/src/AttachAction.php:339-348 — 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 (10 lines × 2) packages/forms/src/Components/FileUpload.php:544— packages/forms/src/Components/FileUpload.php:544-553 | packages/forms/src/Components/FileUpload.php:561-570 — 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 `packages/forms/src/Components/FileUpload.php:544` 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) packages/panels/src/Resources/Pages/CreateRecord.php:290— packages/panels/src/Resources/Pages/CreateRecord.php:290-299 | packages/panels/src/Resources/Pages/EditRecord.php:352-361 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 `packages/panels/src/Resources/Pages/CreateRecord.php:290` 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 (10 lines × 2) packages/schemas/src/Components/Tabs.php:380— packages/schemas/src/Components/Tabs.php:380-389 | packages/schemas/src/Components/Tabs.php:730-739 — 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 (10 lines × 2) packages/forms/src/Components/MarkdownEditor/MarkdownFaker.php:35— packages/forms/src/Components/MarkdownEditor/MarkdownFaker.php:35-44 | packages/forms/src/Components/RichEditor/RichContentFaker.php:65-78 — 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) packages/forms/src/Components/Select.php:1732— packages/forms/src/Components/Select.php:1732-1741 | packages/forms/src/Components/ToggleButtons.php:435-444 — 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 (10 lines × 2) packages/panels/src/Resources/Pages/EditRecord.php:121— packages/panels/src/Resources/Pages/EditRecord.php:121-130 | packages/panels/src/Resources/Pages/ViewRecord.php:106-115 — 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 (10 lines × 2) packages/forms/src/Components/CheckboxList.php:494— packages/forms/src/Components/CheckboxList.php:494-503 | packages/forms/src/Components/Field.php:118-127 — 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 (10 lines × 2) packages/widgets/src/Commands/FileGenerators/ChartWidgetClassGenerator.php:77— packages/widgets/src/Commands/FileGenerators/ChartWidgetClassGenerator.php:77-86 | packages/widgets/src/Commands/FileGenerators/StatsOverviewWidgetClassGenerator.php:53-62 — 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 (16 lines × 2) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:170— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:170-185 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:216-231 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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 `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:170` 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 (16 lines × 2) packages/actions/src/ForceDeleteAction.php:44— packages/actions/src/ForceDeleteAction.php:44-59 | packages/actions/src/RestoreAction.php:50-65 — 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 `packages/actions/src/ForceDeleteAction.php:44` 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 (16 lines × 2) packages/actions/src/Imports/Importer.php:263— packages/actions/src/Imports/Importer.php:263-278 | packages/actions/src/Imports/Importer.php:288-303 — 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 `packages/actions/src/Imports/Importer.php:263` 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 (16 lines × 2) packages/forms/src/Components/Builder.php:451— packages/forms/src/Components/Builder.php:451-466 | packages/forms/src/Components/Repeater.php:424-439 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:451` 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 (16 lines × 2) packages/forms/src/Components/CodeEditor.php:48— packages/forms/src/Components/CodeEditor.php:48-63 | packages/forms/src/Components/MarkdownEditor.php:121-136 — 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 (16 lines × 2) packages/forms/src/Components/Repeater.php:1816— packages/forms/src/Components/Repeater.php:1816-1831 | packages/forms/src/Components/Repeater.php:1959-1974 — 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 after the matched lines, `packages/forms/src/Components/Repeater.php:1976` calls `getTableColumns`, `isCompact` and `packages/forms/src/Components/Repeater.php:1833` 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.
Duplicated block (16 lines × 2) packages/panels/src/Auth/Http/Requests/BlockEmailChangeVerificationRequest.php:34— packages/panels/src/Auth/Http/Requests/BlockEmailChangeVerificationRequest.php:34-49 | packages/panels/src/Auth/Http/Requests/EmailChangeVerificationRequest.php:52-67 — 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 (16 lines × 2) packages/panels/src/Resources/Pages/EditRecord.php:234— packages/panels/src/Resources/Pages/EditRecord.php:234-249 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:86-101 — before extracting anything, compare `packages/panels/src/Resources/Pages/EditRecord.php` and `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Resources/Pages/EditRecord.php:234` 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 (16 lines × 2) packages/forms/src/Testing/TestsForms.php:86— packages/forms/src/Testing/TestsForms.php:86-101 | packages/forms/src/Testing/TestsForms.php:121-136 — 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 `packages/forms/src/Testing/TestsForms.php:86` 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 (16 lines × 2) packages/schemas/src/Testing/TestsSchemas.php:89— packages/schemas/src/Testing/TestsSchemas.php:89-104 | packages/schemas/src/Testing/TestsSchemas.php:118-133 — 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 `packages/schemas/src/Testing/TestsSchemas.php:89` 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 (16 lines × 2) packages/schemas/src/Testing/TestsSchemas.php:208— packages/schemas/src/Testing/TestsSchemas.php:208-223 | packages/schemas/src/Testing/TestsSchemas.php:237-252 — 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 `packages/schemas/src/Testing/TestsSchemas.php:208` 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 (17 lines × 2) packages/actions/src/Action.php:607— packages/actions/src/Action.php:607-623 | packages/actions/src/ActionGroup.php:418-434 — 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 (17 lines × 2) packages/actions/src/Action.php:638— packages/actions/src/Action.php:638-654 | packages/actions/src/ActionGroup.php:439-455 — 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 (17 lines × 2) packages/actions/src/Concerns/CanExportRecords.php:565— packages/actions/src/Concerns/CanExportRecords.php:565-581 | packages/actions/src/ImportAction.php:620-636 — 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 (17 lines × 2) packages/forms/src/Components/DateTimePicker.php:351— packages/forms/src/Components/DateTimePicker.php:351-367 | packages/forms/src/Components/TextInput.php:411-427 — 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 (17 lines × 2) packages/forms/src/Components/ModalTableSelect.php:413— packages/forms/src/Components/ModalTableSelect.php:413-429 | packages/forms/src/Components/Select.php:953-969 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:413` 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 (17 lines × 2) packages/forms/src/Components/ToggleButtons.php:103— packages/forms/src/Components/ToggleButtons.php:103-119 | packages/forms/src/Components/ToggleButtons.php:230-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/ToggleButtons.php:102` calls `isInline` and `packages/forms/src/Components/ToggleButtons.php:229` 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 (17 lines × 2) packages/infolists/src/Components/IconEntry.php:327— packages/infolists/src/Components/IconEntry.php:327-343 | packages/tables/src/Columns/IconColumn.php:348-364 — before extracting anything, compare `packages/infolists/src/Components/IconEntry.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/IconEntry.php:327` 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: `IconComponent` names `Filament\Infolists\View\Components\IconEntryComponent\IconComponent` in one and `Filament\Tables\View\Components\Columns\IconColumnComponent\IconComponent` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/infolists/src/Components/IconEntry.php:325` calls `getTooltip` and `packages/tables/src/Columns/IconColumn.php:346` does not — after which the two agree again for 4 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 (17 lines × 2) packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:31— packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:31-47 | packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php:35-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 both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:30` calls `isRecoverable` and `packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php:34` does not — after which the two agree again for 4 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 (17 lines × 2) packages/query-builder/src/Models/Scopes/QueryBuilderScope.php:115— packages/query-builder/src/Models/Scopes/QueryBuilderScope.php:115-131 | packages/tables/src/Filters/QueryBuilder.php:450-466 — 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 (17 lines × 2) docs-assets/app/app/Filament/Exports/PostExporter.php:16— docs-assets/app/app/Filament/Exports/PostExporter.php:16-32 | docs-assets/app/app/Filament/Imports/PostImporter.php:16-43 — 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 `docs-assets/app/app/Filament/Exports/PostExporter.php:16` 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 (18 lines × 2) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:116— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:116-133 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:118-135 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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 (18 lines × 2) packages/forms/src/Components/Builder.php:604— packages/forms/src/Components/Builder.php:604-621 | packages/forms/src/Components/Repeater.php:562-579 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:604` 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 (18 lines × 2) packages/forms/src/Components/ModalTableSelect.php:257— packages/forms/src/Components/ModalTableSelect.php:257-274 | packages/forms/src/Components/Select.php:820-837 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:257` 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. 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 (18 lines × 2) packages/forms/src/Components/ModalTableSelect.php:382— packages/forms/src/Components/ModalTableSelect.php:382-399 | packages/forms/src/Components/Select.php:922-939 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:382` 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 (18 lines × 2) packages/forms/src/Components/Select.php:1094— packages/forms/src/Components/Select.php:1094-1111 | packages/forms/src/Components/Select.php:1136-1153 — 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 `packages/forms/src/Components/Select.php:1094` 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 (18 lines × 2) packages/infolists/src/Components/Concerns/CanFormatState.php:238— packages/infolists/src/Components/Concerns/CanFormatState.php:238-255 | packages/tables/src/Columns/Concerns/CanFormatState.php:238-255 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/CanFormatState.php:238` 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 (18 lines × 2) packages/infolists/src/Components/TextEntry.php:107— packages/infolists/src/Components/TextEntry.php:107-124 | packages/tables/src/Columns/TextColumn.php:115-132 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) packages/infolists/src/Components/Concerns/HasColor.php:64— packages/infolists/src/Components/Concerns/HasColor.php:64-81 | packages/tables/src/Columns/Concerns/HasColor.php:64-81 — before extracting anything, compare `packages/infolists/src/Components/Concerns/HasColor.php` and `packages/tables/src/Columns/Concerns/HasColor.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 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) packages/infolists/src/Components/Concerns/HasIcon.php:67— packages/infolists/src/Components/Concerns/HasIcon.php:67-84 | packages/tables/src/Columns/Concerns/HasIcon.php:67-84 — 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.
Swallowed exception (empty catch) packages/forms/resources/js/components/markdown-editor.js:220— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/forms/resources/js/components/rich-editor/extension-mention.js:308— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/forms/resources/js/components/rich-editor/extension-mention.js:374— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/forms/resources/js/components/rich-editor/extension-mention.js:415— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/forms/resources/js/utilities/reordering.js:295— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/notifications/resources/js/components/notifications.js:27— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/notifications/resources/js/components/notifications.js:40— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/schemas/resources/js/index.js:142— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/upgrade/src/check-compatibility.php:59— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated block (6 lines × 2) packages/actions/src/AssociateAction.php:276— packages/actions/src/AssociateAction.php:276-281 | packages/actions/src/AttachAction.php:282-287 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 `packages/actions/src/AssociateAction.php:276` 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 (6 lines × 2) packages/forms/src/Components/RichEditor/RichContentAttribute.php:310— packages/forms/src/Components/RichEditor/RichContentAttribute.php:310-315 | packages/forms/src/Components/RichEditor/RichContentRenderer.php:724-729 — 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 (6 lines × 2) packages/infolists/src/View/Components/TextEntryComponent/ItemComponent.php:17— packages/infolists/src/View/Components/TextEntryComponent/ItemComponent.php:17-22 | packages/tables/src/View/Components/Columns/TextColumnComponent/ItemComponent.php:17-22 — before extracting anything, compare `packages/infolists/src/View/Components/TextEntryComponent/ItemComponent.php` and `packages/tables/src/View/Components/Columns/TextColumnComponent/ItemComponent.php` as WHOLE FILES: 87% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (6 lines × 2) packages/panels/src/Auth/Pages/Login.php:334— packages/panels/src/Auth/Pages/Login.php:334-339 | packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:151-156 — 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 (6 lines × 2) packages/actions/src/Exports/ExportColumn.php:113— packages/actions/src/Exports/ExportColumn.php:113-118 | packages/tables/src/Grouping/Group.php:192-197 — 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 (6 lines × 2) packages/infolists/src/View/Components/IconEntryComponent/IconComponent.php:24— packages/infolists/src/View/Components/IconEntryComponent/IconComponent.php:24-29 | packages/tables/src/View/Components/Columns/IconColumnComponent/IconComponent.php:24-29 — before extracting anything, compare `packages/infolists/src/View/Components/IconEntryComponent/IconComponent.php` and `packages/tables/src/View/Components/Columns/IconColumnComponent/IconComponent.php` as WHOLE FILES: 86% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (6 lines × 2) packages/panels/src/Resources/Pages/Concerns/HasRelationManagers.php:171— packages/panels/src/Resources/Pages/Concerns/HasRelationManagers.php:171-176 | packages/panels/src/Resources/Pages/Concerns/HasRelationManagers.php:231-236 — 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 `packages/panels/src/Resources/Pages/Concerns/HasRelationManagers.php:171` 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) packages/panels/src/Resources/Pages/ManageRelatedRecords.php:283— packages/panels/src/Resources/Pages/ManageRelatedRecords.php:283-288 | packages/panels/src/Resources/RelationManagers/RelationManager.php:375-380 — 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 (20 lines × 2) packages/actions/src/Concerns/CanExportRecords.php:214— packages/actions/src/Concerns/CanExportRecords.php:214-233 | packages/actions/src/ImportAction.php:209-228 — 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 (20 lines × 2) packages/actions/src/Exports/Models/Export.php:58— packages/actions/src/Exports/Models/Export.php:58-77 | packages/actions/src/Imports/Models/Import.php:64-83 — 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 (20 lines × 2) packages/infolists/src/Components/ImageEntry.php:157— packages/infolists/src/Components/ImageEntry.php:157-176 | packages/tables/src/Columns/ImageColumn.php:151-170 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (20 lines × 2) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:165— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:165-184 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:139-158 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (20 lines × 2) packages/panels/src/Navigation/NavigationManager.php:232— packages/panels/src/Navigation/NavigationManager.php:232-251 | packages/panels/src/Panel/Concerns/HasNavigation.php:57-76 — 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 (20 lines × 2) packages/support/src/SupportServiceProvider.php:255— packages/support/src/SupportServiceProvider.php:255-274 | packages/support/src/View/ComponentAttributeBag.php:115-134 — 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 `packages/support/src/SupportServiceProvider.php:255` 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 (20 lines × 2) packages/schemas/src/Testing/TestsSchemas.php:346— packages/schemas/src/Testing/TestsSchemas.php:346-365 | packages/schemas/src/Testing/TestsSchemas.php:370-389 — 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 (12 lines × 2) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:158— packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:158-169 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:197-208 — 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 `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:158` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:171` calls `in_array`, `str`, `endsWith` and `packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:209` 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 (12 lines × 2) packages/forms/src/Components/Builder.php:495— packages/forms/src/Components/Builder.php:495-506 | packages/forms/src/Components/Builder.php:545-556 — 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 `packages/forms/src/Components/Builder.php:495` 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) packages/panels/src/Resources/Resource/Concerns/HasGlobalSearch.php:181— packages/panels/src/Resources/Resource/Concerns/HasGlobalSearch.php:181-192 | packages/panels/src/Resources/Resource/Concerns/HasGlobalSearch.php:203-214 — 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 (12 lines × 2) packages/schemas/src/Components/Component.php:214— packages/schemas/src/Components/Component.php:214-225 | packages/schemas/src/Components/Flex.php:95-106 — 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 `packages/schemas/src/Components/Component.php:214` 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 (12 lines × 2) packages/schemas/src/Components/Concerns/HasState.php:1022— packages/schemas/src/Components/Concerns/HasState.php:1022-1033 | packages/support/src/Concerns/HasCellState.php:108-119 — 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 (12 lines × 2) packages/schemas/src/Components/View.php:12— packages/schemas/src/Components/View.php:12-23 | packages/tables/src/Columns/Layout/View.php:12-23 — before extracting anything, compare `packages/schemas/src/Components/View.php` and `packages/tables/src/Columns/Layout/View.php` as WHOLE FILES: 86% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/schemas/src/Components/View.php:12` 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 (12 lines × 2) packages/tables/src/Concerns/CanSearchRecords.php:26— packages/tables/src/Concerns/CanSearchRecords.php:26-37 | packages/tables/src/Concerns/HasFilters.php:63-74 — 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) packages/actions/src/AssociateAction.php:304— packages/actions/src/AssociateAction.php:304-311 | packages/actions/src/AttachAction.php:313-320 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 `packages/actions/src/AssociateAction.php:304` 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) packages/infolists/src/Components/Concerns/CanFormatState.php:289— packages/infolists/src/Components/Concerns/CanFormatState.php:289-296 | packages/tables/src/Columns/Concerns/CanFormatState.php:289-296 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/CanFormatState.php:289` 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) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:265— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:265-272 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:242-249 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:287— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:287-294 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:287-294 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:287` 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 (8 lines × 2) packages/schemas/src/Components/Section.php:109— packages/schemas/src/Components/Section.php:109-116 | packages/schemas/src/Components/Tabs.php:87-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/schemas/src/Components/Section.php:109` 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `null` to `string | array | Htmlable | Closure | null $heading =` in one and `string | Htmlable | Closure | null $label =` 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 (8 lines × 2) packages/tables/src/Commands/FileGenerators/LivewireTableComponentClassGenerator.php:125— packages/tables/src/Commands/FileGenerators/LivewireTableComponentClassGenerator.php:125-132 | packages/widgets/src/Commands/FileGenerators/TableWidgetClassGenerator.php:69-76 — 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 (8 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsMonthOperator.php:68— packages/query-builder/src/Constraints/DateConstraint/Operators/IsMonthOperator.php:68-75 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsYearOperator.php:56-63 — 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (5 members, 50+ identical tokens) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:116— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:116-185 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:118-231 | packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:48-249 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:34-199 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:53-228 — 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) packages/forms/src/Components/CheckboxList.php:190— packages/forms/src/Components/CheckboxList.php:190-297 | packages/forms/src/Components/Select.php:1004-1065 | packages/forms/src/Components/Select.php:1073-1185 | packages/tables/src/Columns/SelectColumn.php:606-663 | packages/tables/src/Columns/SelectColumn.php:671-727 — 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) packages/forms/src/Components/CheckboxList.php:452— packages/forms/src/Components/CheckboxList.php:452-462 | packages/forms/src/Components/ModalTableSelect.php:724-734 | packages/forms/src/Components/Repeater.php:1195-1205 | packages/forms/src/Components/Select.php:1514-1524 | packages/forms/src/Components/TableSelect.php:387-397 — 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) packages/panels/src/Auth/Pages/EditProfile.php:164— packages/panels/src/Auth/Pages/EditProfile.php:164-230 | packages/panels/src/Pages/Tenancy/EditTenantProfile.php:119-153 | packages/panels/src/Pages/Tenancy/RegisterTenant.php:75-111 | packages/panels/src/Resources/Pages/EditRecord.php:208-249 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:64-107 — 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) packages/panels/src/Commands/MakePageCommand.php:450— packages/panels/src/Commands/MakePageCommand.php:450-465 | packages/panels/src/Commands/MakePageCommand.php:470-490 | packages/panels/src/Commands/MakePageCommand.php:495-510 | packages/widgets/src/Commands/MakeWidgetCommand.php:413-428 | packages/widgets/src/Commands/MakeWidgetCommand.php:468-482 — 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) packages/forms/src/Testing/TestsForms.php:259— packages/forms/src/Testing/TestsForms.php:259-288 | packages/forms/src/Testing/TestsForms.php:301-330 | packages/forms/src/Testing/TestsForms.php:343-367 | packages/forms/src/Testing/TestsForms.php:380-404 | packages/forms/src/Testing/TestsForms.php:417-441 — 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.
Duplicated block (24 lines × 2) packages/forms/src/Components/Builder.php:397— packages/forms/src/Components/Builder.php:397-420 | packages/forms/src/Components/Repeater.php:370-393 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:397` 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 (24 lines × 2) packages/forms/src/Components/ModalTableSelect.php:299— packages/forms/src/Components/ModalTableSelect.php:299-322 | packages/forms/src/Components/Select.php:844-867 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:299` 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 (24 lines × 2) packages/notifications/src/Notification.php:255— packages/notifications/src/Notification.php:255-278 | packages/notifications/src/Notification.php:303-326 — 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 `packages/notifications/src/Notification.php:255` 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 (24 lines × 2) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:304— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:304-327 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:318-341 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (24 lines × 2) packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:32— packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:32-55 | packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php:34-57 — before extracting anything, compare `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php` and `packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:32` 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. 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 (24 lines × 2) packages/actions/src/Exports/Concerns/CanBeHidden.php:15— packages/actions/src/Exports/Concerns/CanBeHidden.php:15-38 | packages/query-builder/src/Constraints/Operators/Concerns/CanBeHidden.php:15-38 — before extracting anything, compare `packages/actions/src/Exports/Concerns/CanBeHidden.php` and `packages/query-builder/src/Constraints/Operators/Concerns/CanBeHidden.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/actions/src/Exports/Concerns/CanBeHidden.php:15` 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 × 3) packages/actions/src/Action.php:1029— packages/actions/src/Action.php:1029-1036 | packages/actions/src/Action.php:1066-1073 | packages/actions/src/Action.php:1176-1183 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/actions/src/Action.php:1075` calls `isOutlined` and `packages/actions/src/Action.php:1185` 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 × 3) packages/forms/src/Components/RichEditor.php:1532— packages/forms/src/Components/RichEditor.php:1532-1539 | packages/forms/src/Components/RichEditor.php:1550-1557 | packages/forms/src/Components/RichEditor.php:1568-1575 — 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 `packages/forms/src/Components/RichEditor.php:1532` 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 (8 lines × 3) packages/tables/src/Columns/CheckboxColumn.php:39— packages/tables/src/Columns/CheckboxColumn.php:39-60 | packages/tables/src/Columns/SelectColumn.php:1004-1011 | packages/tables/src/Columns/TextInputColumn.php:231-251 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/tables/src/Columns/CheckboxColumn.php:39` 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 (8 lines × 3) packages/forms/src/Commands/FileGenerators/LivewireFormComponentClassGenerator.php:232— packages/forms/src/Commands/FileGenerators/LivewireFormComponentClassGenerator.php:232-239 | packages/schemas/src/Commands/FileGenerators/LivewireSchemaComponentClassGenerator.php:115-122 | packages/tables/src/Commands/FileGenerators/LivewireTableComponentClassGenerator.php:139-146 — 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.
Duplicated block (8 lines × 3) packages/panels/src/Commands/FileGenerators/ClusterClassGenerator.php:51— packages/panels/src/Commands/FileGenerators/ClusterClassGenerator.php:51-58 | packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:136-143 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:86-93 — 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.
Duplicated block (8 lines × 3) packages/tables/src/Concerns/CanGroupRecords.php:34— packages/tables/src/Concerns/CanGroupRecords.php:34-41 | packages/tables/src/Concerns/CanSortRecords.php:57-64 | packages/tables/src/Concerns/CanSortRecords.php:69-76 — 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.
Duplicated block (7 lines × 3) packages/actions/src/Action.php:1037— packages/actions/src/Action.php:1037-1043 | packages/actions/src/Action.php:1147-1153 | packages/actions/src/Action.php:1185-1191 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/actions/src/Action.php:1034` calls `getIconPosition` and `packages/actions/src/Action.php:1144` 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 (7 lines × 3) packages/actions/src/ActionGroup.php:645— packages/actions/src/ActionGroup.php:645-651 | packages/actions/src/ActionGroup.php:685-691 | packages/actions/src/ActionGroup.php:703-709 — 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.
Duplicated block (7 lines × 3) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150-156 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:90-96 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:108-114 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150` 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 (7 lines × 3) packages/forms/src/Components/Builder.php:1678— packages/forms/src/Components/Builder.php:1678-1684 | packages/forms/src/Components/Repeater.php:1822-1828 | packages/forms/src/Components/Repeater.php:1965-1971 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Builder.php:1685` calls `isCollapsible` and `packages/forms/src/Components/Repeater.php:1829` 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.
Duplicated block (7 lines × 3) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:102— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:102-108 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:104-110 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:278-284 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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 (7 lines × 3) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:258— packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:258-264 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:208-214 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:237-243 — before extracting anything, compare `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php` and `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (12 lines × 2 locations) REDACTED:961— REDACTED:961 · REDACTED:978 — 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 (12 lines × 2 locations) REDACTED:2360— REDACTED:2360 · REDACTED:2380 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) REDACTED:2870— REDACTED:2870 · REDACTED:3009 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) packages/forms/resources/js/components/rich-editor.js:777— packages/forms/resources/js/components/rich-editor.js:777 · packages/forms/resources/js/components/rich-editor.js:811 — 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 (12 lines × 2 locations) packages/support/resources/js/utilities/select.js:1207— packages/support/resources/js/utilities/select.js:1207 · packages/support/resources/js/utilities/select.js:1223 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) packages/tables/resources/js/components/columns/select.js:144— packages/tables/resources/js/components/columns/select.js:144 · packages/tables/resources/js/components/columns/text-input.js:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Change-coupling hub: EditRecord.php → RequestPasswordReset.php, REDACTED, EditTenantProfile.php, RegisterTenant.php, CreateRecord.php, ViewRecord.php packages/panels/src/Resources/Pages/EditRecord.php— `packages/panels/src/Resources/Pages/EditRecord.php` changes together with 6 other files — `packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php`, `packages/panels/src/Auth/Pages/Register.php`, `packages/panels/src/Pages/Tenancy/EditTenantProfile.php`, `packages/panels/src/Pages/Tenancy/RegisterTenant.php`, `packages/panels/src/Resources/Pages/CreateRecord.php`, `packages/panels/src/Resources/Pages/ViewRecord.php` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: EditTenantProfile.php → EditProfile.php, RegisterTenant.php, CreateRecord.php packages/panels/src/Pages/Tenancy/EditTenantProfile.php— `packages/panels/src/Pages/Tenancy/EditTenantProfile.php` changes together with 3 other files — `packages/panels/src/Auth/Pages/EditProfile.php`, `packages/panels/src/Pages/Tenancy/RegisterTenant.php`, `packages/panels/src/Resources/Pages/CreateRecord.php` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: REDACTED → RequestPasswordReset.php, REDACTED, REDACTED packages/panels/src/Auth/Pages/Login.php— `packages/panels/src/Auth/Pages/Login.php` changes together with 3 other files — `packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php`, `packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php`, `packages/panels/src/Auth/Pages/Register.php` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: Radio.php → CheckboxList.php, Select.php, ToggleButtons.php packages/forms/src/Components/Radio.php— `packages/forms/src/Components/Radio.php` changes together with 3 other files — `packages/forms/src/Components/CheckboxList.php`, `packages/forms/src/Components/Select.php`, `packages/forms/src/Components/ToggleButtons.php` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: RichEditor.php → rich-editor.js, extensions.js, MarkdownEditor.php packages/forms/src/Components/RichEditor.php— `packages/forms/src/Components/RichEditor.php` changes together with 3 other files — `packages/forms/resources/js/components/rich-editor.js`, `packages/forms/resources/js/components/rich-editor/extensions.js`, `packages/forms/src/Components/MarkdownEditor.php` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Duplicated block (25 lines × 2) packages/forms/src/Commands/MakeFormCommand.php:131— packages/forms/src/Commands/MakeFormCommand.php:131-155 | packages/forms/src/Commands/MakeLivewireFormCommand.php:162-186 — before extracting anything, compare `packages/forms/src/Commands/MakeFormCommand.php` and `packages/forms/src/Commands/MakeLivewireFormCommand.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 `packages/forms/src/Commands/MakeFormCommand.php:131` 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 (25 lines × 2) packages/forms/src/Components/Concerns/CanBeValidated.php:651— packages/forms/src/Components/Concerns/CanBeValidated.php:651-675 | packages/forms/src/Components/Concerns/CanFixIndistinctState.php:23-47 — 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 (25 lines × 2) packages/schemas/src/Components/Concerns/BelongsToModel.php:39— packages/schemas/src/Components/Concerns/BelongsToModel.php:39-63 | packages/schemas/src/Components/Concerns/BelongsToModel.php:70-94 — 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 (25 lines × 2) packages/tables/src/Columns/SelectColumn.php:627— packages/tables/src/Columns/SelectColumn.php:627-651 | packages/tables/src/Columns/SelectColumn.php:691-715 — 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 `packages/tables/src/Columns/SelectColumn.php:627` 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 (25 lines × 2) packages/tables/src/Testing/TestsColumns.php:216— packages/tables/src/Testing/TestsColumns.php:216-240 | packages/tables/src/Testing/TestsColumns.php:265-289 — 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 `packages/tables/src/Testing/TestsColumns.php:216` 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 (22 lines × 2) packages/actions/src/Concerns/CanExportRecords.php:316— packages/actions/src/Concerns/CanExportRecords.php:316-337 | packages/actions/src/ImportAction.php:255-276 — 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 `packages/actions/src/Concerns/CanExportRecords.php:316` 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 (22 lines × 2) packages/panels/src/Auth/Pages/EditProfile.php:164— packages/panels/src/Auth/Pages/EditProfile.php:164-185 | packages/panels/src/Auth/Pages/EmailVerification/EmailVerificationPrompt.php:69-90 — 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 (22 lines × 2) packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:215— packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:215-236 | packages/panels/src/Resources/Pages/ListRecords.php:172-193 — 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 `packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:215` 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 (22 lines × 2) packages/forms/src/Components/Repeater/TableColumn.php:30— packages/forms/src/Components/Repeater/TableColumn.php:30-63 | packages/infolists/src/Components/RepeatableEntry/TableColumn.php:26-47 — before extracting anything, compare `packages/forms/src/Components/Repeater/TableColumn.php` and `packages/infolists/src/Components/RepeatableEntry/TableColumn.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Repeater/TableColumn.php:30` 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 (22 lines × 2) docs-assets/app/app/Livewire/Panels/Navigation/SidebarCollapsibleOnDesktop.php:17— docs-assets/app/app/Livewire/Panels/Navigation/SidebarCollapsibleOnDesktop.php:17-38 | docs-assets/app/app/Livewire/Panels/Navigation/SidebarCollapsibleWithGroupIcons.php:17-53 — before extracting anything, compare `docs-assets/app/app/Livewire/Panels/Navigation/SidebarCollapsibleOnDesktop.php` and `docs-assets/app/app/Livewire/Panels/Navigation/SidebarCollapsibleWithGroupIcons.php` as WHOLE FILES: 85% 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 (21 lines × 2) packages/forms/src/Components/Builder.php:249— packages/forms/src/Components/Builder.php:249-269 | packages/forms/src/Components/Builder.php:347-367 — 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 `packages/forms/src/Components/Builder.php:249` 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) packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:41— packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:41-61 | packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.php:41-61 — before extracting anything, compare `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php` and `packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.php:62` calls `validationAttribute`, `__` and `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php:62` 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.
Duplicated block (21 lines × 2) packages/panels/src/Commands/MakePageCommand.php:252— packages/panels/src/Commands/MakePageCommand.php:252-272 | packages/widgets/src/Commands/MakeWidgetCommand.php:272-292 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/widgets/src/Commands/MakeWidgetCommand.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakePageCommand.php:252` 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 (21 lines × 2) packages/tables/src/Concerns/CanSearchRecords.php:155— packages/tables/src/Concerns/CanSearchRecords.php:155-175 | packages/tables/src/Concerns/CanSearchRecords.php:181-201 — 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 (21 lines × 2) packages/query-builder/src/Constraints/Concerns/HasLabel.php:15— packages/query-builder/src/Constraints/Concerns/HasLabel.php:15-35 | packages/tables/src/Filters/Concerns/HasLabel.php:16-36 — 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 `packages/query-builder/src/Constraints/Concerns/HasLabel.php:15` 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 (5 lines × 3) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150-154 | packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:135-139 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:108-112 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:150` 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 × 3) packages/schemas/src/View/Components/TextComponent.php:18— packages/schemas/src/View/Components/TextComponent.php:18-22 | packages/support/src/View/Components/BadgeComponent.php:18-22 | packages/support/src/View/Components/LinkComponent.php:18-22 — before extracting anything, compare `packages/schemas/src/View/Components/TextComponent.php` and `packages/support/src/View/Components/LinkComponent.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 × 3) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:76— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:76-80 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:78-82 | packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:125-129 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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) packages/panels/src/Resources/Pages/CreateRecord.php:418— packages/panels/src/Resources/Pages/CreateRecord.php:418-422 | packages/panels/src/Resources/Pages/EditRecord.php:465-469 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:221-225 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 × 3) packages/tables/src/Columns/Summarizers/Average.php:82— packages/tables/src/Columns/Summarizers/Average.php:82-86 | packages/tables/src/Columns/Summarizers/Count.php:81-85 | packages/tables/src/Columns/Summarizers/Sum.php:38-42 — 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 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 (27 lines × 2) packages/forms/src/Components/Builder.php:1724— packages/forms/src/Components/Builder.php:1724-1750 | packages/forms/src/Components/Repeater.php:1636-1662 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:1724` 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 (27 lines × 2) packages/infolists/src/Components/TextEntry.php:418— packages/infolists/src/Components/TextEntry.php:418-444 | packages/tables/src/Columns/TextColumn.php:508-534 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/TextEntry.php:418` 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 (27 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:191— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:191-217 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:191-217 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 (27 lines × 2) packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:147— packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:147-173 | packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php:146-172 — before extracting anything, compare `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php` and `packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) packages/forms/src/Components/ModalTableSelect.php:216— packages/forms/src/Components/ModalTableSelect.php:216-238 | packages/forms/src/Components/Select.php:676-698 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/ModalTableSelect.php:214` calls `getOptionLabels` and `packages/forms/src/Components/Select.php:674` 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.
Duplicated block (23 lines × 2) packages/infolists/src/Components/Concerns/CanFormatState.php:263— packages/infolists/src/Components/Concerns/CanFormatState.php:263-285 | packages/tables/src/Columns/Concerns/CanFormatState.php:263-285 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) packages/infolists/src/Components/TextEntry.php:314— packages/infolists/src/Components/TextEntry.php:314-336 | packages/tables/src/Columns/TextColumn.php:413-435 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/TextEntry.php:314` 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 first that the copies are not typed on the same thing: `IconComponent` names `Filament\Infolists\View\Components\TextEntryComponent\ItemComponent\IconComponent` in one and `Filament\Tables\View\Components\Columns\TextColumnComponent\ItemComponent\IconComponent` 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 (23 lines × 2) packages/infolists/src/Components/Concerns/HasTooltip.php:17— packages/infolists/src/Components/Concerns/HasTooltip.php:17-39 | packages/tables/src/Columns/Concerns/HasTooltip.php:19-58 — before extracting anything, compare `packages/infolists/src/Components/Concerns/HasTooltip.php` and `packages/tables/src/Columns/Concerns/HasTooltip.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/HasTooltip.php:17` 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.
Duplicated block (15 lines × 3) packages/forms/src/Components/Builder.php:1700— packages/forms/src/Components/Builder.php:1700-1714 | packages/forms/src/Components/Repeater.php:1608-1622 | packages/forms/src/Components/Repeater.php:1980-1994 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Repeater.php:1625` calls `grid`, `getGridColumns` and `packages/forms/src/Components/Repeater.php:1997` 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.
Duplicated block (15 lines × 3) packages/support/src/View/Concerns/CanGenerateButtonHtml.php:243— packages/support/src/View/Concerns/CanGenerateButtonHtml.php:243-257 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:155-169 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:183-197 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` and `packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 (15 lines × 3) packages/forms/src/Testing/TestsForms.php:26— packages/forms/src/Testing/TestsForms.php:26-40 | packages/forms/src/Testing/TestsForms.php:87-101 | packages/forms/src/Testing/TestsForms.php:122-136 — 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.
Duplicated block (15 lines × 3) packages/forms/src/Testing/TestsForms.php:261— packages/forms/src/Testing/TestsForms.php:261-275 | packages/forms/src/Testing/TestsForms.php:303-317 | packages/forms/src/Testing/TestsForms.php:345-359 — 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 `packages/forms/src/Testing/TestsForms.php:261` 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.
AC3 · Page structure· Page without a main landmark · ×3
Page without a main landmark docs-assets/app/resources/views/components/layouts/app.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 packages/panels/resources/views/components/layout/base.blade.php:14— 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 packages/support/stubs/scaffolding/resources/views/components/layouts/app.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>.
(anonymous) (cyclomatic 20) packages/schemas/resources/js/index.js:116— (anonymous) has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 20 function items inside it that branch (a function literal at line 129, a function literal at line 197, a function literal at line 266, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 20) packages/support/resources/js/utilities/pluralize.js:2— (anonymous) has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (extractFromString, replace, extract, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 20) packages/panels/resources/js/stores/sidebar.js:1— (anonymous) has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 16 function items inside it that branch (a function literal at line 132, open, a function literal at line 47, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous)::keydown (cyclomatic 20) packages/panels/resources/js/components/global-search.js:152— (anonymous)::keydown 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.
(anonymous)::syncActionModals (cyclomatic 17) packages/actions/resources/js/components/modals.js:95— (anonymous)::syncActionModals has cyclomatic complexity 17 (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.
(anonymous)::handleMenuKeydown (cyclomatic 16) packages/support/resources/js/components/dropdown.js:560— (anonymous)::handleMenuKeydown 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.
Duplicated block (36 lines × 2) packages/forms/src/Components/Select.php:590— packages/forms/src/Components/Select.php:590-625 | packages/tables/src/Columns/SelectColumn.php:406-441 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Select.php:590` 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, `packages/tables/src/Columns/SelectColumn.php:402` calls `elseif` and `packages/forms/src/Components/Select.php:587` 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 (36 lines × 2) packages/forms/src/Components/Select.php:1297— packages/forms/src/Components/Select.php:1297-1332 | packages/forms/src/Components/TableSelect.php:202-237 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 312 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 `packages/forms/src/Components/Select.php:1297` 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 (36 lines × 2) packages/schemas/src/Components/Concerns/HasState.php:1102— packages/schemas/src/Components/Concerns/HasState.php:1102-1137 | packages/support/src/Concerns/HasCellState.php:141-176 — 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 (34 lines × 2) packages/forms/src/Components/ModalTableSelect.php:346— packages/forms/src/Components/ModalTableSelect.php:346-379 | packages/forms/src/Components/Select.php:886-919 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:346` 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 (34 lines × 2) packages/infolists/src/Components/TextEntry.php:484— packages/infolists/src/Components/TextEntry.php:484-517 | packages/tables/src/Columns/TextColumn.php:595-628 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 2) packages/panels/src/Commands/MakePageCommand.php:326— packages/panels/src/Commands/MakePageCommand.php:326-359 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:221-254 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakePageCommand.php:326` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/panels/src/Commands/MakePageCommand.php:322` calls `filled` and `packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:220` 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 (33 lines × 2) packages/forms/src/Components/ModalTableSelect.php:443— packages/forms/src/Components/ModalTableSelect.php:443-475 | packages/forms/src/Components/TableSelect.php:117-149 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 322 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 `packages/forms/src/Components/ModalTableSelect.php:443` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/ModalTableSelect.php:477` calls `strval` and `packages/forms/src/Components/TableSelect.php:151` 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.
Duplicated block (33 lines × 2) packages/panels/src/Resources/Pages/ManageRelatedRecords.php:302— packages/panels/src/Resources/Pages/ManageRelatedRecords.php:302-334 | packages/panels/src/Resources/RelationManagers/RelationManager.php:394-426 — 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 `packages/panels/src/Resources/Pages/ManageRelatedRecords.php:302` 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 (33 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:37— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:37-69 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:37-69 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 (19 lines × 2) packages/actions/src/Exports/Http/Controllers/DownloadExport.php:18— packages/actions/src/Exports/Http/Controllers/DownloadExport.php:18-36 | packages/actions/src/Imports/Http/Controllers/DownloadImportFailureCsv.php:15-33 — 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 (19 lines × 2) packages/forms/src/Components/ModalTableSelect.php:434— packages/forms/src/Components/ModalTableSelect.php:434-452 | packages/forms/src/Components/Select.php:1190-1208 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:434` 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 (19 lines × 2) packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:150— packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:150-168 | packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:192-210 — 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 (14 lines × 3) packages/panels/src/Auth/Pages/EditProfile.php:202— packages/panels/src/Auth/Pages/EditProfile.php:202-215 | packages/panels/src/Pages/Tenancy/EditTenantProfile.php:134-147 | packages/panels/src/Resources/Pages/EditRecord.php:234-247 — before extracting anything, compare `packages/panels/src/Pages/Tenancy/EditTenantProfile.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Auth/Pages/EditProfile.php:202` 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 (14 lines × 3) packages/panels/src/Pages/Tenancy/EditTenantProfile.php:134— packages/panels/src/Pages/Tenancy/EditTenantProfile.php:134-147 | packages/panels/src/Resources/Pages/EditRecord.php:234-247 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:86-99 — before extracting anything, compare `packages/panels/src/Pages/Tenancy/EditTenantProfile.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Pages/Tenancy/EditTenantProfile.php:134` 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 after the matched lines, `packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:101` calls `rememberData` and `packages/panels/src/Pages/Tenancy/EditTenantProfile.php:149` does not — after which the two agree again for 4 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 (14 lines × 3) packages/schemas/src/Components/Concerns/CanBeDisabled.php:36— packages/schemas/src/Components/Concerns/CanBeDisabled.php:36-49 | packages/schemas/src/Components/Concerns/CanBeHidden.php:43-56 | packages/schemas/src/Components/Concerns/CanBeHidden.php:127-140 — 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 `packages/schemas/src/Components/Concerns/CanBeDisabled.php:36` 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 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 (12 lines × 3) packages/forms/src/Components/Select.php:1006— packages/forms/src/Components/Select.php:1006-1017 | packages/forms/src/Components/Select.php:1094-1105 | packages/forms/src/Components/Select.php:1136-1147 — 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.
Duplicated block (12 lines × 3) packages/query-builder/src/Constraints/NumberConstraint/Operators/EqualsOperator.php:61— packages/query-builder/src/Constraints/NumberConstraint/Operators/EqualsOperator.php:61-72 | packages/query-builder/src/Constraints/NumberConstraint/Operators/IsMaxOperator.php:61-72 | packages/query-builder/src/Constraints/NumberConstraint/Operators/IsMinOperator.php:61-72 — 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 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 (12 lines × 3) packages/forms/src/Commands/MakeFormCommand.php:176— packages/forms/src/Commands/MakeFormCommand.php:176-187 | packages/schemas/src/Commands/MakeSchemaCommand.php:110-121 | packages/tables/src/Commands/MakeTableCommand.php:186-197 — before extracting anything, compare `packages/forms/src/Commands/MakeFormCommand.php` and `packages/schemas/src/Commands/MakeSchemaCommand.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) packages/forms/src/Components/MorphToSelect.php:272— packages/forms/src/Components/MorphToSelect.php:272-282 | packages/forms/src/Components/RichEditor/RichEditorTool.php:155-165 | packages/infolists/src/Components/Entry.php:108-118 — 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.
Duplicated block (11 lines × 3) packages/infolists/src/Components/ImageEntry.php:181— packages/infolists/src/Components/ImageEntry.php:181-191 | packages/schemas/src/Components/Image.php:94-104 | packages/tables/src/Columns/ImageColumn.php:175-185 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 × 3) packages/infolists/src/Components/ImageEntry.php:295— packages/infolists/src/Components/ImageEntry.php:295-305 | packages/schemas/src/Components/Image.php:109-119 | packages/tables/src/Columns/ImageColumn.php:289-299 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (10 lines × 5) packages/forms/src/Components/CheckboxList.php:453— packages/forms/src/Components/CheckboxList.php:453-462 | packages/forms/src/Components/ModalTableSelect.php:725-734 | packages/forms/src/Components/Repeater.php:1196-1205 | packages/forms/src/Components/Select.php:1515-1524 | packages/forms/src/Components/TableSelect.php:388-397 — 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 5 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/CheckboxList.php:453` 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 × 5) packages/panels/src/Commands/MakePageCommand.php:451— packages/panels/src/Commands/MakePageCommand.php:451-460 | packages/panels/src/Commands/MakePageCommand.php:471-480 | packages/panels/src/Commands/MakePageCommand.php:496-505 | packages/widgets/src/Commands/MakeWidgetCommand.php:414-423 | packages/widgets/src/Commands/MakeWidgetCommand.php:469-478 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/widgets/src/Commands/MakeWidgetCommand.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakePageCommand.php:451` 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 × 5) packages/panels/src/Auth/Pages/EmailVerification/EmailVerificationPrompt.php:103— packages/panels/src/Auth/Pages/EmailVerification/EmailVerificationPrompt.php:103-112 | packages/panels/src/Auth/Pages/Login.php:218-227 | packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:108-117 | packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php:134-143 | packages/panels/src/Auth/Pages/Register.php:119-128 — before extracting anything, compare `packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php` and `packages/panels/src/Auth/Pages/Register.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) packages/forms/src/Components/ModalTableSelect.php:601— packages/forms/src/Components/ModalTableSelect.php:601-609 | packages/forms/src/Components/Select.php:1358-1366 | packages/forms/src/Components/TableSelect.php:256-264 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:601` 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) packages/panels/src/Commands/FileGenerators/CustomPageClassGenerator.php:63— packages/panels/src/Commands/FileGenerators/CustomPageClassGenerator.php:63-71 | packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:150-158 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:111-119 — 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.
Duplicated block (9 lines × 3) packages/panels/src/Pages/Tenancy/EditTenantProfile.php:168— packages/panels/src/Pages/Tenancy/EditTenantProfile.php:168-176 | packages/panels/src/Resources/Pages/EditRecord.php:254-262 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:112-120 — before extracting anything, compare `packages/panels/src/Pages/Tenancy/EditTenantProfile.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (12 lines × 4) packages/actions/src/Exports/ExportColumn.php:44— packages/actions/src/Exports/ExportColumn.php:44-55 | packages/actions/src/Imports/ImportColumn.php:103-114 | packages/forms/src/Components/Builder/Block.php:33-44 | packages/forms/src/Components/MorphToSelect.php:56-67 — 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.
Duplicated block (12 lines × 4) packages/infolists/src/Components/Entry.php:67— packages/infolists/src/Components/Entry.php:67-78 | packages/query-builder/src/Constraints/Constraint.php:62-73 | packages/tables/src/Columns/Column.php:76-87 | packages/tables/src/Filters/BaseFilter.php:31-42 — 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.
Duplicated block (12 lines × 4) packages/infolists/src/Components/IconEntry.php:195— packages/infolists/src/Components/IconEntry.php:195-206 | packages/infolists/src/Components/IconEntry.php:222-233 | packages/tables/src/Columns/IconColumn.php:223-234 | packages/tables/src/Columns/IconColumn.php:250-261 — before extracting anything, compare `packages/infolists/src/Components/IconEntry.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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.
Sync-over-async blocking bin/fonts.js:72— `fs.readFileSync` in `buildInter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/fonts.js:90— `fs.writeFileSync` in `buildInter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/fonts.js:97— `fs.writeFileSync` in `buildInter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Duplicated block (8 lines × 2 locations) packages/forms/resources/js/components/date-time-picker.js:392— packages/forms/resources/js/components/date-time-picker.js:392 · packages/forms/resources/js/components/date-time-picker.js:404 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) REDACTED:2194— REDACTED:2194 · REDACTED:2225 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) packages/support/resources/js/utilities/select.js:1560— packages/support/resources/js/utilities/select.js:1560 · packages/support/resources/js/utilities/select.js:1569 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Boundary violation [package:third-party-deep-import] packages/forms/resources/js/components/markdown-editor.js:6— packages/forms/resources/js/components/markdown-editor.js:6 imports codemirror/lib/codemirror, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/notifications/resources/js/components/notification.js:1— packages/notifications/resources/js/components/notification.js:1 imports alpinejs/src/utils/once, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] packages/panels/resources/js/echo.js:2— packages/panels/resources/js/echo.js:2 imports pusher-js/dist/web/pusher, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Swallowed exception (caught, then discarded) packages/forms/resources/js/components/rich-editor/extension-local-files.js:305— `catch` 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) packages/support/src/helpers.php:520— `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) packages/upgrade/src/check-compatibility.php:230— `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.
(anonymous) (cyclomatic 21) packages/support/resources/js/partials.js:1— (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 12 function items inside it that branch ((anonymous)::(anonymous)::(anonymous)::updating, a function literal at line 14, (anonymous)::(anonymous)::(anonymous)::key, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 21) packages/panels/resources/js/components/sidebar.js:1— (anonymous) has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function items inside it that branch (handleTab, isHidden, handleEscape, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 34) packages/support/resources/js/components/copyable.js:6— (anonymous) has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 13, other 3, ternaries 2, error handling 1 (nesting depth added 1). None of this is in the body itself: all 34 points belong to 17 function items inside it that branch (copy, updateStandalone, copy::isCurrent, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 34) packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:4— (anonymous) has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 10, ternaries 1 (2 pts) (nesting depth added 3). None of this is in the body itself: all 34 points belong to 17 function items inside it that branch (render::onKeyDown, render::scrollToSelected, render::renderItems, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
richEditorFormComponent::handleToolbarKeydown (cognitive 30) packages/forms/resources/js/components/rich-editor.js:679— richEditorFormComponent::handleToolbarKeydown has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, ternaries 3, loops 1 (2 pts) (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.
richEditorFormComponent::syncToolbarTools (cognitive 18) packages/forms/resources/js/components/rich-editor.js:603— richEditorFormComponent::syncToolbarTools has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (4 pts), boolean chains 3, other 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.
(anonymous)::keydown (cognitive 19) packages/panels/resources/js/components/global-search.js:152— (anonymous)::keydown has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, ternaries 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.
(anonymous)::handleMenuKeydown (cognitive 17) packages/support/resources/js/components/dropdown.js:560— (anonymous)::handleMenuKeydown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, 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.
D4 · Code Duplication· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (8 members, 50+ identical tokens) packages/actions/src/Commands/MakeExporterCommand.php:118— packages/actions/src/Commands/MakeExporterCommand.php:118-159 | packages/actions/src/Commands/MakeImporterCommand.php:125-166 | packages/forms/src/Commands/MakeFormCommand.php:129-171 | packages/forms/src/Commands/MakeLivewireFormCommand.php:160-202 | packages/panels/src/Commands/MakeResourceCommand.php:288-356 | packages/tables/src/Commands/MakeLivewireTableCommand.php:147-182 | packages/tables/src/Commands/MakeTableCommand.php:138-173 | packages/widgets/src/Commands/MakeWidgetCommand.php:487-527 — These 8 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 8 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 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) packages/infolists/src/Components/Concerns/CanFormatState.php:67— packages/infolists/src/Components/Concerns/CanFormatState.php:67-79 | packages/infolists/src/Components/Concerns/CanFormatState.php:95-109 | packages/infolists/src/Components/Concerns/CanFormatState.php:142-152 | packages/infolists/src/Components/Concerns/CanFormatState.php:190-202 | packages/tables/src/Columns/Concerns/CanFormatState.php:67-79 | packages/tables/src/Columns/Concerns/CanFormatState.php:95-109 | packages/tables/src/Columns/Concerns/CanFormatState.php:142-152 | packages/tables/src/Columns/Concerns/CanFormatState.php:190-202 — These 8 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 8 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 8 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) docs-assets/app/app/Livewire/TablesDemo.php:622— docs-assets/app/app/Livewire/TablesDemo.php:622-642 | docs-assets/app/app/Livewire/TablesDemo.php:647-667 | docs-assets/app/app/Livewire/TablesDemo.php:803-824 | docs-assets/app/app/Livewire/TablesDemo.php:829-851 | docs-assets/app/app/Livewire/TablesDemo.php:876-897 | docs-assets/app/app/Livewire/TablesDemo.php:902-924 — 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.
Members sharing a duplicated core (6 members, 50+ identical tokens) packages/forms/src/Components/Builder.php:1237— packages/forms/src/Components/Builder.php:1237-1281 | packages/schemas/src/Components/Concerns/HasContainerGridLayout.php:44-88 | packages/schemas/src/Concerns/HasColumns.php:64-108 | packages/support/src/Concerns/CanOrderColumns.php:44-88 | packages/support/src/Concerns/CanSpanColumns.php:82-126 | packages/support/src/Concerns/CanSpanColumns.php:134-178 — 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.
Duplicated block (42 lines × 2) packages/infolists/src/Components/TextEntry.php:222— packages/infolists/src/Components/TextEntry.php:222-263 | packages/tables/src/Columns/TextColumn.php:331-372 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (42 lines × 2) packages/schemas/src/Components/Concerns/CanGetStateFromRelationships.php:99— packages/schemas/src/Components/Concerns/CanGetStateFromRelationships.php:99-140 | packages/support/src/Concerns/HasCellState.php:359-400 — 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 (31 lines × 2) packages/forms/src/Components/MorphToSelect/Type.php:112— packages/forms/src/Components/MorphToSelect/Type.php:112-142 | packages/forms/src/Components/MorphToSelect/Type.php:162-192 — 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 `packages/forms/src/Components/MorphToSelect/Type.php:112` 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 (31 lines × 2) packages/infolists/src/Components/ImageEntry.php:226— packages/infolists/src/Components/ImageEntry.php:226-256 | packages/tables/src/Columns/ImageColumn.php:220-250 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 3) packages/forms/src/Components/ModalTableSelect.php:624— packages/forms/src/Components/ModalTableSelect.php:624-652 | packages/forms/src/Components/Select.php:1381-1409 | packages/forms/src/Components/TableSelect.php:272-300 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:624` 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 (29 lines × 3) packages/tables/src/Columns/ColorColumn.php:38— packages/tables/src/Columns/ColorColumn.php:38-66 | packages/tables/src/Columns/IconColumn.php:300-328 | packages/tables/src/Columns/ImageColumn.php:488-516 — before extracting anything, compare `packages/tables/src/Columns/ColorColumn.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 133 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/tables/src/Columns/IconColumn.php:332` calls `isListWithLineBreaks` and `packages/tables/src/Columns/ColorColumn.php:70` 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 (29 lines × 2) packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:105— packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php:105-133 | packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php:103-131 — before extracting anything, compare `packages/spatie-laravel-media-library-plugin/src/Infolists/Components/SpatieMediaLibraryImageEntry.php` and `packages/spatie-laravel-media-library-plugin/src/Tables/Columns/SpatieMediaLibraryImageColumn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) packages/actions/src/Action.php:184— packages/actions/src/Action.php:184-216 | packages/actions/src/ActionGroup.php:309-337 — 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 (28 lines × 2) packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:21— packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:21-48 | packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:93-120 — 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 `packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:21` 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 (28 lines × 2) packages/support/src/SupportServiceProvider.php:223— packages/support/src/SupportServiceProvider.php:223-250 | packages/support/src/View/ComponentAttributeBag.php:76-103 — 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 (26 lines × 2) packages/infolists/src/Components/TextEntry.php:573— packages/infolists/src/Components/TextEntry.php:573-598 | packages/tables/src/Columns/TextColumn.php:679-704 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) packages/spatie-laravel-tags-plugin/src/Infolists/Components/SpatieTagsEntry.php:45— packages/spatie-laravel-tags-plugin/src/Infolists/Components/SpatieTagsEntry.php:45-70 | packages/spatie-laravel-tags-plugin/src/Tables/Columns/SpatieTagsColumn.php:44-69 — 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 (24 lines × 4) packages/infolists/src/Components/Concerns/HasColor.php:33— packages/infolists/src/Components/Concerns/HasColor.php:33-56 | packages/infolists/src/Components/Concerns/HasIcon.php:32-55 | packages/tables/src/Columns/Concerns/HasColor.php:33-56 | packages/tables/src/Columns/Concerns/HasIcon.php:32-55 — before extracting anything, compare `packages/infolists/src/Components/Concerns/HasColor.php` and `packages/tables/src/Columns/Concerns/HasColor.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 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/HasColor.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.
Duplicated block (24 lines × 4) packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:268— packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php:268-291 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceFormSchemaClassGenerator.php:72-95 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceInfolistSchemaClassGenerator.php:71-94 | packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceTableClassGenerator.php:77-100 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceFormSchemaClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceInfolistSchemaClassGenerator.php` as WHOLE FILES: 87% 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceInfolistSchemaClassGenerator.php:67` calls `configureConfigureMethod` and `packages/panels/src/Commands/FileGenerators/Resources/Schemas/ResourceFormSchemaClassGenerator.php:68` 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 (20–21 lines × 2) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:138— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:138-158 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:96-115 — 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 `packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:96` 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 (20–21 lines × 2) packages/schemas/src/Components/Tabs.php:442— packages/schemas/src/Components/Tabs.php:442-462 | packages/schemas/src/Components/Tabs.php:791-810 — 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 `packages/schemas/src/Components/Tabs.php:442` 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 (18 lines × 3) packages/forms/src/Components/ModalTableSelect.php:798— packages/forms/src/Components/ModalTableSelect.php:798-815 | packages/forms/src/Components/Select.php:1699-1716 | packages/tables/src/Columns/SelectColumn.php:902-919 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 (18 lines × 3) packages/forms/src/Components/Builder.php:1212— packages/forms/src/Components/Builder.php:1212-1229 | packages/schemas/src/Components/Concerns/HasContainerGridLayout.php:19-36 | packages/schemas/src/Concerns/HasColumns.php:20-37 — 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.
Duplicated block (17–18 lines × 2) packages/forms/src/Components/Concerns/CanBeValidated.php:172— packages/forms/src/Components/Concerns/CanBeValidated.php:172-189 | packages/forms/src/Components/Concerns/CanBeValidated.php:211-227 — 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 `packages/forms/src/Components/Concerns/CanBeValidated.php:172` 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. 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 (17–18 lines × 2) packages/infolists/src/Components/IconEntry.php:307— packages/infolists/src/Components/IconEntry.php:307-324 | packages/tables/src/Columns/IconColumn.php:330-346 — before extracting anything, compare `packages/infolists/src/Components/IconEntry.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 115 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/IconEntry.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 (17 lines × 3) packages/forms/src/Components/ModalTableSelect.php:257— packages/forms/src/Components/ModalTableSelect.php:257-273 | packages/forms/src/Components/Select.php:820-836 | packages/tables/src/Filters/SelectFilter.php:453-469 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 (17 lines × 3) packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264— packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264-280 | packages/tables/src/Grouping/Group.php:446-462 | packages/tables/src/Table/Concerns/CanSearchRecords.php:257-273 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264` 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 (15 lines × 4) packages/forms/src/Components/Concerns/CanBeValidated.php:99— packages/forms/src/Components/Concerns/CanBeValidated.php:99-113 | packages/forms/src/Components/Concerns/CanBeValidated.php:121-135 | packages/forms/src/Components/Concerns/CanBeValidated.php:143-157 | packages/forms/src/Components/Concerns/CanBeValidated.php:443-457 — 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.
Duplicated block (15 lines × 4) packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264— packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264-278 | packages/schemas/src/Components/Concerns/CanGetStateFromRelationships.php:39-53 | packages/tables/src/Grouping/Group.php:446-460 | packages/tables/src/Table/Concerns/CanSearchRecords.php:257-271 — 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 `packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:264` 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 (14 lines × 4) packages/forms/src/Commands/MakeFormCommand.php:129— packages/forms/src/Commands/MakeFormCommand.php:129-142 | packages/forms/src/Commands/MakeLivewireFormCommand.php:160-173 | packages/tables/src/Commands/MakeLivewireTableCommand.php:147-160 | packages/tables/src/Commands/MakeTableCommand.php:138-151 — before extracting anything, compare `packages/forms/src/Commands/MakeFormCommand.php` and `packages/forms/src/Commands/MakeLivewireFormCommand.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 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 (14 lines × 4) packages/schemas/src/Testing/TestsSchemas.php:267— packages/schemas/src/Testing/TestsSchemas.php:267-280 | packages/schemas/src/Testing/TestsSchemas.php:294-307 | packages/schemas/src/Testing/TestsSchemas.php:347-360 | packages/schemas/src/Testing/TestsSchemas.php:371-384 — 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.
Duplicated block (13–14 lines × 2) packages/actions/src/Action.php:828— packages/actions/src/Action.php:828-841 | packages/actions/src/Action.php:937-949 — 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, `packages/actions/src/Action.php:825` calls `hasLabeledFromBreakpoint`, `hasOutlined`, `hasLabelHidden` and `packages/actions/src/Action.php:936` 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 (13–14 lines × 2) packages/infolists/src/Components/ColorEntry.php:66— packages/infolists/src/Components/ColorEntry.php:66-79 | packages/tables/src/Columns/ColorColumn.php:68-80 — before extracting anything, compare `packages/infolists/src/Components/ColorEntry.php` and `packages/tables/src/Columns/ColorColumn.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/ColorEntry.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/infolists/src/Components/ColorEntry.php:64` calls `getAlignment` and `packages/tables/src/Columns/ColorColumn.php:66` 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.
Duplicated block (13 lines × 4) packages/forms/src/Commands/MakeFieldCommand.php:135— packages/forms/src/Commands/MakeFieldCommand.php:135-147 | packages/infolists/src/Commands/MakeEntryCommand.php:135-147 | packages/schemas/src/Commands/MakeComponentCommand.php:151-163 | packages/tables/src/Commands/MakeColumnCommand.php:152-164 — before extracting anything, compare `packages/forms/src/Commands/MakeFieldCommand.php` and `packages/infolists/src/Commands/MakeEntryCommand.php` as WHOLE FILES: this scan already matched 5 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) packages/infolists/src/Components/IconEntry.php:360— packages/infolists/src/Components/IconEntry.php:360-372 | packages/infolists/src/Components/ImageEntry.php:577-589 | packages/tables/src/Columns/IconColumn.php:378-390 | packages/tables/src/Columns/ImageColumn.php:571-583 — 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 `packages/infolists/src/Components/IconEntry.php:360` 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 × 3) packages/support/src/View/Concerns/CanGenerateButtonHtml.php:63— packages/support/src/View/Concerns/CanGenerateButtonHtml.php:63-75 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:54-66 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:63-75 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` and `packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 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 `packages/support/src/View/Concerns/CanGenerateButtonHtml.php:63` 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 (13 lines × 3) packages/panels/src/Resources/Pages/CreateRecord.php:401— packages/panels/src/Resources/Pages/CreateRecord.php:401-413 | packages/panels/src/Resources/Pages/EditRecord.php:448-460 | packages/spatie-laravel-settings-plugin/src/Pages/SettingsPage.php:204-216 — before extracting anything, compare `packages/panels/src/Resources/Pages/CreateRecord.php` and `packages/panels/src/Resources/Pages/EditRecord.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (10 lines × 4) packages/infolists/src/Components/Concerns/CanFormatState.php:128— packages/infolists/src/Components/Concerns/CanFormatState.php:128-137 | packages/infolists/src/Components/Concerns/CanFormatState.php:176-185 | packages/tables/src/Columns/Concerns/CanFormatState.php:128-137 | packages/tables/src/Columns/Concerns/CanFormatState.php:176-185 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/CanFormatState.php:128` 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 (10 lines × 4) packages/tables/src/Testing/TestsActions.php:112— packages/tables/src/Testing/TestsActions.php:112-121 | packages/tables/src/Testing/TestsActions.php:126-135 | packages/tables/src/Testing/TestsActions.php:140-149 | packages/tables/src/Testing/TestsBulkActions.php:126-135 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 3) packages/forms/src/Components/ColorPicker.php:90— packages/forms/src/Components/ColorPicker.php:90-99 | packages/forms/src/Components/DateTimePicker.php:148-157 | packages/forms/src/Components/Select.php:1899-1908 — 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 (10 lines × 3) packages/forms/src/Components/MorphToSelect/Type.php:154— packages/forms/src/Components/MorphToSelect/Type.php:154-163 | packages/forms/src/Components/Select.php:1104-1113 | packages/forms/src/Components/Select.php:1146-1155 — 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 `packages/forms/src/Components/MorphToSelect/Type.php:154` 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 (9 lines × 4) packages/forms/src/Components/ColorPicker.php:76— packages/forms/src/Components/ColorPicker.php:76-84 | packages/forms/src/Components/DateTimePicker.php:117-125 | packages/forms/src/Components/Select.php:1885-1893 | packages/forms/src/Components/TextInput.php:337-345 — 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 4 call sites, so a change lands once.
Duplicated block (9 lines × 4) packages/actions/src/ActionGroup.php:276— packages/actions/src/ActionGroup.php:276-284 | packages/actions/src/Concerns/CanBeAuthorized.php:88-96 | packages/actions/src/Concerns/CanBeAuthorized.php:221-229 | packages/actions/src/Concerns/CanBeHidden.php:63-71 — 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 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 × 4) packages/actions/src/Action.php:1029— packages/actions/src/Action.php:1029-1033 | packages/actions/src/Action.php:1066-1070 | packages/actions/src/Action.php:1140-1144 | packages/actions/src/Action.php:1176-1180 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/actions/src/Action.php:1064` calls `getBadge`, `getBadgeColor` and `packages/actions/src/Action.php:1028` 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.
Duplicated block (5 lines × 4) packages/forms/src/Components/Builder.php:1677— packages/forms/src/Components/Builder.php:1677-1681 | packages/forms/src/Components/Repeater.php:1583-1587 | packages/forms/src/Components/Repeater.php:1821-1825 | packages/forms/src/Components/Repeater.php:1964-1968 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Builder.php:1685` calls `isCollapsible` and `packages/forms/src/Components/Repeater.php:1829` 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 (19 lines × 2 locations) packages/forms/resources/js/components/rich-editor/extension-custom-block.js:55— packages/forms/resources/js/components/rich-editor/extension-custom-block.js:55 · packages/forms/resources/js/components/rich-editor/extension-custom-block.js:90 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) packages/support/resources/js/utilities/select.js:1872— packages/support/resources/js/utilities/select.js:1872 · packages/support/resources/js/utilities/select.js:1892 — 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 locations) packages/forms/resources/js/components/markdown-editor.js:47— packages/forms/resources/js/components/markdown-editor.js:47 · packages/forms/resources/js/components/markdown-editor.js:68 — 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 locations) packages/forms/resources/js/components/rich-editor/extension-custom-block.js:176— packages/forms/resources/js/components/rich-editor/extension-custom-block.js:176 · packages/forms/resources/js/components/rich-editor/extension-image.js:9 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (9 matched lines × 2 locations) · ×2
Duplicated block with local edits (9 matched lines × 2 locations) packages/schemas/resources/js/index.js:260— packages/schemas/resources/js/index.js:260 · packages/support/resources/js/partials.js:12 — the two spans are one implementation copied and then locally edited — 63 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (9 matched lines × 2 locations) packages/tables/resources/js/components/column-manager.js:410— packages/tables/resources/js/components/column-manager.js:410 · packages/tables/resources/js/components/table.js:802 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
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 110 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.
dropdown.default (cyclomatic 106) packages/support/resources/js/components/dropdown.js:21— dropdown.default has cyclomatic complexity 106 (threshold 15). Of this number, 101 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
(anonymous) (cyclomatic 84) packages/tables/resources/js/components/table.js:3— (anonymous) has cyclomatic complexity 84 (threshold 15). Most of this is not in the body itself: 2 of the 84 points are its own statements and the rest belongs to 63 function items inside it that branch (finishTableReorder, handleCheckboxClick, a function literal at line 246, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
table.default (cyclomatic 79) packages/tables/resources/js/components/table.js:3— table.default has cyclomatic complexity 79 (threshold 15). Of this number, 62 points are the body's own statements and 17 belong to 9 function items inside it that branch. 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.
TextEntry.toEmbeddedHtml (cyclomatic 72) packages/infolists/src/Components/TextEntry.php:177— TextEntry.toEmbeddedHtml has cyclomatic complexity 72 (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.
EasyMDE.EasyMDE.render (cyclomatic 72) REDACTED:2346— EasyMDE.EasyMDE.render has cyclomatic complexity 72 (threshold 15). Of this number, 38 points are the body's own statements and 34 belong to 14 function items inside it that branch. 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.
TextColumn.toEmbeddedHtml (cyclomatic 69) packages/tables/src/Columns/TextColumn.php:274— TextColumn.toEmbeddedHtml has cyclomatic complexity 69 (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.
global-search.default (cyclomatic 68) packages/panels/resources/js/components/global-search.js:1— global-search.default has cyclomatic complexity 68 (threshold 15). Of this number, 49 points are the body's own statements and 19 belong to 10 function literals inside it that branch. 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.
Tabs.toEmbeddedHtml (cyclomatic 66) packages/schemas/src/Components/Tabs.php:284— Tabs.toEmbeddedHtml has cyclomatic complexity 66 (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.
Builder.toEmbeddedHtml (cyclomatic 65) packages/forms/src/Components/Builder.php:1653— Builder.toEmbeddedHtml has cyclomatic complexity 65 (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.
CanGenerateButtonHtml.generateButtonHtml (cyclomatic 64) packages/support/src/View/Concerns/CanGenerateButtonHtml.php:29— CanGenerateButtonHtml.generateButtonHtml has cyclomatic complexity 64 (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.
file-upload.fileUploadFormComponent.init (cyclomatic 64) packages/forms/resources/js/components/file-upload.js:130— file-upload.fileUploadFormComponent.init has cyclomatic complexity 64 (threshold 15). Of this number, 18 points are the body's own statements and 46 belong to 16 function items inside it that branch. 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.
EasyMDE.toggleCodeBlock (cyclomatic 64) REDACTED:501— EasyMDE.toggleCodeBlock has cyclomatic complexity 64 (threshold 15). Of this number, 42 points are the body's own statements and 22 belong to 6 function items inside it that branch. 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.
(anonymous) (cyclomatic 61) packages/forms/resources/js/components/rich-editor/mention-suggestion.js:4— (anonymous) has cyclomatic complexity 61 (threshold 15). Most of this is not in the body itself: 1 of the 61 points is its own statement and the rest belongs to 18 function items inside it that branch (items, render::renderItems, render::enterHandler, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Repeater.toEmbeddedHtml (cyclomatic 56) packages/forms/src/Components/Repeater.php:1565— Repeater.toEmbeddedHtml has cyclomatic complexity 56 (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.
reordering.reordering.init (cyclomatic 56) packages/forms/resources/js/utilities/reordering.js:23— reordering.reordering.init has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 15 of the 56 points are its own statements and the rest belongs to 14 function literals inside it that branch (lines 44, 94, 166, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EasyMDE.EasyMDE (cyclomatic 55) REDACTED:1933— EasyMDE.EasyMDE has cyclomatic complexity 55 (threshold 15). Of this number, 53 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
rich-editor.richEditorFormComponent.init (cyclomatic 54) packages/forms/resources/js/components/rich-editor.js:88— rich-editor.richEditorFormComponent.init has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 11 of the 54 points are its own statements and the rest belongs to 18 function items inside it that branch (updateModalMeasurements, a function literal at line 232, a function literal at line 318, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Field.wrapEmbeddedHtml (cyclomatic 52) packages/forms/src/Components/Field.php:344— Field.wrapEmbeddedHtml has cyclomatic complexity 52 (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.
Section.toEmbeddedHtml (cyclomatic 51) packages/schemas/src/Components/Section.php:264— Section.toEmbeddedHtml has cyclomatic complexity 51 (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.
CanGenerateLinkHtml.generateLinkHtml (cyclomatic 51) packages/support/src/View/Concerns/CanGenerateLinkHtml.php:30— CanGenerateLinkHtml.generateLinkHtml has cyclomatic complexity 51 (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.
Repeater.toTableEmbeddedHtml (cyclomatic 48) packages/forms/src/Components/Repeater.php:1957— Repeater.toTableEmbeddedHtml has cyclomatic complexity 48 (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.
FusedGroup.toEmbeddedHtml (cyclomatic 48) packages/schemas/src/Components/FusedGroup.php:221— FusedGroup.toEmbeddedHtml has cyclomatic complexity 48 (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.
CanGenerateIconButtonHtml.generateIconButtonHtml (cyclomatic 48) packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:28— CanGenerateIconButtonHtml.generateIconButtonHtml has cyclomatic complexity 48 (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.
Field.wrapInputHtml (cyclomatic 47) packages/forms/src/Components/Field.php:580— Field.wrapInputHtml has cyclomatic complexity 47 (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.
modals.default (cyclomatic 45) packages/actions/resources/js/components/modals.js:1— modals.default has cyclomatic complexity 45 (threshold 15). Of this number, 35 points are the body's own statements and 10 belong to 6 function literals inside it that branch. 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.
CanGenerateModelForms.getFormComponents (cyclomatic 44) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:46— CanGenerateModelForms.getFormComponents has cyclomatic complexity 44 (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.
SettingsPageClassGenerator.getFormComponents (cyclomatic 44) packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:149— SettingsPageClassGenerator.getFormComponents has cyclomatic complexity 44 (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.
markdownEditorFormComponent (cyclomatic 44) packages/forms/resources/js/components/markdown-editor.js:90— markdownEditorFormComponent has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 1 of the 44 points is its own statement and the rest belongs to 31 function items inside it that branch (getToolbarButton, init, a function literal at line 182, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
editableTableColumn (cyclomatic 42) packages/tables/resources/js/utilities/editable-table-column.js:1— editableTableColumn has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 1 of the 42 points is its own statement and the rest belongs to 18 function items inside it that branch (a function literal at line 70, getAccessibilityAttributes, a function literal at line 47, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DateTimePicker.toEmbeddedHtml (cyclomatic 41) packages/forms/src/Components/DateTimePicker.php:101— DateTimePicker.toEmbeddedHtml has cyclomatic complexity 41 (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.
CanGenerateBadgeHtml.generateBadgeHtml (cyclomatic 41) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:27— CanGenerateBadgeHtml.generateBadgeHtml has cyclomatic complexity 41 (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.
renderOptions (cyclomatic 40) packages/support/resources/js/utilities/select.js:306— renderOptions has cyclomatic complexity 40 (threshold 15). Of this number, 37 points are the body's own statements and 3 belong to 5 function literals inside it that branch. 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.
tabsSchemaComponent.update (cyclomatic 39) packages/schemas/resources/js/components/tabs.js:617— tabsSchemaComponent.update has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 15 of the 39 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 659, 654). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
tabs.tabsSchemaComponent.update (cyclomatic 37) packages/schemas/resources/js/components/tabs.js:617— tabs.tabsSchemaComponent.update has cyclomatic complexity 37 (threshold 15). Of this number, 17 points are the body's own statements and 20 belong to one function literal inside it that branches. 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.
EmailAuthentication.verifyCode (cyclomatic 36) packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php:164— EmailAuthentication.verifyCode has cyclomatic complexity 36 (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.
MakePageCommand.createResourceManageRelatedRecordsPage (cyclomatic 36) packages/panels/src/Commands/MakePageCommand.php:513— MakePageCommand.createResourceManageRelatedRecordsPage has cyclomatic complexity 36 (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.
SupportServiceProvider.packageBooted (cyclomatic 36) packages/support/src/SupportServiceProvider.php:166— SupportServiceProvider.packageBooted has cyclomatic complexity 36 (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.
Builder.generateBlockPickerHtml (cyclomatic 35) packages/forms/src/Components/Builder.php:1432— Builder.generateBlockPickerHtml has cyclomatic complexity 35 (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.
RichEditor.toEmbeddedHtml (cyclomatic 34) packages/forms/src/Components/RichEditor.php:1693— RichEditor.toEmbeddedHtml has cyclomatic complexity 34 (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.
ToggleButtons.toEmbeddedHtml (cyclomatic 34) packages/forms/src/Components/ToggleButtons.php:93— ToggleButtons.toEmbeddedHtml has cyclomatic complexity 34 (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.
CanGenerateModelTables.getTableColumns (cyclomatic 34) packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:51— CanGenerateModelTables.getTableColumns has cyclomatic complexity 34 (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.
date-time-picker.dateTimePickerFormComponent.init (cyclomatic 34) packages/forms/resources/js/components/date-time-picker.js:88— date-time-picker.dateTimePickerFormComponent.init has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 3 of the 34 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 260, 148, 172, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
(anonymous) (cyclomatic 34) packages/support/resources/js/components/copyable.js:6— (anonymous) has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 17 function items inside it that branch (updateStandalone, copy, copy::isCurrent, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LocalFilesPlugin (cyclomatic 34) packages/forms/resources/js/components/rich-editor/extension-local-files.js:43— LocalFilesPlugin has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to 22 function items inside it that branch (a function literal at line 277, handlePaste, startUpload::finish, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanExportRecords.setUp (cyclomatic 33) packages/actions/src/Concerns/CanExportRecords.php:77— CanExportRecords.setUp has cyclomatic complexity 33 (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.
EntanglesStateWithSingularRelationship.relationship (cyclomatic 33) packages/schemas/src/Components/Concerns/EntanglesStateWithSingularRelationship.php:33— EntanglesStateWithSingularRelationship.relationship has cyclomatic complexity 33 (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.
merge-tag-suggestion.default (cyclomatic 32) packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:4— merge-tag-suggestion.default has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 11 function literals inside it that branch (lines 74, 152, 34, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
(anonymous) (cyclomatic 32) packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:4— (anonymous) has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 17 function items inside it that branch (render::scrollToSelected, render::onKeyDown, render::renderItems, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
onBeforeCreate (cyclomatic 32) packages/forms/resources/js/components/rich-editor/extension-mention.js:324— onBeforeCreate has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 8 function items inside it that branch ((anonymous)::items, a function literal at line 344, toItemsArray, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TextInput.toEmbeddedHtml (cyclomatic 31) packages/forms/src/Components/TextInput.php:327— TextInput.toEmbeddedHtml has cyclomatic complexity 31 (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.
CanGenerateModelInfolists.getInfolistComponents (cyclomatic 31) packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:32— CanGenerateModelInfolists.getInfolistComponents has cyclomatic complexity 31 (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.
CanGenerateDropdownItemHtml.generateDropdownItemHtml (cyclomatic 31) packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:28— CanGenerateDropdownItemHtml.generateDropdownItemHtml has cyclomatic complexity 31 (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.
InteractsWithTable.bootedInteractsWithTable (cyclomatic 31) packages/tables/src/Concerns/InteractsWithTable.php:49— InteractsWithTable.bootedInteractsWithTable has cyclomatic complexity 31 (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.
rich-editor.richEditorFormComponent.handleToolbarKeydown (cyclomatic 31) packages/forms/resources/js/components/rich-editor.js:679— rich-editor.richEditorFormComponent.handleToolbarKeydown has cyclomatic complexity 31 (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.
Select.openDropdown (cyclomatic 31) packages/support/resources/js/utilities/select.js:1369— Select.openDropdown has cyclomatic complexity 31 (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.
copyable.default (cyclomatic 31) packages/support/resources/js/components/copyable.js:6— copyable.default has cyclomatic complexity 31 (threshold 15). Of this number, 24 points are the body's own statements and 7 belong to 3 function items inside it that branch. 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.
richEditorFormComponent::handleToolbarKeydown (cyclomatic 31) packages/forms/resources/js/components/rich-editor.js:679— richEditorFormComponent::handleToolbarKeydown has cyclomatic complexity 31 (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.
Select.getOptionsFromRelationship (cyclomatic 30) packages/forms/src/Components/Select.php:1071— Select.getOptionsFromRelationship has cyclomatic complexity 30 (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.
ToggleButtons.toGroupedEmbeddedHtml (cyclomatic 30) packages/forms/src/Components/ToggleButtons.php:226— ToggleButtons.toGroupedEmbeddedHtml has cyclomatic complexity 30 (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.
Tabs.toEmbeddedHtmlForLivewireProperty (cyclomatic 30) packages/schemas/src/Components/Tabs.php:653— Tabs.toEmbeddedHtmlForLivewireProperty has cyclomatic complexity 30 (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.
handleDropdownKeydown (cyclomatic 30) packages/support/resources/js/utilities/select.js:1262— handleDropdownKeydown has cyclomatic complexity 30 (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.
Repeater.toSimpleEmbeddedHtml (cyclomatic 29) packages/forms/src/Components/Repeater.php:1814— Repeater.toSimpleEmbeddedHtml 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.
EasyMDE.EasyMDE.createToolbar (cyclomatic 28) REDACTED:3107— EasyMDE.EasyMDE.createToolbar has cyclomatic complexity 28 (threshold 15). Of this number, 20 points are the body's own statements and 8 belong to 3 function literals inside it that branch. 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.
tabs.tabsSchemaComponent.positionOverflow (cyclomatic 28) packages/schemas/resources/js/components/tabs.js:449— tabs.tabsSchemaComponent.positionOverflow has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 2 function literals inside it that branch. 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.
tabsSchemaComponent.positionOverflow (cyclomatic 28) packages/schemas/resources/js/components/tabs.js:449— tabsSchemaComponent.positionOverflow has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 4 function items inside it that branch. 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.
Action.canRenderOptimizedLink (cyclomatic 27) packages/actions/src/Action.php:816— Action.canRenderOptimizedLink has cyclomatic complexity 27 (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.
Entry.wrapEmbeddedHtml (cyclomatic 27) packages/infolists/src/Components/Entry.php:255— Entry.wrapEmbeddedHtml has cyclomatic complexity 27 (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.
Select.getLabelsForMultipleSelection (cyclomatic 27) packages/support/resources/js/utilities/select.js:684— Select.getLabelsForMultipleSelection has cyclomatic complexity 27 (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.
tableFilters (cyclomatic 27) packages/tables/resources/js/components/table.js:695— tableFilters has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 13 function items inside it that branch (handleActionClick, a function literal at line 769, a function literal at line 822, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 27) packages/support/resources/js/components/one-time-code.js:1— (anonymous) has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 1 of the 27 points is its own statement and the rest belongs to 17 function items inside it that branch (a function literal at line 152, a function literal at line 61, submitIfComplete, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Select.relationship (cyclomatic 26) packages/forms/src/Components/Select.php:798— Select.relationship has cyclomatic complexity 26 (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.
CodeEntry.toEmbeddedHtml (cyclomatic 26) packages/infolists/src/Components/CodeEntry.php:76— CodeEntry.toEmbeddedHtml 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.
ImageEntry.toEmbeddedHtml (cyclomatic 26) packages/infolists/src/Components/ImageEntry.php:468— ImageEntry.toEmbeddedHtml 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.
HasComponents.registerLivewireComponents (cyclomatic 26) packages/panels/src/Panel/Concerns/HasComponents.php:575— HasComponents.registerLivewireComponents has cyclomatic complexity 26 (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.
CanFormatState.formatState (cyclomatic 26) packages/tables/src/Columns/Concerns/CanFormatState.php:378— CanFormatState.formatState 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.
ImageColumn.toEmbeddedHtml (cyclomatic 26) packages/tables/src/Columns/ImageColumn.php:461— ImageColumn.toEmbeddedHtml 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.
modal.default (cyclomatic 26) packages/support/resources/js/components/modal.js:49— modal.default has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 222, a function literal at line 235, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 26) packages/support/resources/js/components/modal.js:49— (anonymous) has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 20 function items inside it that branch (a function literal at line 222, setUpTextSelectionClosePrevention::textSelectionClosePreventionMouseUpHandler, a function literal at line 235, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Select.toEmbeddedHtml (cyclomatic 25) packages/forms/src/Components/Select.php:1867— Select.toEmbeddedHtml has cyclomatic complexity 25 (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.
HasComponents.getAction (cyclomatic 25) packages/schemas/src/Concerns/HasComponents.php:86— HasComponents.getAction has cyclomatic complexity 25 (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.
EasyMDE.createToolbarButton (cyclomatic 25) REDACTED:218— EasyMDE.createToolbarButton 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.
AssociateAction.getRecordSelect (cyclomatic 24) packages/actions/src/AssociateAction.php:217— AssociateAction.getRecordSelect has cyclomatic complexity 24 (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.
AttachAction.getRecordSelect (cyclomatic 24) packages/actions/src/AttachAction.php:218— AttachAction.getRecordSelect has cyclomatic complexity 24 (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.
CanFormatState.formatState (cyclomatic 24) packages/infolists/src/Components/Concerns/CanFormatState.php:378— CanFormatState.formatState has cyclomatic complexity 24 (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.
CanSortRecords.applySortingToTableQuery (cyclomatic 24) packages/tables/src/Concerns/CanSortRecords.php:79— CanSortRecords.applySortingToTableQuery has cyclomatic complexity 24 (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.
one-time-code.default (cyclomatic 24) packages/support/resources/js/components/one-time-code.js:1— one-time-code.default has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 152, 61, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PrepareCsvExport.handle (cyclomatic 23) packages/actions/src/Exports/Jobs/PrepareCsvExport.php:58— PrepareCsvExport.handle 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.
NavigationManager.get (cyclomatic 23) packages/panels/src/Navigation/NavigationManager.php:48— NavigationManager.get has cyclomatic complexity 23 (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.
InteractsWithRelationshipTable.makeTable (cyclomatic 23) packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:110— InteractsWithRelationshipTable.makeTable 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.
TextInputColumn.toEmbeddedHtml (cyclomatic 23) packages/tables/src/Columns/TextInputColumn.php:204— TextInputColumn.toEmbeddedHtml 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.
SelectFilter.setUp (cyclomatic 23) packages/tables/src/Filters/SelectFilter.php:45— SelectFilter.setUp 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.
reordering.reordering.reconcile (cyclomatic 23) packages/forms/resources/js/utilities/reordering.js:300— reordering.reordering.reconcile has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 3 function literals inside it that branch. 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.
rich-editor.richEditorFormComponent.mountToolAction (cyclomatic 23) packages/forms/resources/js/components/rich-editor.js:827— rich-editor.richEditorFormComponent.mountToolAction has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 872, 861, 878, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
editable-table-column.editableTableColumn.initEditableColumn (cyclomatic 23) packages/tables/resources/js/utilities/editable-table-column.js:31— editable-table-column.editableTableColumn.initEditableColumn has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 70, 47, 34, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TranslationFileLineParser.parse (cyclomatic 22) bin/TranslationTool/src/DataObjects/TranslationFileLineParser.php:12— TranslationFileLineParser.parse has cyclomatic complexity 22 (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.
InteractsWithActions.callMountedAction (cyclomatic 22) packages/actions/src/Concerns/InteractsWithActions.php:361— InteractsWithActions.callMountedAction 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.
Type.setUp (cyclomatic 22) packages/forms/src/Components/MorphToSelect/Type.php:69— Type.setUp 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.
IconEntry.toEmbeddedHtml (cyclomatic 22) packages/infolists/src/Components/IconEntry.php:262— IconEntry.toEmbeddedHtml 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.
RelationManager.getDefaultActionAuthorizationResponse (cyclomatic 22) packages/panels/src/Resources/RelationManagers/RelationManager.php:346— RelationManager.getDefaultActionAuthorizationResponse 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.
Icon.toEmbeddedHtml (cyclomatic 22) packages/schemas/src/Components/Icon.php:78— Icon.toEmbeddedHtml 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.
Text.toEmbeddedHtml (cyclomatic 22) packages/schemas/src/Components/Text.php:123— Text.toEmbeddedHtml has cyclomatic complexity 22 (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.
Select.handleSearch (cyclomatic 22) packages/support/resources/js/utilities/select.js:1730— Select.handleSearch has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
tabs.tabsSchemaComponent.init (cyclomatic 22) packages/schemas/resources/js/components/tabs.js:52— tabs.tabsSchemaComponent.init has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 75, 160, 153, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
tabsSchemaComponent.init (cyclomatic 22) packages/schemas/resources/js/components/tabs.js:52— tabsSchemaComponent.init has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (boundFocusHandler, boundResetHandler, a function literal at line 89, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FileUpload.toEmbeddedHtml (cyclomatic 21) packages/forms/src/Components/FileUpload.php:842— FileUpload.toEmbeddedHtml has cyclomatic complexity 21 (threshold 15). 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.
KeyValue.toEmbeddedHtml (cyclomatic 21) packages/forms/src/Components/KeyValue.php:376— KeyValue.toEmbeddedHtml has cyclomatic complexity 21 (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.
Select.fillStateFromRelationship (cyclomatic 21) packages/forms/src/Components/Select.php:1188— Select.fillStateFromRelationship has cyclomatic complexity 21 (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.
ColorEntry.toEmbeddedHtml (cyclomatic 21) packages/infolists/src/Components/ColorEntry.php:21— ColorEntry.toEmbeddedHtml has cyclomatic complexity 21 (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.
setUpEventListeners (cyclomatic 21) packages/support/resources/js/utilities/select.js:1059— setUpEventListeners has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 9 function items inside it that branch (refreshOptionLabelListener, a function literal at line 1093, documentClickListener, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InteractsWithActions.mountDefaultActions (cyclomatic 20) packages/actions/src/Concerns/InteractsWithActions.php:136— InteractsWithActions.mountDefaultActions 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.
HasComponents.getComponent (cyclomatic 20) packages/schemas/src/Concerns/HasComponents.php:172— HasComponents.getComponent 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.
CanReadModelSchemas.parseDefaultExpression (cyclomatic 20) packages/support/src/Commands/Concerns/CanReadModelSchemas.php:207— CanReadModelSchemas.parseDefaultExpression 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. This is NOT this file's highest cyclomatic complexity: CanReadModelSchemas.parseColumnType (cyclomatic 23) 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.
ColorColumn.toEmbeddedHtml (cyclomatic 20) packages/tables/src/Columns/ColorColumn.php:21— ColorColumn.toEmbeddedHtml 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.
IconColumn.toEmbeddedHtml (cyclomatic 20) packages/tables/src/Columns/IconColumn.php:283— IconColumn.toEmbeddedHtml has cyclomatic complexity 20 (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.
CanSummarizeRecords.getTableSummarySelectedState (cyclomatic 20) packages/tables/src/Concerns/CanSummarizeRecords.php:85— CanSummarizeRecords.getTableSummarySelectedState 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.
HasRecords.getTableRecords (cyclomatic 20) packages/tables/src/Concerns/HasRecords.php:96— HasRecords.getTableRecords 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.
EasyMDE.EasyMDE.uploadImage (cyclomatic 20) REDACTED:2849— EasyMDE.EasyMDE.uploadImage has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 2919, onErrorSup, a function literal at line 2898). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
sidebar.default (cyclomatic 20) packages/panels/resources/js/stores/sidebar.js:1— sidebar.default has cyclomatic complexity 20 (threshold 15). Of this number, 11 points are the body's own statements and 9 belong to 5 function literals inside it that branch. 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.
tabs.tabsSchemaComponent.scrollOverflow (cyclomatic 20) packages/schemas/resources/js/components/tabs.js:377— tabs.tabsSchemaComponent.scrollOverflow has cyclomatic complexity 20 (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.
index.document.addEventListener("alpine:init") (cyclomatic 20) packages/schemas/resources/js/index.js:116— index.document.addEventListener("alpine:init") has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 119, 197, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
partials.document.addEventListener("livewire:init") (cyclomatic 20) packages/support/resources/js/partials.js:1— partials.document.addEventListener("livewire:init") has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 73, a function literal at line 14, a function literal at line 108, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tabsSchemaComponent.scrollOverflow (cyclomatic 20) packages/schemas/resources/js/components/tabs.js:377— tabsSchemaComponent.scrollOverflow has cyclomatic complexity 20 (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.
dateTimePickerFormComponent::handleCalendarKeydown (cyclomatic 20) packages/forms/resources/js/components/date-time-picker.js:472— dateTimePickerFormComponent::handleCalendarKeydown has cyclomatic complexity 20 (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.
colorPickerFormComponent (cyclomatic 20) packages/forms/resources/js/components/color-picker.js:6— colorPickerFormComponent has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 13 function items inside it that branch (init, a function literal at line 50, a function literal at line 33, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Action.canRenderOptimizedGrouped (cyclomatic 19) packages/actions/src/Action.php:930— Action.canRenderOptimizedGrouped 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.
ImporterClassGenerator.getImporterColumns (cyclomatic 19) packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:116— ImporterClassGenerator.getImporterColumns 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.
ModalTableSelect.fillStateFromRelationship (cyclomatic 19) packages/forms/src/Components/ModalTableSelect.php:432— ModalTableSelect.fillStateFromRelationship 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.
Select.getInValidationRuleValues (cyclomatic 19) packages/forms/src/Components/Select.php:1776— Select.getInValidationRuleValues 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.
InteractsWithParentRecord.resolveParentRecord (cyclomatic 19) packages/panels/src/Resources/Pages/Concerns/InteractsWithParentRecord.php:84— InteractsWithParentRecord.resolveParentRecord 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.
Callout.toEmbeddedHtml (cyclomatic 19) packages/schemas/src/Components/Callout.php:237— Callout.toEmbeddedHtml 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.
Schema.renderEmbeddedHtml (cyclomatic 19) packages/schemas/src/Schema.php:169— Schema.renderEmbeddedHtml 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.
SelectFilter.apply (cyclomatic 19) packages/tables/src/Filters/SelectFilter.php:185— SelectFilter.apply 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.
UpgradeDirectoryStructureToV4Command.moveClass (cyclomatic 19) packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:324— UpgradeDirectoryStructureToV4Command.moveClass 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.
markdown-editor.markdownEditorFormComponent.init (cyclomatic 19) packages/forms/resources/js/components/markdown-editor.js:121— markdown-editor.markdownEditorFormComponent.init has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 182, 233, 256, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Component.toSchemaHtml (cyclomatic 18) packages/schemas/src/Components/Component.php:135— Component.toSchemaHtml 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.
OptionsArrayStateCast.get (cyclomatic 18) packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:19— OptionsArrayStateCast.get 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.
HasComponents.getComponentByStatePath (cyclomatic 18) packages/schemas/src/Concerns/HasComponents.php:237— HasComponents.getComponentByStatePath 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.
CheckTranslationsCommand.scan (cyclomatic 18) packages/support/src/Commands/CheckTranslationsCommand.php:80— CheckTranslationsCommand.scan 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.
CanAskForViewLocation.askForViewLocation (cyclomatic 18) packages/support/src/Commands/Concerns/CanAskForViewLocation.php:22— CanAskForViewLocation.askForViewLocation 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.
CanManipulateFiles.getRelativePath (cyclomatic 18) packages/support/src/Commands/Concerns/CanManipulateFiles.php:85— CanManipulateFiles.getRelativePath has cyclomatic complexity 18 (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.
ComponentAttributeBag.merge (cyclomatic 18) packages/support/src/View/ComponentAttributeBag.php:228— ComponentAttributeBag.merge 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.
sidebar.default (cyclomatic 18) packages/panels/resources/js/components/sidebar.js:1— sidebar.default has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
pluralize.default (cyclomatic 18) packages/support/resources/js/utilities/pluralize.js:2— pluralize.default has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (extractFromString, extract, replace). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
reordering::reconcile (cyclomatic 18) packages/forms/resources/js/utilities/reordering.js:300— reordering::reconcile 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.
addProseMirrorPlugins (cyclomatic 18) packages/forms/resources/js/components/rich-editor/extension-custom-block.js:251— addProseMirrorPlugins has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 15 function items inside it that branch (hydrateCustomBlockPreviews, a function literal at line 269, a function literal at line 372, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AdminPanelProvider.panel (cyclomatic 17) docs-assets/app/app/Providers/Filament/AdminPanelProvider.php:39— AdminPanelProvider.panel 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.
ActionGroup.toEmbeddedHtml (cyclomatic 17) packages/actions/src/ActionGroup.php:468— ActionGroup.toEmbeddedHtml 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.
InteractsWithRecord.getRecord (cyclomatic 17) packages/actions/src/Concerns/InteractsWithRecord.php:99— InteractsWithRecord.getRecord has cyclomatic complexity 17 (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.
ImportAction.setUp (cyclomatic 17) packages/actions/src/ImportAction.php:81— ImportAction.setUp 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.
BaseFileUpload.getUploadedFiles (cyclomatic 17) packages/forms/src/Components/BaseFileUpload.php:925— BaseFileUpload.getUploadedFiles 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.
CheckboxList.relationship (cyclomatic 17) packages/forms/src/Components/CheckboxList.php:188— CheckboxList.relationship 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.
TableSelect.fillStateFromRelationship (cyclomatic 17) packages/forms/src/Components/TableSelect.php:107— TableSelect.fillStateFromRelationship 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.
OptionStateCast.get (cyclomatic 17) packages/schemas/src/Components/StateCasts/OptionStateCast.php:16— OptionStateCast.get has cyclomatic complexity 17 (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.
InteractsWithSchemas.loadDeferredSchema (cyclomatic 17) packages/schemas/src/Concerns/InteractsWithSchemas.php:138— InteractsWithSchemas.loadDeferredSchema 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.
InteractsWithSchemas.cacheSchema (cyclomatic 17) packages/schemas/src/Concerns/InteractsWithSchemas.php:350— InteractsWithSchemas.cacheSchema 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.
EvaluatesClosures.resolveClosureDependencyForEvaluation (cyclomatic 17) packages/support/src/Concerns/EvaluatesClosures.php:43— EvaluatesClosures.resolveClosureDependencyForEvaluation 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.
Column.renderInLayout (cyclomatic 17) packages/tables/src/Columns/Column.php:141— Column.renderInLayout has cyclomatic complexity 17 (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.
TextColumn.canRenderOptimized (cyclomatic 17) packages/tables/src/Columns/TextColumn.php:187— TextColumn.canRenderOptimized has cyclomatic complexity 17 (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.
date-time-picker.dateTimePickerFormComponent.togglePanelVisibility (cyclomatic 17) packages/forms/resources/js/components/date-time-picker.js:672— date-time-picker.dateTimePickerFormComponent.togglePanelVisibility has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 704, 728). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: date-time-picker.dateTimePickerFormComponent.handleCalendarKeydown (cyclomatic 20) 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.
EasyMDE.EasyMDE.markdown (cyclomatic 17) REDACTED:2271— EasyMDE.EasyMDE.markdown has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
EasyMDE.EasyMDE.createStatusbar (cyclomatic 17) REDACTED:3231— EasyMDE.EasyMDE.createStatusbar has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
Select.createOptionElement (cyclomatic 17) packages/support/resources/js/utilities/select.js:507— Select.createOptionElement 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. This is NOT this file's highest cyclomatic complexity: Select.setUpEventListeners (cyclomatic 21) 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.
interceptNotificationRequest (cyclomatic 17) packages/notifications/resources/js/components/notifications.js:110— interceptNotificationRequest has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 162, capture, a function literal at line 136, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
fileUploadFormComponent::init (cyclomatic 17) packages/forms/resources/js/components/file-upload.js:130— fileUploadFormComponent::init has cyclomatic complexity 17 (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.
addProseMirrorPlugins (cyclomatic 17) packages/forms/resources/js/components/rich-editor/extension-mention.js:258— addProseMirrorPlugins has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 7 function items inside it that branch (hydrateMentions, a function literal at line 265, a function literal at line 286, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InteractsWithActions.mountAction (cyclomatic 16) packages/actions/src/Concerns/InteractsWithActions.php:224— InteractsWithActions.mountAction 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.
DateTimePicker.getDateLimitValidationRule (cyclomatic 16) packages/forms/src/Components/DateTimePicker.php:809— DateTimePicker.getDateLimitValidationRule 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.
ModalTableSelect.saveStateToRelationship (cyclomatic 16) packages/forms/src/Components/ModalTableSelect.php:584— ModalTableSelect.saveStateToRelationship 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.
ModalTableSelect.toEmbeddedHtml (cyclomatic 16) packages/forms/src/Components/ModalTableSelect.php:907— ModalTableSelect.toEmbeddedHtml 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.
Select.saveStateToRelationship (cyclomatic 16) packages/forms/src/Components/Select.php:1341— Select.saveStateToRelationship 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.
HasChildComponents.getChildSchema (cyclomatic 16) packages/schemas/src/Components/Concerns/HasChildComponents.php:105— HasChildComponents.getChildSchema 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.
Flex.toEmbeddedHtml (cyclomatic 16) packages/schemas/src/Components/Flex.php:47— Flex.toEmbeddedHtml 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.
DateTimeStateCast.get (cyclomatic 16) packages/schemas/src/Components/StateCasts/DateTimeStateCast.php:18— DateTimeStateCast.get 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.
SpatieMediaLibraryFileUpload.setUp (cyclomatic 16) packages/spatie-laravel-media-library-plugin/src/Forms/Components/SpatieMediaLibraryFileUpload.php:52— SpatieMediaLibraryFileUpload.setUp 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.
HasCluster.askForCluster (cyclomatic 16) packages/support/src/Commands/Concerns/HasCluster.php:27— HasCluster.askForCluster 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.
Summarizer.getState (cyclomatic 16) packages/tables/src/Columns/Summarizers/Summarizer.php:72— Summarizer.getState 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.
HasBulkActions.getSelectedTableRecordsQuery (cyclomatic 16) packages/tables/src/Concerns/HasBulkActions.php:316— HasBulkActions.getSelectedTableRecordsQuery 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.
color-picker.colorPickerFormComponent.init (cyclomatic 16) packages/forms/resources/js/components/color-picker.js:22— color-picker.colorPickerFormComponent.init has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 50, 33, 58, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EasyMDE.getState (cyclomatic 16) REDACTED:362— EasyMDE.getState 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.
EasyMDE._toggleBlock (cyclomatic 16) REDACTED:1481— EasyMDE._toggleBlock 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.
Select.updateOptionLabelInList (cyclomatic 16) packages/support/resources/js/utilities/select.js:1187— Select.updateOptionLabelInList 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. This is NOT this file's highest cyclomatic complexity: Select.setUpEventListeners (cyclomatic 21) 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.
chart.applyChartColors (cyclomatic 16) packages/widgets/resources/js/components/chart.js:249— chart.applyChartColors 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.
dateTimePickerFormComponent (cognitive 181) packages/forms/resources/js/components/date-time-picker.js:27— dateTimePickerFormComponent has cognitive complexity 181 (threshold 15). Drivers by points: if/else 82 (86 pts), boolean chains 44, other 27, ternaries 16 (23 pts), match/switch 1 (nesting depth added 11). Most of this is not in the body itself: 1 of the 181 points is its own statement and the rest belongs to 62 function items inside it that branch (handleCalendarKeydown, a function literal at line 260, dateIsDisabled, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Builder.toEmbeddedHtml (cognitive 142) packages/forms/src/Components/Builder.php:1653— Builder.toEmbeddedHtml has cognitive complexity 142 (threshold 15). Drivers by points: if/else 24 (85 pts), boolean chains 35, ternaries 3 (15 pts), loops 2 (7 pts) (nesting depth added 78). 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.
toggleCodeBlock (cognitive 140) REDACTED:501— toggleCodeBlock has cognitive complexity 140 (threshold 15). Drivers by points: if/else 42 (92 pts), loops 6 (19 pts), boolean chains 16, ternaries 5 (13 pts) (nesting depth added 71). Of this number, 114 points are the body's own statements and 26 belong to 7 function items inside it that branch. 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.
Repeater.toTableEmbeddedHtml (cognitive 134) packages/forms/src/Components/Repeater.php:1957— Repeater.toTableEmbeddedHtml has cognitive complexity 134 (threshold 15). Drivers by points: if/else 22 (73 pts), ternaries 6 (31 pts), boolean chains 18, loops 4 (12 pts) (nesting depth added 84). 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.
Tabs.toEmbeddedHtml (cognitive 126) packages/schemas/src/Components/Tabs.php:284— Tabs.toEmbeddedHtml has cognitive complexity 126 (threshold 15). Drivers by points: ternaries 28 (71 pts), if/else 23 (40 pts), loops 6 (8 pts), boolean chains 7 (nesting depth added 62). 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.
Repeater.toEmbeddedHtml (cognitive 121) packages/forms/src/Components/Repeater.php:1565— Repeater.toEmbeddedHtml has cognitive complexity 121 (threshold 15). Drivers by points: if/else 21 (70 pts), boolean chains 27, ternaries 4 (17 pts), loops 2 (7 pts) (nesting depth added 67). 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.
(anonymous) (cognitive 110) packages/tables/resources/js/components/table.js:3— (anonymous) has cognitive complexity 110 (threshold 15). Drivers by points: if/else 57 (74 pts), boolean chains 18, loops 4 (5 pts), other 5, ternaries 3 (5 pts), error handling 2 (3 pts) (nesting depth added 21). Most of this is not in the body itself: 1 of the 110 points is its own statement and the rest belongs to 63 function items inside it that branch (finishTableReorder, handleCheckboxClick, toggleCollapseGroup, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
render (cognitive 101) REDACTED:2346— render has cognitive complexity 101 (threshold 15). Drivers by points: if/else 43 (66 pts), ternaries 15 (17 pts), boolean chains 14, loops 2 (4 pts) (nesting depth added 27). Of this number, 38 points are the body's own statements and 63 belong to 22 function items inside it that branch. 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.
TextEntry.toEmbeddedHtml (cognitive 100) packages/infolists/src/Components/TextEntry.php:177— TextEntry.toEmbeddedHtml has cognitive complexity 100 (threshold 15). Drivers by points: if/else 25 (44 pts), ternaries 25 (29 pts), boolean chains 15, loops 5 (11 pts), match/switch 1 (nesting depth added 29). 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.
TextColumn.toEmbeddedHtml (cognitive 100) packages/tables/src/Columns/TextColumn.php:274— TextColumn.toEmbeddedHtml has cognitive complexity 100 (threshold 15). Drivers by points: if/else 28 (53 pts), ternaries 23 (27 pts), boolean chains 15, loops 2 (4 pts), 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.
dropdown.default (cognitive 99) packages/support/resources/js/components/dropdown.js:21— dropdown.default has cognitive complexity 99 (threshold 15). Drivers by points: if/else 52 (56 pts), boolean chains 32, ternaries 8 (10 pts), loops 1 (nesting depth added 6). Of this number, 94 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
table.default (cognitive 99) packages/tables/resources/js/components/table.js:3— table.default has cognitive complexity 99 (threshold 15). Drivers by points: if/else 54 (71 pts), boolean chains 18, loops 4 (5 pts), error handling 2 (3 pts), ternaries 2 (nesting depth added 19). Of this number, 81 points are the body's own statements and 18 belong to 9 function items inside it that branch. 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.
Field.wrapEmbeddedHtml (cognitive 91) packages/forms/src/Components/Field.php:344— Field.wrapEmbeddedHtml has cognitive complexity 91 (threshold 15). Drivers by points: if/else 24 (45 pts), boolean chains 23, ternaries 8 (19 pts), loops 1 (4 pts) (nesting depth added 35). 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.
FusedGroup.toEmbeddedHtml (cognitive 82) packages/schemas/src/Components/FusedGroup.php:221— FusedGroup.toEmbeddedHtml has cognitive complexity 82 (threshold 15). Drivers by points: if/else 28 (54 pts), boolean chains 14, ternaries 7 (10 pts), loops 2 (4 pts) (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.
Section.toEmbeddedHtml (cognitive 81) packages/schemas/src/Components/Section.php:264— Section.toEmbeddedHtml has cognitive complexity 81 (threshold 15). Drivers by points: if/else 23 (49 pts), boolean chains 21, ternaries 7 (11 pts) (nesting depth added 30). 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.
CanGenerateModelForms.getFormComponents (cognitive 79) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:46— CanGenerateModelForms.getFormComponents has cognitive complexity 79 (threshold 15). Drivers by points: if/else 30 (70 pts), boolean chains 5, loops 2, match/switch 1 (2 pts) (nesting depth added 41). 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.
EasyMDE.EasyMDE (cognitive 72) REDACTED:1933— EasyMDE.EasyMDE has cognitive complexity 72 (threshold 15). Drivers by points: if/else 26 (41 pts), boolean chains 27, loops 2 (4 pts) (nesting depth added 17). Of this number, 66 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
Builder.generateBlockPickerHtml (cognitive 70) packages/forms/src/Components/Builder.php:1432— Builder.generateBlockPickerHtml has cognitive complexity 70 (threshold 15). Drivers by points: ternaries 16 (33 pts), if/else 11 (28 pts), loops 3 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 37). 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.
RichEditor.toEmbeddedHtml (cognitive 69) packages/forms/src/Components/RichEditor.php:1693— RichEditor.toEmbeddedHtml has cognitive complexity 69 (threshold 15). Drivers by points: if/else 15 (37 pts), loops 7 (15 pts), ternaries 10 (14 pts), boolean chains 3 (nesting depth added 34). 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.
CanGenerateButtonHtml.generateButtonHtml (cognitive 69) packages/support/src/View/Concerns/CanGenerateButtonHtml.php:29— CanGenerateButtonHtml.generateButtonHtml has cognitive complexity 69 (threshold 15). Drivers by points: ternaries 27 (32 pts), if/else 18 (19 pts), boolean chains 16, match/switch 2 (nesting depth added 6). 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.
InteractsWithRelationshipTable.makeTable (cognitive 68) packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:110— InteractsWithRelationshipTable.makeTable has cognitive complexity 68 (threshold 15). Drivers by points: if/else 18 (53 pts), loops 6 (15 pts) (nesting depth added 44). 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.
(anonymous) (cognitive 68) packages/forms/resources/js/components/rich-editor/mention-suggestion.js:4— (anonymous) has cognitive complexity 68 (threshold 15). Drivers by points: if/else 30 (37 pts), ternaries 9 (13 pts), boolean chains 9, other 7, error handling 1 (2 pts) (nesting depth added 12). None of this is in the body itself: all 68 points belong to 18 function items inside it that branch (items, render::renderItems, render::scrollToSelected, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanGenerateModelTables.getTableColumns (cognitive 67) packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:51— CanGenerateModelTables.getTableColumns has cognitive complexity 67 (threshold 15). Drivers by points: if/else 24 (51 pts), boolean chains 7, ternaries 1 (4 pts), match/switch 1 (3 pts), loops 2 (nesting depth added 32). 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.
Field.wrapInputHtml (cognitive 65) packages/forms/src/Components/Field.php:580— Field.wrapInputHtml has cognitive complexity 65 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 13 (18 pts), boolean chains 17, loops 2 (6 pts) (nesting depth added 19). 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.
MakePageCommand.createResourceManageRelatedRecordsPage (cognitive 64) packages/panels/src/Commands/MakePageCommand.php:513— MakePageCommand.createResourceManageRelatedRecordsPage has cognitive complexity 64 (threshold 15). Drivers by points: if/else 18 (38 pts), boolean chains 14, ternaries 2 (7 pts), error handling 2 (5 pts) (nesting depth added 28). 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.
renderOptions (cognitive 62) packages/support/resources/js/utilities/select.js:306— renderOptions has cognitive complexity 62 (threshold 15). Drivers by points: if/else 21 (40 pts), boolean chains 15, other 3, ternaries 2 (3 pts), loops 1 (nesting depth added 20). Of this number, 58 points are the body's own statements and 4 belong to 5 function literals inside it that branch. 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.
SettingsPageClassGenerator.getFormComponents (cognitive 61) packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:149— SettingsPageClassGenerator.getFormComponents has cognitive complexity 61 (threshold 15). Drivers by points: if/else 14 (29 pts), boolean chains 19, ternaries 3 (9 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 22). 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.
LocalFilesPlugin (cognitive 61) packages/forms/resources/js/components/rich-editor/extension-local-files.js:43— LocalFilesPlugin has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (36 pts), loops 3 (10 pts), boolean chains 6, error handling 3 (6 pts), ternaries 2, other 1 (nesting depth added 28). None of this is in the body itself: all 61 points belong to 22 function items inside it that branch (a function literal at line 277, handlePaste, startUpload::finish, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanGenerateModelInfolists.getInfolistComponents (cognitive 60) packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:32— CanGenerateModelInfolists.getInfolistComponents has cognitive complexity 60 (threshold 15). Drivers by points: if/else 23 (47 pts), boolean chains 4, ternaries 1 (4 pts), match/switch 1 (3 pts), loops 2 (nesting depth added 29). 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.
DateTimePicker.toEmbeddedHtml (cognitive 59) packages/forms/src/Components/DateTimePicker.php:101— DateTimePicker.toEmbeddedHtml has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 23, ternaries 5 (9 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.
TranslationFileLineParser.parse (cognitive 58) bin/TranslationTool/src/DataObjects/TranslationFileLineParser.php:12— TranslationFileLineParser.parse has cognitive complexity 58 (threshold 15). Drivers by points: if/else 11 (38 pts), ternaries 2 (10 pts), boolean chains 5, loops 2 (5 pts) (nesting depth added 38). 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.
Repeater.toSimpleEmbeddedHtml (cognitive 58) packages/forms/src/Components/Repeater.php:1814— Repeater.toSimpleEmbeddedHtml has cognitive complexity 58 (threshold 15). Drivers by points: if/else 8 (25 pts), boolean chains 15, ternaries 3 (12 pts), loops 2 (6 pts) (nesting depth added 30). 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.
ToggleButtons.toEmbeddedHtml (cognitive 55) packages/forms/src/Components/ToggleButtons.php:93— ToggleButtons.toEmbeddedHtml has cognitive complexity 55 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 14 (23 pts), boolean chains 5, loops 1, match/switch 1 (nesting depth added 22). 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.
CanGenerateLinkHtml.generateLinkHtml (cognitive 55) packages/support/src/View/Concerns/CanGenerateLinkHtml.php:30— CanGenerateLinkHtml.generateLinkHtml has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 23 (29 pts), if/else 13, boolean chains 11, match/switch 2 (nesting depth added 6). 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.
rich-editor.richEditorFormComponent.init (cognitive 55) packages/forms/resources/js/components/rich-editor.js:88— rich-editor.richEditorFormComponent.init has cognitive complexity 55 (threshold 15). Drivers by points: if/else 28 (36 pts), ternaries 7 (11 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 13). Most of this is not in the body itself: 10 of the 55 points are its own statements and the rest belongs to 18 function items inside it that branch (updateModalMeasurements, a function literal at line 318, a function literal at line 408, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
HasComponents.getAction (cognitive 54) packages/schemas/src/Concerns/HasComponents.php:86— HasComponents.getAction has cognitive complexity 54 (threshold 15). Drivers by points: if/else 15 (39 pts), boolean chains 8, ternaries 1 (4 pts), loops 2 (3 pts) (nesting depth added 28). 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.
HasComponents.registerLivewireComponents (cognitive 51) packages/panels/src/Panel/Concerns/HasComponents.php:575— HasComponents.registerLivewireComponents has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 6 (17 pts), boolean chains 7 (nesting depth added 26). 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.
file-upload.fileUploadFormComponent.init (cognitive 51) packages/forms/resources/js/components/file-upload.js:130— file-upload.fileUploadFormComponent.init has cognitive complexity 51 (threshold 15). Drivers by points: if/else 28 (30 pts), boolean chains 19, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 15 of the 51 points are its own statements and the rest belongs to 16 function items inside it that branch (a function literal at line 414, handleFileProcessing, onVisible, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
HasComponents.getComponent (cognitive 50) packages/schemas/src/Concerns/HasComponents.php:172— HasComponents.getComponent has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (36 pts), loops 3 (10 pts), boolean chains 4 (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.
ToggleButtons.toGroupedEmbeddedHtml (cognitive 49) packages/forms/src/Components/ToggleButtons.php:226— ToggleButtons.toGroupedEmbeddedHtml has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 14 (23 pts), if/else 9 (20 pts), boolean chains 4, loops 1, match/switch 1 (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.
CanGenerateIconButtonHtml.generateIconButtonHtml (cognitive 49) packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:28— CanGenerateIconButtonHtml.generateIconButtonHtml has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 22 (26 pts), boolean chains 13, if/else 8, match/switch 2 (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.
(anonymous) (cognitive 49) packages/actions/resources/js/components/modals.js:1— (anonymous) has cognitive complexity 49 (threshold 15). Drivers by points: if/else 30 (34 pts), boolean chains 10, other 2, ternaries 2, loops 1 (nesting depth added 4). None of this is in the body itself: all 49 points belong to 21 function items inside it that branch (syncActionModals, restorePreviouslyFocusedElement, rememberPreviouslyFocusedElement, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
global-search.default (cognitive 47) packages/panels/resources/js/components/global-search.js:1— global-search.default has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 20 (nesting depth added 6). Of this number, 37 points are the body's own statements and 10 belong to 10 function literals inside it that branch. 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.
tabsSchemaComponent.update (cognitive 47) packages/schemas/resources/js/components/tabs.js:617— tabsSchemaComponent.update has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 20, if/else 15 (20 pts), ternaries 2 (5 pts), other 2 (nesting depth added 8). Of this number, 20 points are the body's own statements and 27 belong to 2 function literals inside it that branch. 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.
markdownEditorFormComponent (cognitive 47) packages/forms/resources/js/components/markdown-editor.js:90— markdownEditorFormComponent has cognitive complexity 47 (threshold 15). Drivers by points: if/else 32 (34 pts), other 6, boolean chains 3, ternaries 1 (3 pts), error handling 1 (nesting depth added 4). None of this is in the body itself: all 47 points belong to 31 function items inside it that branch (getToolbarButton, init, a function literal at line 182, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Select.toEmbeddedHtml (cognitive 45) packages/forms/src/Components/Select.php:1867— Select.toEmbeddedHtml has cognitive complexity 45 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 11, ternaries 6 (11 pts), loops 2 (6 pts) (nesting depth added 19). 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.
Tabs.toEmbeddedHtmlForLivewireProperty (cognitive 45) packages/schemas/src/Components/Tabs.php:653— Tabs.toEmbeddedHtmlForLivewireProperty has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 15 (29 pts), if/else 6 (9 pts), loops 4, boolean chains 3 (nesting depth added 17). 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.
EntanglesStateWithSingularRelationship.relationship (cognitive 44) packages/schemas/src/Components/Concerns/EntanglesStateWithSingularRelationship.php:33— EntanglesStateWithSingularRelationship.relationship has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (17 pts), loops 9 (13 pts), boolean chains 12, ternaries 1 (2 pts) (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.
EasyMDE.EasyMDE.createToolbar (cognitive 43) REDACTED:3107— EasyMDE.EasyMDE.createToolbar has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 10, loops 4 (6 pts) (nesting depth added 15). Of this number, 31 points are the body's own statements and 12 belong to 3 function literals inside it that branch. 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.
getLabelsForMultipleSelection (cognitive 43) packages/support/resources/js/utilities/select.js:684— getLabelsForMultipleSelection has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 4 (9 pts), boolean chains 6, error handling 1 (2 pts) (nesting depth added 19). 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.
CanGenerateBadgeHtml.generateBadgeHtml (cognitive 42) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:27— CanGenerateBadgeHtml.generateBadgeHtml has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 18 (21 pts), boolean chains 11, if/else 9, match/switch 1 (nesting depth added 3). 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.
openDropdown (cognitive 42) packages/support/resources/js/utilities/select.js:1369— openDropdown has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (22 pts), boolean chains 13, ternaries 3 (5 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.
Select.relationship (cognitive 41) packages/forms/src/Components/Select.php:798— Select.relationship has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 8, ternaries 1 (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.
onBeforeCreate (cognitive 41) packages/forms/resources/js/components/rich-editor/extension-mention.js:324— onBeforeCreate has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (12 pts), other 10, ternaries 4 (7 pts), boolean chains 6, error handling 2 (6 pts) (nesting depth added 11). Most of this is not in the body itself: 1 of the 41 points is its own statement and the rest belongs to 8 function items inside it that branch (a function literal at line 344, (anonymous)::items, (anonymous)::items, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FileUpload.toEmbeddedHtml (cognitive 40) packages/forms/src/Components/FileUpload.php:842— FileUpload.toEmbeddedHtml has cognitive complexity 40 (threshold 15). Drivers by points: loops 5 (19 pts), if/else 7 (11 pts), ternaries 6 (7 pts), boolean chains 3 (nesting depth added 19). 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.
modals.default (cognitive 40) packages/actions/resources/js/components/modals.js:1— modals.default has cognitive complexity 40 (threshold 15). Drivers by points: if/else 25 (29 pts), boolean chains 9, loops 1, ternaries 1 (nesting depth added 4). Of this number, 34 points are the body's own statements and 6 belong to 6 function literals inside it that branch. 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.
editableTableColumn (cognitive 40) packages/tables/resources/js/utilities/editable-table-column.js:1— editableTableColumn has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 13, other 6, ternaries 3, error handling 2 (nesting depth added 1). None of this is in the body itself: all 40 points belong to 18 function items inside it that branch (a function literal at line 70, getAccessibilityAttributes, a function literal at line 47, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SupportServiceProvider.packageBooted (cognitive 38) packages/support/src/SupportServiceProvider.php:166— SupportServiceProvider.packageBooted has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (20 pts), ternaries 6 (8 pts), match/switch 6, boolean chains 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.
handleDropdownKeydown (cognitive 38) packages/support/resources/js/utilities/select.js:1262— handleDropdownKeydown has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (24 pts), ternaries 3 (8 pts), boolean chains 4, match/switch 1, other 1 (nesting depth added 18). 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.
tabs.tabsSchemaComponent.update (cognitive 37) packages/schemas/resources/js/components/tabs.js:617— tabs.tabsSchemaComponent.update has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 12, ternaries 2 (5 pts) (nesting depth added 8). Of this number, 19 points are the body's own statements and 18 belong to one function literal inside it that branches. 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.
tabsSchemaComponent.positionOverflow (cognitive 37) packages/schemas/resources/js/components/tabs.js:449— tabsSchemaComponent.positionOverflow has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 6, loops 4 (6 pts), ternaries 1 (nesting depth added 12). Of this number, 31 points are the body's own statements and 6 belong to 4 function items inside it that branch. 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.
EmailAuthentication.verifyCode (cognitive 36) packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php:164— EmailAuthentication.verifyCode has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 17, if/else 11 (12 pts), ternaries 7 (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.
date-time-picker.dateTimePickerFormComponent.init (cognitive 36) packages/forms/resources/js/components/date-time-picker.js:88— date-time-picker.dateTimePickerFormComponent.init has cognitive complexity 36 (threshold 15). Drivers by points: if/else 33 (34 pts), boolean chains 2 (nesting depth added 1). Most of this is not in the body itself: 2 of the 36 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 260, 148, 194, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PrepareCsvExport.handle (cognitive 35) packages/actions/src/Exports/Jobs/PrepareCsvExport.php:58— PrepareCsvExport.handle has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (27 pts), loops 3 (5 pts), boolean chains 3 (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.
Select.getOptionsFromRelationship (cognitive 35) packages/forms/src/Components/Select.php:1071— Select.getOptionsFromRelationship has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 11 (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.
ColorEntry.toEmbeddedHtml (cognitive 35) packages/infolists/src/Components/ColorEntry.php:21— ColorEntry.toEmbeddedHtml has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 16 (30 pts), if/else 3 (4 pts), loops 1 (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.
Text.toEmbeddedHtml (cognitive 35) packages/schemas/src/Components/Text.php:123— Text.toEmbeddedHtml has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 9 (17 pts), if/else 9 (15 pts), boolean chains 3 (nesting depth added 14). 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.
CanSortRecords.applySortingToTableQuery (cognitive 35) packages/tables/src/Concerns/CanSortRecords.php:79— CanSortRecords.applySortingToTableQuery has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 4 (10 pts), boolean chains 5, loops 1 (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.
SelectFilter.setUp (cognitive 35) packages/tables/src/Filters/SelectFilter.php:45— SelectFilter.setUp has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (22 pts), ternaries 6 (11 pts), boolean chains 2 (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.
tabs.tabsSchemaComponent.positionOverflow (cognitive 35) packages/schemas/resources/js/components/tabs.js:449— tabs.tabsSchemaComponent.positionOverflow has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 4 (6 pts), boolean chains 4, ternaries 1 (nesting depth added 12). Of this number, 29 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
(anonymous) (cognitive 35) packages/support/resources/js/partials.js:1— (anonymous) has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (30 pts), ternaries 1 (2 pts), boolean chains 1, loops 1, other 1 (nesting depth added 15). None of this is in the body itself: all 35 points belong to 12 function items inside it that branch (a function literal at line 14, (anonymous)::(anonymous)::(anonymous)::updating, (anonymous)::(anonymous)::(anonymous)::key, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InteractsWithParentRecord.resolveParentRecord (cognitive 34) packages/panels/src/Resources/Pages/Concerns/InteractsWithParentRecord.php:84— InteractsWithParentRecord.resolveParentRecord has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 2 (6 pts), boolean chains 5, loops 2 (3 pts) (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.
ComponentAttributeBag.merge (cognitive 34) packages/support/src/View/ComponentAttributeBag.php:228— ComponentAttributeBag.merge has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 4, loops 3 (4 pts) (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.
partials.document.addEventListener("livewire:init") (cognitive 34) packages/support/resources/js/partials.js:1— partials.document.addEventListener("livewire:init") has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (30 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 15). None of this is in the body itself: all 34 points belong to 5 function items inside it that branch (a function literal at line 14, a function literal at line 73, a function literal at line 108, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanExportRecords.setUp (cognitive 33) packages/actions/src/Concerns/CanExportRecords.php:77— CanExportRecords.setUp has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 7 (8 pts), boolean chains 5, loops 4, match/switch 2 (nesting depth added 3). 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.
DateTimeStateCast.get (cognitive 33) packages/schemas/src/Components/StateCasts/DateTimeStateCast.php:18— DateTimeStateCast.get has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (4 pts) (nesting depth added 17). 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.
InteractsWithTable.bootedInteractsWithTable (cognitive 33) packages/tables/src/Concerns/InteractsWithTable.php:49— InteractsWithTable.bootedInteractsWithTable has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 10, ternaries 2 (5 pts) (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.
AssociateAction.getRecordSelect (cognitive 32) packages/actions/src/AssociateAction.php:217— AssociateAction.getRecordSelect has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (14 pts), if/else 10 (11 pts), boolean chains 5, loops 1 (2 pts) (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.
ListRecords.makeTable (cognitive 32) packages/panels/src/Resources/Pages/ListRecords.php:116— ListRecords.makeTable has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 5 (10 pts) (nesting depth added 18). 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.
merge-tag-suggestion.default (cognitive 32) packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:4— merge-tag-suggestion.default has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20 (22 pts), boolean chains 10 (nesting depth added 2). None of this is in the body itself: all 32 points belong to 11 function literals inside it that branch (lines 152, 74, 34, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
createToolbarButton (cognitive 32) REDACTED:218— createToolbarButton has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (22 pts), loops 3 (5 pts), boolean chains 4, ternaries 1 (nesting depth added 7). 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.
Select.fillStateFromRelationship (cognitive 31) packages/forms/src/Components/Select.php:1188— Select.fillStateFromRelationship has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 4 (10 pts), boolean chains 5 (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.
TextInput.toEmbeddedHtml (cognitive 31) packages/forms/src/Components/TextInput.php:327— TextInput.toEmbeddedHtml has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 16, ternaries 8, if/else 5, loops 1 (2 pts) (nesting depth added 1). 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.
ColorColumn.toEmbeddedHtml (cognitive 31) packages/tables/src/Columns/ColorColumn.php:21— ColorColumn.toEmbeddedHtml has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (24 pts), if/else 3 (4 pts), boolean chains 2, loops 1 (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.
rich-editor.richEditorFormComponent.handleToolbarKeydown (cognitive 31) packages/forms/resources/js/components/rich-editor.js:679— rich-editor.richEditorFormComponent.handleToolbarKeydown has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 6, ternaries 3 (4 pts), loops 1 (2 pts) (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.
Select.updateOptionLabelInList (cognitive 31) packages/support/resources/js/utilities/select.js:1187— Select.updateOptionLabelInList has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 5 (9 pts), boolean chains 2 (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.
AttachAction.getRecordSelect (cognitive 30) packages/actions/src/AttachAction.php:218— AttachAction.getRecordSelect has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 8 (13 pts), if/else 9 (10 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.
Select.getOptionLabels (cognitive 30) packages/forms/src/Components/Select.php:632— Select.getOptionLabels has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 17). 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.
Entry.wrapEmbeddedHtml (cognitive 30) packages/infolists/src/Components/Entry.php:255— Entry.wrapEmbeddedHtml has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 11, ternaries 5 (6 pts), match/switch 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.
Callout.toEmbeddedHtml (cognitive 30) packages/schemas/src/Components/Callout.php:237— Callout.toEmbeddedHtml has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 6, ternaries 1 (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.
CanGenerateDropdownItemHtml.generateDropdownItemHtml (cognitive 30) packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:28— CanGenerateDropdownItemHtml.generateDropdownItemHtml has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 13, boolean chains 8, if/else 7 (8 pts), match/switch 1 (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.
CanSummarizeRecords.getTableSummarySelectedState (cognitive 30) packages/tables/src/Concerns/CanSummarizeRecords.php:85— CanSummarizeRecords.getTableSummarySelectedState has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 3 (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.
InteractsWithToolbarButtons.applyDisableToolbarButtonsModification (cognitive 29) packages/forms/src/Components/Concerns/InteractsWithToolbarButtons.php:132— InteractsWithToolbarButtons.applyDisableToolbarButtonsModification has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (25 pts), loops 2 (4 pts) (nesting depth added 19). 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.
Select.getInValidationRuleValues (cognitive 29) packages/forms/src/Components/Select.php:1776— Select.getInValidationRuleValues has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 3, loops 1 (3 pts), ternaries 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.
ImageEntry.toEmbeddedHtml (cognitive 29) packages/infolists/src/Components/ImageEntry.php:468— ImageEntry.toEmbeddedHtml has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (13 pts), if/else 8 (10 pts), boolean chains 5, loops 1 (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.
Wizard.toEmbeddedHtml (cognitive 29) packages/schemas/src/Components/Wizard.php:403— Wizard.toEmbeddedHtml has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). 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.
HasComponents.getComponentByStatePath (cognitive 29) packages/schemas/src/Concerns/HasComponents.php:237— HasComponents.getComponentByStatePath has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (6 pts), boolean chains 4, ternaries 2 (4 pts) (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.
ImageColumn.toEmbeddedHtml (cognitive 29) packages/tables/src/Columns/ImageColumn.php:461— ImageColumn.toEmbeddedHtml has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 11 (13 pts), if/else 8 (10 pts), boolean chains 5, loops 1 (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.
TextInputColumn.toEmbeddedHtml (cognitive 29) packages/tables/src/Columns/TextInputColumn.php:204— TextInputColumn.toEmbeddedHtml has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 14 (19 pts), if/else 6 (8 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.
QueryBuilder.getRuleSummaries (cognitive 29) packages/tables/src/Filters/QueryBuilder.php:93— QueryBuilder.getRuleSummaries has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 4 (10 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 18). 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.
setUpEventListeners (cognitive 29) packages/support/resources/js/utilities/select.js:1059— setUpEventListeners has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 9, error handling 1 (4 pts) (nesting depth added 9). Most of this is not in the body itself: 4 of the 29 points are its own statements and the rest belongs to 9 function items inside it that branch (refreshOptionLabelListener, a function literal at line 1093, documentClickListener, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BaseFileUpload.getUploadedFiles (cognitive 28) packages/forms/src/Components/BaseFileUpload.php:925— BaseFileUpload.getUploadedFiles has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 4 (5 pts), boolean chains 2, loops 1 (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.
CodeEntry.toEmbeddedHtml (cognitive 28) packages/infolists/src/Components/CodeEntry.php:76— CodeEntry.toEmbeddedHtml has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 12 (14 pts), if/else 10 (11 pts), boolean chains 3 (nesting depth added 3). 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.
CanReadModelSchemas.parseDefaultExpression (cognitive 28) packages/support/src/Commands/Concerns/CanReadModelSchemas.php:207— CanReadModelSchemas.parseDefaultExpression has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (21 pts), boolean chains 5, loops 1 (2 pts) (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.
EasyMDE._toggleHeading (cognitive 28) REDACTED:1273— EasyMDE._toggleHeading has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 2, loops 1 (nesting depth added 11). Most of this is not in the body itself: 2 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 1284). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
markdown (cognitive 28) REDACTED:2271— markdown has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 9 (nesting depth added 9). Of this number, 22 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
CheckboxList.relationship (cognitive 27) packages/forms/src/Components/CheckboxList.php:188— CheckboxList.relationship has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (24 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.
ModalTableSelect.getOptionLabelsFromRelationship (cognitive 27) packages/forms/src/Components/ModalTableSelect.php:338— ModalTableSelect.getOptionLabelsFromRelationship has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 12). 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.
ModalTableSelect.toEmbeddedHtml (cognitive 27) packages/forms/src/Components/ModalTableSelect.php:907— ModalTableSelect.toEmbeddedHtml has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 2 (7 pts), ternaries 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.
RichContentFaker.mention (cognitive 27) packages/forms/src/Components/RichEditor/RichContentFaker.php:448— RichContentFaker.mention has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (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.
RelationshipJoiner.prepareQueryForNoConstraints (cognitive 27) packages/support/src/Services/RelationshipJoiner.php:26— RelationshipJoiner.prepareQueryForNoConstraints has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 14). 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.
CanFormatState.formatState (cognitive 27) packages/tables/src/Columns/Concerns/CanFormatState.php:378— CanFormatState.formatState has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 5, ternaries 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.
HasBulkActions.getSelectedTableRecordsQuery (cognitive 27) packages/tables/src/Concerns/HasBulkActions.php:316— HasBulkActions.getSelectedTableRecordsQuery has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 2 (5 pts) (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.
reordering.reordering.init (cognitive 27) packages/forms/resources/js/utilities/reordering.js:23— reordering.reordering.init has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 18, if/else 9. Of this number, 14 points are the body's own statements and 13 belong to 14 function literals inside it that branch. 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.
copyable.default (cognitive 27) packages/support/resources/js/components/copyable.js:6— copyable.default has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 10, ternaries 2, error handling 1 (nesting depth added 1). Of this number, 24 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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.
Action.canRenderOptimizedLink (cognitive 26) packages/actions/src/Action.php:816— Action.canRenderOptimizedLink has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 26. 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.
InteractsWithActions.callMountedAction (cognitive 26) packages/actions/src/Concerns/InteractsWithActions.php:361— InteractsWithActions.callMountedAction has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), error handling 5 (6 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 5). 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.
CheckboxList.toEmbeddedHtml (cognitive 26) packages/forms/src/Components/CheckboxList.php:537— CheckboxList.toEmbeddedHtml has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 3 (5 pts), boolean chains 2, loops 1 (2 pts) (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.
ModalTableSelect.fillStateFromRelationship (cognitive 26) packages/forms/src/Components/ModalTableSelect.php:432— ModalTableSelect.fillStateFromRelationship has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 5, ternaries 2 (5 pts) (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.
CanAskForViewLocation.askForViewLocation (cognitive 26) packages/support/src/Commands/Concerns/CanAskForViewLocation.php:22— CanAskForViewLocation.askForViewLocation has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 6, loops 2 (3 pts), ternaries 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.
HasRecords.getTableRecords (cognitive 26) packages/tables/src/Concerns/HasRecords.php:96— HasRecords.getTableRecords has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 7 (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.
EasyMDE.EasyMDE.autosave (cognitive 26) REDACTED:2716— EasyMDE.EasyMDE.autosave has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 4, ternaries 1 (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.
Select.updateSelectedDisplay (cognitive 26) packages/support/resources/js/utilities/select.js:582— Select.updateSelectedDisplay has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 2 (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.
(anonymous) (cognitive 26) packages/support/resources/js/components/one-time-code.js:1— (anonymous) has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18, boolean chains 3, other 3, ternaries 2. None of this is in the body itself: all 26 points belong to 17 function items inside it that branch (a function literal at line 152, a function literal at line 61, submitIfComplete, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
createStatusbar (cognitive 26) REDACTED:3231— createStatusbar has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, loops 2 (nesting depth added 9). Of this number, 21 points are the body's own statements and 5 belong to 12 function items inside it that branch. 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.
ActionGroup.toEmbeddedHtml (cognitive 25) packages/actions/src/ActionGroup.php:468— ActionGroup.toEmbeddedHtml has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (6 pts), ternaries 4, 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.
InteractsWithActions.mountDefaultActions (cognitive 25) packages/actions/src/Concerns/InteractsWithActions.php:136— InteractsWithActions.mountDefaultActions has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (9 pts), ternaries 2 (5 pts) (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.
Flex.toEmbeddedHtml (cognitive 25) packages/schemas/src/Components/Flex.php:47— Flex.toEmbeddedHtml has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 4 (6 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (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.
HasCellState.getStateFromRecord (cognitive 25) packages/support/src/Concerns/HasCellState.php:123— HasCellState.getStateFromRecord has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 4 (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.
tableFilters (cognitive 25) packages/tables/resources/js/components/table.js:695— tableFilters has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13, boolean chains 11, other 1. None of this is in the body itself: all 25 points belong to 13 function items inside it that branch (handleActionClick, a function literal at line 769, a function literal at line 822, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 25) packages/support/resources/js/components/modal.js:49— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, boolean chains 8. None of this is in the body itself: all 25 points belong to 20 function items inside it that branch (a function literal at line 222, setUpTextSelectionClosePrevention::textSelectionClosePreventionMouseUpHandler, a function literal at line 235, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanFormatState.formatState (cognitive 24) packages/infolists/src/Components/Concerns/CanFormatState.php:378— CanFormatState.formatState has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 5, ternaries 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.
RepeatableEntry.toEmbeddedTableHtml (cognitive 24) packages/infolists/src/Components/RepeatableEntry.php:250— RepeatableEntry.toEmbeddedTableHtml has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (4 pts), ternaries 2 (4 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.
NavigationManager.get (cognitive 24) packages/panels/src/Navigation/NavigationManager.php:48— NavigationManager.get has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16, ternaries 4 (6 pts), boolean chains 2 (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.
Select.applyDisabledState (cognitive 24) packages/support/resources/js/utilities/select.js:2115— Select.applyDisabledState has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 4 (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.
(anonymous) (cognitive 24) packages/panels/resources/js/stores/sidebar.js:1— (anonymous) has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 5, ternaries 1 (nesting depth added 3). None of this is in the body itself: all 24 points belong to 16 function items inside it that branch (setUpMediaQuery, setUpMediaQuery::desktopMediaQueryListener, a function literal at line 132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ImportColumn.resolveRelatedRecords (cognitive 23) packages/actions/src/Imports/ImportColumn.php:512— ImportColumn.resolveRelatedRecords has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (3 pts), ternaries 2 (3 pts), boolean chains 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.
DateTimePicker.getDateLimitValidationRule (cognitive 23) packages/forms/src/Components/DateTimePicker.php:809— DateTimePicker.getDateLimitValidationRule has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (7 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (2 pts) (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.
Type.setUp (cognitive 23) packages/forms/src/Components/MorphToSelect/Type.php:69— Type.setUp has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14, ternaries 4 (6 pts), boolean chains 2, loops 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, 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.
TableSelect.fillStateFromRelationship (cognitive 23) packages/forms/src/Components/TableSelect.php:107— TableSelect.fillStateFromRelationship has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 2 (5 pts), boolean chains 4 (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.
SelectFilter.apply (cognitive 23) packages/tables/src/Filters/SelectFilter.php:185— SelectFilter.apply has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 3). 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.
rich-editor.richEditorFormComponent.mountToolAction (cognitive 23) packages/forms/resources/js/components/rich-editor.js:827— rich-editor.richEditorFormComponent.mountToolAction has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, ternaries 4 (5 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 872, 861, 878, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Select.getSelectedOptionLabels (cognitive 23) packages/support/resources/js/utilities/select.js:1696— Select.getSelectedOptionLabels has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 3 (7 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.
handleSearch (cognitive 23) packages/support/resources/js/utilities/select.js:1730— handleSearch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8, ternaries 2, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 1771). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
_toggleBlock (cognitive 23) REDACTED:1481— _toggleBlock has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, ternaries 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.
InteractsWithToolbarButtons.applyEnableToolbarButtonsModification (cognitive 22) packages/forms/src/Components/Concerns/InteractsWithToolbarButtons.php:194— InteractsWithToolbarButtons.applyEnableToolbarButtonsModification has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (4 pts), boolean chains 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.
MakeRelationManagerCommand.handle (cognitive 22) packages/panels/src/Commands/MakeRelationManagerCommand.php:239— MakeRelationManagerCommand.handle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, 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.
HasState.dehydrateState (cognitive 22) packages/schemas/src/Components/Concerns/HasState.php:322— HasState.dehydrateState has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 12). 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.
Icon.toEmbeddedHtml (cognitive 22) packages/schemas/src/Components/Icon.php:78— Icon.toEmbeddedHtml has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 6, loops 1 (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.
InteractsWithSchemas.loadDeferredSchema (cognitive 22) packages/schemas/src/Concerns/InteractsWithSchemas.php:138— InteractsWithSchemas.loadDeferredSchema has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 5, loops 2 (3 pts) (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.
EasyMDE.toggleSideBySide (cognitive 22) REDACTED:1100— EasyMDE.toggleSideBySide has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 7 belong to 2 function items inside it that branch. 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.
markdown-editor.markdownEditorFormComponent.init (cognitive 22) packages/forms/resources/js/components/markdown-editor.js:121— markdown-editor.markdownEditorFormComponent.init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 182, 233, 256, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
modal.default (cognitive 22) packages/support/resources/js/components/modal.js:49— modal.default has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15, boolean chains 7. Of this number, 11 points are the body's own statements and 11 belong to 6 function items inside it that branch. 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.
one-time-code.default (cognitive 22) packages/support/resources/js/components/one-time-code.js:1— one-time-code.default has cognitive complexity 22 (threshold 15). Drivers by points: if/else 18, boolean chains 3, ternaries 1. Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 152, 61, 26, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
tabsSchemaComponent.init (cognitive 22) packages/schemas/resources/js/components/tabs.js:52— tabsSchemaComponent.init has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 5 (nesting depth added 3). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 11 function items inside it that branch (boundFocusHandler, boundResetHandler, a function literal at line 89, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
addProseMirrorPlugins (cognitive 22) packages/forms/resources/js/components/rich-editor/extension-custom-block.js:251— addProseMirrorPlugins has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). None of this is in the body itself: all 22 points belong to 15 function items inside it that branch (hydrateCustomBlockPreviews, a function literal at line 269, a function literal at line 372, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Repeater.saveToRelationship (cognitive 21) packages/forms/src/Components/Repeater.php:1034— Repeater.saveToRelationship has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 1 (3 pts), loops 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.
RichEditor.getGroupedCustomBlocks (cognitive 21) packages/forms/src/Components/RichEditor.php:1463— RichEditor.getGroupedCustomBlocks has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (7 pts), if/else 3 (4 pts), boolean chains 2 (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.
RichContentFaker.insertInlineNode (cognitive 21) packages/forms/src/Components/RichEditor/RichContentFaker.php:659— RichContentFaker.insertInlineNode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, ternaries 2 (3 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.
InteractsWithSchemas.cacheSchema (cognitive 21) packages/schemas/src/Concerns/InteractsWithSchemas.php:350— InteractsWithSchemas.cacheSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (21 pts) (nesting depth added 5). 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.
Schema.renderEmbeddedHtml (cognitive 21) packages/schemas/src/Schema.php:169— Schema.renderEmbeddedHtml has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 5, boolean chains 3, 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.
reordering.reordering.reconcile (cognitive 21) packages/forms/resources/js/utilities/reordering.js:300— reordering.reordering.reconcile has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 8 (nesting depth added 6). Of this number, 18 points are the body's own statements and 3 belong to 3 function literals inside it that branch. 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.
EasyMDE.togglePreview (cognitive 21) REDACTED:1177— EasyMDE.togglePreview has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (4 pts), boolean chains 1, ternaries 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.
(anonymous) (cognitive 21) packages/schemas/resources/js/index.js:116— (anonymous) has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2, error handling 2, loops 2 (nesting depth added 2). None of this is in the body itself: all 21 points belong to 20 function items inside it that branch (a function literal at line 197, a function literal at line 129, a function literal at line 266, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ImporterClassGenerator.getImporterColumns (cognitive 20) packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:116— ImporterClassGenerator.getImporterColumns has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 2, boolean chains 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.
BaseFileUpload.getValidationRules (cognitive 20) packages/forms/src/Components/BaseFileUpload.php:710— BaseFileUpload.getValidationRules has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (3 pts), ternaries 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.
KeyValue.toEmbeddedHtml (cognitive 20) packages/forms/src/Components/KeyValue.php:376— KeyValue.toEmbeddedHtml has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 3. 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.
ModalTableSelect.saveStateToRelationship (cognitive 20) packages/forms/src/Components/ModalTableSelect.php:584— ModalTableSelect.saveStateToRelationship has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5 (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.
Select.saveStateToRelationship (cognitive 20) packages/forms/src/Components/Select.php:1341— Select.saveStateToRelationship has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5 (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.
HasComponents.discoverComponents (cognitive 20) packages/panels/src/Panel/Concerns/HasComponents.php:501— HasComponents.discoverComponents has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, ternaries 1 (2 pts), 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.
Page.getResourceBreadcrumbs (cognitive 20) packages/panels/src/Resources/Pages/Page.php:237— Page.getResourceBreadcrumbs has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (2 pts) (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.
HasState.hydrateState (cognitive 20) packages/schemas/src/Components/Concerns/HasState.php:475— HasState.hydrateState has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), boolean chains 3 (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.
OptionsArrayStateCast.get (cognitive 20) packages/schemas/src/Components/StateCasts/OptionsArrayStateCast.php:19— OptionsArrayStateCast.get has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8 (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.
CanSearchRecords.applyGlobalSearchToTableQuery (cognitive 20) packages/tables/src/Concerns/CanSearchRecords.php:140— CanSearchRecords.applyGlobalSearchToTableQuery has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (5 pts) (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.
HasBulkActions.getAllSelectableTableRecordKeys (cognitive 20) packages/tables/src/Concerns/HasBulkActions.php:97— HasBulkActions.getAllSelectableTableRecordKeys has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (9 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.
HasBulkActions.getGroupedSelectableTableRecordKeys (cognitive 20) packages/tables/src/Concerns/HasBulkActions.php:151— HasBulkActions.getGroupedSelectableTableRecordKeys has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 4 (8 pts), boolean chains 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.
UpgradeDirectoryStructureToV4Command.moveClass (cognitive 20) packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:324— UpgradeDirectoryStructureToV4Command.moveClass has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 8 (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.
ConvertStaticConfigurationToConfigureUsingFunction.refactor (cognitive 20) packages/upgrade/src/Rector/ConvertStaticConfigurationToConfigureUsingFunction.php:77— ConvertStaticConfigurationToConfigureUsingFunction.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (6 pts), ternaries 1 (2 pts) (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.
EasyMDE.toggleFullScreen (cognitive 20) REDACTED:411— EasyMDE.toggleFullScreen has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, ternaries 1 (2 pts) (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.
(anonymous) (cognitive 20) packages/support/resources/js/utilities/pluralize.js:2— (anonymous) has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 2, ternaries 2, other 1 (nesting depth added 2). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (extractFromString, extract, replace, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tabsSchemaComponent.scrollOverflow (cognitive 20) packages/schemas/resources/js/components/tabs.js:377— tabsSchemaComponent.scrollOverflow has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (9 pts), ternaries 1 (nesting depth added 1). 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.
reordering::reconcile (cognitive 20) packages/forms/resources/js/utilities/reordering.js:300— reordering::reconcile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, other 2 (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.
uploadImage (cognitive 20) REDACTED:2849— uploadImage has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, ternaries 1 (2 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 7 function items inside it that branch (onload, onErrorSup, onprogress, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
InteractsWithActions.unmountAction (cognitive 19) packages/actions/src/Concerns/InteractsWithActions.php:915— InteractsWithActions.unmountAction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts), error handling 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.
InteractsWithSchemas.getSchemaComponentForFileUpload (cognitive 19) packages/schemas/src/Concerns/InteractsWithSchemas.php:707— InteractsWithSchemas.getSchemaComponentForFileUpload has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts), boolean chains 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.
InstallCommand.ignorePublishedAssets (cognitive 19) packages/support/src/Commands/InstallCommand.php:210— InstallCommand.ignorePublishedAssets has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 4 (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.
SelectColumn.toEmbeddedHtml (cognitive 19) packages/tables/src/Columns/SelectColumn.php:935— SelectColumn.toEmbeddedHtml has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 4 (5 pts), loops 1 (2 pts), boolean chains 1 (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.
AddTraitByTraitRector.refactor (cognitive 19) packages/upgrade/src/Rector/AddTraitByTraitRector.php:48— AddTraitByTraitRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (6 pts) (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.
EasyMDE.getState (cognitive 19) REDACTED:362— EasyMDE.getState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, loops 1 (nesting depth added 3). 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.
tabs.tabsSchemaComponent.scrollOverflow (cognitive 19) packages/schemas/resources/js/components/tabs.js:377— tabs.tabsSchemaComponent.scrollOverflow has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), ternaries 1 (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.
index.document.addEventListener("alpine:init") (cognitive 19) packages/schemas/resources/js/index.js:116— index.document.addEventListener("alpine:init") has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, loops 2, error handling 1 (nesting depth added 2). None of this is in the body itself: all 19 points belong to 7 function literals inside it that branch (lines 119, 197, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
pluralize.default (cognitive 19) packages/support/resources/js/utilities/pluralize.js:2— pluralize.default has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, loops 2, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (extractFromString, extract, replace). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
normalizeListItemContent (cognitive 19) packages/forms/resources/js/components/rich-editor/normalize-list-item-content.js:1— normalizeListItemContent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 1 (2 pts), other 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.
Action.canRenderOptimizedGrouped (cognitive 18) packages/actions/src/Action.php:930— Action.canRenderOptimizedGrouped has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 18. 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.
InteractsWithActions.mountAction (cognitive 18) packages/actions/src/Concerns/InteractsWithActions.php:224— InteractsWithActions.mountAction has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), error handling 4, loops 1 (2 pts), boolean chains 1 (nesting depth added 3). 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.
RichContentRenderer.customBlocks (cognitive 18) packages/forms/src/Components/RichEditor/RichContentRenderer.php:629— RichContentRenderer.customBlocks has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 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.
CanGenerateUrls.getUrl (cognitive 18) packages/panels/src/Resources/Resource/Concerns/CanGenerateUrls.php:16— CanGenerateUrls.getUrl has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 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.
Actions.toEmbeddedHtml (cognitive 18) packages/schemas/src/Components/Actions.php:180— Actions.toEmbeddedHtml has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 5, loops 1 (2 pts) (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.
HasState.getConstantStateFromRecord (cognitive 18) packages/schemas/src/Components/Concerns/HasState.php:1087— HasState.getConstantStateFromRecord has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4 (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.
SpatieMediaLibraryFileUpload.setUp (cognitive 18) packages/spatie-laravel-media-library-plugin/src/Forms/Components/SpatieMediaLibraryFileUpload.php:52— SpatieMediaLibraryFileUpload.setUp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 3, error handling 2 (3 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 3). 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.
AssetsCommand.handle (cognitive 18) packages/support/src/Commands/AssetsCommand.php:23— AssetsCommand.handle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 6 (7 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.
CanAskForResource.askForResource (cognitive 18) packages/support/src/Commands/Concerns/CanAskForResource.php:16— CanAskForResource.askForResource has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (2 pts), boolean chains 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.
HasCluster.askForCluster (cognitive 18) packages/support/src/Commands/Concerns/HasCluster.php:27— HasCluster.askForCluster has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, match/switch 1 (2 pts) (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.
Summarizer.getState (cognitive 18) packages/tables/src/Columns/Summarizers/Summarizer.php:72— Summarizer.getState has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, ternaries 1 (2 pts) (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.
TextColumn.toOptimizedHtml (cognitive 18) packages/tables/src/Columns/TextColumn.php:216— TextColumn.toOptimizedHtml has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 3). 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.
HasBulkActions.getSelectedTableRecords (cognitive 18) packages/tables/src/Concerns/HasBulkActions.php:251— HasBulkActions.getSelectedTableRecords has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 2 (4 pts), 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.
UpgradeDirectoryStructureToV4Command.handle (cognitive 18) packages/upgrade/src/Commands/UpgradeDirectoryStructureToV4Command.php:54— UpgradeDirectoryStructureToV4Command.handle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 6). 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.
sidebar.default (cognitive 18) packages/panels/resources/js/stores/sidebar.js:1— sidebar.default has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4 (nesting depth added 2). Of this number, 11 points are the body's own statements and 7 belong to 5 function literals inside it that branch. 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.
getLabelForSingleSelection (cognitive 18) packages/support/resources/js/utilities/select.js:925— getLabelForSingleSelection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, error handling 1 (2 pts) (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.
colorPickerFormComponent (cognitive 18) packages/forms/resources/js/components/color-picker.js:6— colorPickerFormComponent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, boolean chains 3, ternaries 2 (3 pts) (nesting depth added 1). None of this is in the body itself: all 18 points belong to 13 function items inside it that branch (init, a function literal at line 50, a function literal at line 33, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ImportAction.setUp (cognitive 17) packages/actions/src/ImportAction.php:81— ImportAction.setUp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, loops 2 (3 pts), boolean chains 2, error handling 1 (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.
Select.resolveOptionLabel (cognitive 17) packages/forms/src/Components/Select.php:580— Select.resolveOptionLabel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 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.
IconEntry.toEmbeddedHtml (cognitive 17) packages/infolists/src/Components/IconEntry.php:262— IconEntry.toEmbeddedHtml has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 6 (7 pts), loops 1, match/switch 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.
Component.toSchemaHtml (cognitive 17) packages/schemas/src/Components/Component.php:135— Component.toSchemaHtml has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 6, boolean chains 2, match/switch 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.
HasChildComponents.getChildSchema (cognitive 17) packages/schemas/src/Components/Concerns/HasChildComponents.php:105— HasChildComponents.getChildSchema has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 5, 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.
OptionStateCast.get (cognitive 17) packages/schemas/src/Components/StateCasts/OptionStateCast.php:16— OptionStateCast.get has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (8 pts) (nesting depth added 1). 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.
Tabs.getActiveTab (cognitive 17) packages/schemas/src/Components/Tabs.php:147— Tabs.getActiveTab has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (6 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.
Wizard.getStartStep (cognitive 17) packages/schemas/src/Components/Wizard.php:312— Wizard.getStartStep has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (6 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.
HasStateBindingModifiers.getStateBindingModifiers (cognitive 17) packages/schemas/src/Concerns/HasStateBindingModifiers.php:83— HasStateBindingModifiers.getStateBindingModifiers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (6 pts) (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.
CanManipulateFiles.getRelativePath (cognitive 17) packages/support/src/Commands/Concerns/CanManipulateFiles.php:85— CanManipulateFiles.getRelativePath has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 12, if/else 3, loops 1, ternaries 1. 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.
EvaluatesClosures.resolveClosureDependencyForEvaluation (cognitive 17) packages/support/src/Concerns/EvaluatesClosures.php:43— EvaluatesClosures.resolveClosureDependencyForEvaluation has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 7 (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.
SelectColumn.getOptionLabel (cognitive 17) packages/tables/src/Columns/SelectColumn.php:394— SelectColumn.getOptionLabel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 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.
rich-editor.richEditorFormComponent.syncToolbarTools (cognitive 17) packages/forms/resources/js/components/rich-editor.js:603— rich-editor.richEditorFormComponent.syncToolbarTools has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
toggleButtonsFormComponent (cognitive 17) packages/forms/resources/js/components/toggle-buttons.js:1— toggleButtonsFormComponent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 2, other 1 (nesting depth added 4). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 9 function items inside it that branch (select, a function literal at line 56, isSelected, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ListTranslations.__invoke (cognitive 16) bin/TranslationTool/src/Commands/ListTranslations.php:11— ListTranslations.__invoke has cognitive complexity 16 (threshold 15). Drivers by points: loops 3 (6 pts), if/else 2 (5 pts), ternaries 1 (4 pts), boolean chains 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.
ExporterClassGenerator.getExporterColumns (cognitive 16) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:114— ExporterClassGenerator.getExporterColumns has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (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.
InteractsWithRecord.getRecord (cognitive 16) packages/actions/src/Concerns/InteractsWithRecord.php:99— InteractsWithRecord.getRecord has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 1. 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.
EditAction.setUp (cognitive 16) packages/actions/src/EditAction.php:28— EditAction.setUp has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (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.
ImportColumn.getDataValidationRules (cognitive 16) packages/actions/src/Imports/ImportColumn.php:408— ImportColumn.getDataValidationRules has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 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.
CanBeValidated.distinct (cognitive 16) packages/forms/src/Components/Concerns/CanBeValidated.php:647— CanBeValidated.distinct has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 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.
RepeatableEntry.getItemState (cognitive 16) packages/infolists/src/Components/RepeatableEntry.php:128— RepeatableEntry.getItemState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (4 pts), loops 1 (2 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.
Notification.toEmbeddedHtml (cognitive 16) packages/notifications/src/Notification.php:354— Notification.toEmbeddedHtml has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, loops 1 (2 pts), 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.
HasSubNavigation.getCachedSubNavigation (cognitive 16) packages/panels/src/Pages/Concerns/HasSubNavigation.php:52— HasSubNavigation.getCachedSubNavigation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (6 pts), loops 3 (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.
HasState.searchOtherComponentWithStatePath (cognitive 16) packages/schemas/src/Components/Concerns/HasState.php:406— HasState.searchOtherComponentWithStatePath has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, loops 2 (3 pts) (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.
HasState.getState (cognitive 16) packages/schemas/src/Concerns/HasState.php:587— HasState.getState has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 1 (2 pts) (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.
IconColumn.toEmbeddedHtml (cognitive 16) packages/tables/src/Columns/IconColumn.php:283— IconColumn.toEmbeddedHtml has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 5 (6 pts), boolean chains 1, loops 1, match/switch 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.
TextColumn.canRenderOptimized (cognitive 16) packages/tables/src/Columns/TextColumn.php:187— TextColumn.canRenderOptimized has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 14, if/else 2. 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.
HasFilters.removeTableFilter (cognitive 16) packages/tables/src/Concerns/HasFilters.php:77— HasFilters.removeTableFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (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.
extensions.default (cognitive 16) packages/forms/resources/js/components/rich-editor/extensions.js:41— extensions.default has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4, boolean chains 2, error handling 1, loops 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
createOptionElement (cognitive 16) packages/support/resources/js/utilities/select.js:507— createOptionElement has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 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.
interceptNotificationRequest (cognitive 16) packages/notifications/resources/js/components/notifications.js:110— interceptNotificationRequest has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, other 1 (nesting depth added 1). None of this is in the body itself: all 16 points belong to 8 function items inside it that branch (capture, a function literal at line 136, a function literal at line 162, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
fileUploadFormComponent::init (cognitive 16) packages/forms/resources/js/components/file-upload.js:130— fileUploadFormComponent::init has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 5, other 1, ternaries 1. 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.
selectTableColumn (cognitive 16) packages/tables/resources/js/components/columns/select.js:7— selectTableColumn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 2). None of this is in the body itself: all 16 points belong to 7 function items inside it that branch (syncServerState, a function literal at line 117, init::syncAccessibilityAttributes, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 16) packages/forms/resources/js/components/rich-editor/extensions.js:41— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 4, boolean chains 2, error handling 1, loops 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to 3 function items inside it that branch. 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.
createSideBySide (cognitive 16) REDACTED:3048— createSideBySide has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
Change coupling clique: DisableAppAuthenticationAction.php, RegenerateAppAuthenticationRecoveryCodesAction.php, SetUpAppAuthenticationAction.php, AppAuthentication.php, DisableEmailAuthenticationAction.php, SetUpEmailAuthenticationAction.php packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php— 6 files — `packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php`, `packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php`, `packages/panels/src/Auth/MultiFactor/App/Actions/SetUpAppAuthenticationAction.php`, `packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php`, `packages/panels/src/Auth/MultiFactor/Email/Actions/DisableEmailAuthenticationAction.php`, `packages/panels/src/Auth/MultiFactor/Email/Actions/SetUpEmailAuthenticationAction.php` — all change together with no explicit dependency: a fully-connected co-change clique, not 15 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.
D4 · Code Duplication· Near-duplicate member family (5 members, 37 shared lines) · ×1
Near-duplicate member family (5 members, 37 shared lines) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:48— packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:48-159 | packages/support/src/View/Concerns/CanGenerateButtonHtml.php:56-257 | packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:49-156 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:51-169 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:56-197 — These 5 members are variants of one another: a block of 37 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 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· Near-duplicate member family (4 members, 30 shared lines) · ×1
Near-duplicate member family (4 members, 30 shared lines) packages/forms/src/Components/Builder.php:1655— packages/forms/src/Components/Builder.php:1655-1957 | packages/forms/src/Components/Repeater.php:1567-1811 | packages/forms/src/Components/Repeater.php:1816-1954 | packages/forms/src/Components/Repeater.php:1959-2193 — These 4 members are variants of one another: a block of 30 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· Near-duplicate member family (4 members, 11 shared lines) · ×1
Near-duplicate member family (4 members, 11 shared lines) packages/actions/src/Action.php:1014— packages/actions/src/Action.php:1014-1044 | packages/actions/src/Action.php:1049-1084 | packages/actions/src/Action.php:1123-1154 | packages/actions/src/Action.php:1159-1192 — These 4 members are variants of one another: a block of 11 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.
Near-duplicate member pair (128 shared lines) packages/forms/src/Components/ModalTableSelect.php:434— packages/forms/src/Components/ModalTableSelect.php:434-581 | packages/forms/src/Components/Select.php:1190-1338 — These two members are variants of one another: 128 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (108 shared lines) packages/forms/src/Components/ToggleButtons.php:95— packages/forms/src/Components/ToggleButtons.php:95-223 | packages/forms/src/Components/ToggleButtons.php:228-342 — These two members are variants of one another: 108 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (92 shared lines) packages/actions/src/AssociateAction.php:219— packages/actions/src/AssociateAction.php:219-355 | packages/actions/src/AttachAction.php:220-364 — These two members are variants of one another: 92 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (69 shared lines) packages/forms/src/Components/ModalTableSelect.php:340— packages/forms/src/Components/ModalTableSelect.php:340-429 | packages/forms/src/Components/Select.php:800-996 — These two members are variants of one another: 69 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:245— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:245-279 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:245-279 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:287— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:287-303 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:287-303 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (11 members, 50+ identical tokens) packages/infolists/src/Components/CodeEntry.php:78— packages/infolists/src/Components/CodeEntry.php:78-218 | packages/infolists/src/Components/ColorEntry.php:23-141 | packages/infolists/src/Components/IconEntry.php:264-375 | packages/infolists/src/Components/ImageEntry.php:470-607 | packages/infolists/src/Components/RepeatableEntry.php:196-247 | packages/infolists/src/Components/RepeatableEntry.php:252-345 | packages/infolists/src/Components/TextEntry.php:179-601 | packages/tables/src/Columns/ColorColumn.php:23-135 | packages/tables/src/Columns/IconColumn.php:285-393 | packages/tables/src/Columns/ImageColumn.php:463-601 | packages/tables/src/Columns/TextColumn.php:276-707 — These 11 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 11 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 11 times.
D4 · Code Duplication· Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (9 members, 50+ identical tokens) packages/forms/src/Components/ModalTableSelect.php:739— packages/forms/src/Components/ModalTableSelect.php:739-770 | packages/forms/src/Components/Select.php:1529-1560 | packages/forms/src/Components/TableSelect.php:341-372 | packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php:257-280 | packages/schemas/src/Components/Concerns/CanGetStateFromRelationships.php:22-55 | packages/tables/src/Columns/SelectColumn.php:827-860 | packages/tables/src/Filters/Concerns/HasRelationship.php:58-87 | packages/tables/src/Grouping/Group.php:439-462 | packages/tables/src/Table/Concerns/CanSearchRecords.php:250-273 — These 9 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 9 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 9 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) packages/panels/src/Commands/MakeClusterCommand.php:152— packages/panels/src/Commands/MakeClusterCommand.php:152-186 | packages/panels/src/Commands/MakePageCommand.php:322-364 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:156-194 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:221-259 | packages/support/src/Commands/Concerns/CanAskForRelatedModel.php:18-40 | packages/support/src/Commands/Concerns/CanAskForSchema.php:16-41 | packages/widgets/src/Commands/MakeWidgetCommand.php:311-362 — These 7 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 7 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 7 times.
Duplicated block (86 lines × 2) packages/forms/src/Components/ModalTableSelect.php:586— packages/forms/src/Components/ModalTableSelect.php:586-671 | packages/forms/src/Components/Select.php:1343-1428 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:586` 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 (70 lines × 2) packages/infolists/src/Components/Concerns/CanFormatState.php:380— packages/infolists/src/Components/Concerns/CanFormatState.php:380-449 | packages/tables/src/Columns/Concerns/CanFormatState.php:388-457 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/Concerns/CanFormatState.php:380` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/infolists/src/Components/Concerns/CanFormatState.php:378` calls `formatState` and `packages/tables/src/Columns/Concerns/CanFormatState.php:386` 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 (69–70 lines × 2) packages/infolists/src/Components/ImageEntry.php:535— packages/infolists/src/Components/ImageEntry.php:535-604 | packages/tables/src/Columns/ImageColumn.php:530-598 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/infolists/src/Components/ImageEntry.php:534` calls `getAlignment` and `packages/tables/src/Columns/ImageColumn.php:528` does not — after which the two agree again for 4 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 (55 lines × 2) packages/forms/src/Components/Concerns/HasHint.php:35— packages/forms/src/Components/Concerns/HasHint.php:35-89 | packages/infolists/src/Components/Concerns/HasHint.php:34-88 — before extracting anything, compare `packages/forms/src/Components/Concerns/HasHint.php` and `packages/infolists/src/Components/Concerns/HasHint.php` as WHOLE FILES: 96% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Concerns/HasHint.php:35` 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 (51 lines × 2) packages/forms/src/Components/ToggleButtons.php:130— packages/forms/src/Components/ToggleButtons.php:130-180 | packages/forms/src/Components/ToggleButtons.php:251-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/ToggleButtons.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 (49–50 lines × 2) packages/tables/src/Columns/ColorColumn.php:23— packages/tables/src/Columns/ColorColumn.php:23-71 | packages/tables/src/Columns/IconColumn.php:285-334 — before extracting anything, compare `packages/tables/src/Columns/ColorColumn.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 133 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 (49 lines × 2) packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:117— packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:117-165 | packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:179-227 — 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 `packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:117` 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 (46 lines × 2) packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:141— packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:141-186 | packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php:141-186 — before extracting anything, compare `packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php` and `packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 137 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 (45 lines × 2) packages/actions/src/AssociateAction.php:227— packages/actions/src/AssociateAction.php:227-271 | packages/actions/src/AttachAction.php:232-276 — before extracting anything, compare `packages/actions/src/AssociateAction.php` and `packages/actions/src/AttachAction.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 103 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 (44–45 lines × 2) packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:43— packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:43-86 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:62-106 — before extracting anything, compare `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php` and `packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:43` 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 (43 lines × 3) packages/actions/src/DeleteBulkAction.php:31— packages/actions/src/DeleteBulkAction.php:31-73 | packages/actions/src/ForceDeleteBulkAction.php:31-73 | packages/actions/src/RestoreBulkAction.php:31-73 — before extracting anything, compare `packages/actions/src/ForceDeleteBulkAction.php` and `packages/actions/src/RestoreBulkAction.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 `packages/actions/src/DeleteBulkAction.php:31` 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 (41 lines × 2) packages/forms/src/Components/Select.php:1217— packages/forms/src/Components/Select.php:1217-1257 | packages/forms/src/Components/TableSelect.php:132-172 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 312 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 `packages/forms/src/Components/Select.php:1217` 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 (40–41 lines × 2) packages/forms/src/Components/ToggleButtons.php:183— packages/forms/src/Components/ToggleButtons.php:183-223 | packages/forms/src/Components/ToggleButtons.php:303-342 — 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 `packages/forms/src/Components/ToggleButtons.php:183` 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 (38–39 lines × 2) packages/infolists/src/Components/ImageEntry.php:476— packages/infolists/src/Components/ImageEntry.php:476-513 | packages/tables/src/Columns/ImageColumn.php:471-509 — before extracting anything, compare `packages/infolists/src/Components/ImageEntry.php` and `packages/tables/src/Columns/ImageColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 234 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/ImageEntry.php:476` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/tables/src/Columns/ImageColumn.php:469` calls `getAlignment` and `packages/infolists/src/Components/ImageEntry.php:474` does not — after which the two agree again for 4 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 (38 lines × 4) packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php:63— packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php:63-100 | packages/query-builder/src/Constraints/TextConstraint/Operators/EndsWithOperator.php:63-100 | packages/query-builder/src/Constraints/TextConstraint/Operators/EqualsOperator.php:63-100 | packages/query-builder/src/Constraints/TextConstraint/Operators/StartsWithOperator.php:63-100 — before extracting anything, compare `packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php` and `packages/query-builder/src/Constraints/TextConstraint/Operators/EndsWithOperator.php` as WHOLE FILES: 86% 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 `packages/query-builder/src/Constraints/TextConstraint/Operators/ContainsOperator.php:63` 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 (35–38 lines × 2) packages/support/src/Commands/Concerns/CanAskForComponentLocation.php:24— packages/support/src/Commands/Concerns/CanAskForComponentLocation.php:24-61 | packages/support/src/Commands/Concerns/CanAskForLivewireComponentLocation.php:44-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.
Duplicated block (37 lines × 2) packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:126— packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:126-162 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:141-177 — before extracting anything, compare `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php` and `packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 146 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:126` 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 (33 lines × 3) packages/infolists/src/Components/CodeEntry.php:78— packages/infolists/src/Components/CodeEntry.php:78-110 | packages/infolists/src/Components/ColorEntry.php:23-55 | packages/infolists/src/Components/IconEntry.php:264-296 — before extracting anything, compare `packages/infolists/src/Components/CodeEntry.php` and `packages/infolists/src/Components/ColorEntry.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 `packages/infolists/src/Components/CodeEntry.php:78` 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 (31–32 lines × 2) packages/forms/src/Components/ModalTableSelect.php:485— packages/forms/src/Components/ModalTableSelect.php:485-515 | packages/forms/src/Components/Select.php:1243-1274 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:485` 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 (32 lines × 2) packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:153— packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:153-184 | packages/panels/src/Resources/Pages/ListRecords.php:137-168 — 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 `packages/panels/src/Resources/Concerns/InteractsWithRelationshipTable.php:153` 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 (28–31 lines × 2) packages/forms/src/Components/Field.php:383— packages/forms/src/Components/Field.php:383-413 | packages/schemas/src/Components/FusedGroup.php:300-327 — before extracting anything, compare `packages/forms/src/Components/Field.php` and `packages/schemas/src/Components/FusedGroup.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Field.php:383` 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 (26–30 lines × 4) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:72— packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:72-97 | packages/support/src/View/Concerns/CanGenerateButtonHtml.php:91-120 | packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:68-93 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:94-123 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php` and `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 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 `packages/support/src/View/Concerns/CanGenerateButtonHtml.php:91` 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.
Duplicated block (30 lines × 3) packages/forms/src/Components/ModalTableSelect.php:478— packages/forms/src/Components/ModalTableSelect.php:478-507 | packages/forms/src/Components/Select.php:1236-1265 | packages/forms/src/Components/TableSelect.php:151-180 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:478` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/ModalTableSelect.php:477` calls `strval` and `packages/forms/src/Components/Select.php:1235` does not — after which the two agree again for 4 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 (26–30 lines × 2) packages/forms/src/Components/Builder.php:1852— packages/forms/src/Components/Builder.php:1852-1881 | packages/forms/src/Components/Repeater.php:1746-1771 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:1852` 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 (30 lines × 2) packages/forms/src/Components/ModalTableSelect.php:515— packages/forms/src/Components/ModalTableSelect.php:515-544 | packages/forms/src/Components/TableSelect.php:182-211 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 322 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 `packages/forms/src/Components/ModalTableSelect.php:515` 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 (29 lines × 6) packages/forms/src/Components/Builder.php:1247— packages/forms/src/Components/Builder.php:1247-1275 | packages/schemas/src/Components/Concerns/HasContainerGridLayout.php:54-82 | packages/schemas/src/Concerns/HasColumns.php:78-106 | packages/support/src/Concerns/CanOrderColumns.php:54-82 | packages/support/src/Concerns/CanSpanColumns.php:92-120 | packages/support/src/Concerns/CanSpanColumns.php:144-172 — there are 6 copies across 5 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Builder.php:1247` 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 after the matched lines, `packages/support/src/Concerns/CanOrderColumns.php:85` calls `evaluate` and `packages/schemas/src/Concerns/HasColumns.php:108` 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 (27–29 lines × 5) packages/infolists/src/Components/CodeEntry.php:84— packages/infolists/src/Components/CodeEntry.php:84-110 | packages/infolists/src/Components/ColorEntry.php:29-55 | packages/infolists/src/Components/IconEntry.php:270-296 | packages/tables/src/Columns/ColorColumn.php:31-59 | packages/tables/src/Columns/IconColumn.php:293-321 — before extracting anything, compare `packages/infolists/src/Components/CodeEntry.php` and `packages/infolists/src/Components/ColorEntry.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 `packages/infolists/src/Components/CodeEntry.php:84` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/tables/src/Columns/ColorColumn.php:29` calls `getAlignment` and `packages/infolists/src/Components/CodeEntry.php:82` does not — after which the two agree again for 4 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 (25–29 lines × 3) packages/forms/src/Components/ModalTableSelect.php:526— packages/forms/src/Components/ModalTableSelect.php:526-554 | packages/forms/src/Components/Select.php:1288-1312 | packages/forms/src/Components/TableSelect.php:193-217 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:526` 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 after the matched lines, `packages/forms/src/Components/ModalTableSelect.php:555` calls `strval` and `packages/forms/src/Components/Select.php:1313` does not — after which the two agree again for 4 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 (27–28 lines × 3) packages/infolists/src/Components/ColorEntry.php:36— packages/infolists/src/Components/ColorEntry.php:36-62 | packages/infolists/src/Components/IconEntry.php:277-303 | packages/infolists/src/Components/ImageEntry.php:493-520 — before extracting anything, compare `packages/infolists/src/Components/ColorEntry.php` and `packages/infolists/src/Components/IconEntry.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 116 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 `packages/infolists/src/Components/ColorEntry.php:36` 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 (25–28 lines × 2) packages/forms/src/Components/Builder.php:316— packages/forms/src/Components/Builder.php:316-343 | packages/forms/src/Components/Repeater.php:292-316 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (27–28 lines × 2) packages/infolists/src/Components/RepeatableEntry.php:202— packages/infolists/src/Components/RepeatableEntry.php:202-229 | packages/infolists/src/Components/RepeatableEntry.php:255-281 — 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 `packages/infolists/src/Components/RepeatableEntry.php:202` 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 (22–27 lines × 5) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:70— packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:70-91 | packages/support/src/View/Concerns/CanGenerateButtonHtml.php:89-115 | packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:66-87 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:80-104 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:92-117 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php` and `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:105` calls `merge` and `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:92` 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 (27 lines × 3) packages/infolists/src/Components/Concerns/CanFormatState.php:439— packages/infolists/src/Components/Concerns/CanFormatState.php:439-465 | packages/tables/src/Columns/Concerns/CanFormatState.php:447-473 | packages/tables/src/Columns/Summarizers/Concerns/CanFormatState.php:182-208 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/tables/src/Columns/Summarizers/Concerns/CanFormatState.php:210` calls `blank`, `evaluate` and `packages/infolists/src/Components/Concerns/CanFormatState.php:467` 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 (26–27 lines × 2) packages/infolists/src/Components/TextEntry.php:190— packages/infolists/src/Components/TextEntry.php:190-216 | packages/tables/src/Columns/TextColumn.php:300-325 — before extracting anything, compare `packages/infolists/src/Components/TextEntry.php` and `packages/tables/src/Columns/TextColumn.php` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 202 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/infolists/src/Components/TextEntry.php:190` 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 (26 lines × 4) packages/forms/src/Components/ModalTableSelect.php:745— packages/forms/src/Components/ModalTableSelect.php:745-770 | packages/forms/src/Components/Select.php:1535-1560 | packages/forms/src/Components/TableSelect.php:347-372 | packages/tables/src/Filters/Concerns/HasRelationship.php:62-87 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 (26 lines × 3) packages/forms/src/Components/ModalTableSelect.php:556— packages/forms/src/Components/ModalTableSelect.php:556-581 | packages/forms/src/Components/Select.php:1313-1338 | packages/forms/src/Components/TableSelect.php:218-243 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:556` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/ModalTableSelect.php:555` calls `strval` and `packages/forms/src/Components/Select.php:1312` does not — after which the two agree again for 4 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 (18–26 lines × 2) packages/actions/src/Exports/Concerns/CanFormatState.php:135— packages/actions/src/Exports/Concerns/CanFormatState.php:135-160 | packages/actions/src/Imports/ContentGenerators/CsvImportFailureContentGenerator.php:26-43 — 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 (25 lines × 7) packages/infolists/src/Components/CodeEntry.php:90— packages/infolists/src/Components/CodeEntry.php:90-114 | packages/infolists/src/Components/ColorEntry.php:35-59 | packages/infolists/src/Components/IconEntry.php:276-300 | packages/infolists/src/Components/ImageEntry.php:492-517 | packages/infolists/src/Components/RepeatableEntry.php:209-233 | packages/infolists/src/Components/RepeatableEntry.php:261-285 | packages/infolists/src/Components/TextEntry.php:196-220 — before extracting anything, compare `packages/infolists/src/Components/CodeEntry.php` and `packages/infolists/src/Components/ColorEntry.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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 `packages/infolists/src/Components/CodeEntry.php:90` 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 after the matched lines, `packages/infolists/src/Components/RepeatableEntry.php:235` calls `grid`, `getGridColumns` and `packages/infolists/src/Components/RepeatableEntry.php:287` 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 (25 lines × 4) packages/tables/src/Columns/ColorColumn.php:39— packages/tables/src/Columns/ColorColumn.php:39-63 | packages/tables/src/Columns/IconColumn.php:301-325 | packages/tables/src/Columns/ImageColumn.php:489-513 | packages/tables/src/Columns/TextColumn.php:305-329 — before extracting anything, compare `packages/tables/src/Columns/ColorColumn.php` and `packages/tables/src/Columns/IconColumn.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 133 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 `packages/tables/src/Columns/ColorColumn.php:39` 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 (25 lines × 3) packages/forms/src/Commands/MakeFieldCommand.php:121— packages/forms/src/Commands/MakeFieldCommand.php:121-145 | packages/infolists/src/Commands/MakeEntryCommand.php:121-145 | packages/schemas/src/Commands/MakeComponentCommand.php:137-161 — before extracting anything, compare `packages/forms/src/Commands/MakeFieldCommand.php` and `packages/infolists/src/Commands/MakeEntryCommand.php` as WHOLE FILES: this scan already matched 5 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Commands/MakeFieldCommand.php:121` 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 (24 lines × 3) packages/query-builder/src/Constraints/RelationshipConstraint/Operators/EqualsOperator.php:57— packages/query-builder/src/Constraints/RelationshipConstraint/Operators/EqualsOperator.php:57-80 | packages/query-builder/src/Constraints/RelationshipConstraint/Operators/HasMaxOperator.php:57-80 | packages/query-builder/src/Constraints/RelationshipConstraint/Operators/HasMinOperator.php:57-80 — before extracting anything, compare `packages/query-builder/src/Constraints/RelationshipConstraint/Operators/EqualsOperator.php` and `packages/query-builder/src/Constraints/RelationshipConstraint/Operators/HasMaxOperator.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.
Duplicated block (21–24 lines × 2) packages/forms/src/Components/Builder.php:1798— packages/forms/src/Components/Builder.php:1798-1821 | packages/forms/src/Components/Repeater.php:1703-1723 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 `packages/forms/src/Components/Builder.php:1798` 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 (21–23 lines × 6) docs-assets/app/app/Livewire/TablesDemo.php:622— docs-assets/app/app/Livewire/TablesDemo.php:622-642 | docs-assets/app/app/Livewire/TablesDemo.php:647-667 | docs-assets/app/app/Livewire/TablesDemo.php:803-824 | docs-assets/app/app/Livewire/TablesDemo.php:829-851 | docs-assets/app/app/Livewire/TablesDemo.php:876-897 | docs-assets/app/app/Livewire/TablesDemo.php:902-924 — all 6 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 `docs-assets/app/app/Livewire/TablesDemo.php:622` 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 (23 lines × 4) packages/forms/src/Components/CheckboxList.php:361— packages/forms/src/Components/CheckboxList.php:361-383 | packages/forms/src/Components/ModalTableSelect.php:666-688 | packages/forms/src/Components/Select.php:1423-1445 | packages/forms/src/Components/TableSelect.php:307-329 — 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 4 call sites, so a change lands once.
Duplicated block (22 lines × 4) packages/actions/src/SelectAction.php:52— packages/actions/src/SelectAction.php:52-73 | packages/forms/src/Components/Concerns/HasOptions.php:38-59 | packages/query-builder/src/Constraints/SelectConstraint.php:130-151 | packages/tables/src/Filters/Concerns/HasOptions.php:40-61 — before extracting anything, compare `packages/query-builder/src/Constraints/SelectConstraint.php` and `packages/tables/src/Filters/Concerns/HasOptions.php` as WHOLE FILES: 87% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–22 lines × 4) packages/forms/src/Components/Field.php:245— packages/forms/src/Components/Field.php:245-266 | packages/infolists/src/Components/Entry.php:230-249 | packages/schemas/src/Components/Actions.php:150-165 | packages/schemas/src/Components/FusedGroup.php:201-218 — before extracting anything, compare `packages/forms/src/Components/Field.php` and `packages/schemas/src/Components/FusedGroup.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/schemas/src/Components/FusedGroup.php:199` calls `fieldWrapperView` and `packages/forms/src/Components/Field.php:243` does not — after which the two agree again for 4 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 (20–22 lines × 3) packages/forms/src/Components/Repeater.php:1792— packages/forms/src/Components/Repeater.php:1792-1811 | packages/forms/src/Components/Repeater.php:1934-1954 | packages/forms/src/Components/Repeater.php:2172-2193 — 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 `packages/forms/src/Components/Repeater.php:1792` 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 (18–22 lines × 2) packages/forms/src/Components/Field.php:521— packages/forms/src/Components/Field.php:521-542 | packages/schemas/src/Components/FusedGroup.php:403-420 — before extracting anything, compare `packages/forms/src/Components/Field.php` and `packages/schemas/src/Components/FusedGroup.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Field.php:521` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/Field.php:519` calls `filled` and `packages/schemas/src/Components/FusedGroup.php:400` 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.
Duplicated block (19–21 lines × 7) packages/actions/src/Commands/MakeExporterCommand.php:140— packages/actions/src/Commands/MakeExporterCommand.php:140-158 | packages/actions/src/Commands/MakeImporterCommand.php:147-165 | packages/forms/src/Commands/MakeFormCommand.php:153-171 | packages/forms/src/Commands/MakeLivewireFormCommand.php:184-202 | packages/panels/src/Commands/MakeResourceCommand.php:311-331 | packages/tables/src/Commands/MakeLivewireTableCommand.php:164-182 | packages/tables/src/Commands/MakeTableCommand.php:155-173 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/actions/src/Commands/MakeImporterCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 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 `packages/panels/src/Commands/MakeResourceCommand.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.
Duplicated block (20–21 lines × 3) packages/actions/src/Commands/MakeExporterCommand.php:118— packages/actions/src/Commands/MakeExporterCommand.php:118-137 | packages/actions/src/Commands/MakeImporterCommand.php:125-144 | packages/panels/src/Commands/MakeResourceCommand.php:288-308 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/actions/src/Commands/MakeImporterCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 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 `packages/actions/src/Commands/MakeExporterCommand.php:118` 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.
Duplicated block (20 lines × 4) packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:230— packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:230-249 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:180-199 | packages/spatie-laravel-settings-plugin/src/Commands/FileGenerators/SettingsPageClassGenerator.php:254-273 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:209-228 — before extracting anything, compare `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php` and `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:230` 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 (20 lines × 3) packages/forms/src/Commands/MakeLivewireFormCommand.php:235— packages/forms/src/Commands/MakeLivewireFormCommand.php:235-254 | packages/schemas/src/Commands/MakeLivewireSchemaCommand.php:121-140 | packages/tables/src/Commands/MakeLivewireTableCommand.php:195-214 — before extracting anything, compare `packages/forms/src/Commands/MakeLivewireFormCommand.php` and `packages/schemas/src/Commands/MakeLivewireSchemaCommand.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16–20 lines × 3) packages/forms/src/Components/Builder.php:1811— packages/forms/src/Components/Builder.php:1811-1826 | packages/forms/src/Components/Repeater.php:1713-1728 | packages/forms/src/Components/Repeater.php:2086-2105 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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 (19 lines × 3) packages/forms/src/Components/ModalTableSelect.php:458— packages/forms/src/Components/ModalTableSelect.php:458-476 | packages/forms/src/Components/Select.php:1217-1235 | packages/forms/src/Components/TableSelect.php:132-150 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:458` 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 after the matched lines, `packages/forms/src/Components/ModalTableSelect.php:477` calls `strval` and `packages/forms/src/Components/Select.php:1236` does not — after which the two agree again for 4 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 (13–19 lines × 2) packages/forms/src/Components/Select.php:1831— packages/forms/src/Components/Select.php:1831-1843 | packages/tables/src/Columns/SelectColumn.php:159-177 — before extracting anything, compare `packages/forms/src/Components/Select.php` and `packages/tables/src/Columns/SelectColumn.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 166 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 (18 lines × 5) packages/forms/src/Components/ModalTableSelect.php:749— packages/forms/src/Components/ModalTableSelect.php:749-766 | packages/forms/src/Components/Select.php:1539-1556 | packages/forms/src/Components/TableSelect.php:351-368 | packages/tables/src/Columns/SelectColumn.php:837-854 | packages/tables/src/Filters/Concerns/HasRelationship.php:66-83 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:749` 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 (17 lines × 5) packages/forms/src/Components/CheckboxList.php:258— packages/forms/src/Components/CheckboxList.php:258-274 | packages/forms/src/Components/Select.php:1045-1061 | packages/forms/src/Components/Select.php:1159-1175 | packages/tables/src/Columns/SelectColumn.php:643-659 | packages/tables/src/Columns/SelectColumn.php:707-723 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (16–17 lines × 2) packages/actions/src/Action.php:894— packages/actions/src/Action.php:894-909 | packages/actions/src/Action.php:977-993 — 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 `packages/actions/src/Action.php:894` 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 (16 lines × 6) packages/forms/src/Components/ModalTableSelect.php:749— packages/forms/src/Components/ModalTableSelect.php:749-764 | packages/forms/src/Components/Select.php:1539-1554 | packages/forms/src/Components/TableSelect.php:351-366 | packages/schemas/src/Components/Concerns/CanGetStateFromRelationships.php:38-53 | packages/tables/src/Columns/SelectColumn.php:837-852 | packages/tables/src/Filters/Concerns/HasRelationship.php:66-81 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 (16 lines × 4) packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:125— packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:125-140 | packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:53-68 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:39-54 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:58-73 — before extracting anything, compare `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php` and `packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 57 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:125` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:122` calls `getModelFqn` and `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:50` 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.
Duplicated block (12–16 lines × 4) packages/forms/src/Components/Builder.php:1813— packages/forms/src/Components/Builder.php:1813-1824 | packages/forms/src/Components/Repeater.php:1715-1726 | packages/forms/src/Components/Repeater.php:1899-1914 | packages/forms/src/Components/Repeater.php:2088-2103 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/Repeater.php:1916` calls `foreach`, `$extraItemAction`, `toHtml` and `packages/forms/src/Components/Builder.php:1825` 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 (16 lines × 3) packages/actions/src/Action.php:1054— packages/actions/src/Action.php:1054-1069 | packages/actions/src/Action.php:1128-1143 | packages/actions/src/Action.php:1164-1179 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/actions/src/Action.php:1071` calls `getIconPosition` and `packages/actions/src/Action.php:1145` 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 (15 lines × 5) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:123— packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:123-137 | packages/support/src/View/Concerns/CanGenerateButtonHtml.php:192-206 | packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php:108-122 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:129-143 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:150-164 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php` and `packages/support/src/View/Concerns/CanGenerateButtonHtml.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 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 `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:123` 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 (11–15 lines × 4) packages/forms/src/Components/ModalTableSelect.php:453— packages/forms/src/Components/ModalTableSelect.php:453-463 | packages/forms/src/Components/ModalTableSelect.php:517-531 | packages/forms/src/Components/TableSelect.php:127-137 | packages/forms/src/Components/TableSelect.php:184-198 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/TableSelect.php` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 322 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 `packages/forms/src/Components/ModalTableSelect.php:453` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/forms/src/Components/ModalTableSelect.php:533` calls `getResults` and `packages/forms/src/Components/ModalTableSelect.php:464` does not — after which the two agree again for 4 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 (13–15 lines × 4) packages/tables/src/Columns/Layout/Grid.php:74— packages/tables/src/Columns/Layout/Grid.php:74-88 | packages/tables/src/Columns/Layout/Panel.php:35-47 | packages/tables/src/Columns/Layout/Split.php:39-53 | packages/tables/src/Columns/Layout/Stack.php:54-68 — before extracting anything, compare `packages/tables/src/Columns/Layout/Panel.php` and `packages/tables/src/Columns/Layout/Split.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 `packages/tables/src/Columns/Layout/Grid.php:74` 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–15 lines × 3) packages/forms/src/Components/ModalTableSelect.php:413— packages/forms/src/Components/ModalTableSelect.php:413-427 | packages/forms/src/Components/Select.php:953-967 | packages/tables/src/Filters/SelectFilter.php:507-519 — before extracting anything, compare `packages/forms/src/Components/ModalTableSelect.php` and `packages/forms/src/Components/Select.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 556 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 `packages/forms/src/Components/ModalTableSelect.php:413` 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.
Duplicated block (14 lines × 8) packages/actions/src/Commands/MakeExporterCommand.php:141— packages/actions/src/Commands/MakeExporterCommand.php:141-154 | packages/actions/src/Commands/MakeImporterCommand.php:148-161 | packages/forms/src/Commands/MakeFormCommand.php:154-167 | packages/forms/src/Commands/MakeLivewireFormCommand.php:185-198 | packages/panels/src/Commands/MakeResourceCommand.php:314-327 | packages/tables/src/Commands/MakeLivewireTableCommand.php:165-178 | packages/tables/src/Commands/MakeTableCommand.php:156-169 | packages/widgets/src/Commands/MakeWidgetCommand.php:494-507 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/actions/src/Commands/MakeImporterCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `packages/widgets/src/Commands/MakeWidgetCommand.php:510` calls `confirm` and `packages/actions/src/Commands/MakeExporterCommand.php:155` 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 (14 lines × 5) packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:122— packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:122-135 | packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php:124-137 | packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:52-65 | packages/infolists/src/Commands/FileGenerators/Concerns/CanGenerateModelInfolists.php:38-51 | packages/tables/src/Commands/FileGenerators/Concerns/CanGenerateModelTables.php:57-70 — before extracting anything, compare `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php` and `packages/actions/src/Commands/FileGenerators/ImporterClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 71 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 `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:122` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/actions/src/Commands/FileGenerators/ExporterClassGenerator.php:120` calls `getModelFqn` and `packages/forms/src/Commands/FileGenerators/Concerns/CanGenerateModelForms.php:50` does not — after which the two agree again for 4 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 (4–14 lines × 4) packages/forms/src/Components/Field.php:424— packages/forms/src/Components/Field.php:424-436 | packages/schemas/src/Components/Actions.php:213-216 | packages/schemas/src/Components/FusedGroup.php:336-349 | packages/schemas/src/Components/Section.php:330-333 — before extracting anything, compare `packages/forms/src/Components/Field.php` and `packages/schemas/src/Components/FusedGroup.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Components/Field.php:424` 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–14 lines × 2) packages/forms/src/Components/RichEditor.php:1420— packages/forms/src/Components/RichEditor.php:1420-1431 | packages/forms/src/Components/RichEditor/RichContentAttribute.php:259-272 — 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 `packages/forms/src/Components/RichEditor.php:1420` 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–12 lines × 4) packages/forms/src/Components/Builder.php:1766— packages/forms/src/Components/Builder.php:1766-1777 | packages/forms/src/Components/Repeater.php:1671-1680 | packages/forms/src/Components/Repeater.php:1871-1880 | packages/forms/src/Components/Repeater.php:2063-2072 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/forms/src/Components/Repeater.php:1670` calls `getItemLabel` and `packages/forms/src/Components/Builder.php:1764` 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.
Duplicated block (11–12 lines × 2) packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:104— packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:104-114 | packages/panels/src/Auth/MultiFactor/App/Actions/RegenerateAppAuthenticationRecoveryCodesAction.php:83-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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:104` 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.
Duplicated block (9 lines × 7) packages/actions/src/DeleteAction.php:22— packages/actions/src/DeleteAction.php:22-30 | packages/actions/src/DetachAction.php:24-32 | packages/actions/src/DissociateAction.php:24-32 | packages/actions/src/EditAction.php:30-38 | packages/actions/src/ForceDeleteAction.php:22-30 | packages/actions/src/ReplicateAction.php:36-44 | packages/actions/src/RestoreAction.php:22-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 all 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `packages/actions/src/DeleteAction.php:22` 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.
Duplicated block (9 lines × 5) packages/actions/src/DeleteBulkAction.php:29— packages/actions/src/DeleteBulkAction.php:29-37 | packages/actions/src/DetachBulkAction.php:28-36 | packages/actions/src/DissociateBulkAction.php:29-37 | packages/actions/src/ForceDeleteBulkAction.php:29-37 | packages/actions/src/RestoreBulkAction.php:29-37 — before extracting anything, compare `packages/actions/src/ForceDeleteBulkAction.php` and `packages/actions/src/RestoreBulkAction.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 65 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 `packages/actions/src/DeleteBulkAction.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. 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 (8–9 lines × 3) packages/infolists/src/Components/CodeEntry.php:134— packages/infolists/src/Components/CodeEntry.php:134-141 | packages/infolists/src/Components/ColorEntry.php:80-88 | packages/tables/src/Columns/ColorColumn.php:81-89 — before extracting anything, compare `packages/infolists/src/Components/CodeEntry.php` and `packages/infolists/src/Components/ColorEntry.php` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 97 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. 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 × 6) packages/panels/src/Commands/MakeClusterCommand.php:175— packages/panels/src/Commands/MakeClusterCommand.php:175-181 | packages/panels/src/Commands/MakePageCommand.php:353-359 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:182-188 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:248-254 | packages/support/src/Commands/Concerns/CanAskForRelatedModel.php:28-34 | packages/widgets/src/Commands/MakeWidgetCommand.php:351-357 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakeClusterCommand.php:175` 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 (3–7 lines × 4) packages/forms/src/Components/Builder.php:1779— packages/forms/src/Components/Builder.php:1779-1781 | packages/forms/src/Components/Repeater.php:1682-1684 | packages/forms/src/Components/Repeater.php:1884-1890 | packages/forms/src/Components/Repeater.php:2076-2082 — before extracting anything, compare `packages/forms/src/Components/Builder.php` and `packages/forms/src/Components/Repeater.php` as WHOLE FILES: this scan already matched 23 separate duplicated blocks between them, totalling at least 347 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. 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 before the matched lines, `packages/forms/src/Components/Repeater.php:1883` calls `$moveUpAction`, `disabled`, `isDisabled` and `packages/forms/src/Components/Builder.php:1779` does not — after which the two agree again for 4 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 (6 lines × 8) packages/infolists/src/Components/Concerns/CanFormatState.php:70— packages/infolists/src/Components/Concerns/CanFormatState.php:70-75 | packages/infolists/src/Components/Concerns/CanFormatState.php:100-105 | packages/infolists/src/Components/Concerns/CanFormatState.php:143-148 | packages/infolists/src/Components/Concerns/CanFormatState.php:193-198 | packages/tables/src/Columns/Concerns/CanFormatState.php:70-75 | packages/tables/src/Columns/Concerns/CanFormatState.php:100-105 | packages/tables/src/Columns/Concerns/CanFormatState.php:143-148 | packages/tables/src/Columns/Concerns/CanFormatState.php:193-198 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/infolists/src/Components/Concerns/CanFormatState.php:97` calls `getContainer`, `getDefaultIsoDateDisplayFormat` and `packages/infolists/src/Components/Concerns/CanFormatState.php:67` 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 (6 lines × 7) packages/panels/src/Commands/MakeClusterCommand.php:176— packages/panels/src/Commands/MakeClusterCommand.php:176-181 | packages/panels/src/Commands/MakePageCommand.php:354-359 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:183-188 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:249-254 | packages/support/src/Commands/Concerns/CanAskForRelatedModel.php:29-34 | packages/support/src/Commands/Concerns/CanAskForSchema.php:30-35 | packages/widgets/src/Commands/MakeWidgetCommand.php:352-357 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakeClusterCommand.php:176` 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 (6 lines × 4) packages/actions/src/Action.php:1039— packages/actions/src/Action.php:1039-1044 | packages/actions/src/Action.php:1079-1084 | packages/actions/src/Action.php:1149-1154 | packages/actions/src/Action.php:1187-1192 — 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 `packages/actions/src/Action.php:1039` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `packages/actions/src/Action.php:1078` calls `getLabeledFromBreakpoint` and `packages/actions/src/Action.php:1038` 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 (6 lines × 3) packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:177— packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php:177-182 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:151-156 | packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php:181-186 — before extracting anything, compare `packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php` and `packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (2–5 lines × 7) packages/panels/src/Commands/MakeClusterCommand.php:183— packages/panels/src/Commands/MakeClusterCommand.php:183-184 | packages/panels/src/Commands/MakePageCommand.php:361-362 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:190-194 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:256-257 | packages/support/src/Commands/Concerns/CanAskForRelatedModel.php:36-40 | packages/support/src/Commands/Concerns/CanAskForSchema.php:37-38 | packages/widgets/src/Commands/MakeWidgetCommand.php:359-360 — before extracting anything, compare `packages/panels/src/Commands/MakePageCommand.php` and `packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/panels/src/Commands/MakeClusterCommand.php:183` 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. 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 (4–5 lines × 3) packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:62— packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:62-66 | packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php:74-77 | packages/support/src/View/Concerns/CanGenerateLinkHtml.php:84-88 — before extracting anything, compare `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php` and `packages/support/src/View/Concerns/CanGenerateIconButtonHtml.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 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 `packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:62` 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.
Duplicated block (43 lines × 2) packages/schemas/src/Components/Concerns/CanOpenUrl.php:16— packages/schemas/src/Components/Concerns/CanOpenUrl.php:16-58 | packages/tables/src/Columns/Concerns/CanOpenUrl.php:16-58 — before extracting anything, compare `packages/schemas/src/Components/Concerns/CanOpenUrl.php` and `packages/tables/src/Columns/Concerns/CanOpenUrl.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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/schemas/src/Components/Concerns/CanOpenUrl.php:16` 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 (60 lines × 2) packages/tables/src/Columns/Concerns/CanBeHidden.php:19— packages/tables/src/Columns/Concerns/CanBeHidden.php:19-78 | packages/tables/src/Filters/Concerns/CanBeHidden.php:17-76 — before extracting anything, compare `packages/tables/src/Columns/Concerns/CanBeHidden.php` and `packages/tables/src/Filters/Concerns/CanBeHidden.php` as WHOLE FILES: 95% 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `packages/tables/src/Columns/Concerns/CanBeHidden.php:19` 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 (16 lines × 7) docs-assets/app/app/Livewire/Panels/Navigation/ActiveIcon.php:16— docs-assets/app/app/Livewire/Panels/Navigation/ActiveIcon.php:16-34 | docs-assets/app/app/Livewire/Panels/Navigation/Badge.php:16-34 | docs-assets/app/app/Livewire/Panels/Navigation/BadgeColor.php:16-34 | docs-assets/app/app/Livewire/Panels/Navigation/BadgeTooltip.php:16-35 | docs-assets/app/app/Livewire/Panels/Navigation/ChangeIcon.php:16-31 | docs-assets/app/app/Livewire/Panels/Navigation/CustomItems.php:16-31 | docs-assets/app/app/Livewire/Panels/Navigation/SortItems.php:16-33 — before extracting anything, compare `docs-assets/app/app/Livewire/Panels/Navigation/Badge.php` and `docs-assets/app/app/Livewire/Panels/Navigation/BadgeColor.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.
Duplicated block (32 lines × 3) docs-assets/app/app/Livewire/Panels/Navigation/Group.php:17— docs-assets/app/app/Livewire/Panels/Navigation/Group.php:17-50 | docs-assets/app/app/Livewire/Panels/Navigation/GroupCollapsible.php:17-48 | docs-assets/app/app/Livewire/Panels/Navigation/GroupNotCollapsible.php:17-48 — before extracting anything, compare `docs-assets/app/app/Livewire/Panels/Navigation/Group.php` and `docs-assets/app/app/Livewire/Panels/Navigation/GroupCollapsible.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.
Duplicated block (10 lines × 14) packages/forms/src/Commands/MakeFieldCommand.php:107— packages/forms/src/Commands/MakeFieldCommand.php:107-116 | packages/forms/src/Commands/MakeFormCommand.php:115-124 | packages/forms/src/Commands/MakeLivewireFormCommand.php:146-155 | packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php:123-132 | packages/infolists/src/Commands/MakeEntryCommand.php:107-116 | packages/panels/src/Commands/MakePageCommand.php:208-217 | packages/schemas/src/Commands/MakeComponentCommand.php:123-132 | packages/schemas/src/Commands/MakeLivewireSchemaCommand.php:107-116 | packages/schemas/src/Commands/MakeSchemaCommand.php:96-105 | packages/spatie-laravel-settings-plugin/src/Commands/MakeSettingsPageCommand.php:142-151 | packages/tables/src/Commands/MakeColumnCommand.php:111-120 | packages/tables/src/Commands/MakeLivewireTableCommand.php:133-142 | packages/tables/src/Commands/MakeTableCommand.php:124-133 | packages/widgets/src/Commands/MakeWidgetCommand.php:207-216 — before extracting anything, compare `packages/forms/src/Commands/MakeFieldCommand.php` and `packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 × 9) packages/forms/src/Commands/MakeFieldCommand.php:164— packages/forms/src/Commands/MakeFieldCommand.php:164-172 | packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php:186-194 | packages/infolists/src/Commands/MakeEntryCommand.php:164-172 | packages/panels/src/Commands/MakePageCommand.php:705-713 | packages/schemas/src/Commands/MakeComponentCommand.php:180-188 | packages/schemas/src/Commands/MakeLivewireSchemaCommand.php:157-165 | packages/tables/src/Commands/MakeColumnCommand.php:182-190 | packages/tables/src/Commands/MakeLivewireTableCommand.php:233-241 | packages/widgets/src/Commands/MakeWidgetCommand.php:532-540 — before extracting anything, compare `packages/forms/src/Commands/MakeFieldCommand.php` and `packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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 × 6) packages/panels/src/Auth/Pages/EditProfile.php:519— packages/panels/src/Auth/Pages/EditProfile.php:519-528 | packages/panels/src/Auth/Pages/PasswordReset/RequestPasswordReset.php:224-232 | packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php:257-265 | packages/panels/src/Auth/Pages/Register.php:333-341 | packages/panels/src/Pages/Tenancy/EditTenantProfile.php:249-258 | packages/panels/src/Pages/Tenancy/RegisterTenant.php:203-212 — before extracting anything, compare `packages/panels/src/Auth/Pages/PasswordReset/ResetPassword.php` and `packages/panels/src/Auth/Pages/Register.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. 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 × 15) packages/actions/src/ActionGroup.php:762— packages/actions/src/ActionGroup.php:762-772 | packages/actions/src/Concerns/HasExtraModalOverlayAttributes.php:21-31 | packages/actions/src/Concerns/HasExtraModalWindowAttributes.php:24-34 | packages/forms/src/Components/Concerns/HasExtraFieldWrapperAttributes.php:24-34 | packages/forms/src/Components/Concerns/HasExtraInputAttributes.php:24-34 | packages/forms/src/Components/DateTimePicker.php:425-435 | packages/infolists/src/Components/Concerns/HasExtraEntryWrapperAttributes.php:24-34 | packages/panels/src/Navigation/Concerns/HasExtraSidebarAttributes.php:24-34 | packages/panels/src/Navigation/Concerns/HasExtraTopbarAttributes.php:24-34 | packages/support/src/Concerns/HasExtraAlpineAttributes.php:24-34 | packages/support/src/Concerns/HasExtraAttributes.php:24-34 | packages/tables/src/Columns/Concerns/HasExtraCellAttributes.php:24-34 | packages/tables/src/Columns/Concerns/HasExtraHeaderAttributes.php:24-34 | packages/tables/src/Columns/ImageColumn.php:328-338 | packages/tables/src/Table/Concerns/HasRecordUrl.php:93-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 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 15 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.
Duplicated block (7 lines × 13) packages/actions/src/ActionGroup.php:780— packages/actions/src/ActionGroup.php:780-786 | packages/actions/src/Concerns/HasExtraModalOverlayAttributes.php:39-45 | packages/actions/src/Concerns/HasExtraModalWindowAttributes.php:42-48 | packages/forms/src/Components/Concerns/HasExtraFieldWrapperAttributes.php:42-48 | packages/forms/src/Components/Concerns/HasExtraInputAttributes.php:42-48 | packages/forms/src/Components/DateTimePicker.php:709-715 | packages/infolists/src/Components/Concerns/HasExtraEntryWrapperAttributes.php:42-48 | packages/panels/src/Navigation/Concerns/HasExtraSidebarAttributes.php:42-48 | packages/panels/src/Navigation/Concerns/HasExtraTopbarAttributes.php:42-48 | packages/support/src/Concerns/HasExtraAlpineAttributes.php:42-48 | packages/support/src/Concerns/HasExtraAttributes.php:42-48 | packages/tables/src/Columns/Concerns/HasExtraCellAttributes.php:42-48 | packages/tables/src/Columns/Concerns/HasExtraHeaderAttributes.php:42-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 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.
Duplicated block (7 lines × 14) packages/actions/src/Commands/MakeExporterCommand.php:189— packages/actions/src/Commands/MakeExporterCommand.php:189-197 | packages/actions/src/Commands/MakeImporterCommand.php:217-227 | packages/forms/src/Commands/MakeFieldCommand.php:152-159 | packages/forms/src/Commands/MakeFormCommand.php:192-199 | packages/forms/src/Commands/MakeLivewireFormCommand.php:266-276 | packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php:173-181 | packages/infolists/src/Commands/MakeEntryCommand.php:152-159 | packages/panels/src/Commands/MakeRelationManagerCommand.php:600-618 | packages/schemas/src/Commands/MakeComponentCommand.php:168-175 | packages/schemas/src/Commands/MakeLivewireSchemaCommand.php:145-152 | packages/schemas/src/Commands/MakeSchemaCommand.php:126-132 | packages/tables/src/Commands/MakeColumnCommand.php:169-177 | packages/tables/src/Commands/MakeLivewireTableCommand.php:219-228 | packages/tables/src/Commands/MakeTableCommand.php:202-210 — before extracting anything, compare `packages/actions/src/Commands/MakeExporterCommand.php` and `packages/actions/src/Commands/MakeImporterCommand.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 88 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 (7 lines × 5) packages/infolists/src/Components/Concerns/CanFormatState.php:84— packages/infolists/src/Components/Concerns/CanFormatState.php:84-90 | packages/infolists/src/Components/Concerns/CanFormatState.php:114-120 | packages/infolists/src/Components/Concerns/CanFormatState.php:301-307 | packages/infolists/src/Components/Concerns/CanFormatState.php:312-318 | packages/tables/src/Columns/Concerns/CanFormatState.php:84-90 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 5) packages/infolists/src/Components/Concerns/CanFormatState.php:157— packages/infolists/src/Components/Concerns/CanFormatState.php:157-161 | packages/infolists/src/Components/Concerns/CanFormatState.php:166-170 | packages/infolists/src/Components/Concerns/CanFormatState.php:207-211 | packages/infolists/src/Components/Concerns/CanFormatState.php:216-220 | packages/tables/src/Columns/Concerns/CanFormatState.php:157-161 — before extracting anything, compare `packages/infolists/src/Components/Concerns/CanFormatState.php` and `packages/tables/src/Columns/Concerns/CanFormatState.php` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 181 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) packages/forms/src/Testing/TestsForms.php:25— packages/forms/src/Testing/TestsForms.php:25-72 | packages/forms/src/Testing/TestsForms.php:86-116 | packages/forms/src/Testing/TestsForms.php:121-151 | packages/forms/src/Testing/TestsForms.php:188-225 | packages/forms/src/Testing/TestsForms.php:230-254 | packages/schemas/src/Testing/TestsSchemas.php:25-56 | packages/schemas/src/Testing/TestsSchemas.php:61-84 | packages/schemas/src/Testing/TestsSchemas.php:165-203 | packages/schemas/src/Testing/TestsSchemas.php:266-288 | packages/schemas/src/Testing/TestsSchemas.php:293-315 | packages/schemas/src/Testing/TestsSchemas.php:346-365 | packages/schemas/src/Testing/TestsSchemas.php:370-389 — These 12 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 12 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 12 times.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) packages/tables/src/Testing/TestsColumns.php:205— packages/tables/src/Testing/TestsColumns.php:205-249 | packages/tables/src/Testing/TestsColumns.php:254-298 | packages/tables/src/Testing/TestsColumns.php:303-339 | packages/tables/src/Testing/TestsColumns.php:344-380 | packages/tables/src/Testing/TestsColumns.php:385-417 | packages/tables/src/Testing/TestsColumns.php:422-454 | packages/tables/src/Testing/TestsColumns.php:459-492 | packages/tables/src/Testing/TestsColumns.php:497-530 | packages/tables/src/Testing/TestsColumns.php:535-568 | packages/tables/src/Testing/TestsColumns.php:573-606 — These 10 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 10 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 10 times.
Duplicated block (24–25 lines × 4) packages/tables/src/Testing/TestsColumns.php:385— packages/tables/src/Testing/TestsColumns.php:385-408 | packages/tables/src/Testing/TestsColumns.php:422-445 | packages/tables/src/Testing/TestsColumns.php:535-559 | packages/tables/src/Testing/TestsColumns.php:573-597 — 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 `packages/tables/src/Testing/TestsColumns.php:385` 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 (18–19 lines × 10) packages/tables/src/Testing/TestsColumns.php:207— packages/tables/src/Testing/TestsColumns.php:207-224 | packages/tables/src/Testing/TestsColumns.php:256-273 | packages/tables/src/Testing/TestsColumns.php:305-323 | packages/tables/src/Testing/TestsColumns.php:346-364 | packages/tables/src/Testing/TestsColumns.php:387-404 | packages/tables/src/Testing/TestsColumns.php:424-441 | packages/tables/src/Testing/TestsColumns.php:461-479 | packages/tables/src/Testing/TestsColumns.php:499-517 | packages/tables/src/Testing/TestsColumns.php:537-555 | packages/tables/src/Testing/TestsColumns.php:575-593 — all 10 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.
Duplicated block (12 lines × 5) packages/forms/src/Testing/TestsForms.php:259— packages/forms/src/Testing/TestsForms.php:259-270 | packages/forms/src/Testing/TestsForms.php:301-312 | packages/forms/src/Testing/TestsForms.php:343-354 | packages/forms/src/Testing/TestsForms.php:380-391 | packages/forms/src/Testing/TestsForms.php:417-428 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `packages/forms/src/Testing/TestsForms.php:259` 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 × 8) packages/forms/src/Testing/TestsForms.php:231— packages/forms/src/Testing/TestsForms.php:231-241 | packages/schemas/src/Testing/TestsSchemas.php:26-36 | packages/schemas/src/Testing/TestsSchemas.php:62-72 | packages/schemas/src/Testing/TestsSchemas.php:166-176 | packages/schemas/src/Testing/TestsSchemas.php:267-277 | packages/schemas/src/Testing/TestsSchemas.php:294-304 | packages/schemas/src/Testing/TestsSchemas.php:347-357 | packages/schemas/src/Testing/TestsSchemas.php:371-381 — there are 8 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 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (11 lines × 4) packages/schemas/src/Testing/TestsSchemas.php:90— packages/schemas/src/Testing/TestsSchemas.php:90-100 | packages/schemas/src/Testing/TestsSchemas.php:119-129 | packages/schemas/src/Testing/TestsSchemas.php:209-219 | packages/schemas/src/Testing/TestsSchemas.php:238-248 — 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.
Duplicated block (8 lines × 8) packages/forms/src/Testing/TestsForms.php:26— packages/forms/src/Testing/TestsForms.php:26-33 | packages/forms/src/Testing/TestsForms.php:87-94 | packages/forms/src/Testing/TestsForms.php:122-129 | packages/forms/src/Testing/TestsForms.php:231-238 | packages/schemas/src/Testing/TestsSchemas.php:62-69 | packages/schemas/src/Testing/TestsSchemas.php:166-173 | packages/schemas/src/Testing/TestsSchemas.php:267-274 | packages/schemas/src/Testing/TestsSchemas.php:294-301 — there are 8 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 8 sites; resolving a subset leaves the remainder to drift apart.
Off the main sequence: filament/support — filament/support: abstractness 0.13, instability 0.00, distance 0.87 — zone of pain — concrete and depended on by 11 project(s), so it's rigid to change.
Duplication concentrated across 5 sibling directories (5 clone groups) packages/forms/resources/js/components/select.js:25— 5 duplicated blocks under packages/ have copies in at least two of the sibling directories forms, panels, schemas, support, tables — 1 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (145 matched lines × 2 locations) · ×1
Duplicated block with local edits (145 matched lines × 2 locations) packages/forms/resources/js/components/rich-editor/extension-mention.js:20— packages/forms/resources/js/components/rich-editor/extension-mention.js:20 · packages/forms/resources/js/components/rich-editor/extension-merge-tag.js:15 — the two spans are one implementation copied and then locally edited — 636 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (66 matched lines × 2 locations) · ×1
Duplicated block with local edits (66 matched lines × 2 locations) packages/forms/resources/js/components/rich-editor/mention-suggestion.js:187— packages/forms/resources/js/components/rich-editor/mention-suggestion.js:187 · packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:95 — the two spans are one implementation copied and then locally edited — 314 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (33 lines × 2 locations) packages/forms/resources/js/components/rich-editor/extension-grid-column.js:27— packages/forms/resources/js/components/rich-editor/extension-grid-column.js:27 · packages/forms/resources/js/components/rich-editor/extension-grid.js:114 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (31 matched lines × 2 locations) · ×1
Duplicated block with local edits (31 matched lines × 2 locations) packages/forms/resources/js/components/rich-editor/mention-suggestion.js:130— packages/forms/resources/js/components/rich-editor/mention-suggestion.js:130 · packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js:50 — the two spans are one implementation copied and then locally edited — 167 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (25 matched lines × 2 locations) · ×1
Duplicated block with local edits (25 matched lines × 2 locations) packages/widgets/resources/js/components/chart.js:58— packages/widgets/resources/js/components/chart.js:58 · packages/widgets/resources/js/components/stats-overview/stat/chart.js:35 — the two spans are one implementation copied and then locally edited — 117 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (17 lines × 3 locations) packages/forms/resources/js/components/date-time-picker.js:192— packages/forms/resources/js/components/date-time-picker.js:192 · packages/forms/resources/js/components/date-time-picker.js:214 · packages/forms/resources/js/components/date-time-picker.js:236 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) packages/forms/resources/js/components/rich-editor/extension-local-files.js:182— packages/forms/resources/js/components/rich-editor/extension-local-files.js:182 · packages/forms/resources/js/components/rich-editor/extension-local-files.js:229 — 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.
R10 · Code Duplication· Duplicated block with local edits (16 matched lines × 2 locations) · ×1
Duplicated block with local edits (16 matched lines × 2 locations) packages/support/resources/js/components/dropdown.js:560— packages/support/resources/js/components/dropdown.js:560 · packages/support/resources/js/components/dropdown.js:640 — the two spans are one implementation copied and then locally edited — 84 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (14 lines × 2 locations) packages/tables/resources/js/components/columns/checkbox.js:3— packages/tables/resources/js/components/columns/checkbox.js:3 · packages/tables/resources/js/components/columns/toggle.js:3 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (13 lines × 2 locations) packages/forms/resources/js/components/file-upload.js:683— packages/forms/resources/js/components/file-upload.js:683 · packages/forms/resources/js/components/file-upload.js:700 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×1
Duplicated block with local edits (12 matched lines × 2 locations) packages/schemas/resources/js/components/tabs.js:158— packages/schemas/resources/js/components/tabs.js:158 · packages/schemas/resources/js/components/wizard.js:30 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (10 lines × 2 locations) REDACTED:2129— REDACTED:2129 · REDACTED:2148 — 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.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×1
Duplicated block with local edits (10 matched lines × 2 locations) packages/tables/resources/js/components/column-manager.js:193— packages/tables/resources/js/components/column-manager.js:193 · packages/tables/resources/js/components/column-manager.js:234 — the two spans are one implementation copied and then locally edited — 54 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (7 lines × 2 locations) packages/forms/resources/js/components/file-upload.js:327— packages/forms/resources/js/components/file-upload.js:327 · packages/forms/resources/js/components/rich-editor/extension-local-files.js:36 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function EasyMDE (cyclomatic 53, cognitive 63) REDACTED:1933— EasyMDE has cyclomatic complexity 53 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function toggleCodeBlock (cyclomatic 42, cognitive 114) REDACTED:501— toggleCodeBlock has cyclomatic complexity 42 and cognitive complexity 114; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderOptions (cyclomatic 37, cognitive 58) packages/support/resources/js/utilities/select.js:306— renderOptions has cyclomatic complexity 37 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 35, cognitive 38) REDACTED:2346— render has cyclomatic complexity 35 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function openDropdown (cyclomatic 31, cognitive 42) packages/support/resources/js/utilities/select.js:1369— openDropdown has cyclomatic complexity 31 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleToolbarKeydown (cyclomatic 31, cognitive 30) packages/forms/resources/js/components/rich-editor.js:679— handleToolbarKeydown has cyclomatic complexity 31 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleDropdownKeydown (cyclomatic 30, cognitive 38) packages/support/resources/js/utilities/select.js:1262— handleDropdownKeydown has cyclomatic complexity 30 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getLabelsForMultipleSelection (cyclomatic 27, cognitive 43) packages/support/resources/js/utilities/select.js:684— getLabelsForMultipleSelection has cyclomatic complexity 27 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createToolbarButton (cyclomatic 25, cognitive 32) REDACTED:218— createToolbarButton has cyclomatic complexity 25 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function positionOverflow (cyclomatic 25, cognitive 31) packages/schemas/resources/js/components/tabs.js:449— positionOverflow has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 23, cognitive 25) packages/schemas/resources/js/components/tabs.js:659— (anonymous) has cyclomatic complexity 23 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createToolbar (cyclomatic 20, cognitive 31) REDACTED:3107— createToolbar has cyclomatic complexity 20 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function scrollOverflow (cyclomatic 20, cognitive 20) packages/schemas/resources/js/components/tabs.js:377— scrollOverflow has cyclomatic complexity 20 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function keydown (cyclomatic 20, cognitive 19) packages/panels/resources/js/components/global-search.js:152— keydown has cyclomatic complexity 20 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleCalendarKeydown (cyclomatic 20, cognitive 12) packages/forms/resources/js/components/date-time-picker.js:472— handleCalendarKeydown has cyclomatic complexity 20 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function reconcile (cyclomatic 18, cognitive 20) packages/forms/resources/js/utilities/reordering.js:300— reconcile has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function init (cyclomatic 17, cognitive 16) packages/forms/resources/js/components/file-upload.js:130— init has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createOptionElement (cyclomatic 17, cognitive 16) packages/support/resources/js/utilities/select.js:507— createOptionElement has cyclomatic complexity 17 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function syncActionModals (cyclomatic 17, cognitive 15) packages/actions/resources/js/components/modals.js:95— syncActionModals has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateOptionLabelInList (cyclomatic 16, cognitive 31) packages/support/resources/js/utilities/select.js:1187— updateOptionLabelInList has cyclomatic complexity 16 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 3219 lines of code REDACTED:1— REDACTED has 3219 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/support/resources/js/utilities/select.js · ×1
packages/support/resources/js/utilities/select.js: 2039 lines of code packages/support/resources/js/utilities/select.js:1— packages/support/resources/js/utilities/select.js has 2039 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/forms/resources/js/components/file-upload.js · ×1
packages/forms/resources/js/components/file-upload.js: 1001 lines of code packages/forms/resources/js/components/file-upload.js:1— packages/forms/resources/js/components/file-upload.js has 1001 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/forms/resources/js/components/rich-editor.js · ×1
packages/forms/resources/js/components/rich-editor.js: 933 lines of code packages/forms/resources/js/components/rich-editor.js:1— packages/forms/resources/js/components/rich-editor.js has 933 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/schemas/resources/js/components/tabs.js · ×1
packages/schemas/resources/js/components/tabs.js: 822 lines of code packages/schemas/resources/js/components/tabs.js:1— packages/schemas/resources/js/components/tabs.js has 822 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/forms/resources/js/components/date-time-picker.js · ×1
packages/forms/resources/js/components/date-time-picker.js: 815 lines of code packages/forms/resources/js/components/date-time-picker.js:1— packages/forms/resources/js/components/date-time-picker.js has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/tables/resources/js/components/table.js · ×1
packages/tables/resources/js/components/table.js: 703 lines of code packages/tables/resources/js/components/table.js:1— packages/tables/resources/js/components/table.js has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/support/resources/js/components/dropdown.js · ×1
packages/support/resources/js/components/dropdown.js: 579 lines of code packages/support/resources/js/components/dropdown.js:1— packages/support/resources/js/components/dropdown.js has 579 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/forms/resources/js/components/markdown-editor.js · ×1
packages/forms/resources/js/components/markdown-editor.js: 442 lines of code packages/forms/resources/js/components/markdown-editor.js:1— packages/forms/resources/js/components/markdown-editor.js has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/forms/resources/js/utilities/reordering.js · ×1
packages/forms/resources/js/utilities/reordering.js: 426 lines of code packages/forms/resources/js/utilities/reordering.js:1— packages/forms/resources/js/utilities/reordering.js has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No typecheck script — test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Unused dependency '@tiptap/extension-mention' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'esbuild-postcss' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'inter-ui' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: load packages/forms/resources/js/components/file-upload.js:301— `load` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
README/code drift docs/02-getting-started.md:5— docs/02-getting-started.md links to `introduction/installation#installing-the-panel-builder`, but `docs/introduction/installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-getting-started.md:8— docs/02-getting-started.md links to `components`, but `docs/components` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-getting-started.md:28— docs/02-getting-started.md links to `resources`, but `docs/resources` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-getting-started.md:40— docs/02-getting-started.md links to `widgets`, but `docs/widgets` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/02-getting-started.md:48— docs/02-getting-started.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:11— docs/05-panel-configuration.md links to `resources/overview`, but `docs/resources/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:11— docs/05-panel-configuration.md links to `navigation/custom-pages`, but `docs/navigation/custom-pages` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:11— docs/05-panel-configuration.md links to `widgets/overview`, but `docs/widgets/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:85— docs/05-panel-configuration.md links to `advanced/render-hooks#available-render-hooks`, but `docs/advanced/render-hooks` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:282— docs/05-panel-configuration.md links to `resources/creating-records`, but `docs/resources/creating-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:282— docs/05-panel-configuration.md links to `resources/editing-records`, but `docs/resources/editing-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:321— docs/05-panel-configuration.md links to `advanced/assets`, but `docs/advanced/assets` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/05-panel-configuration.md:407— docs/05-panel-configuration.md links to `introduction/installation#publishing-configuration`, but `docs/introduction/installation` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/13-deployment.md:9— docs/13-deployment.md links to `introduction/optimizing-local-development`, but `docs/introduction/optimizing-local-development` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/13-deployment.md:15— docs/13-deployment.md links to `users/overview#authorizing-access-to-the-panel`, but `docs/users/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/14-upgrade-guide.md:279— docs/14-upgrade-guide.md links to `styling/overview#creating-a-custom-theme`, but `docs/styling/overview` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/14-upgrade-guide.md:558— docs/14-upgrade-guide.md links to `actions/import#customizing-the-import-job-retries`, but `docs/actions/import` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/14-upgrade-guide.md:558— docs/14-upgrade-guide.md links to `actions/export#customizing-the-export-job-retries`, but `docs/actions/export` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/01-overview.md:70— docs/01-introduction/01-overview.md links to `../styling`, but `docs/styling` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/01-overview.md:76— docs/01-introduction/01-overview.md links to `../testing`, but `docs/testing` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/02-installation.md:51— docs/01-introduction/02-installation.md links to `../getting-started`, but `docs/getting-started` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/02-installation.md:90— docs/01-introduction/02-installation.md links to `../components`, but `docs/components` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/02-installation.md:113— docs/01-introduction/02-installation.md links to `../notifications`, but `docs/notifications` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/01-introduction/04-optimizing-local-development.md:7— docs/01-introduction/04-optimizing-local-development.md links to `../deployment`, but `docs/deployment` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/03-resources/01-overview.md:77— docs/03-resources/01-overview.md links to `deleting-records#handling-soft-deletes`, but `docs/03-resources/deleting-records` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate packages/forms/resources/js/components/rich-editor/mention-suggestion.js:174— `rect.top < containerRect.top || rect.bottom > containerRect.bottom` appears character-identically in 2 files — packages/forms/resources/js/components/rich-editor/mention-suggestion.js, packages/forms/resources/js/components/rich-editor/merge-tag-suggestion.js. 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 packages/forms/resources/js/utilities/reordering.js:401— `style.display !== 'none' && style.visibility !== 'hidden' && element.getClientRects().length > 0` appears character-identically in 2 files — packages/forms/resources/js/utilities/reordering.js, packages/support/resources/js/components/dropdown.js. 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 packages/support/resources/js/components/copyable.js:96— `this.isDestroyed || !this.$el.isConnected` appears character-identically in 2 files — packages/support/resources/js/components/copyable.js, packages/support/resources/js/components/modal.js. 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 packages/forms/resources/js/components/color-picker.js:23— `this.state === null || this.state === ''` appears character-identically in 2 files — packages/forms/resources/js/components/color-picker.js, packages/support/resources/js/utilities/select.js. 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 packages/panels/src/Panel/Concerns/HasTenancy.php:103— `! array_is_list($items) || $items === []` appears character-identically in 2 files — packages/panels/src/Panel/Concerns/HasTenancy.php, packages/panels/src/Panel/Concerns/HasUserMenu.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 packages/tables/src/Columns/Summarizers/Summarizer.php:144— `! is_string($column) || $column !== "{$joinTable}.*"` appears character-identically in 2 files — packages/tables/src/Columns/Summarizers/Summarizer.php, packages/tables/src/Concerns/CanSummarizeRecords.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 packages/forms/resources/views/components/field-wrapper.blade.php:145— `$beforeContentSchema || $afterContentSchema` appears character-identically in 3 files — packages/forms/resources/views/components/field-wrapper.blade.php, packages/forms/src/Components/Field.php, packages/schemas/src/Components/FusedGroup.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 packages/forms/src/Components/Builder.php:1729— `$collapseAllActionIsVisible || $expandAllActionIsVisible` appears character-identically in 2 files — packages/forms/src/Components/Builder.php, packages/forms/src/Components/Repeater.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 packages/tables/src/Columns/Concerns/HasColor.php:43— `$condition instanceof Closure && $column` appears character-identically in 2 files — packages/tables/src/Columns/Concerns/HasColor.php, packages/tables/src/Columns/Concerns/HasIcon.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 packages/infolists/src/Components/Concerns/HasColor.php:43— `$condition instanceof Closure && $component` appears character-identically in 2 files — packages/infolists/src/Components/Concerns/HasColor.php, packages/infolists/src/Components/Concerns/HasIcon.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 packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:39— `$constraint instanceof DateConstraint && $constraint` appears character-identically in 2 files — packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php, packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.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 packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php:132— `$get('mode') !== 'relative' || $get('preset') !== 'custom'` appears character-identically in 2 files — packages/query-builder/src/Constraints/DateConstraint/Operators/IsAfterOperator.php, packages/query-builder/src/Constraints/DateConstraint/Operators/IsBeforeOperator.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 packages/forms/src/Components/Field.php:616— `$hasAlpineDisabledClasses || $hasAlpineValidClasses` appears character-identically in 2 files — packages/forms/src/Components/Field.php, packages/support/resources/views/components/input/wrapper.blade.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 packages/schemas/src/Components/Callout.php:286— `$hasHeading || $hasDescription || $hasFooter` appears character-identically in 2 files — packages/schemas/src/Components/Callout.php, packages/support/resources/views/components/callout.blade.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 packages/support/resources/views/components/badge.blade.php:86— `$hasLoadingIndicator && $loadingIndicatorTarget` appears character-identically in 10 files — packages/support/resources/views/components/badge.blade.php, packages/support/resources/views/components/button/index.blade.php, packages/support/resources/views/components/dropdown/list/item.blade.php, packages/support/resources/views/components/icon-button.blade.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 packages/schemas/src/Components/Tabs.php:865— `$icon && $iconPosition === IconPosition::After` appears character-identically in 2 files — packages/schemas/src/Components/Tabs.php, packages/support/resources/views/components/tabs/item.blade.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 packages/schemas/src/Components/Tabs.php:855— `$icon && $iconPosition === IconPosition::Before` appears character-identically in 2 files — packages/schemas/src/Components/Tabs.php, packages/support/resources/views/components/tabs/item.blade.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 packages/support/src/View/Concerns/CanGenerateBadgeHtml.php:105— `$icon || $iconAlias || $hasLoadingIndicator` appears character-identically in 5 files — packages/support/src/View/Concerns/CanGenerateBadgeHtml.php, packages/support/src/View/Concerns/CanGenerateButtonHtml.php, packages/support/src/View/Concerns/CanGenerateDropdownItemHtml.php, packages/support/src/View/Concerns/CanGenerateIconButtonHtml.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 packages/infolists/src/Components/TextEntry.php:355— `$isBadge || $isCopyable || filled($tooltip)` appears character-identically in 2 files — packages/infolists/src/Components/TextEntry.php, packages/tables/src/Columns/TextColumn.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 packages/infolists/src/Components/Concerns/CanFormatState.php:394— `$isHtml && ($state instanceof LabelInterface) && (! ($state instanceof Htmlable)) && (! ($state instanceof Stringable))` appears character-identically in 2 files — packages/infolists/src/Components/Concerns/CanFormatState.php, packages/tables/src/Columns/Concerns/CanFormatState.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 packages/forms/src/Components/TagsInput.php:261— `$isPrefixInline && (count($prefixActions) || $prefixIcon || filled($prefixLabel))` appears character-identically in 2 files — packages/forms/src/Components/TagsInput.php, packages/forms/src/Components/TextInput.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 packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:100— `$isRecoverable && $get('useRecoveryCode')` appears character-identically in 2 files — packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.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 packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php:69— `$isRecoverable && (! $get('useRecoveryCode'))` appears character-identically in 2 files — packages/panels/src/Auth/MultiFactor/App/Actions/DisableAppAuthenticationAction.php, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.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 packages/forms/src/Components/Builder.php:1776— `$isReorderableWithDragAndDrop && $reorderAction` appears character-identically in 2 files — packages/forms/src/Components/Builder.php, packages/forms/src/Components/Repeater.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 packages/panels/resources/views/livewire/sidebar.blade.php:22— `$isSidebarCollapsibleOnDesktop || $isSidebarFullyCollapsibleOnDesktop` appears character-identically in 2 files — packages/panels/resources/views/livewire/sidebar.blade.php, packages/panels/resources/views/livewire/topbar.blade.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.
Orphaned file packages/forms/src/Commands/MakeRichContentCustomBlockCommand.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 packages/forms/src/Commands/FileGenerators/RichContentCustomBlockClassGenerator.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 packages/panels/src/View/PanelsIconAlias.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 docs-assets/app/app/Livewire/Forms/FieldsOverview.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 packages/widgets/src/ChartWidget/Concerns/HasFiltersSchema.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 docs-assets/app/app/Providers/Filament/TenantMenuGroupingDemoPanelProvider.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 packages/upgrade/src/Rector/AddPanelParamToRouteMethodsRector.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 packages/forms/src/Components/RichEditor/TipTapExtensions/GridExtension.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.
Documentation: contradicts the code docs/01-introduction/05-version-support-policy.md— The version support policy describes how pull requests are accepted for new features and bug fixes, but it is stale given that Filament 4.23 has already reached its end-of-life. Update the policy to reflect current major-version release cycles and any remaining supported versions.
Documentation: no project overview docs/03-resources/05-viewing-records.md— The title 'Viewing records' begins a document that does not quote any opening line stating what the project is or what it does for readers; this is an overview gap. Add a one-line description of the resource-view feature and its purpose above the first code block.
Documentation: no project overview docs/03-resources/11-widgets.md— The title 'Using widgets on resource pages' begins without any opening line stating what the project is or what it does for readers. Add a one-line overview of widget usage on resource pages above the first code block.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a documented retention period / data-expiry.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 58 significant file(s) lose their only recent owner: packages/panels/src/Auth/MultiFactor/Email/EmailAuthentication.php, packages/panels/src/Commands/FileGenerators/Resources/ResourceClassGenerator.php, packages/actions/src/AttachAction.php, packages/schemas/src/Testing/TestsSchemas.php, packages/panels/src/Commands/FileGenerators/Resources/RelationManagerClassGenerator.php, packages/panels/src/Commands/FileGenerators/Resources/Pages/ResourceManageRelatedRecordsPageClassGenerator.php, packages/query-builder/src/Constraints/RelationshipConstraint/Operators/IsRelatedToOperator.php, packages/support/src/Assets/AssetManager.php (+50 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 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 (60 single-owned of 522 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; 522 of the 1496 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/actions/src/Concerns/HasData.php, packages/upgrade/src/Rector/AddPanelParamToRouteMethodsRector.php.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 7 of 17 project(s) overshoot their size bounds, lowering Project Cohesion to 1.8/10. The most over is `packages/panels` (24387 LoC, 257 module-visible types across 79 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· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 8 of 522 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (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; 522 of the 1496 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/forms/src/Commands/MakeRichContentCustomBlockCommand.php, packages/forms/src/Commands/FileGenerators/RichContentCustomBlockClassGenerator.php, packages/panels/src/View/PanelsIconAlias.php, docs-assets/app/app/Livewire/Forms/FieldsOverview.php, packages/widgets/src/ChartWidget/Concerns/HasFiltersSchema.php, docs-assets/app/app/Providers/Filament/TenantMenuGroupingDemoPanelProvider.php, packages/upgrade/src/Rector/AddPanelParamToRouteMethodsRector.php, packages/forms/src/Components/RichEditor/TipTapExtensions/GridExtension.php. 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.
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.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/upgrade`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· PHP static analysis does not check null everywhere · ×1
PHP static analysis does not check null everywhere — 0/5 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.
Outdated (npm): pixelmatch — pixelmatch is pinned at 7.2.0; registry.npmjs.org publishes 8.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): puppeteer — puppeteer is pinned at 25.4.0; registry.npmjs.org publishes 25.16.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 70 file(s) — `docs-assets/app/app/Support/DemoData.php`, `packages/actions/src/Concerns/InteractsWithActions.php`, `packages/actions/src/CreateAction.php`, `packages/actions/src/EditAction.php`, `packages/actions/src/Exports/Concerns/CanFormatState.php`, … (+65 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
Run 01a1669b-264b-7773-bc5e-b9f1036d87a0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 23 · Warnings: 1388 · Recommendations: 92 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 02:33 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.