Public report of symfony/dependency-injection, published 17 November 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.11.4). Assert 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, 17 November 2026, 15:49 UTC · Survey ID cd_d110ace3f0ed4ece9650a9329d05313f
symfony/dependency-injection
Measured 17 November 2026, 15:48 UTC, at code version 155aee0
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 0.3 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 medium codebase: 24,083 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Maturity, 41.6
Findings by how serious they are
4 critical362 serious31 minor
20 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 15:48 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work 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 ▸
39of 39 dimensions measured by tools.
386of 397 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
39dimensions across 5 lenses, read from 24,083 lines of product code in 12 projects.
symfony/dependency-injection falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram. It scores 49.2 out of 100 and is rated Weak, and none of its four critical findings concern security.
Maturity, at 41.6, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6.1 points. Completing the README comes next, worth about 4.0 points. Raising Maturity to 70 would lift the score to about 55.1.
One set of files in separate parts keeps changing together, which points to a hidden dependency. Making the hidden dependencies explicit would close this risk. The loop of parts of the code that depend on each other needs breaking by moving the shared parts into a project of their own.
The product code is 24,083 lines, about €62,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.
Test isolation · Production project references a test project: Loader → Tests Loader/PhpFileLoader.php
We compare 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: 5 findings
These 5 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one.
€21,000 to €100,000, for 346 to 1,096 hours of work, about 0.4 person-years for one engineer
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 49. 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
Medium: 24,083 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Record your significant design decisions.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 3.8 points · Medium effort · CI/CD gates
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 €62,000 to build again, about 0.4 person-years of work. Its weakest lens is Maturity, at 41.6 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Record your significant design decisions. Of all the actions in this report, it raises the score most for the work it takes: about 6.1 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 5.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 10,211 lines over the last 90 days, which is about 41,411 lines a year. At that pace, the extra work comes to an estimated 6.4 to 38.3 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 our 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, never less than 2% to 5% and never more than 40% to 60% in all; 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, which only happens where the projects form a dependency cycle. A graph without cycles 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.
16 modules, with 32 dependencies between them. One loop runs through 9 of the modules, marked above the diagonal.
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.
Symfony.Component.DependencyInjection.Attribute uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Attribute, while a change to Symfony.Component.DependencyInjection.Attribute can't break Symfony.Component.DependencyInjection.
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.
3→10 Symfony.Component.DependencyInjection.LazyProxy.Instantiator uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
6 pairs of types, where a type in Symfony.Component.DependencyInjection.LazyProxy.Instantiator uses a type in Symfony.Component.DependencyInjection.
Symfony.Component.DependencyInjection.LazyProxy.Instantiator uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.LazyProxy.Instantiator, while a change to Symfony.Component.DependencyInjection.LazyProxy.Instantiator can't break Symfony.Component.DependencyInjection.
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.
Symfony.Component.DependencyInjection.Loader uses Symfony.Component.DependencyInjection.Exception, so a change to Symfony.Component.DependencyInjection.Exception can break Symfony.Component.DependencyInjection.Loader, while a change to Symfony.Component.DependencyInjection.Loader can't break Symfony.Component.DependencyInjection.Exception.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Loader uses a module listed above it, which is the healthy direction.
4→6 Symfony.Component.DependencyInjection.Loader uses Symfony.Component.DependencyInjection.Loader.Configuratorpart of a loop✕
Connections
1 pair of types, where a type in Symfony.Component.DependencyInjection.Loader uses a type in Symfony.Component.DependencyInjection.Loader.Configurator.
Symfony.Component.DependencyInjection.Loader uses Symfony.Component.DependencyInjection.Loader.Configurator, so a change to Symfony.Component.DependencyInjection.Loader.Configurator can break Symfony.Component.DependencyInjection.Loader, while a change to Symfony.Component.DependencyInjection.Loader can't break Symfony.Component.DependencyInjection.Loader.Configurator.
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.
4→10 Symfony.Component.DependencyInjection.Loader uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
4 pairs of types, where a type in Symfony.Component.DependencyInjection.Loader uses a type in Symfony.Component.DependencyInjection.
Symfony.Component.DependencyInjection.Loader uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Loader, while a change to Symfony.Component.DependencyInjection.Loader can't break Symfony.Component.DependencyInjection.
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.
5→10 Symfony.Component.DependencyInjection.ParameterBag uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
1 pair of types, where a type in Symfony.Component.DependencyInjection.ParameterBag uses a type in Symfony.Component.DependencyInjection.
Symfony.Component.DependencyInjection.ParameterBag uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.ParameterBag, while a change to Symfony.Component.DependencyInjection.ParameterBag can't break Symfony.Component.DependencyInjection.
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.
3 pairs of types, where a type in Symfony.Component.DependencyInjection.Loader.Configurator uses a type in Symfony.Component.DependencyInjection.Loader.
Symfony.Component.DependencyInjection.Loader.Configurator uses Symfony.Component.DependencyInjection.Loader, so a change to Symfony.Component.DependencyInjection.Loader can break Symfony.Component.DependencyInjection.Loader.Configurator, while a change to Symfony.Component.DependencyInjection.Loader.Configurator can't break Symfony.Component.DependencyInjection.Loader.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Loader.Configurator uses a module listed above it, which is the healthy direction.
6→10 Symfony.Component.DependencyInjection.Loader.Configurator uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
13 pairs of types, where a type in Symfony.Component.DependencyInjection.Loader.Configurator uses a type in Symfony.Component.DependencyInjection.
Symfony.Component.DependencyInjection.Loader.Configurator uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Loader.Configurator, while a change to Symfony.Component.DependencyInjection.Loader.Configurator can't break Symfony.Component.DependencyInjection.
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.
2 pairs of types, where a type in Symfony.Component.DependencyInjection.Extension uses a type in Symfony.Component.DependencyInjection.Loader.Configurator.
Symfony.Component.DependencyInjection.Extension uses Symfony.Component.DependencyInjection.Loader.Configurator, so a change to Symfony.Component.DependencyInjection.Loader.Configurator can break Symfony.Component.DependencyInjection.Extension, while a change to Symfony.Component.DependencyInjection.Extension can't break Symfony.Component.DependencyInjection.Loader.Configurator.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Extension uses a module listed above it, which is the healthy direction.
7→10 Symfony.Component.DependencyInjection.Extension uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
7 pairs of types, where a type in Symfony.Component.DependencyInjection.Extension uses a type in Symfony.Component.DependencyInjection.
Symfony.Component.DependencyInjection.Extension uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Extension, while a change to Symfony.Component.DependencyInjection.Extension can't break Symfony.Component.DependencyInjection.
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.
1 pair of types, where a type in Symfony.Component.DependencyInjection.Loader.Configurator.Traits uses a type in Symfony.Component.DependencyInjection.Loader.Configurator.
Symfony.Component.DependencyInjection.Loader.Configurator.Traits uses Symfony.Component.DependencyInjection.Loader.Configurator, so a change to Symfony.Component.DependencyInjection.Loader.Configurator can break Symfony.Component.DependencyInjection.Loader.Configurator.Traits, while a change to Symfony.Component.DependencyInjection.Loader.Configurator.Traits can't break Symfony.Component.DependencyInjection.Loader.Configurator.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Loader.Configurator.Traits uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.Exception, so a change to Symfony.Component.DependencyInjection.Exception can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.Exception.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Compiler uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.Attribute, so a change to Symfony.Component.DependencyInjection.Attribute can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.Attribute.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Compiler uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.ParameterBag, so a change to Symfony.Component.DependencyInjection.ParameterBag can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.ParameterBag.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Compiler uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.Extension, so a change to Symfony.Component.DependencyInjection.Extension can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.Extension.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Compiler uses a module listed above it, which is the healthy direction.
9→10 Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjectionpart of a loop✕
Connections
71 pairs of types, where a type in Symfony.Component.DependencyInjection.Compiler uses a type in Symfony.Component.DependencyInjection. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.
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.
9→11 Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.Argumentpart of a loop✕
Connections
1 pair of types, where a type in Symfony.Component.DependencyInjection.Compiler uses a type in Symfony.Component.DependencyInjection.Argument.
Symfony.Component.DependencyInjection.Compiler uses Symfony.Component.DependencyInjection.Argument, so a change to Symfony.Component.DependencyInjection.Argument can break Symfony.Component.DependencyInjection.Compiler, while a change to Symfony.Component.DependencyInjection.Compiler can't break Symfony.Component.DependencyInjection.Argument.
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.
Symfony.Component.DependencyInjection uses Symfony.Component.DependencyInjection.LazyProxy.Instantiator, so a change to Symfony.Component.DependencyInjection.LazyProxy.Instantiator can break Symfony.Component.DependencyInjection, while a change to Symfony.Component.DependencyInjection can't break Symfony.Component.DependencyInjection.LazyProxy.Instantiator.
Position
Below the diagonal: Symfony.Component.DependencyInjection uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection uses Symfony.Component.DependencyInjection.ParameterBag, so a change to Symfony.Component.DependencyInjection.ParameterBag can break Symfony.Component.DependencyInjection, while a change to Symfony.Component.DependencyInjection can't break Symfony.Component.DependencyInjection.ParameterBag.
Position
Below the diagonal: Symfony.Component.DependencyInjection uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection uses Symfony.Component.DependencyInjection.Extension, so a change to Symfony.Component.DependencyInjection.Extension can break Symfony.Component.DependencyInjection, while a change to Symfony.Component.DependencyInjection can't break Symfony.Component.DependencyInjection.Extension.
Position
Below the diagonal: Symfony.Component.DependencyInjection uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection uses Symfony.Component.DependencyInjection.Compiler, so a change to Symfony.Component.DependencyInjection.Compiler can break Symfony.Component.DependencyInjection, while a change to Symfony.Component.DependencyInjection can't break Symfony.Component.DependencyInjection.Compiler.
Position
Below the diagonal: Symfony.Component.DependencyInjection uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Argument uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Argument, while a change to Symfony.Component.DependencyInjection.Argument can't break Symfony.Component.DependencyInjection.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Argument uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Config uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Config, while a change to Symfony.Component.DependencyInjection.Config can't break Symfony.Component.DependencyInjection.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Config uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in Symfony.Component.DependencyInjection.Kernel uses a type in Symfony.Component.DependencyInjection.Loader.Configurator.
Symfony.Component.DependencyInjection.Kernel uses Symfony.Component.DependencyInjection.Loader.Configurator, so a change to Symfony.Component.DependencyInjection.Loader.Configurator can break Symfony.Component.DependencyInjection.Kernel, while a change to Symfony.Component.DependencyInjection.Kernel can't break Symfony.Component.DependencyInjection.Loader.Configurator.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Kernel uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Kernel uses Symfony.Component.DependencyInjection.Extension, so a change to Symfony.Component.DependencyInjection.Extension can break Symfony.Component.DependencyInjection.Kernel, while a change to Symfony.Component.DependencyInjection.Kernel can't break Symfony.Component.DependencyInjection.Extension.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Kernel uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Kernel uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Kernel, while a change to Symfony.Component.DependencyInjection.Kernel can't break Symfony.Component.DependencyInjection.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Kernel uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.LazyProxy.PhpDumper uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.LazyProxy.PhpDumper, while a change to Symfony.Component.DependencyInjection.LazyProxy.PhpDumper can't break Symfony.Component.DependencyInjection.
Position
Below the diagonal: Symfony.Component.DependencyInjection.LazyProxy.PhpDumper uses a module listed above it, which is the healthy direction.
Loader.Configurator uses Symfony.Component.DependencyInjection.Loader.Configurator, so a change to Symfony.Component.DependencyInjection.Loader.Configurator can break Loader.Configurator, while a change to Loader.Configurator can't break Symfony.Component.DependencyInjection.Loader.Configurator.
Position
Below the diagonal: Loader.Configurator uses a module listed above it, which is the healthy direction.
Loader.Configurator uses Symfony.Component.DependencyInjection.Argument, so a change to Symfony.Component.DependencyInjection.Argument can break Loader.Configurator, while a change to Loader.Configurator can't break Symfony.Component.DependencyInjection.Argument.
Position
Below the diagonal: Loader.Configurator uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Dumper uses Symfony.Component.DependencyInjection.Compiler, so a change to Symfony.Component.DependencyInjection.Compiler can break Symfony.Component.DependencyInjection.Dumper, while a change to Symfony.Component.DependencyInjection.Dumper can't break Symfony.Component.DependencyInjection.Compiler.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Dumper uses a module listed above it, which is the healthy direction.
Symfony.Component.DependencyInjection.Dumper uses Symfony.Component.DependencyInjection, so a change to Symfony.Component.DependencyInjection can break Symfony.Component.DependencyInjection.Dumper, while a change to Symfony.Component.DependencyInjection.Dumper can't break Symfony.Component.DependencyInjection.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Dumper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in Symfony.Component.DependencyInjection.Dumper uses a type in Symfony.Component.DependencyInjection.LazyProxy.PhpDumper.
Symfony.Component.DependencyInjection.Dumper uses Symfony.Component.DependencyInjection.LazyProxy.PhpDumper, so a change to Symfony.Component.DependencyInjection.LazyProxy.PhpDumper can break Symfony.Component.DependencyInjection.Dumper, while a change to Symfony.Component.DependencyInjection.Dumper can't break Symfony.Component.DependencyInjection.LazyProxy.PhpDumper.
Position
Below the diagonal: Symfony.Component.DependencyInjection.Dumper uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 50.6 · Adequate · gated by D1, D2, 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
A05:2025 — Injection
8
Medium
Roadmap
Top priorities: 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; Expand the README with getting-started, architecture overview and a project map; Add a CI workflow that builds and runs the test suite on every push/PR.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
Run what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
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.
Bring the 118 bodies over 15 down to 15 or less in Cognitive Complexity — start with ContentLoaderTrait.parseDefinition (cognitive 220), EnvVarProcessor.getEnv (cognitive 178), AutowirePass.autowireMethod (cognitive 169).
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 — 4
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 — 362
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 — 31
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 20
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
This survey 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. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 39 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, 386 of 397 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 or a scanner, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 4 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D21 Naming Consistency — not measured this run — We 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — We 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.
D24 Comment Value — not measured this run — We 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D26 Project Cohesion — not measured this run — We 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. `(repository root)` (24083 LoC, 233 module-visible types across 15 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `Argument/LazyClosure.php`, `Argument/RewindableGenerator.php`, `Attribute/Autowire.php`, `Compiler/AttributeAutoconfigurationPass.php`, `Container.php`, … (+7 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We 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 Symfony DependencyInjection and a PSR-11 container (Psr\Container), whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — We 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, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust 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.
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.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — We 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, Rust, Go, Swift, Erlang, F# and Visual Basic 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 (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do 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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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.
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.
+ 71 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with ContentLoaderTrait.parseDefinition (cyclomatic 127), EnvVarProcessor.getEnv (cyclomatic 105), CheckTypeDeclarationsPass.checkType (cyclomatic 75). — 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 Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 113 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 118 bodies over 15 down to 15 or less in Cognitive Complexity — start with ContentLoaderTrait.parseDefinition (cognitive 220), EnvVarProcessor.getEnv (cognitive 178), AutowirePass.autowireMethod (cognitive 169). — 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 118 together lifts Cognitive Complexity from 2.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 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 8 MethodTooLong finding(s) in God Classes — start with ContentLoaderTrait.php (2), EnvVarProcessor.php, XmlDumper.php. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 FileTooLong finding(s) in God Classes — start with REDACTED, ContainerBuilder.php, ContentLoaderTrait.php. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with ContainerBuilder.php, Definition.php, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
19 duplicated block group(s) detected. 2.6 % of the production lines (615 of 24,083) are in a reported copy. A further 16 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (9 corresponding lines) · ×3ServicesResetter.php:121
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with DefaultsConfigurator.php (2), ServicesResetter.php. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ContentLoaderTrait.php (2), XmlDumper.php. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with REDACTED, ParameterBag.php. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling0.0 / 10Critical✓ 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.
12 production modules (source-import), 1 dependency cycle(s), 2 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 1 module(s) off the main sequence.
Circular dependencyContainer.php:15
Unstable project Dumper
Unstable project Kernel
Off the main sequence: Exception
What to do
Resolve the 1 Circular dependency finding(s) in Coupling — start with Container.php. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Unstable project Dumper finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project Kernel finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
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 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with ServiceConfigurator.php, PrototypeConfigurator.php, InlineServiceConfigurator.php. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.3 / 10Stronggated by 79 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
9 skipped (9 with a documented reason), 81 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1749 tests.
No assertions: testNamedAliasByParameterNameIsDeprecated · ×79Tests/Compiler/AutowirePassTest.php:1268
No assertions (declared): testWhenEnv · ×2Tests/Loader/PhpFileLoaderTest.php:379
What to do
Resolve the 79 No assertions finding(s) in Test Quality — start with CheckTypeDeclarationsPassTest.php (36), CheckAliasValidityPassTest.php (5), CheckDefinitionValidityPassTest.php (5). — One of this dimension's main actionable groups (79 warning-level).
Detailed fixes: d10_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: 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: REDACTED (7×67=469); ContainerBuilder.php (14×23=322); Compiler/MergeExtensionConfigurationPass.php (9×32=288)
Hotspot: REDACTED · ×11REDACTED:1914
What to do
Resolve the 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, ContainerBuilder.php, MergeExtensionConfigurationPass.php. — One of this dimension's main actionable groups (11 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.9 / 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.
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Compiler/DecoratorServicePass.php. Counted over 97 of the 231 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
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).
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 24083 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: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
49 % of calls cross a namespace and 2 % go through an interface, but 97 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
8 finding(s): 0 critical, 0 high, 8 medium, 0 low. semgrep hit a parse error in 82 file(s) — `Argument/LazyClosure.php` (line 27), `Argument/RewindableGenerator.php` (line 24, line 25), `Attribute/Autowire.php` (line 27, line 28), `Compiler/AttributeAutoconfigurationPass.php` (line 40), `Container.php` (line 207, line 386), … (+77 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
4 of 97 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Loader/Configurator/EnvConfigurator.php. Counted over 97 of the 231 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 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with TaggedIteratorArgument.php. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Change coupling finding(s) in Change Coupling — start with XmlDumper.php, AnalyzeServiceReferencesPass.php. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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.
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.
The projects (root) → Argument → (root) (one cycle inside a mutually-dependent group of 12 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference. — Container.php:15
What to do
Break project reference cycles by extracting shared abstractions into a separate project; keep the graph a DAG.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation7.5 / 10Strong✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
`Loader` (production) references the test project `Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference. — Loader/PhpFileLoader.php:19
What to do
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 57 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
Expand the README with getting-started, architecture overview and a project map.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Most of the production code is in directories of its own, but 21 application file(s) sit at the repository root beside the build and tooling files (`Alias.php`, `ChildDefinition.php`, `Container.php`, `ContainerBuilder.php`, `ContainerInterface.php` and 16 more).
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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.
No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
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 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.
The `match` arm on line 401 (`\is_array($value) && $xmlAttr .= ' type="collection"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject. — Dumper/XmlDumper.php:401
The `match` arm on line 402 (`$value instanceof IteratorArgument && $xmlAttr .= ' type="iterator"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject. — Dumper/XmlDumper.php:402
The `match` arm on line 403 (`$value instanceof ServiceLocatorArgument && $xmlAttr .= ' type="service_locator"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject. — Dumper/XmlDumper.php:403
The `match` arm on line 404 (`$value instanceof ServiceClosureArgument && !$value->getValues()[0] instanceof Reference && $xmlAttr .= ' type="service_closure"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject. — Dumper/XmlDumper.php:404
What to do
Each finding names the mutation inside the `case` label or `when` guard and the short-circuiting operator that decides whether it happens at all. Confirm from the two, then move the change out of the label: a JavaScript or PHP `case` expression, a PHP `match` arm's conditions, a Java `when` guard, a Kotlin `when` branch's conditions, a Ruby `when` clause or `in … if` guard, a Python `case … if` guard, a Dart `when` guard, a Rust `match` guard, a Scala `case … if` guard, an F# rule's `when` guard and a Visual Basic `Case` clause are evaluated while the switch is still MATCHING — on labels that are then not selected, and not at all once an earlier label has matched or an operand to its left has answered. Leave the label reading only and put the increment in the arm's BODY, where it runs exactly when the arm is chosen, or hoist it above the switch if it must happen on every subject.
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?
X27 · Collection changed while being enumerated7.9 / 10Strong✓ Tool-verified
Other · Code Health — Whether a `foreach` leaves the array or collection it is walking alone — PHP raises nothing, but the loop's view and the collection part: an array walked by value (and a Doctrine or Laravel collection) is walked as the snapshot taken when the loop began, so an element added in the body is never visited and one removed is visited anyway; an array walked by reference (`as &$v`) and an SPL container (`SplObjectStorage`, `ArrayObject`, `SplQueue`) are walked live, so an added element is walked too and a removal skips the next one; and after an `array_splice`, `array_shift` or sort every later key names a different element.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
line 1860 walks `$arguments` by value, so the walk is the snapshot taken when the loop began, and line 1887 changes that same collection with `$arguments = …` before the next iteration: the loop carries on over the old value while the body now works on the new one. PHP raises nothing, so the loop completes over a different set than the code meant. — REDACTED:1860
What to do
Each finding names the two lines that cannot both stand — the `foreach` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`$kept = array_filter($items, $keep)`, `$batch->reject(…)`); for a worklist, loop `while (($next = array_shift($queue)) !== null)` so what is added is visited; walk a copy (`foreach (array_values($items) as …)`, `foreach (clone $storage as …)`) and change the original; remove only the CURRENT element (`unset($items[$key])`), which an array walk tolerates; or — where only the first match was ever meant — `break` straight after the change.
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. (×2) — REDACTED:145, REDACTED:169
`catch (\Throwable)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — Compiler/MergeExtensionConfigurationPass.php:163
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.
This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
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 — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 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.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
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.
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D11 Test Reliability — Test reliability not included — no .php test runner
D12 Dependency Hygiene — Not scored — 4 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
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+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
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) — 12 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 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, Scala, Rust and Java, 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
M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — no CI workflow found
P2 Observability — This repository's PHP source (1 module(s), 231 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the PHP source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
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.
Project dependency cycle Container.php:15— The projects (root) → Argument → (root) (one cycle inside a mutually-dependent group of 12 projects) form a reference cycle. Cyclic dependencies prevent independent build/test/deploy, blur ownership, and tend to grow into a big ball of mud. Break the cycle by extracting the shared types into a separate project both can reference.
AX8 · Test isolation· Production project references a test project · ×1
Production project references a test project: Loader → Tests Loader/PhpFileLoader.php:19— `Loader` (production) references the test project `Tests`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
Boundary-crossing change coupling: TaggedIteratorArgument.php ↔ YamlFileLoader.php Argument/TaggedIteratorArgument.php:1— `Argument/TaggedIteratorArgument.php` (context Argument) and `Loader/YamlFileLoader.php` (context Loader) sit in DIFFERENT parts of the tree yet 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 — 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 `10860717` [DependencyInjection] Deprecate default index/priority methods when d…; `06ae1463` [DependencyInjection] Auto exclude referencing service in `TaggedIter…; `86457a08` [DependencyInjection] added Ability to define a priority method for t… — run `git show` on any of them.
No assertions: testNamedAliasByParameterNameIsDeprecated Tests/Compiler/AutowirePassTest.php:1268— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessAcceptsClassImplementingAliasedInterface Tests/Compiler/CheckAliasValidityPassTest.php:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresArbitraryAlias Tests/Compiler/CheckAliasValidityPassTest.php:45— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresTargetWithFactory Tests/Compiler/CheckAliasValidityPassTest.php:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresTargetWithoutClass Tests/Compiler/CheckAliasValidityPassTest.php:65— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresDeprecatedAlias Tests/Compiler/CheckAliasValidityPassTest.php:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresMethodCalls Tests/Compiler/CheckCircularReferencesPassTest.php:109— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresLazyServices Tests/Compiler/CheckCircularReferencesPassTest.php:120— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessIgnoresIteratorArguments Tests/Compiler/CheckCircularReferencesPassTest.php:147— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessAcceptsServiceLocatorWithoutClass Tests/Compiler/CheckDefinitionValidityPassTest.php:43— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcess Tests/Compiler/CheckDefinitionValidityPassTest.php:66— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValidTags Tests/Compiler/CheckDefinitionValidityPassTest.php:78— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testDynamicPrivateName Tests/Compiler/CheckDefinitionValidityPassTest.php:147— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessSkipsDefinitionsWithErrors Tests/Compiler/CheckDefinitionValidityPassTest.php:159— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcess Tests/Compiler/CheckExceptionOnInvalidReferenceBehaviorPassTest.php:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessDefinitionWithBindings Tests/Compiler/CheckExceptionOnInvalidReferenceBehaviorPassTest.php:74— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAllowsBuilderWithoutSetup Tests/Compiler/CheckFactoryBuilderCircularReferencePassTest.php:89— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAllowsStringFactoryWithSelfSetterCycle Tests/Compiler/CheckFactoryBuilderCircularReferencePassTest.php:108— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAllowsConstructorArgInlinedSetterCycle Tests/Compiler/CheckFactoryBuilderCircularReferencePassTest.php:123— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIgnoresLazyConsumer Tests/Compiler/CheckFactoryBuilderCircularReferencePassTest.php:143— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testIgnoresInlinedDefinitionFactoryWithoutCycle Tests/Compiler/CheckFactoryBuilderCircularReferencePassTest.php:186— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcess Tests/Compiler/CheckReferenceValidityPassTest.php:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessSuccessWhenPassingTooManyArgumentInConstructor Tests/Compiler/CheckTypeDeclarationsPassTest.php:103— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessSuccessWhenPassingAnIteratorArgumentToIterable Tests/Compiler/CheckTypeDeclarationsPassTest.php:398— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testProcessSuccessWhenPassingATaggedClassMapArgumentToArrayOrIterable Tests/Compiler/CheckTypeDeclarationsPassTest.php:410— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Hotspot: REDACTED REDACTED:1914— REDACTED changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in PhpDumper.dumpValue at line 1914. 2 of those changes were fix/bug commits, and the other 5 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +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.
Hotspot: ContainerBuilder.php ContainerBuilder.php:683— ContainerBuilder.php changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in ContainerBuilder.merge at line 683. 4 of those changes were fix/bug commits, and the other 10 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- ContainerBuilder.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: Compiler/MergeExtensionConfigurationPass.php Compiler/MergeExtensionConfigurationPass.php:50— Compiler/MergeExtensionConfigurationPass.php changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in MergeExtensionConfigurationPass.process at line 50. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/MergeExtensionConfigurationPass.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: REDACTED REDACTED:123— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in KernelTrait.initializeContainer at line 123. 1 of those changes was a fix/bug commit, and the other 5 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +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.
Hotspot: Compiler/CheckTypeDeclarationsPass.php Compiler/CheckTypeDeclarationsPass.php:168— Compiler/CheckTypeDeclarationsPass.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in CheckTypeDeclarationsPass.checkType at line 168. 1 of those changes was a fix/bug commit, and the other 1 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/CheckTypeDeclarationsPass.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: Compiler/PriorityTaggedServiceTrait.php Compiler/PriorityTaggedServiceTrait.php:39— Compiler/PriorityTaggedServiceTrait.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in PriorityTaggedServiceTrait.findAndSortTaggedServices at line 39. 1 of those changes was a fix/bug commit, and the other 2 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/PriorityTaggedServiceTrait.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: Dumper/XmlDumper.php Dumper/XmlDumper.php:299— Dumper/XmlDumper.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in XmlDumper.convertParameters at line 299. 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Dumper/XmlDumper.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: Compiler/BeforeAfterSorter.php Compiler/BeforeAfterSorter.php:97— Compiler/BeforeAfterSorter.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in BeforeAfterSorter.sortWithPriorities at line 97. 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/BeforeAfterSorter.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: Argument/LazyClosure.php Argument/LazyClosure.php:52— Argument/LazyClosure.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in LazyClosure.getCode at line 52. 2 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Argument/LazyClosure.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: Compiler/ServiceLocatorTagPass.php Compiler/ServiceLocatorTagPass.php:35— Compiler/ServiceLocatorTagPass.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ServiceLocatorTagPass.processValue at line 35. 1 of those changes was a fix/bug commit, and the other 1 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/ServiceLocatorTagPass.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: Compiler/DecoratorServicePass.php Compiler/DecoratorServicePass.php:33— Compiler/DecoratorServicePass.php changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in DecoratorServicePass.process at line 33. 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-08-19..2026-11-17, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-19 00:03:58 +01:00' --until='2026-11-17 00:03:58 +01:00' --full-history --no-merges -- Compiler/DecoratorServicePass.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.
MethodTooLong: ContentLoaderTrait.parseDefinition Loader/ContentLoaderTrait.php:297— MethodTooLong — parseDefinition runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× 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: EnvVarProcessor.getEnv EnvVarProcessor.php:71— MethodTooLong — getEnv runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: ContentLoaderTrait.resolveServices Loader/ContentLoaderTrait.php:771— MethodTooLong — resolveServices runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: XmlDumper.convertParameters Dumper/XmlDumper.php:299— MethodTooLong — convertParameters runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: AutowirePass.autowireMethod Compiler/AutowirePass.php:269— MethodTooLong — autowireMethod runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: PriorityTaggedServiceTrait.findAndSortTaggedServices Compiler/PriorityTaggedServiceTrait.php:39— MethodTooLong — findAndSortTaggedServices runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.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: CheckTypeDeclarationsPass.checkType Compiler/CheckTypeDeclarationsPass.php:168— MethodTooLong — checkType runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.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: ContainerBuilder.createService ContainerBuilder.php:1165— MethodTooLong — createService runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.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.
Low cohesion: ServiceConfigurator (LCOM4 25) Loader/Configurator/ServiceConfigurator.php:20— ServiceConfigurator's methods fall into 25 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 25 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: PrototypeConfigurator (LCOM4 18) Loader/Configurator/PrototypeConfigurator.php:21— PrototypeConfigurator's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InlineServiceConfigurator (LCOM4 12) Loader/Configurator/InlineServiceConfigurator.php:19— InlineServiceConfigurator's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Definition (LCOM4 9) Definition.php:23— Definition'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: Extension (LCOM4 4) Extension/Extension.php:27— Extension's methods fall into 4 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 4 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.
X21 · Side-effecting pattern guard· Pattern guard mutates state while matching · ×4
Pattern guard mutates state while matching Dumper/XmlDumper.php:401— The `match` arm on line 401 (`\is_array($value) && $xmlAttr .= ' type="collection"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject.
Pattern guard mutates state while matching Dumper/XmlDumper.php:402— The `match` arm on line 402 (`$value instanceof IteratorArgument && $xmlAttr .= ' type="iterator"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject.
Pattern guard mutates state while matching Dumper/XmlDumper.php:403— The `match` arm on line 403 (`$value instanceof ServiceLocatorArgument && $xmlAttr .= ' type="service_locator"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject.
Pattern guard mutates state while matching Dumper/XmlDumper.php:404— The `match` arm on line 404 (`$value instanceof ServiceClosureArgument && !$value->getValues()[0] instanceof Reference && $xmlAttr .= ' type="service_closure"' =>`) changes `$xmlAttr` with `$xmlAttr .= …` while the `match` is deciding whether that arm applies. PHP evaluates a `match` arm's conditions one after another during MATCHING, and stops at the first that is identical to the subject — so the change lands whenever this arm is merely TESTED, whether or not it is then chosen, and never once an earlier arm has matched. And `&&` short-circuits, so it is skipped altogether whenever the operand to its left already decides the condition. The accounting therefore depends on evaluation order and on how many arms the subject was compared against, not on any statement a reader can point at: a counter kept this way misses exactly the path the left operand rules out, so it cannot reach a limit it is checked against on that path. Move the change out of the condition — leave it reading only (`$xmlAttr + 1 >= $limit`) and make the mutation part of the arm's RESULT, where it runs precisely when the arm is chosen, or hoist it above the `match` if it must happen for every subject.
FileTooLong: REDACTED REDACTED— FileTooLong — 1472 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 972 over it, 2.94× 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: ./ContainerBuilder.php ContainerBuilder.php— FileTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ContainerBuilder (64-2004). The bar is 500 significant lines; this is 340 over it, 1.68× 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: Loader/ContentLoaderTrait.php Loader/ContentLoaderTrait.php— FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 109 over it, 1.22× 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.
TooManyMethods: ContainerBuilder ContainerBuilder.php:64— 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: Definition Definition.php:23— 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: PhpDumper REDACTED:57— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) ServicesResetter.php:121— ServicesResetter.php:121-129 | Container.php:461-469 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) Loader/Configurator/DefaultsConfigurator.php:46— Loader/Configurator/DefaultsConfigurator.php:46-54 | Loader/Configurator/Traits/TagTrait.php:25-33 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) Loader/Configurator/DefaultsConfigurator.php:66— Loader/Configurator/DefaultsConfigurator.php:66-74 | Loader/Configurator/Traits/TagTrait.php:43-51 — These two members are one piece of code written twice and then edited apart: 9 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.
Duplicated block (10 lines × 2) Dumper/XmlDumper.php:330— Dumper/XmlDumper.php:330-339 | Dumper/XmlDumper.php:388-397 — 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 `Dumper/XmlDumper.php:330` 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) Loader/ContentLoaderTrait.php:246— Loader/ContentLoaderTrait.php:246-255 | Loader/ContentLoaderTrait.php:583-592 — 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 `Loader/ContentLoaderTrait.php:246` 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) Loader/ContentLoaderTrait.php:411— Loader/ContentLoaderTrait.php:411-420 | Loader/ContentLoaderTrait.php:483-492 — 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 `Loader/ContentLoaderTrait.php:411` 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.
ClassTooLong: ContainerBuilder ContainerBuilder.php:64— ClassTooLong — 794 significant lines (blank, comment-only and punctuation-only lines excluded), 80 methods. The bar is 400 significant lines; this is 394 over it, 1.99× 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: AutowirePass Compiler/AutowirePass.php:39— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 13 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: XmlDumper.php ↔ YamlDumper.php Dumper/XmlDumper.php:1— `Dumper/XmlDumper.php` and `Dumper/YamlDumper.php` change together 59% of the time (59 of the 100 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 59 shared commits counted here, the most recent 3 are `7b810f30` [DependencyInjection] Support autowiring env vars as closures or `Str…; `821403e9` CS fixes - native_function_invocation & static_lambda; `4f33b0c6` PHP CS Fixer: enable static_lambda — run `git show` on any of them.
Change coupling: AnalyzeServiceReferencesPass.php ↔ ServiceReferenceGraphEdge.php Compiler/AnalyzeServiceReferencesPass.php:1— `Compiler/AnalyzeServiceReferencesPass.php` and `Compiler/ServiceReferenceGraphEdge.php` 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 — 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 `dfb5367d` [DependencyInjection] Fix circular references through expressions; `0d17dedc` [DependencyInjection] Fix sharing services used only by tagged iterators; `5ec6098a` [DI] fix taking lazy services into account when dumping the container — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) REDACTED:1465— REDACTED:1465-1478 | REDACTED:1483-1496 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) ParameterBag/ParameterBag.php:269— ParameterBag/ParameterBag.php:269-282 | ParameterBag/ParameterBag.php:287-300 — These two members are one piece of code written twice and then edited apart: 14 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 (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) REDACTED:71— REDACTED:71-80 | REDACTED:85-94 — These two members are one piece of code written twice and then edited apart: 10 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.
Edited copy of a member (10 corresponding lines) ContainerBuilder.php:1993— ContainerBuilder.php:1993-2002 | Dumper/XmlDumper.php:481-490 — These two members are one piece of code written twice and then edited apart: 10 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.
Duplicated block (11 lines × 2) Compiler/BeforeAfterSorter.php:48— Compiler/BeforeAfterSorter.php:48-58 | Compiler/BeforeAfterSorter.php:113-123 — 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 `Compiler/BeforeAfterSorter.php:48` 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) Loader/Configurator/ContainerConfigurator.php:55— Loader/Configurator/ContainerConfigurator.php:55-65 | Loader/FileLoader.php:458-468 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) Compiler/PriorityTaggedServiceTrait.php:127— Compiler/PriorityTaggedServiceTrait.php:127-135 | Compiler/ResolveTaggedClassMapArgumentPass.php:90-98 — 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) Loader/Configurator/Traits/FactoryTrait.php:27— Loader/Configurator/Traits/FactoryTrait.php:27-35 | Loader/Configurator/Traits/FromCallableTrait.php:44-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 3) Compiler/AutowirePass.php:152— Compiler/AutowirePass.php:152-156 | Compiler/AutowireRequiredMethodsPass.php:28-32 | Compiler/AutowireRequiredPropertiesPass.php:35-39 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Compiler/AutowirePass.php:158` calls `log`, `sprintf`, `getClass` and `Compiler/AutowireRequiredMethodsPass.php:34` 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 × 3) Loader/Configurator/DefaultsConfigurator.php:87— Loader/Configurator/DefaultsConfigurator.php:87-91 | Loader/Configurator/Traits/TagTrait.php:56-60 | Loader/ContentLoaderTrait.php:1009-1013 — before extracting anything, compare `Loader/Configurator/DefaultsConfigurator.php` and `Loader/Configurator/Traits/TagTrait.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. 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 `Loader/Configurator/DefaultsConfigurator.php:87` 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.
Swallowed exception (empty catch) REDACTED:145— 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) REDACTED:169— 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.
ContentLoaderTrait.parseDefinition (cyclomatic 127) Loader/ContentLoaderTrait.php:297— ContentLoaderTrait.parseDefinition has cyclomatic complexity 127 (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.
EnvVarProcessor.getEnv (cyclomatic 105) EnvVarProcessor.php:71— EnvVarProcessor.getEnv has cyclomatic complexity 105 (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.
CheckTypeDeclarationsPass.checkType (cyclomatic 75) Compiler/CheckTypeDeclarationsPass.php:168— CheckTypeDeclarationsPass.checkType has cyclomatic complexity 75 (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.
ContainerBuilder.createService (cyclomatic 68) ContainerBuilder.php:1165— ContainerBuilder.createService has cyclomatic complexity 68 (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.
PhpDumper.dumpValue (cyclomatic 67) REDACTED:1914— PhpDumper.dumpValue has cyclomatic complexity 67 (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.
AutowirePass.autowireMethod (cyclomatic 65) Compiler/AutowirePass.php:269— AutowirePass.autowireMethod 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.
XmlDumper.convertParameters (cyclomatic 64) Dumper/XmlDumper.php:299— XmlDumper.convertParameters has cyclomatic complexity 64 (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.
ResolveBindingsPass.processValue (cyclomatic 58) Compiler/ResolveBindingsPass.php:95— ResolveBindingsPass.processValue has cyclomatic complexity 58 (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.
ContentLoaderTrait.resolveServices (cyclomatic 55) Loader/ContentLoaderTrait.php:771— ContentLoaderTrait.resolveServices has cyclomatic complexity 55 (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.
PhpDumper.dump (cyclomatic 52) REDACTED:136— PhpDumper.dump 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.
PhpDumper.addService (cyclomatic 52) REDACTED:866— PhpDumper.addService 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.
PriorityTaggedServiceTrait.findAndSortTaggedServices (cyclomatic 47) Compiler/PriorityTaggedServiceTrait.php:39— PriorityTaggedServiceTrait.findAndSortTaggedServices 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.
PhpDumper.addNewInstance (cyclomatic 46) REDACTED:1192— PhpDumper.addNewInstance has cyclomatic complexity 46 (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.
XmlDumper.addService (cyclomatic 46) Dumper/XmlDumper.php:95— XmlDumper.addService has cyclomatic complexity 46 (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.
FileLoader.registerClasses (cyclomatic 44) Loader/FileLoader.php:128— FileLoader.registerClasses 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.
ResolveNamedArgumentsPass.processValue (cyclomatic 42) Compiler/ResolveNamedArgumentsPass.php:29— ResolveNamedArgumentsPass.processValue has cyclomatic complexity 42 (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.
KernelTrait.initializeContainer (cyclomatic 41) REDACTED:123— KernelTrait.initializeContainer 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.
YamlDumper.dumpValue (cyclomatic 38) Dumper/YamlDumper.php:252— YamlDumper.dumpValue has cyclomatic complexity 38 (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.
ResolveInstanceofConditionalsPass.processDefinition (cyclomatic 35) Compiler/ResolveInstanceofConditionalsPass.php:78— ResolveInstanceofConditionalsPass.processDefinition 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.
PhpDumper.addInlineService (cyclomatic 35) REDACTED:1085— PhpDumper.addInlineService 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.
RegisterServiceSubscribersPass.processValue (cyclomatic 34) Compiler/RegisterServiceSubscribersPass.php:36— RegisterServiceSubscribersPass.processValue 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.
YamlDumper.addService (cyclomatic 33) Dumper/YamlDumper.php:59— YamlDumper.addService has cyclomatic complexity 33 (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.
MergeExtensionConfigurationPass.process (cyclomatic 32) Compiler/MergeExtensionConfigurationPass.php:50— MergeExtensionConfigurationPass.process has cyclomatic complexity 32 (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.
ResolveInvalidReferencesPass.processValue (cyclomatic 32) Compiler/ResolveInvalidReferencesPass.php:59— ResolveInvalidReferencesPass.processValue has cyclomatic complexity 32 (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.
BeforeAfterSorter.sortWithPriorities (cyclomatic 31) Compiler/BeforeAfterSorter.php:97— BeforeAfterSorter.sortWithPriorities 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.
PhpDumper.isTrivialInstance (cyclomatic 30) REDACTED:740— PhpDumper.isTrivialInstance 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.
PhpDumper.getServiceCall (cyclomatic 30) REDACTED:2141— PhpDumper.getServiceCall 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.
AnalyzeServiceReferencesPass.processValue (cyclomatic 29) Compiler/AnalyzeServiceReferencesPass.php:83— AnalyzeServiceReferencesPass.processValue 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.
ContainerBuilder.doResolveServices (cyclomatic 29) ContainerBuilder.php:1358— ContainerBuilder.doResolveServices 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.
MergeExtensionConfigurationPass.forwardExtensionAliases (cyclomatic 27) Compiler/MergeExtensionConfigurationPass.php:179— MergeExtensionConfigurationPass.forwardExtensionAliases 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.
PhpDumper.collectCircularReferences (cyclomatic 27) REDACTED:447— PhpDumper.collectCircularReferences 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.
AbstractRecursivePass.getConstructor (cyclomatic 25) Compiler/AbstractRecursivePass.php:117— AbstractRecursivePass.getConstructor 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.
InlineServiceDefinitionsPass.isInlineableDefinition (cyclomatic 24) Compiler/InlineServiceDefinitionsPass.php:176— InlineServiceDefinitionsPass.isInlineableDefinition 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.
ResolveChildDefinitionsPass.doResolveDefinition (cyclomatic 24) Compiler/ResolveChildDefinitionsPass.php:74— ResolveChildDefinitionsPass.doResolveDefinition 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.
ContainerBuilder.addResource (cyclomatic 24) ContainerBuilder.php:280— ContainerBuilder.addResource 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.
AutowirePass.doProcessValue (cyclomatic 23) Compiler/AutowirePass.php:119— AutowirePass.doProcessValue 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.
AutowirePass.getCombinedAlias (cyclomatic 23) Compiler/AutowirePass.php:733— AutowirePass.getCombinedAlias 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.
CheckDefinitionValidityPass.process (cyclomatic 23) Compiler/CheckDefinitionValidityPass.php:37— CheckDefinitionValidityPass.process 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.
ContainerBuilder.merge (cyclomatic 23) ContainerBuilder.php:683— ContainerBuilder.merge 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.
AutowireLocator.__construct (cyclomatic 22) Attribute/AutowireLocator.php:36— AutowireLocator.__construct 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.
AttributeAutoconfigurationPass.processValue (cyclomatic 22) Compiler/AttributeAutoconfigurationPass.php:79— AttributeAutoconfigurationPass.processValue has cyclomatic complexity 22 (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.
PhpDumper.addInlineReference (cyclomatic 22) REDACTED:1031— PhpDumper.addInlineReference has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ResolveDecoratorStackPass.process (cyclomatic 21) Compiler/ResolveDecoratorStackPass.php:30— ResolveDecoratorStackPass.process 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.
ContainerBuilder.resolveEnvPlaceholders (cyclomatic 21) ContainerBuilder.php:1640— ContainerBuilder.resolveEnvPlaceholders 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.
PhpDumper.generateProxyClasses (cyclomatic 21) REDACTED:569— PhpDumper.generateProxyClasses 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.
AbstractConfigurator.processValue (cyclomatic 21) Loader/Configurator/AbstractConfigurator.php:64— AbstractConfigurator.processValue 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.
AbstractRecursivePass.processValue (cyclomatic 20) Compiler/AbstractRecursivePass.php:67— AbstractRecursivePass.processValue 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.
PhpConfigReferenceDumpPass.process (cyclomatic 20) Compiler/PhpConfigReferenceDumpPass.php:95— PhpConfigReferenceDumpPass.process 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.
ResolveTaggedClassMapArgumentPass.processValue (cyclomatic 20) Compiler/ResolveTaggedClassMapArgumentPass.php:27— ResolveTaggedClassMapArgumentPass.processValue 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.
AutowireRequiredMethodsPass.processValue (cyclomatic 19) Compiler/AutowireRequiredMethodsPass.php:26— AutowireRequiredMethodsPass.processValue 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.
CheckArgumentsValidityPass.processValue (cyclomatic 19) Compiler/CheckArgumentsValidityPass.php:32— CheckArgumentsValidityPass.processValue 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.
InlineServiceDefinitionsPass.process (cyclomatic 19) Compiler/InlineServiceDefinitionsPass.php:42— InlineServiceDefinitionsPass.process 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.
ServiceLocatorTagPass.processValue (cyclomatic 19) Compiler/ServiceLocatorTagPass.php:35— ServiceLocatorTagPass.processValue 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.
PhpDumper.addServiceInclude (cyclomatic 19) REDACTED:642— PhpDumper.addServiceInclude has cyclomatic complexity 19 (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.
KernelTrait.dumpContainer (cyclomatic 19) REDACTED:374— KernelTrait.dumpContainer 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.
PhpFileLoader.callConfigurator (cyclomatic 19) Loader/PhpFileLoader.php:144— PhpFileLoader.callConfigurator 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.
AutowirePass.autowireCalls (cyclomatic 18) Compiler/AutowirePass.php:193— AutowirePass.autowireCalls 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.
JsonSchemaConfigDumpPass.process (cyclomatic 18) Compiler/JsonSchemaConfigDumpPass.php:30— JsonSchemaConfigDumpPass.process has cyclomatic complexity 18 (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.
RegisterAsCallableAttributesPass.process (cyclomatic 18) Compiler/RegisterAsCallableAttributesPass.php:30— RegisterAsCallableAttributesPass.process 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.
Preloader.doPreload (cyclomatic 18) Dumper/Preloader.php:81— Preloader.doPreload 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.
ContentLoaderTrait.parseDefaults (cyclomatic 18) Loader/ContentLoaderTrait.php:219— ContentLoaderTrait.parseDefaults 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.
FileLoader.findClasses (cyclomatic 18) Loader/FileLoader.php:346— FileLoader.findClasses 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.
DecoratorServicePass.process (cyclomatic 17) Compiler/DecoratorServicePass.php:33— DecoratorServicePass.process 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.
PhpDumper.addServiceInstance (cyclomatic 17) REDACTED:692— PhpDumper.addServiceInstance 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.
LazyServiceDumper.getProxyCode (cyclomatic 17) LazyProxy/PhpDumper/LazyServiceDumper.php:112— LazyServiceDumper.getProxyCode 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.
PhpFileLoader.load (cyclomatic 17) Loader/PhpFileLoader.php:37— PhpFileLoader.load 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.
ParameterBag.get (cyclomatic 17) ParameterBag/ParameterBag.php:66— ParameterBag.get 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.
LazyClosure.getCode (cyclomatic 16) Argument/LazyClosure.php:52— LazyClosure.getCode 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.
Autowire.__construct (cyclomatic 16) Attribute/Autowire.php:40— Autowire.__construct 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.
AbstractRecursivePass.getReflectionMethod (cyclomatic 16) Compiler/AbstractRecursivePass.php:193— AbstractRecursivePass.getReflectionMethod 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.
AutowirePass.getAutowiredReference (cyclomatic 16) Compiler/AutowirePass.php:465— AutowirePass.getAutowiredReference 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.
ResolveLazyProxyPass.createProxyDefinition (cyclomatic 16) Compiler/ResolveLazyProxyPass.php:63— ResolveLazyProxyPass.createProxyDefinition 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.
Container.make (cyclomatic 16) Container.php:215— Container.make 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.
ContainerBuilder.doGet (cyclomatic 16) ContainerBuilder.php:603— ContainerBuilder.doGet 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.
PhpDumper.startClass (cyclomatic 16) REDACTED:1292— PhpDumper.startClass 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.
FileLoader.import (cyclomatic 16) Loader/FileLoader.php:74— FileLoader.import 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.
ContentLoaderTrait.parseDefinition (cognitive 220) Loader/ContentLoaderTrait.php:297— ContentLoaderTrait.parseDefinition has cognitive complexity 220 (threshold 15). Drivers by points: if/else 82 (156 pts), ternaries 11 (25 pts), boolean chains 18, loops 7 (14 pts), match/switch 3 (7 pts) (nesting depth added 99). 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.
EnvVarProcessor.getEnv (cognitive 178) EnvVarProcessor.php:71— EnvVarProcessor.getEnv has cognitive complexity 178 (threshold 15). Drivers by points: if/else 64 (118 pts), ternaries 13 (26 pts), boolean chains 22, error handling 3 (7 pts), loops 2 (5 pts) (nesting depth added 74). 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.
AutowirePass.autowireMethod (cognitive 169) Compiler/AutowirePass.php:269— AutowirePass.autowireMethod has cognitive complexity 169 (threshold 15). Drivers by points: if/else 26 (84 pts), ternaries 12 (43 pts), boolean chains 18, loops 5 (15 pts), error handling 2 (9 pts) (nesting depth added 106). 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.
PhpDumper.dumpValue (cognitive 140) REDACTED:1914— PhpDumper.dumpValue has cognitive complexity 140 (threshold 15). Drivers by points: if/else 25 (64 pts), ternaries 13 (46 pts), loops 6 (18 pts), boolean chains 12 (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.
XmlDumper.convertParameters (cognitive 119) Dumper/XmlDumper.php:299— XmlDumper.convertParameters has cognitive complexity 119 (threshold 15). Drivers by points: if/else 28 (69 pts), loops 6 (20 pts), boolean chains 14, match/switch 3 (8 pts), ternaries 3 (8 pts) (nesting depth added 65). 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.
ContentLoaderTrait.resolveServices (cognitive 110) Loader/ContentLoaderTrait.php:771— ContentLoaderTrait.resolveServices has cognitive complexity 110 (threshold 15). Drivers by points: if/else 39 (93 pts), boolean chains 12, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 57). 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.
ResolveNamedArgumentsPass.processValue (cognitive 102) Compiler/ResolveNamedArgumentsPass.php:29— ResolveNamedArgumentsPass.processValue has cognitive complexity 102 (threshold 15). Drivers by points: if/else 18 (48 pts), ternaries 6 (24 pts), loops 6 (18 pts), boolean chains 12 (nesting depth added 60). 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.
PhpDumper.addService (cognitive 100) REDACTED:866— PhpDumper.addService has cognitive complexity 100 (threshold 15). Drivers by points: ternaries 17 (46 pts), if/else 20 (33 pts), boolean chains 14, loops 2 (7 pts) (nesting depth added 47). 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.
PriorityTaggedServiceTrait.findAndSortTaggedServices (cognitive 97) Compiler/PriorityTaggedServiceTrait.php:39— PriorityTaggedServiceTrait.findAndSortTaggedServices has cognitive complexity 97 (threshold 15). Drivers by points: if/else 18 (50 pts), loops 7 (17 pts), ternaries 7 (16 pts), boolean chains 12, match/switch 1 (2 pts) (nesting depth added 52). 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.
FileLoader.registerClasses (cognitive 97) Loader/FileLoader.php:128— FileLoader.registerClasses has cognitive complexity 97 (threshold 15). Drivers by points: if/else 24 (65 pts), loops 7 (15 pts), ternaries 5 (10 pts), boolean chains 7 (nesting depth added 54). 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.
PhpDumper.dump (cognitive 94) REDACTED:136— PhpDumper.dump has cognitive complexity 94 (threshold 15). Drivers by points: if/else 23 (44 pts), loops 11 (28 pts), boolean chains 12, ternaries 6 (10 pts) (nesting depth added 42). 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.
ResolveBindingsPass.processValue (cognitive 93) Compiler/ResolveBindingsPass.php:95— ResolveBindingsPass.processValue has cognitive complexity 93 (threshold 15). Drivers by points: if/else 27 (59 pts), boolean chains 24, loops 4 (6 pts), error handling 2 (4 pts) (nesting depth added 36). 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.
XmlDumper.addService (cognitive 93) Dumper/XmlDumper.php:95— XmlDumper.addService has cognitive complexity 93 (threshold 15). Drivers by points: if/else 33 (53 pts), loops 9 (21 pts), ternaries 4 (15 pts), boolean chains 4 (nesting depth added 43). 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.
ContainerBuilder.createService (cognitive 91) ContainerBuilder.php:1165— ContainerBuilder.createService has cognitive complexity 91 (threshold 15). Drivers by points: if/else 31 (50 pts), boolean chains 25, ternaries 6 (12 pts), loops 3, error handling 1 (nesting depth added 25). 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.
CheckTypeDeclarationsPass.checkType (cognitive 87) Compiler/CheckTypeDeclarationsPass.php:168— CheckTypeDeclarationsPass.checkType has cognitive complexity 87 (threshold 15). Drivers by points: if/else 33 (46 pts), boolean chains 24, error handling 3 (9 pts), loops 2 (4 pts), ternaries 2 (4 pts) (nesting depth added 23). 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.
ResolveInstanceofConditionalsPass.processDefinition (cognitive 80) Compiler/ResolveInstanceofConditionalsPass.php:78— ResolveInstanceofConditionalsPass.processDefinition has cognitive complexity 80 (threshold 15). Drivers by points: if/else 13 (38 pts), loops 7 (19 pts), ternaries 6 (15 pts), boolean chains 8 (nesting depth added 46). 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.
PhpDumper.addNewInstance (cognitive 76) REDACTED:1192— PhpDumper.addNewInstance has cognitive complexity 76 (threshold 15). Drivers by points: if/else 17 (32 pts), ternaries 10 (26 pts), boolean chains 15, loops 2 (3 pts) (nesting depth added 32). 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.
YamlDumper.dumpValue (cognitive 70) Dumper/YamlDumper.php:252— YamlDumper.dumpValue has cognitive complexity 70 (threshold 15). Drivers by points: if/else 21 (47 pts), ternaries 5 (17 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 39). 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.
BeforeAfterSorter.sortWithPriorities (cognitive 69) Compiler/BeforeAfterSorter.php:97— BeforeAfterSorter.sortWithPriorities has cognitive complexity 69 (threshold 15). Drivers by points: if/else 13 (41 pts), loops 9 (16 pts), boolean chains 6, ternaries 2 (6 pts) (nesting depth added 39). 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.
MergeExtensionConfigurationPass.forwardExtensionAliases (cognitive 66) Compiler/MergeExtensionConfigurationPass.php:179— MergeExtensionConfigurationPass.forwardExtensionAliases has cognitive complexity 66 (threshold 15). Drivers by points: if/else 14 (45 pts), loops 6 (13 pts), boolean chains 4, error handling 1 (4 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.
PhpDumper.generateProxyClasses (cognitive 61) REDACTED:569— PhpDumper.generateProxyClasses has cognitive complexity 61 (threshold 15). Drivers by points: if/else 12 (39 pts), loops 4 (11 pts), ternaries 3 (10 pts), boolean chains 1 (nesting depth added 41). 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.
MergeExtensionConfigurationPass.process (cognitive 58) Compiler/MergeExtensionConfigurationPass.php:50— MergeExtensionConfigurationPass.process has cognitive complexity 58 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 9 (16 pts), error handling 4 (10 pts), boolean chains 5, ternaries 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KernelTrait.initializeContainer (cognitive 58) REDACTED:123— KernelTrait.initializeContainer has cognitive complexity 58 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 13, loops 4 (8 pts), ternaries 4 (7 pts), error handling 2 (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.
RegisterServiceSubscribersPass.processValue (cognitive 56) Compiler/RegisterServiceSubscribersPass.php:36— RegisterServiceSubscribersPass.processValue has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (36 pts), ternaries 4 (11 pts), boolean chains 7, loops 2 (nesting depth added 24). 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.
PhpDumper.getServiceCall (cognitive 51) REDACTED:2141— PhpDumper.getServiceCall has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 5 (17 pts), boolean chains 11, loops 1 (nesting depth added 22). 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.
CheckArgumentsValidityPass.processValue (cognitive 50) Compiler/CheckArgumentsValidityPass.php:32— CheckArgumentsValidityPass.processValue has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (46 pts), loops 3 (4 pts) (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.
ContainerBuilder.resolveEnvPlaceholders (cognitive 49) ContainerBuilder.php:1640— ContainerBuilder.resolveEnvPlaceholders has cognitive complexity 49 (threshold 15). Drivers by points: if/else 14 (33 pts), ternaries 3 (8 pts), loops 3 (5 pts), boolean chains 3 (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.
YamlDumper.addService (cognitive 49) Dumper/YamlDumper.php:59— YamlDumper.addService has cognitive complexity 49 (threshold 15). Drivers by points: if/else 24 (31 pts), loops 4 (8 pts), ternaries 3 (8 pts), boolean chains 2 (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.
PhpDumper.collectCircularReferences (cognitive 47) REDACTED:447— PhpDumper.collectCircularReferences has cognitive complexity 47 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 5 (15 pts), boolean chains 10 (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.
ResolveDecoratorStackPass.process (cognitive 46) Compiler/ResolveDecoratorStackPass.php:30— ResolveDecoratorStackPass.process has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (34 pts), loops 6 (12 pts) (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.
ContainerBuilder.doResolveServices (cognitive 46) ContainerBuilder.php:1358— ContainerBuilder.doResolveServices has cognitive complexity 46 (threshold 15). Drivers by points: loops 8 (20 pts), if/else 5 (17 pts), ternaries 4 (9 pts) (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.
ResolveInvalidReferencesPass.processValue (cognitive 45) Compiler/ResolveInvalidReferencesPass.php:59— ResolveInvalidReferencesPass.processValue has cognitive complexity 45 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 9, error handling 1 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts) (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.
PhpDumper.isTrivialInstance (cognitive 43) REDACTED:740— PhpDumper.isTrivialInstance has cognitive complexity 43 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 16, loops 2 (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.
CheckDefinitionValidityPass.process (cognitive 41) Compiler/CheckDefinitionValidityPass.php:37— CheckDefinitionValidityPass.process has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 8, loops 4 (7 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.
PhpDumper.addInlineService (cognitive 41) REDACTED:1085— PhpDumper.addInlineService has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 16, if/else 11 (15 pts), ternaries 5 (8 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.
InlineServiceDefinitionsPass.process (cognitive 40) Compiler/InlineServiceDefinitionsPass.php:42— InlineServiceDefinitionsPass.process has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 6 (11 pts), boolean chains 2 (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.
RegisterAsCallableAttributesPass.process (cognitive 40) Compiler/RegisterAsCallableAttributesPass.php:30— RegisterAsCallableAttributesPass.process has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (23 pts), ternaries 2 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 24). 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.
ResolveTaggedClassMapArgumentPass.processValue (cognitive 39) Compiler/ResolveTaggedClassMapArgumentPass.php:27— ResolveTaggedClassMapArgumentPass.processValue has cognitive complexity 39 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 4 (10 pts), loops 5 (9 pts), boolean chains 2 (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.
AnalyzeServiceReferencesPass.processValue (cognitive 38) Compiler/AnalyzeServiceReferencesPass.php:83— AnalyzeServiceReferencesPass.processValue has cognitive complexity 38 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 9, loops 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutowirePass.autowireCalls (cognitive 38) Compiler/AutowirePass.php:193— AutowirePass.autowireCalls has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (25 pts), loops 3 (4 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (3 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.
DecoratorServicePass.sortByOrderConstraints (cognitive 38) Compiler/DecoratorServicePass.php:194— DecoratorServicePass.sortByOrderConstraints has cognitive complexity 38 (threshold 15). Drivers by points: loops 9 (22 pts), if/else 4 (14 pts), error handling 1 (2 pts) (nesting depth added 24). 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.
ContainerBuilder.addResource (cognitive 38) ContainerBuilder.php:280— ContainerBuilder.addResource has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 3 (6 pts), boolean chains 5 (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.
AbstractRecursivePass.getConstructor (cognitive 37) Compiler/AbstractRecursivePass.php:117— AbstractRecursivePass.getConstructor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (23 pts), ternaries 2 (5 pts), boolean chains 4, loops 2 (4 pts), error handling 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.
AutowirePass.doProcessValue (cognitive 36) Compiler/AutowirePass.php:119— AutowirePass.doProcessValue has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 6, ternaries 2 (6 pts), loops 1 (2 pts), error handling 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.
AbstractRecursivePass.processValue (cognitive 35) Compiler/AbstractRecursivePass.php:67— AbstractRecursivePass.processValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 19). 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.
PhpDumper.addServiceInclude (cognitive 34) REDACTED:642— PhpDumper.addServiceInclude has cognitive complexity 34 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 5 (10 pts), boolean chains 6, ternaries 1 (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.
PhpFileLoader.load (cognitive 34) Loader/PhpFileLoader.php:37— PhpFileLoader.load has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (5 pts), ternaries 1 (4 pts), boolean chains 3 (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.
AttributeAutoconfigurationPass.processValue (cognitive 33) Compiler/AttributeAutoconfigurationPass.php:79— AttributeAutoconfigurationPass.processValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 4 (10 pts), boolean chains 8, error handling 1 (2 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.
AutowireRequiredMethodsPass.processValue (cognitive 33) Compiler/AutowireRequiredMethodsPass.php:26— AutowireRequiredMethodsPass.processValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 6 (9 pts), boolean chains 4, ternaries 1 (4 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.
ContainerBuilder.merge (cognitive 33) ContainerBuilder.php:683— ContainerBuilder.merge has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 9 (13 pts), boolean chains 4 (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.
ContentLoaderTrait.parseDefaults (cognitive 33) Loader/ContentLoaderTrait.php:219— ContentLoaderTrait.parseDefaults has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 4 (6 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.
AutowireLocator.__construct (cognitive 32) Attribute/AutowireLocator.php:36— AutowireLocator.__construct has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 9, ternaries 2 (6 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileLoader.findClasses (cognitive 32) Loader/FileLoader.php:346— FileLoader.findClasses has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 5 (8 pts), ternaries 1 (3 pts), error handling 1 (2 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.
ServiceLocatorTagPass.processValue (cognitive 31) Compiler/ServiceLocatorTagPass.php:35— ServiceLocatorTagPass.processValue has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 2 (4 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.
ParameterBag.get (cognitive 31) ParameterBag/ParameterBag.php:66— ParameterBag.get has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 5, loops 2 (5 pts) (nesting depth added 15). 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.
AutowirePass.createTypeNotFoundMessage (cognitive 29) Compiler/AutowirePass.php:603— AutowirePass.createTypeNotFoundMessage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (11 pts), boolean chains 2, error handling 1 (2 pts), 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.
LazyServiceDumper.getProxyCode (cognitive 29) LazyProxy/PhpDumper/LazyServiceDumper.php:112— LazyServiceDumper.getProxyCode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (21 pts), ternaries 2 (3 pts), boolean chains 2, loops 1 (2 pts), error handling 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.
AutowirePass.getCombinedAlias (cognitive 28) Compiler/AutowirePass.php:733— AutowirePass.getCombinedAlias has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 6 (11 pts), boolean chains 9, if/else 5 (7 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.
InlineServiceDefinitionsPass.isInlineableDefinition (cognitive 28) Compiler/InlineServiceDefinitionsPass.php:176— InlineServiceDefinitionsPass.isInlineableDefinition has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 12, loops 2 (3 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.
PhpConfigReferenceDumpPass.process (cognitive 28) Compiler/PhpConfigReferenceDumpPass.php:95— PhpConfigReferenceDumpPass.process has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 5 (7 pts), boolean chains 2, ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveChildDefinitionsPass.doResolveDefinition (cognitive 28) Compiler/ResolveChildDefinitionsPass.php:74— ResolveChildDefinitionsPass.doResolveDefinition has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21 (23 pts), loops 3 (4 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, 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.
KernelTrait.dumpContainer (cognitive 27) REDACTED:374— KernelTrait.dumpContainer has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (5 pts), boolean chains 4, error handling 1 (3 pts), ternaries 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.
BeforeAfterSorter.sort (cognitive 26) Compiler/BeforeAfterSorter.php:40— BeforeAfterSorter.sort has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 5 (11 pts), boolean chains 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.
DecoratorServicePass.process (cognitive 25) Compiler/DecoratorServicePass.php:33— DecoratorServicePass.process has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 4 (6 pts), ternaries 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.
AttributeAutoconfigurationPass.process (cognitive 24) Compiler/AttributeAutoconfigurationPass.php:32— AttributeAutoconfigurationPass.process has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 5 (11 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.
AutowirePass.getAutowiredReference (cognitive 24) Compiler/AutowirePass.php:465— AutowirePass.getAutowiredReference has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (3 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.
Container.make (cognitive 24) Container.php:215— Container.make has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpDumper.stripComments (cognitive 24) REDACTED:2480— PhpDumper.stripComments has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 pts), ternaries 1 (4 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.
Preloader.doPreload (cognitive 24) Dumper/Preloader.php:81— Preloader.doPreload has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 4 (5 pts), error handling 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.
ContentLoaderTrait.parseCallable (cognitive 24) Loader/ContentLoaderTrait.php:727— ContentLoaderTrait.parseCallable 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.
ServicesResetter.resetInstance (cognitive 24) ServicesResetter.php:76— ServicesResetter.resetInstance has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonSchemaConfigDumpPass.process (cognitive 23) Compiler/JsonSchemaConfigDumpPass.php:30— JsonSchemaConfigDumpPass.process has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 6 (8 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.
ResettableServicePass.process (cognitive 23) Compiler/ResettableServicePass.php:26— ResettableServicePass.process has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 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.
ResolveAutowireInlineAttributesPass.registerAutowireInlineAttributes (cognitive 22) Compiler/ResolveAutowireInlineAttributesPass.php:86— ResolveAutowireInlineAttributesPass.registerAutowireInlineAttributes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpDumper.addInlineReference (cognitive 22) REDACTED:1031— PhpDumper.addInlineReference has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 7, ternaries 2, loops 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.
FileLoader.import (cognitive 22) Loader/FileLoader.php:74— FileLoader.import has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (2 pts), error handling 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.
ReplaceAliasByActualDefinitionPass.process (cognitive 21) Compiler/ReplaceAliasByActualDefinitionPass.php:36— ReplaceAliasByActualDefinitionPass.process has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LazyClosure.getCode (cognitive 20) Argument/LazyClosure.php:52— LazyClosure.getCode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (6 pts), boolean chains 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.
CheckFactoryBuilderCircularReferencePass.process (cognitive 20) Compiler/CheckFactoryBuilderCircularReferencePass.php:39— CheckFactoryBuilderCircularReferencePass.process has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 2, 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.
CheckFactoryBuilderCircularReferencePass.setupReferencesCurrent (cognitive 20) Compiler/CheckFactoryBuilderCircularReferencePass.php:89— CheckFactoryBuilderCircularReferencePass.setupReferencesCurrent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveBindingsPass.process (cognitive 20) Compiler/ResolveBindingsPass.php:40— ResolveBindingsPass.process has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts), ternaries 1 (3 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.
TagDecoratorPass.process (cognitive 20) Compiler/TagDecoratorPass.php:24— TagDecoratorPass.process has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (6 pts) (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.
PhpDumper.addServiceMethodCalls (cognitive 20) REDACTED:795— PhpDumper.addServiceMethodCalls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (7 pts), loops 3 (4 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.
PhpDumper.getAutoloadFile (cognitive 20) REDACTED:2391— PhpDumper.getAutoloadFile has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 4, loops 2 (3 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.
PhpFileLoader.callConfigurator (cognitive 20) Loader/PhpFileLoader.php:144— PhpFileLoader.callConfigurator has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 3, match/switch 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.
AbstractRecursivePass.getReflectionMethod (cognitive 19) Compiler/AbstractRecursivePass.php:193— AbstractRecursivePass.getReflectionMethod has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveUnusedDefinitionsPass.process (cognitive 19) Compiler/RemoveUnusedDefinitionsPass.php:32— RemoveUnusedDefinitionsPass.process has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (6 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveInstanceofConditionalsPass.filterAutoconfigured (cognitive 19) Compiler/ResolveInstanceofConditionalsPass.php:223— ResolveInstanceofConditionalsPass.filterAutoconfigured has cognitive complexity 19 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 4, ternaries 2 (4 pts), boolean chains 1 (nesting depth added 8). 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.
ResolveParameterPlaceHoldersPass.processValue (cognitive 19) Compiler/ResolveParameterPlaceHoldersPass.php:62— ResolveParameterPlaceHoldersPass.processValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContainerBuilder.getReflectionClass (cognitive 19) ContainerBuilder.php:414— ContainerBuilder.getReflectionClass has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (5 pts), boolean chains 1, error handling 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.
GraphvizDumper.findEdges (cognitive 19) Dumper/GraphvizDumper.php:112— GraphvizDumper.findEdges has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), loops 2 (4 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.
PhpDumper.startClass (cognitive 19) REDACTED:1292— PhpDumper.startClass has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, ternaries 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.
PhpDumper.getDefinitionsFromArguments (cognitive 19) REDACTED:1856— PhpDumper.getDefinitionsFromArguments has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpDumper.export (cognitive 19) REDACTED:2323— PhpDumper.export has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (7 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.
EnvPlaceholderParameterBag.get (cognitive 19) ParameterBag/EnvPlaceholderParameterBag.php:29— EnvPlaceholderParameterBag.get has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (6 pts), boolean chains 4 (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.
ServiceLocator.createNotFoundException (cognitive 19) ServiceLocator.php:94— ServiceLocator.createNotFoundException has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 4 (5 pts), error handling 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.
CheckExceptionOnInvalidReferenceBehaviorPass.processValue (cognitive 18) Compiler/CheckExceptionOnInvalidReferenceBehaviorPass.php:45— CheckExceptionOnInvalidReferenceBehaviorPass.processValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, 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.
CheckTypeDeclarationsPass.processValue (cognitive 18) Compiler/CheckTypeDeclarationsPass.php:81— CheckTypeDeclarationsPass.processValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveHotPathPass.processValue (cognitive 18) Compiler/ResolveHotPathPass.php:41— ResolveHotPathPass.processValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 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.
Container.reset (cognitive 18) Container.php:284— Container.reset has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (6 pts), error handling 2 (3 pts), loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContainerBuilder.addObjectResource (cognitive 18) ContainerBuilder.php:379— ContainerBuilder.addObjectResource has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContainerBuilder.doGet (cognitive 18) ContainerBuilder.php:603— ContainerBuilder.doGet has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, error handling 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.
ContainerBuilder.findTaggedResourceIds (cognitive 18) ContainerBuilder.php:1486— ContainerBuilder.findTaggedResourceIds has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 7, 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.
PhpDumper.addDefaultParametersMethod (cognitive 18) REDACTED:1642— PhpDumper.addDefaultParametersMethod has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, 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.
RegisterAutoconfigureAttributesPass.registerForAutoconfiguration (cognitive 17) Compiler/RegisterAutoconfigureAttributesPass.php:61— RegisterAutoconfigureAttributesPass.registerForAutoconfiguration has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (4 pts), boolean chains 3, match/switch 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.
RemoveMissingDependenciesPass.process (cognitive 17) Compiler/RemoveMissingDependenciesPass.php:33— RemoveMissingDependenciesPass.process has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 3 (8 pts) (nesting depth added 9). 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.
ResolveClassPass.process (cognitive 17) Compiler/ResolveClassPass.php:24— ResolveClassPass.process has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 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.
ResolveLazyProxyPass.createProxyDefinition (cognitive 17) Compiler/ResolveLazyProxyPass.php:63— ResolveLazyProxyPass.createProxyDefinition has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 3, ternaries 2 (3 pts), 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.
ValidateEnvPlaceholdersPass.process (cognitive 17) Compiler/ValidateEnvPlaceholdersPass.php:33— ValidateEnvPlaceholdersPass.process has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 5 (7 pts), boolean chains 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.
ContainerBuilder.compile (cognitive 17) ContainerBuilder.php:881— ContainerBuilder.compile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 3 (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.
PhpDumper.addServiceInstance (cognitive 17) REDACTED:692— PhpDumper.addServiceInstance has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, if/else 3 (4 pts), ternaries 1 (2 pts), loops 1, match/switch 1 (nesting depth added 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.
PhpDumper.doExport (cognitive 17) REDACTED:2357— PhpDumper.doExport has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5 (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.
AbstractConfigurator.processValue (cognitive 17) Loader/Configurator/AbstractConfigurator.php:64— AbstractConfigurator.processValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, match/switch 2 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 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.
AutowireRequiredPropertiesPass.processValue (cognitive 16) Compiler/AutowireRequiredPropertiesPass.php:33— AutowireRequiredPropertiesPass.processValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolveDecoratorStackPass.resolveStack (cognitive 16) Compiler/ResolveDecoratorStackPass.php:137— ResolveDecoratorStackPass.resolveStack has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), loops 3 (5 pts), ternaries 1 (3 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.
PhpDumper.addInlineRequires (cognitive 16) REDACTED:1592— PhpDumper.addInlineRequires has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 3 (5 pts), boolean chains 2, ternaries 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.
PhpDumper.getClasses (cognitive 16) REDACTED:2422— PhpDumper.getClasses has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContentLoaderTrait.parseDefinitions (cognitive 16) Loader/ContentLoaderTrait.php:179— ContentLoaderTrait.parseDefinitions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), boolean chains 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) Attribute/AutowireIterator.php:37— Attribute/AutowireIterator.php:37-52 | Attribute/AutowireLocator.php:43-98 | Loader/Configurator/ContainerConfigurator.php:190-203 | Loader/Configurator/ContainerConfigurator.php:216-229 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) Dumper/XmlDumper.php:261— Dumper/XmlDumper.php:261-281 | Dumper/YamlDumper.php:200-217 — These two members are one piece of code written twice and then edited apart: 18 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) ContainerBuilder.php:1821— ContainerBuilder.php:1821-1835 | ContainerBuilder.php:1845-1859 — These two members are one piece of code written twice and then edited apart: 15 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 (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) Alias.php:72— Alias.php:72-84 | Definition.php:668-681 — These two members are one piece of code written twice and then edited apart: 13 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 copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) Compiler/CheckDefinitionValidityPass.php:92— Compiler/CheckDefinitionValidityPass.php:92-99 | Loader/Configurator/DefaultsConfigurator.php:87-94 | Loader/Configurator/Traits/TagTrait.php:56-63 | Loader/ContentLoaderTrait.php:1009-1016 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) Definition.php:110— Definition.php:110-120 | Definition.php:714-724 — These two members are one piece of code written twice and then edited apart: 11 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) Kernel/BundleExtension.php:59— Kernel/BundleExtension.php:59-65 | Extension/AbstractExtension.php:57-63 — These two members are one piece of code written twice and then edited apart: 7 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 copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) Alias.php:111— Alias.php:111-122 | Argument/ArgumentTrait.php:23-34 | Definition.php:832-843 | Reference.php:42-53 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) Compiler/AutowireAsDecoratorPass.php:28— Compiler/AutowireAsDecoratorPass.php:28-32 | Compiler/RegisterAutoconfigureAttributesPass.php:33-37 — These two members are one piece of code written twice and then edited apart: 5 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.
Duplicated block (19 lines × 2) Compiler/PriorityTaggedServiceTrait.php:74— Compiler/PriorityTaggedServiceTrait.php:74-92 | Compiler/ResolveTaggedClassMapArgumentPass.php:59-77 — 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 (18 lines × 2) Loader/FileLoader.php:178— Loader/FileLoader.php:178-195 | Loader/PhpFileLoader.php:158-175 — 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 `Loader/FileLoader.php:178` 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, `Loader/FileLoader.php:196` calls `addContainerExcludedTag` and `Loader/PhpFileLoader.php:176` 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 lines × 2) Loader/Configurator/ContainerConfigurator.php:75— Loader/Configurator/ContainerConfigurator.php:75-87 | Loader/FileLoader.php:441-453 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 3) Dumper/XmlDumper.php:333— Dumper/XmlDumper.php:333-341 | Dumper/XmlDumper.php:371-379 | Dumper/XmlDumper.php:391-399 — 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 (8 lines × 3) Attribute/AutowireIterator.php:39— Attribute/AutowireIterator.php:39-46 | Loader/Configurator/ContainerConfigurator.php:192-199 | Loader/Configurator/ContainerConfigurator.php:218-225 — 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 `Attribute/AutowireIterator.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 (8 lines × 2) Loader/ContentLoaderTrait.php:617— Loader/ContentLoaderTrait.php:617-624 | Loader/ContentLoaderTrait.php:639-646 — 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 × 4) Attribute/AutowireIterator.php:38— Attribute/AutowireIterator.php:38-44 | Attribute/AutowireLocator.php:44-50 | Loader/Configurator/ContainerConfigurator.php:191-197 | Loader/Configurator/ContainerConfigurator.php:217-223 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Attribute/AutowireIterator.php:38` 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) Attribute/AutowireLocator.php:72— Attribute/AutowireLocator.php:72-78 | Compiler/RegisterServiceSubscribersPass.php:80-86 — 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 `Attribute/AutowireLocator.php:72` 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 (6 lines × 2) Compiler/AutowireRequiredMethodsPass.php:30— Compiler/AutowireRequiredMethodsPass.php:30-35 | Compiler/AutowireRequiredPropertiesPass.php:37-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.
Duplicated block (5 lines × 2) Compiler/ServiceReferenceGraph.php:46— Compiler/ServiceReferenceGraph.php:46-50 | ContainerBuilder.php:1018-1022 — 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.
Off the main sequence: Exception — Exception: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
X27 · Collection changed while being enumerated· Collection is structurally changed while it is being enumerated · ×1
Collection is structurally changed while it is being enumerated REDACTED:1860— line 1860 walks `$arguments` by value, so the walk is the snapshot taken when the loop began, and line 1887 changes that same collection with `$arguments = …` before the next iteration: the loop carries on over the old value while the body now works on the new one. PHP raises nothing, so the loop completes over a different set than the code meant.
Swallowed exception (caught, then discarded) Compiler/MergeExtensionConfigurationPass.php:163— `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.
Duplicated predicate Compiler/AttributeAutoconfigurationPass.php:81— `!$value instanceof Definition || !$value` appears character-identically in 7 files — Compiler/AttributeAutoconfigurationPass.php, Compiler/AutowirePass.php, Compiler/AutowireRequiredMethodsPass.php, Compiler/AutowireRequiredPropertiesPass.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 Compiler/PriorityTaggedServiceTrait.php:108— `!($attribute = $attributes[$i]) && $phpAttributes` appears character-identically in 2 files — Compiler/PriorityTaggedServiceTrait.php, Compiler/ResolveTaggedClassMapArgumentPass.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 ContainerBuilder.php:1762— `!class_exists($class) && !interface_exists($class, false) && !trait_exists($class, false)` appears character-identically in 2 files — ContainerBuilder.php, Dumper/Preloader.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 ContainerBuilder.php:1190— `$callable instanceof Reference || $callable instanceof Definition` appears character-identically in 2 files — ContainerBuilder.php, REDACTED. 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 Container.php:465— `$service instanceof LazyLoadingInterface && !$service` appears character-identically in 2 files — Container.php, ServicesResetter.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 Container.php:461— `$service instanceof LazyObjectInterface && !$service` appears character-identically in 2 files — Container.php, ServicesResetter.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 Compiler/ResolveHotPathPass.php:63— `$value instanceof Reference && ContainerBuilder::IGNORE_ON_UNINITIALIZED_REFERENCE !== $value` appears character-identically in 2 files — Compiler/ResolveHotPathPass.php, Compiler/ResolveNoPreloadPass.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 Attribute/AutowireIterator.php:46— `false !== $defaultIndexMethod || false !== $defaultPriorityMethod` appears character-identically in 3 files — Attribute/AutowireIterator.php, Attribute/AutowireLocator.php, Loader/Configurator/ContainerConfigurator.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 Loader/Configurator/EnvConfigurator.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 Compiler/AutowireRequiredPropertiesPass.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 Compiler/CheckCircularReferencesPass.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 Extension/ExtensionTrait.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 11 significant file(s) lose their only recent owner: Compiler/DecoratorServicePass.php, Kernel/AbstractKernel.php, Compiler/AttributeAutoconfigurationPass.php, Compiler/ValidateEnvPlaceholdersPass.php, Compiler/RemoveMissingDependenciesPass.php, Compiler/CheckFactoryBuilderCircularReferencePass.php, Kernel/Resources/config/services.php, ServicesResetter.php (+3 more). Pair on, review, or document these before any departure.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 97 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, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 97 of the 231 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: Loader/Configurator/EnvConfigurator.php, Compiler/AutowireRequiredPropertiesPass.php, Compiler/CheckCircularReferencesPass.php, Extension/ExtensionTrait.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.
Thin README README.md:1— The root README is 57 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No src/ separation — Most of the production code is in directories of its own, but 21 application file(s) sit at the repository root beside the build and tooling files (`Alias.php`, `ChildDefinition.php`, `Container.php`, `ContainerBuilder.php`, `ContainerInterface.php` and 16 more).
No SAST — No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
X5 · Nullable reference types· PHP static analysis does not check null everywhere · ×1
PHP static analysis does not check null everywhere — This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
Skipped (documented): testSetterInjectionWithPriority Tests/Compiler/AutowireRequiredMethodsPassTest.php:66— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testAutoconfiguredTagWithClosureAttributes Tests/Compiler/IntegrationTest.php:389— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testAutoconfiguredTagWithClosureAttributesViaLocator Tests/Compiler/IntegrationTest.php:412— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testAutoconfiguredResourceTagWithClosureAttributes Tests/Compiler/IntegrationTest.php:466— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testAutoconfiguredResourceTagWithClosureAttributesOnMarkerInterface Tests/Compiler/IntegrationTest.php:492— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testNestedLocatorConfiguredViaAttribute Tests/Compiler/IntegrationTest.php:739— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testSubscribedServiceWithAutowireLocatorAttribute Tests/Compiler/IntegrationTest.php:772— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testProcessGeneratesExpectedReferenceFile Tests/Compiler/PhpConfigReferenceDumpPassTest.php:103— Skipped with a documented reason — a deferral, not lazy debt: reported incomplete at run time by markTestIncomplete()
Skipped (documented): testTypeConversionsWithNativePhp Tests/Loader/IniFileLoaderTest.php:50— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
No assertions (declared): testWhenEnv Tests/Loader/PhpFileLoaderTest.php:379— This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.
No assertions (declared): testNotWhenEnv Tests/Loader/PhpFileLoaderTest.php:390— This test performs no assertions and its author said so, with the test framework's own declaration for exactly that (PHPUnit `#[DoesNotPerformAssertions]`, which switches off PHPUnit's "This test did not perform any assertions" warning). It is reported for visibility and is NOT counted against this dimension's score: D10 looks for tests that verify nothing unintentionally. Worth a read anyway — such a test passes as long as the code under it does not throw, so if it was meant to check something, the declaration is now hiding that it does not.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
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 12 file(s) — `Argument/LazyClosure.php`, `Argument/RewindableGenerator.php`, `Attribute/Autowire.php`, `Compiler/AttributeAutoconfigurationPass.php`, `Container.php`, … (+7 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
0
—
Run 01a1ea32-4d92-742b-8e54-e5350f44ebf2 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 4 · Warnings: 362 · Recommendations: 20 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 15:48 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.