Public report of doctrine/orm, published 13 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, 13 November 2026, 21:40 UTC · Survey ID cd_76173c583cc7424baff1e7b9b9adc90a
doctrine/orm
Measured 13 November 2026, 21:39 UTC, at code version 678c053
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change 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: 48,356 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Security and Compliance, 43
Findings by how serious they are
38 critical384 serious95 minor
23 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
13 November 2026, 21:39 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.
503of 517 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
39dimensions across 6 lenses, read from 48,356 lines of product code in 2 projects.
doctrine/orm falls short of our standard for production, in part because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 53 out of 100 and is rated Adequate, and all 38 of its critical findings are security problems.
Security and Compliance, at 43, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 9 points. Fixing the six pipeline jobs with more access than they need comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 62.
Thirty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one password or key is open to anyone who can read the repository. Pinning each tool to an exact version, setting a waiting period for automatic updates and replacing the exposed password or key would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed.
The product code is 48,356 lines, about €140,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.
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: 20 findings
These 20 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.
Code Duplication · Near-duplicate member pair (265 shared lines) src/Tools/SchemaTool.php
€47,000 to €230,000, for 775 to 2,459 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. 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: 48,356 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
Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault).
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 9 points · Medium effort · Data Protection
2
Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
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.
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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Security and Compliance, at 43 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault). Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 8,624 lines over the last 90 days, which is about 34,975 lines a year. At that pace, the extra work comes to an estimated 3.5 to 21.1 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: 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.
48 modules, with 128 dependencies between them. One loop runs through 24 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 8 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Doctrine.ORM.Cache.Exception uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Exception, while a change to Doctrine.ORM.Cache.Exception can't break Doctrine.ORM.Cache.
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→26 Doctrine.ORM.Cache.Logging uses Doctrine.ORM.Cachepart of a loop✕
Connections
9 pairs of types, where a type in Doctrine.ORM.Cache.Logging uses a type in Doctrine.ORM.Cache.
Doctrine.ORM.Cache.Logging uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Logging, while a change to Doctrine.ORM.Cache.Logging can't break Doctrine.ORM.Cache.
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→27 Doctrine.ORM.Id uses Doctrine.ORMpart of a loop✕
Connections
5 pairs of types, where a type in Doctrine.ORM.Id uses a type in Doctrine.ORM.
Doctrine.ORM.Id uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Id, while a change to Doctrine.ORM.Id can't break Doctrine.ORM.
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→34 Doctrine.ORM.Query.AST uses Doctrine.ORM.Querypart of a loop✕
Connections
59 pairs of types, where a type in Doctrine.ORM.Query.AST uses a type in Doctrine.ORM.Query. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Doctrine.ORM.Query.AST uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Query.AST, while a change to Doctrine.ORM.Query.AST can't break Doctrine.ORM.Query.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→27 Doctrine.ORM.Repository uses Doctrine.ORMpart of a loop✕
Connections
4 pairs of types, where a type in Doctrine.ORM.Repository uses a type in Doctrine.ORM.
Doctrine.ORM.Repository uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Repository, while a change to Doctrine.ORM.Repository can't break Doctrine.ORM.
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.
7→13 Doctrine.ORM.Utility uses Doctrine.ORM.Mappingpart of a loop✕
Connections
2 pairs of types, where a type in Doctrine.ORM.Utility uses a type in Doctrine.ORM.Mapping.
Doctrine.ORM.Utility uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Utility, while a change to Doctrine.ORM.Utility can't break Doctrine.ORM.Mapping.
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.
7→27 Doctrine.ORM.Utility uses Doctrine.ORMpart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Utility uses a type in Doctrine.ORM.
Doctrine.ORM.Utility uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Utility, while a change to Doctrine.ORM.Utility can't break Doctrine.ORM.
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.
Doctrine.ORM.Persisters.Entity uses Doctrine.ORM.Utility, so a change to Doctrine.ORM.Utility can break Doctrine.ORM.Persisters.Entity, while a change to Doctrine.ORM.Persisters.Entity can't break Doctrine.ORM.Utility.
Position
Below the diagonal: Doctrine.ORM.Persisters.Entity uses a module listed above it, which is the healthy direction.
8→13 Doctrine.ORM.Persisters.Entity uses Doctrine.ORM.Mappingpart of a loop✕
Connections
9 pairs of types, where a type in Doctrine.ORM.Persisters.Entity uses a type in Doctrine.ORM.Mapping.
Doctrine.ORM.Persisters.Entity uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Persisters.Entity, while a change to Doctrine.ORM.Persisters.Entity can't break Doctrine.ORM.Mapping.
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.
8→27 Doctrine.ORM.Persisters.Entity uses Doctrine.ORMpart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Persisters.Entity uses a type in Doctrine.ORM.
Doctrine.ORM.Persisters.Entity uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Persisters.Entity, while a change to Doctrine.ORM.Persisters.Entity can't break Doctrine.ORM.
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.
8→34 Doctrine.ORM.Persisters.Entity uses Doctrine.ORM.Querypart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Persisters.Entity uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Persisters.Entity uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Persisters.Entity, while a change to Doctrine.ORM.Persisters.Entity can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Query.AST.Functions uses Doctrine.ORM.Query.AST, so a change to Doctrine.ORM.Query.AST can break Doctrine.ORM.Query.AST.Functions, while a change to Doctrine.ORM.Query.AST.Functions can't break Doctrine.ORM.Query.AST.
Position
Below the diagonal: Doctrine.ORM.Query.AST.Functions uses a module listed above it, which is the healthy direction.
9→34 Doctrine.ORM.Query.AST.Functions uses Doctrine.ORM.Querypart of a loop✕
Connections
51 pairs of types, where a type in Doctrine.ORM.Query.AST.Functions uses a type in Doctrine.ORM.Query. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Doctrine.ORM.Query.AST.Functions uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Query.AST.Functions, while a change to Doctrine.ORM.Query.AST.Functions can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Query.Exec uses Doctrine.ORM.Query.AST, so a change to Doctrine.ORM.Query.AST can break Doctrine.ORM.Query.Exec, while a change to Doctrine.ORM.Query.Exec can't break Doctrine.ORM.Query.AST.
Position
Below the diagonal: Doctrine.ORM.Query.Exec uses a module listed above it, which is the healthy direction.
10→27 Doctrine.ORM.Query.Exec uses Doctrine.ORMpart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Query.Exec uses a type in Doctrine.ORM.
Doctrine.ORM.Query.Exec uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Query.Exec, while a change to Doctrine.ORM.Query.Exec can't break Doctrine.ORM.
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.
10→34 Doctrine.ORM.Query.Exec uses Doctrine.ORM.Querypart of a loop✕
Connections
4 pairs of types, where a type in Doctrine.ORM.Query.Exec uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Query.Exec uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Query.Exec, while a change to Doctrine.ORM.Query.Exec can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Persisters uses Doctrine.ORM.Persisters.Entity, so a change to Doctrine.ORM.Persisters.Entity can break Doctrine.ORM.Persisters, while a change to Doctrine.ORM.Persisters can't break Doctrine.ORM.Persisters.Entity.
Position
Below the diagonal: Doctrine.ORM.Persisters uses a module listed above it, which is the healthy direction.
11→12 Doctrine.ORM.Persisters uses Doctrine.ORM.Exceptionpart of a loop✕
Connections
2 pairs of types, where a type in Doctrine.ORM.Persisters uses a type in Doctrine.ORM.Exception.
Doctrine.ORM.Persisters uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Persisters, while a change to Doctrine.ORM.Persisters can't break Doctrine.ORM.Exception.
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.
11→13 Doctrine.ORM.Persisters uses Doctrine.ORM.Mappingpart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Persisters uses a type in Doctrine.ORM.Mapping.
Doctrine.ORM.Persisters uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Persisters, while a change to Doctrine.ORM.Persisters can't break Doctrine.ORM.Mapping.
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.
Doctrine.ORM.Exception uses Doctrine.ORM.Cache.Exception, so a change to Doctrine.ORM.Cache.Exception can break Doctrine.ORM.Exception, while a change to Doctrine.ORM.Exception can't break Doctrine.ORM.Cache.Exception.
Position
Below the diagonal: Doctrine.ORM.Exception uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Exception uses Doctrine.ORM.Persisters, so a change to Doctrine.ORM.Persisters can break Doctrine.ORM.Exception, while a change to Doctrine.ORM.Exception can't break Doctrine.ORM.Persisters.
Position
Below the diagonal: Doctrine.ORM.Exception uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Mapping uses Doctrine.ORM.Id, so a change to Doctrine.ORM.Id can break Doctrine.ORM.Mapping, while a change to Doctrine.ORM.Mapping can't break Doctrine.ORM.Id.
Position
Below the diagonal: Doctrine.ORM.Mapping uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Mapping uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Mapping, while a change to Doctrine.ORM.Mapping can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Mapping uses a module listed above it, which is the healthy direction.
13→27 Doctrine.ORM.Mapping uses Doctrine.ORMpart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Mapping uses a type in Doctrine.ORM.
Doctrine.ORM.Mapping uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Mapping, while a change to Doctrine.ORM.Mapping can't break Doctrine.ORM.
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.
Doctrine.ORM.Mapping.Exception uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Mapping.Exception, while a change to Doctrine.ORM.Mapping.Exception can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Mapping.Exception uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Persisters.Exception uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Persisters.Exception, while a change to Doctrine.ORM.Persisters.Exception can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Persisters.Exception uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Proxy uses Doctrine.ORM.Utility, so a change to Doctrine.ORM.Utility can break Doctrine.ORM.Proxy, while a change to Doctrine.ORM.Proxy can't break Doctrine.ORM.Utility.
Position
Below the diagonal: Doctrine.ORM.Proxy uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Proxy uses Doctrine.ORM.Persisters.Entity, so a change to Doctrine.ORM.Persisters.Entity can break Doctrine.ORM.Proxy, while a change to Doctrine.ORM.Proxy can't break Doctrine.ORM.Persisters.Entity.
Position
Below the diagonal: Doctrine.ORM.Proxy uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Proxy uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Proxy, while a change to Doctrine.ORM.Proxy can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Proxy uses a module listed above it, which is the healthy direction.
16→27 Doctrine.ORM.Proxy uses Doctrine.ORMpart of a loop✕
Connections
2 pairs of types, where a type in Doctrine.ORM.Proxy uses a type in Doctrine.ORM.
Doctrine.ORM.Proxy uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Proxy, while a change to Doctrine.ORM.Proxy can't break Doctrine.ORM.
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.
Doctrine.ORM.Cache.Persister uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Cache.Persister, while a change to Doctrine.ORM.Cache.Persister can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister uses a module listed above it, which is the healthy direction.
17→26 Doctrine.ORM.Cache.Persister uses Doctrine.ORM.Cachepart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Cache.Persister uses a type in Doctrine.ORM.Cache.
Doctrine.ORM.Cache.Persister uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Persister, while a change to Doctrine.ORM.Cache.Persister can't break Doctrine.ORM.Cache.
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.
Doctrine.ORM.Event uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Event, while a change to Doctrine.ORM.Event can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Event uses a module listed above it, which is the healthy direction.
18→27 Doctrine.ORM.Event uses Doctrine.ORMpart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Event uses a type in Doctrine.ORM.
Doctrine.ORM.Event uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Event, while a change to Doctrine.ORM.Event can't break Doctrine.ORM.
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.
Doctrine.ORM.Internal.Hydration uses Doctrine.ORM.Utility, so a change to Doctrine.ORM.Utility can break Doctrine.ORM.Internal.Hydration, while a change to Doctrine.ORM.Internal.Hydration can't break Doctrine.ORM.Utility.
Position
Below the diagonal: Doctrine.ORM.Internal.Hydration uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Internal.Hydration uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Internal.Hydration, while a change to Doctrine.ORM.Internal.Hydration can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Internal.Hydration uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Internal.Hydration uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Internal.Hydration, while a change to Doctrine.ORM.Internal.Hydration can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Internal.Hydration uses a module listed above it, which is the healthy direction.
19→27 Doctrine.ORM.Internal.Hydration uses Doctrine.ORMpart of a loop✕
Connections
3 pairs of types, where a type in Doctrine.ORM.Internal.Hydration uses a type in Doctrine.ORM.
Doctrine.ORM.Internal.Hydration uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Internal.Hydration, while a change to Doctrine.ORM.Internal.Hydration can't break Doctrine.ORM.
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.
19→34 Doctrine.ORM.Internal.Hydration uses Doctrine.ORM.Querypart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Internal.Hydration uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Internal.Hydration uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Internal.Hydration, while a change to Doctrine.ORM.Internal.Hydration can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Mapping.Builder uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Mapping.Builder, while a change to Doctrine.ORM.Mapping.Builder can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Mapping.Builder uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Mapping.Driver uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Mapping.Driver, while a change to Doctrine.ORM.Mapping.Driver can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Mapping.Driver uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Persisters.Collection uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Persisters.Collection, while a change to Doctrine.ORM.Persisters.Collection can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Persisters.Collection uses a module listed above it, which is the healthy direction.
22→27 Doctrine.ORM.Persisters.Collection uses Doctrine.ORMpart of a loop✕
Connections
5 pairs of types, where a type in Doctrine.ORM.Persisters.Collection uses a type in Doctrine.ORM.
Doctrine.ORM.Persisters.Collection uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Persisters.Collection, while a change to Doctrine.ORM.Persisters.Collection can't break Doctrine.ORM.
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.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Collection uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Cache.Persister, so a change to Doctrine.ORM.Cache.Persister can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.Cache.Persister.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Collection uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Persisters.Collection, so a change to Doctrine.ORM.Persisters.Collection can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.Persisters.Collection.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Collection uses a module listed above it, which is the healthy direction.
23→26 Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Cachepart of a loop✕
Connections
5 pairs of types, where a type in Doctrine.ORM.Cache.Persister.Collection uses a type in Doctrine.ORM.Cache.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.Cache.
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.
23→27 Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORMpart of a loop✕
Connections
8 pairs of types, where a type in Doctrine.ORM.Cache.Persister.Collection uses a type in Doctrine.ORM.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.
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.
23→34 Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Querypart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Cache.Persister.Collection uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Cache.Persister.Collection uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Cache.Persister.Collection, while a change to Doctrine.ORM.Cache.Persister.Collection can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Persisters.Entity, so a change to Doctrine.ORM.Persisters.Entity can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.Persisters.Entity.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Entity uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Entity uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Cache.Persister, so a change to Doctrine.ORM.Cache.Persister can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.Cache.Persister.
Position
Below the diagonal: Doctrine.ORM.Cache.Persister.Entity uses a module listed above it, which is the healthy direction.
24→26 Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Cachepart of a loop✕
Connections
9 pairs of types, where a type in Doctrine.ORM.Cache.Persister.Entity uses a type in Doctrine.ORM.Cache.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.Cache.
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.
24→27 Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORMpart of a loop✕
Connections
5 pairs of types, where a type in Doctrine.ORM.Cache.Persister.Entity uses a type in Doctrine.ORM.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.
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.
24→34 Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Querypart of a loop✕
Connections
2 pairs of types, where a type in Doctrine.ORM.Cache.Persister.Entity uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Cache.Persister.Entity uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Cache.Persister.Entity, while a change to Doctrine.ORM.Cache.Persister.Entity can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Internal uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Internal, while a change to Doctrine.ORM.Internal can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Internal uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Internal uses Doctrine.ORM.Event, so a change to Doctrine.ORM.Event can break Doctrine.ORM.Internal, while a change to Doctrine.ORM.Internal can't break Doctrine.ORM.Event.
Position
Below the diagonal: Doctrine.ORM.Internal uses a module listed above it, which is the healthy direction.
25→27 Doctrine.ORM.Internal uses Doctrine.ORMpart of a loop✕
Connections
1 pair of types, where a type in Doctrine.ORM.Internal uses a type in Doctrine.ORM.
Doctrine.ORM.Internal uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Internal, while a change to Doctrine.ORM.Internal can't break Doctrine.ORM.
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.
Doctrine.ORM.Cache uses Doctrine.ORM.Cache.Exception, so a change to Doctrine.ORM.Cache.Exception can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Cache.Exception.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Cache.Logging, so a change to Doctrine.ORM.Cache.Logging can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Cache.Logging.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Utility, so a change to Doctrine.ORM.Utility can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Utility.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Persisters.Entity, so a change to Doctrine.ORM.Persisters.Entity can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Persisters.Entity.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Persisters.Collection, so a change to Doctrine.ORM.Persisters.Collection can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Persisters.Collection.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Cache.Persister.Collection, so a change to Doctrine.ORM.Cache.Persister.Collection can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Cache.Persister.Collection.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Cache uses Doctrine.ORM.Cache.Persister.Entity, so a change to Doctrine.ORM.Cache.Persister.Entity can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Cache.Persister.Entity.
Position
Below the diagonal: Doctrine.ORM.Cache uses a module listed above it, which is the healthy direction.
26→27 Doctrine.ORM.Cache uses Doctrine.ORMpart of a loop✕
Connections
16 pairs of types, where a type in Doctrine.ORM.Cache uses a type in Doctrine.ORM.
Doctrine.ORM.Cache uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.
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.
26→34 Doctrine.ORM.Cache uses Doctrine.ORM.Querypart of a loop✕
Connections
2 pairs of types, where a type in Doctrine.ORM.Cache uses a type in Doctrine.ORM.Query.
Doctrine.ORM.Cache uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Cache, while a change to Doctrine.ORM.Cache can't break Doctrine.ORM.Query.
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.
Doctrine.ORM uses Doctrine.ORM.Repository, so a change to Doctrine.ORM.Repository can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Repository.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Utility, so a change to Doctrine.ORM.Utility can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Utility.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Persisters.Entity, so a change to Doctrine.ORM.Persisters.Entity can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Persisters.Entity.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Query.Exec, so a change to Doctrine.ORM.Query.Exec can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Query.Exec.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Proxy, so a change to Doctrine.ORM.Proxy can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Proxy.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Event, so a change to Doctrine.ORM.Event can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Event.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Internal.Hydration, so a change to Doctrine.ORM.Internal.Hydration can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Internal.Hydration.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Persisters.Collection, so a change to Doctrine.ORM.Persisters.Collection can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Persisters.Collection.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Internal, so a change to Doctrine.ORM.Internal can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Internal.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
Doctrine.ORM uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Cache.
Position
Below the diagonal: Doctrine.ORM uses a module listed above it, which is the healthy direction.
27→34 Doctrine.ORM uses Doctrine.ORM.Querypart of a loop✕
Connections
13 pairs of types, where a type in Doctrine.ORM uses a type in Doctrine.ORM.Query.
Doctrine.ORM uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM, while a change to Doctrine.ORM can't break Doctrine.ORM.Query.
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.
Doctrine.ORM.Cache.Region uses Doctrine.ORM.Cache, so a change to Doctrine.ORM.Cache can break Doctrine.ORM.Cache.Region, while a change to Doctrine.ORM.Cache.Region can't break Doctrine.ORM.Cache.
Position
Below the diagonal: Doctrine.ORM.Cache.Region uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Internal.UnitOfWork uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Internal.UnitOfWork, while a change to Doctrine.ORM.Internal.UnitOfWork can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Internal.UnitOfWork uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Internal.UnitOfWork uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Internal.UnitOfWork, while a change to Doctrine.ORM.Internal.UnitOfWork can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Internal.UnitOfWork uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query.Filter uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Query.Filter, while a change to Doctrine.ORM.Query.Filter can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Query.Filter uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query.Filter uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Query.Filter, while a change to Doctrine.ORM.Query.Filter can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Query.Filter uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query.Filter uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Query.Filter, while a change to Doctrine.ORM.Query.Filter can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Query.Filter uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Tools, while a change to Doctrine.ORM.Tools can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Tools uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Tools, while a change to Doctrine.ORM.Tools can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Tools uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools uses Doctrine.ORM.Event, so a change to Doctrine.ORM.Event can break Doctrine.ORM.Tools, while a change to Doctrine.ORM.Tools can't break Doctrine.ORM.Event.
Position
Below the diagonal: Doctrine.ORM.Tools uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools, while a change to Doctrine.ORM.Tools can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools.Console, while a change to Doctrine.ORM.Tools.Console can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools.Console uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Event uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Tools.Event, while a change to Doctrine.ORM.Tools.Event can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Tools.Event uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Event uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools.Event, while a change to Doctrine.ORM.Tools.Event can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools.Event uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Query.Expr, so a change to Doctrine.ORM.Query.Expr can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Query.Expr.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
105 pairs of types, where a type in Doctrine.ORM.Query uses a type in Doctrine.ORM.Query.AST. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Doctrine.ORM.Query uses Doctrine.ORM.Query.AST, so a change to Doctrine.ORM.Query.AST can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Query.AST.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Query.AST.Functions, so a change to Doctrine.ORM.Query.AST.Functions can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Query.AST.Functions.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Query.Exec, so a change to Doctrine.ORM.Query.Exec can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Query.Exec.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Exception, so a change to Doctrine.ORM.Exception can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Exception.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Query uses Doctrine.ORM.Query.Filter, so a change to Doctrine.ORM.Query.Filter can break Doctrine.ORM.Query, while a change to Doctrine.ORM.Query can't break Doctrine.ORM.Query.Filter.
Position
Below the diagonal: Doctrine.ORM.Query uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.Command uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Tools.Console.Command, while a change to Doctrine.ORM.Tools.Console.Command can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.Command uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.Command uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools.Console.Command, while a change to Doctrine.ORM.Tools.Console.Command can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.Command uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.Command uses Doctrine.ORM.Tools.Console, so a change to Doctrine.ORM.Tools.Console can break Doctrine.ORM.Tools.Console.Command, while a change to Doctrine.ORM.Tools.Console.Command can't break Doctrine.ORM.Tools.Console.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.Command uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.EntityManagerProvider uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools.Console.EntityManagerProvider, while a change to Doctrine.ORM.Tools.Console.EntityManagerProvider can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.EntityManagerProvider uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.EntityManagerProvider uses Doctrine.ORM.Tools.Console, so a change to Doctrine.ORM.Tools.Console can break Doctrine.ORM.Tools.Console.EntityManagerProvider, while a change to Doctrine.ORM.Tools.Console.EntityManagerProvider can't break Doctrine.ORM.Tools.Console.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.EntityManagerProvider uses a module listed above it, which is the healthy direction.
(global) uses Doctrine.ORM.Query.AST, so a change to Doctrine.ORM.Query.AST can break (global), while a change to (global) can't break Doctrine.ORM.Query.AST.
Position
Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Decorator uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Decorator, while a change to Doctrine.ORM.Decorator can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Decorator uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Decorator uses Doctrine.ORM.Proxy, so a change to Doctrine.ORM.Proxy can break Doctrine.ORM.Decorator, while a change to Doctrine.ORM.Decorator can't break Doctrine.ORM.Proxy.
Position
Below the diagonal: Doctrine.ORM.Decorator uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Decorator uses Doctrine.ORM.Internal.Hydration, so a change to Doctrine.ORM.Internal.Hydration can break Doctrine.ORM.Decorator, while a change to Doctrine.ORM.Decorator can't break Doctrine.ORM.Internal.Hydration.
Position
Below the diagonal: Doctrine.ORM.Decorator uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Decorator uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Decorator, while a change to Doctrine.ORM.Decorator can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Decorator uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Decorator uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Decorator, while a change to Doctrine.ORM.Decorator can't break Doctrine.ORM.Query.
Position
Below the diagonal: Doctrine.ORM.Decorator uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.Command.SchemaTool uses Doctrine.ORM.Tools, so a change to Doctrine.ORM.Tools can break Doctrine.ORM.Tools.Console.Command.SchemaTool, while a change to Doctrine.ORM.Tools.Console.Command.SchemaTool can't break Doctrine.ORM.Tools.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.Command.SchemaTool uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Console.Command.SchemaTool uses Doctrine.ORM.Tools.Console.Command, so a change to Doctrine.ORM.Tools.Console.Command can break Doctrine.ORM.Tools.Console.Command.SchemaTool, while a change to Doctrine.ORM.Tools.Console.Command.SchemaTool can't break Doctrine.ORM.Tools.Console.Command.
Position
Below the diagonal: Doctrine.ORM.Tools.Console.Command.SchemaTool uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM.Query.AST, so a change to Doctrine.ORM.Query.AST can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.Query.AST.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM.Query.AST.Functions, so a change to Doctrine.ORM.Query.AST.Functions can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.Query.AST.Functions.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM.Query.Exec, so a change to Doctrine.ORM.Query.Exec can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.Query.Exec.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM.Mapping, so a change to Doctrine.ORM.Mapping can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.Mapping.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM, so a change to Doctrine.ORM can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
Doctrine.ORM.Tools.Pagination uses Doctrine.ORM.Query, so a change to Doctrine.ORM.Query can break Doctrine.ORM.Tools.Pagination, while a change to Doctrine.ORM.Tools.Pagination can't break Doctrine.ORM.Query.
Position
Below the diagonal: Doctrine.ORM.Tools.Pagination uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 52% · Adequate · gated by 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
40
High / Critical
A03:2025 — Software Supply Chain Failures
12
Medium
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive; Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Code Duplication: Edited copy of a member (16 corresponding lines)
src/Tools/Pagination/LimitSubqueryWalker.php
6.7
Mixed
Explicit Debt: TodoComment
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 38
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 — 384
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 — 95
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 23
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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, 503 of 517 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 READ here — but this repository measures it: a coverage step in CI (`phpunit -c ci/github/phpunit/${{ matrix.extension }}.xml --c…`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
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 — 12 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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
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.
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. `src/Cache/AssociationCacheEntry.php`, `src/Cache/CacheKey.php`, `src/Cache/CollectionCacheEntry.php`, `src/Cache/CollectionCacheKey.php`, `src/Cache/DefaultCache.php`, … (+109 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.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 160 commits in the last 90 days, yet 82 of 126 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — 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 and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — 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.
X27 Collection changed while being enumerated — 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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 and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.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.
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.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
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.
43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was XmlDriver.loadMetadataForClass at 140. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Parser.ScalarExpression at 19 — they are counted neither in the figure above nor in this dimension's score.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with XmlDriver.loadMetadataForClass (cyclomatic 140), AttributeDriver.loadMetadataForClass (cyclomatic 95), UnitOfWork.createEntity (cyclomatic 68). — 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 3 together lifts Cyclomatic Complexity from 5.7 to about 6.5/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.
+ 84 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with XmlDriver.loadMetadataForClass (cognitive 353). — Refactoring it lifts Cognitive Complexity from 2.9 to about 3.5/10.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.2 / 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 13 TooManyMethods finding(s) in God Classes — start with ClassMetadata.php, Parser.php, UnitOfWork.php. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 8 ClassTooLong finding(s) in God Classes — start with Parser.php, UnitOfWork.php, SqlWalker.php. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 MethodTooLong finding(s) in God Classes — start with SchemaTool.php (2), UnitOfWork.php (2), XmlDriver.php. — One of this dimension's main actionable groups (8 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.
69 duplicated block group(s) detected. 5.7 % of the production lines (2,759 of 48,356) are in a reported copy. A further 51 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 (12 corresponding lines) · ×5src/Persisters/SqlExpressionVisitor.php:58
Edited copy of a member (18 corresponding lines) · ×4src/Query/Parser.php:2751
Edited copy of a member (13 corresponding lines) · ×4src/Cache/Persister/Collection/AbstractCollectionPersister.php:49
Edited copy of a member (4 corresponding lines) · ×4src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:27
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SqlWalker.php (3), DefaultQueryCache.php, XmlDriver.php. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with SqlExpressionVisitor.php, OneToManyPersister.php, ManyToManyPersister.php. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with Parser.php, BasicEntityPersister.php, ClassMetadata.php. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_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 6 Low cohesion finding(s) in Cohesion (LCOM4) — start with JoinTableMapping.php, ClassMetadataBuilder.php, DiscriminatorColumnMapping.php. — One of this dimension's main actionable groups (6 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.8 / 10Stronggated by 50 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.
53 skipped (53 with a documented reason), 73 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3058 tests.
No assertions: testDisablingNativeLazyObjectsIsDeprecated · ×50tests/Tests/ORM/ConfigurationTest.php:226
No assertions (declared): testBulkUpdateNonScalarParameterDDC1341 · ×23tests/Tests/ORM/Functional/ClassTableInheritanceTest.php:329
What to do
Resolve the 50 No assertions finding(s) in Test Quality — start with PaginationTest.php (29), LockTest.php (3), GH10913Test.php (3). — One of this dimension's main actionable groups (50 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.
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with SchemaTool.php. — One of this dimension's main actionable groups (1 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 Factor9.3 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/Tools/Pagination/PaginatorQuery.php. Counted over 126 of the 472 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
22 deducted task-comment markers across 48356 LoC (0.0/KLoC) → score 9.9. 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.
Resolve the 18 TodoComment finding(s) in Explicit Debt — start with UnitOfWork.php (4), ClassMetadata.php (4), ObjectHydrator.php (3). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 4 FixmeComment finding(s) in Explicit Debt — start with OrmFunctionalTestCase.php, DatabaseDriverTest.php, UnitOfWork.php. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 build units (Composer) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.1 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
65 % of calls cross a namespace and 38 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
High interface indirection
What to do
Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
40 finding(s): 0 critical, 37 high, 3 medium, 0 low. 35 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 114 file(s) — `src/Cache/AssociationCacheEntry.php` (line 14, line 15), `src/Cache/CacheKey.php` (line 13), `src/Cache/CollectionCacheEntry.php` (line 10), `src/Cache/CollectionCacheKey.php` (line 22, line 29, line 30), `src/Cache/DefaultCache.php` (line 23, line 24, line 35), … (+109 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 29 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (29 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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 Change coupling finding(s) in Change Coupling — start with EntityManagerDecorator.php. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether 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 12 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.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No encryption usage (Laravel's Crypt facade or encrypt() helper, an Eloquent 'encrypted' cast, openssl_encrypt, libsodium's sodium_crypto_secretbox/aead, defuse/php-encryption, phpseclib, CipherSweet) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — docs/en/cookbook/generated-columns/Person.php:11
What to do
Encrypt sensitive data at rest (an Eloquent 'encrypted' cast or Crypt::encryptString, libsodium's sodium_crypto_secretbox, or CipherSweet for searchable fields) and manage keys in a vault (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (URL::forceScheme('https') / URL::forceHttps() in Laravel, or requires_channel: https / route schemes in Symfony) so data in transit is always encrypted.
Do you agree with this assessment?
C4 · Data Retention7.5 / 10Strong✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (an Eloquent model's prunable() for model:prune, or a command that deletes rows past their retention — PruneOld… / PurgeExpired…).
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Maturity · Maturity — Whether the 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.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
Do you agree with this assessment?
P1 · CI/CD gates8.0 / 10Strong✓ 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.
A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `composer` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
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.
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. — src/Tools/SchemaTool.php:1414
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/2 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
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 — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, a change-history library on the models — spatie/laravel-activitylog's LogsActivity, owen-it/laravel-auditing's Auditable, venturecraft/revisionable, Gedmo Loggable — or an Eloquent model event, observer or Doctrine listener that records each change) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
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 — 72 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 applicable: this repository's PHP imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
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
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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.
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.
D11 Test Reliability — Test reliability not included — no .php test runner
D12 Dependency Hygiene — Not scored — 12 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.
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 — API consistency is measured on C# only; the exposed PHP surface was not measured.
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. Aggregate roots were found in only one source directory (docs), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — 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
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) — 114 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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).
D5 Coupling — Not applicable — this Composer build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 5 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 30 value object(s); its 5 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 63 current-state document(s) make no claim of a kind M4 checks. 25 claim(s) of kinds M4 does not check were not checked (path 2, environment variable 23); M4 checks only links and versions and artefact counts.
P2 Observability — This repository's PHP source (2 module(s), 480 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 — no outbound HTTP usage detected — no HTTP client call or construction in the PHP source (service entry point: docs/en/tutorials/pagination/cursor-pagination.php:5 ($_GET[))
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
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.
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
No assertions: testDisablingNativeLazyObjectsIsDeprecated tests/Tests/ORM/ConfigurationTest.php:226— 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: testFindWithNullLockModeIsDeprecated tests/Tests/ORM/Functional/Locking/LockTest.php:133— 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: testRefreshWithNullLockModeIsDeprecated tests/Tests/ORM/Functional/Locking/LockTest.php:149— 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: testFindWithoutLockModeIsNotDeprecated tests/Tests/ORM/Functional/Locking/LockTest.php:164— 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: testIterateSimpleWithoutJoinWithOrder tests/Tests/ORM/Functional/PaginationTest.php:277— 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: testIterateSimpleWithoutJoinWithOrderAndLimit tests/Tests/ORM/Functional/PaginationTest.php:286— 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: testIterateSimpleWithoutJoinWithOrderAndLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:295— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testIterateSimpleWithOutputWalkerWithoutJoinWithComplexOrder tests/Tests/ORM/Functional/PaginationTest.php:304— 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: testIterateSimpleWithOutputWalkerWithoutJoinWithComplexOrderAndLimit tests/Tests/ORM/Functional/PaginationTest.php:313— 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: testIterateSimpleWithOutputWalkerWithoutJoinWithComplexOrderAndLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:322— 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: testIterateWithFetchJoinWithOrder tests/Tests/ORM/Functional/PaginationTest.php:341— 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: testIterateWithFetchJoinWithOrderAndLimit tests/Tests/ORM/Functional/PaginationTest.php:349— 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: testIterateWithFetchJoinWithOrderAndLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:357— 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: testIterateWithRegularJoinWithOrderByColumnFromJoined tests/Tests/ORM/Functional/PaginationTest.php:365— 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: testIterateWithRegularJoinWithOrderByColumnFromJoinedWithLimit tests/Tests/ORM/Functional/PaginationTest.php:373— 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: testIterateWithRegularJoinWithOrderByColumnFromJoinedWithLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:381— 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: testIterateWithOutputWalkersWithRegularJoinWithComplexOrderByReferencingJoined tests/Tests/ORM/Functional/PaginationTest.php:389— 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: testIterateWithOutputWalkersWithRegularJoinWithComplexOrderByReferencingJoinedWithLimit tests/Tests/ORM/Functional/PaginationTest.php:399— 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: testIterateWithOutputWalkersWithRegularJoinWithComplexOrderByReferencingJoinedWithLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:409— 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: testIterateWithFetchJoinWithOrderByColumnFromJoined tests/Tests/ORM/Functional/PaginationTest.php:419— 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: testIterateWithFetchJoinWithOrderByColumnFromJoinedWithLimit tests/Tests/ORM/Functional/PaginationTest.php:427— 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: testIterateWithFetchJoinWithOrderByColumnFromJoinedWithLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:435— 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: testIterateWithOutputWalkersWithFetchJoinWithComplexOrderByReferencingJoined tests/Tests/ORM/Functional/PaginationTest.php:443— 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: testIterateWithOutputWalkersWithFetchJoinWithComplexOrderByReferencingJoinedWithLimit tests/Tests/ORM/Functional/PaginationTest.php:451— 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: testIterateWithOutputWalkersWithFetchJoinWithComplexOrderByReferencingJoinedWithLimitAndOffset tests/Tests/ORM/Functional/PaginationTest.php:459— 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.
TodoComment src/PersistentCollection.php:295— // TODO: If the keys are persistent as well (not yet implemented) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UnitOfWork.php:2453— // TODO: if $coll is already scheduled for recreation ... what to do? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UnitOfWork.php:2669— // TODO: Is this even computed right in all cases of composite keys? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UnitOfWork.php:2743— // TODO: Is there a faster approach? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UnitOfWork.php:2751— // TODO: This is very imperformant, ignore it? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Tools/SchemaTool.php:304— // TODO: This seems rather hackish, can we optimize it? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Tools/SchemaTool.php:624— // TODO: This seems rather hackish, can we optimize it? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Tools/Pagination/LimitSubqueryWalker.php:118— // TODO: check complex orderby items too... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Query/Parser.php:267— // TODO: Is there a way to remove this? It may impact the mixed hydration resultset a lot! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Mapping/ClassMetadata.php:740— //TODO: 3.0 Remove this. Can use fieldMappings[$fieldName]['columnName'] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Mapping/ClassMetadata.php:746— // TODO: REMOVE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Mapping/ClassMetadata.php:748— // TODO: REMOVE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Mapping/ClassMetadata.php:751— //TODO: Does not really need to be serialized. Could be moved to runtime. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Internal/Hydration/ArrayHydrator.php:89— // TODO: Exception if $key === null ? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Internal/Hydration/ObjectHydrator.php:278— // TODO: Abstract this code and UnitOfWork::createEntity() equivalent? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Internal/Hydration/ObjectHydrator.php:347— // TODO: Add special case code where we hydrate the right join objects into identity map at least — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Internal/Hydration/ObjectHydrator.php:449— // TODO: Just check hints['fetched'] here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/Cache/Persister/Entity/AbstractEntityPersister.php:560— // todo: move to argument in next major release — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: ClassMetadata src/Mapping/ClassMetadata.php:87— TooManyMethods — 121 methods. The bar is 30 methods; this is 91 over it, 4.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: Parser src/Query/Parser.php:54— TooManyMethods — 117 methods. The bar is 30 methods; this is 87 over it, 3.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UnitOfWork src/UnitOfWork.php:95— TooManyMethods — 99 methods. The bar is 30 methods; this is 69 over it, 3.30× 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: SqlWalker src/Query/SqlWalker.php:52— TooManyMethods — 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Configuration src/Configuration.php:44— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: QueryBuilder src/QueryBuilder.php:47— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractQuery src/AbstractQuery.php:47— 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.
TooManyMethods: BasicEntityPersister src/Persisters/Entity/BasicEntityPersister.php:98— 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.
TooManyMethods: Expr src/Query/Expr.php:26— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EntityManager src/EntityManager.php:62— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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: PersistentCollection src/PersistentCollection.php:42— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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: Query src/Query.php:46— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractEntityPersister src/Cache/Persister/Entity/AbstractEntityPersister.php:38— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Parser src/Query/Parser.php:54— ClassTooLong — 1620 significant lines (blank, comment-only and punctuation-only lines excluded), 117 methods. The bar is 400 significant lines; this is 1220 over it, 4.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: UnitOfWork src/UnitOfWork.php:95— ClassTooLong — 1358 significant lines (blank, comment-only and punctuation-only lines excluded), 99 methods. The bar is 400 significant lines; this is 958 over it, 3.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SqlWalker src/Query/SqlWalker.php:52— ClassTooLong — 1126 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 400 significant lines; this is 726 over it, 2.82× 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: BasicEntityPersister src/Persisters/Entity/BasicEntityPersister.php:98— ClassTooLong — 966 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 400 significant lines; this is 566 over it, 2.42× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ClassMetadata src/Mapping/ClassMetadata.php:87— ClassTooLong — 915 significant lines (blank, comment-only and punctuation-only lines excluded), 121 methods. The bar is 400 significant lines; this is 515 over it, 2.29× 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: SchemaTool src/Tools/SchemaTool.php:73— ClassTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 399 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XmlDriver src/Mapping/Driver/XmlDriver.php:44— ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 76 over it, 1.19× 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: QueryBuilder src/QueryBuilder.php:47— ClassTooLong — 462 significant lines (blank, comment-only and punctuation-only lines excluded), 66 methods. The bar is 400 significant lines; this is 62 over it, 1.16× 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.
MethodTooLong: XmlDriver.loadMetadataForClass src/Mapping/Driver/XmlDriver.php:82— MethodTooLong — loadMetadataForClass runs 321 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 221 over it, 3.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: AttributeDriver.loadMetadataForClass src/Mapping/Driver/AttributeDriver.php:82— MethodTooLong — loadMetadataForClass runs 295 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 195 over it, 2.95× 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: SchemaTool.experimentalGetSchemaFromMetadata src/Tools/SchemaTool.php:523— MethodTooLong — experimentalGetSchemaFromMetadata runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: SchemaTool.getSchemaFromMetadata src/Tools/SchemaTool.php:198— MethodTooLong — getSchemaFromMetadata runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: UnitOfWork.createEntity src/UnitOfWork.php:2480— MethodTooLong — createEntity runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: ObjectHydrator.hydrateRowData src/Internal/Hydration/ObjectHydrator.php:322— MethodTooLong — hydrateRowData runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SchemaValidator.validateClass src/Tools/SchemaValidator.php:109— MethodTooLong — validateClass runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: UnitOfWork.computeChangeSet src/UnitOfWork.php:600— MethodTooLong — computeChangeSet runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (7 lines × 2) src/Cache/DefaultQueryCache.php:235— src/Cache/DefaultQueryCache.php:235-241 | src/Cache/DefaultQueryCache.php:329-335 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Cache/DefaultQueryCache.php:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Mapping/Driver/XmlDriver.php:372— src/Mapping/Driver/XmlDriver.php:372-378 | src/Mapping/Driver/XmlDriver.php:405-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Query/SqlWalker.php:324— src/Query/SqlWalker.php:324-330 | src/Query/SqlWalker.php:348-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Query/SqlWalker.php:753— src/Query/SqlWalker.php:753-759 | src/Query/SqlWalker.php:784-790 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Query/SqlWalker.php:753` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Tools/Console/Command/ClearCache/CollectionRegionCommand.php:28— src/Tools/Console/Command/ClearCache/CollectionRegionCommand.php:28-34 | src/Tools/Console/Command/ClearCache/EntityRegionCommand.php:27-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/Console/Command/ClearCache/CollectionRegionCommand.php:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Persisters/Entity/BasicEntityPersister.php:1072— src/Persisters/Entity/BasicEntityPersister.php:1072-1078 | src/Persisters/Entity/BasicEntityPersister.php:1844-1850 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Internal/Hydration/ArrayHydrator.php:51— src/Internal/Hydration/ArrayHydrator.php:51-57 | src/Internal/Hydration/ScalarHydrator.php:19-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/Query/SqlWalker.php:218— src/Query/SqlWalker.php:218-224 | src/Query/TreeWalkerAdapter.php:60-66 — 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.
FileTooLong: Query/Parser.php src/Query/Parser.php— FileTooLong — 1653 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: Parser (54-3544). The bar is 500 significant lines; this is 1153 over it, 3.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/UnitOfWork.php src/UnitOfWork.php— FileTooLong — 1439 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: UnitOfWork (95-3534). The bar is 500 significant lines; this is 939 over it, 2.88× 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: Query/SqlWalker.php src/Query/SqlWalker.php— FileTooLong — 1166 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: SqlWalker (52-2374). The bar is 500 significant lines; this is 666 over it, 2.33× 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: Entity/BasicEntityPersister.php src/Persisters/Entity/BasicEntityPersister.php— FileTooLong — 1023 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: BasicEntityPersister (98-2052). The bar is 500 significant lines; this is 523 over it, 2.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Mapping/ClassMetadata.php src/Mapping/ClassMetadata.php— FileTooLong — 978 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ClassMetadata (87-2807). The bar is 500 significant lines; this is 478 over it, 1.96× 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: Tools/SchemaTool.php src/Tools/SchemaTool.php— FileTooLong — 860 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: SchemaTool (73-1647). The bar is 500 significant lines; this is 360 over it, 1.72× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Driver/XmlDriver.php src/Mapping/Driver/XmlDriver.php— FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: XmlDriver (44-1020). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Low cohesion: JoinTableMapping (LCOM4 6) src/Mapping/JoinTableMapping.php:13— JoinTableMapping's methods fall into 6 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 6 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: ClassMetadataBuilder (LCOM4 5) src/Mapping/Builder/ClassMetadataBuilder.php:15— ClassMetadataBuilder's methods fall into 5 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 5 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: DiscriminatorColumnMapping (LCOM4 5) src/Mapping/DiscriminatorColumnMapping.php:15— DiscriminatorColumnMapping's methods fall into 5 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 5 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: EmbeddedClassMapping (LCOM4 5) src/Mapping/EmbeddedClassMapping.php:12— EmbeddedClassMapping's methods fall into 5 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 5 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: FieldMapping (LCOM4 5) src/Mapping/FieldMapping.php:14— FieldMapping's methods fall into 5 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 5 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: JoinColumnMapping (LCOM4 5) src/Mapping/JoinColumnMapping.php:12— JoinColumnMapping's methods fall into 5 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 5 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.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×5
Edited copy of a member (12 corresponding lines) src/Persisters/SqlExpressionVisitor.php:58— src/Persisters/SqlExpressionVisitor.php:58-69 | src/Query/QueryExpressionVisitor.php:68-79 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/Persisters/Collection/OneToManyPersister.php:87— src/Persisters/Collection/OneToManyPersister.php:87-98 | src/Persisters/Collection/OneToManyPersister.php:136-150 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/Persisters/Collection/ManyToManyPersister.php:338— src/Persisters/Collection/ManyToManyPersister.php:338-349 | src/Persisters/Entity/BasicEntityPersister.php:2004-2015 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/PersistentCollection.php:138— src/PersistentCollection.php:138-155 | src/PersistentCollection.php:164-175 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) src/Query/Parser.php:1361— src/Query/Parser.php:1361-1372 | src/Query/Parser.php:3150-3162 — These two members are one piece of code written twice and then edited apart: 12 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.
FixmeComment tests/Tests/OrmFunctionalTestCase.php:908— //FIXME: two different configs! $conn and the created entity manager have — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/Tests/ORM/Functional/DatabaseDriverTest.php:342— // FIXME: Condition here is fugly. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/UnitOfWork.php:2700— // FIXME: Can break easily with composite keys if join column values are in — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment src/Persisters/Entity/BasicEntityPersister.php:319— // FIXME: Order with composite keys might not be correct — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×4
Edited copy of a member (18 corresponding lines) src/Query/Parser.php:2751— src/Query/Parser.php:2751-2768 | src/Query/Parser.php:2776-2793 — 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.
Edited copy of a member (18 corresponding lines) src/Persisters/Entity/BasicEntityPersister.php:1171— src/Persisters/Entity/BasicEntityPersister.php:1171-1188 | src/Persisters/Entity/JoinedSubclassPersister.php:317-336 — 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.
Edited copy of a member (18 corresponding lines) src/Mapping/ClassMetadata.php:1572— src/Mapping/ClassMetadata.php:1572-1589 | src/Mapping/DefaultQuoteStrategy.php:113-136 — 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.
Edited copy of a member (18 corresponding lines) src/PersistentCollection.php:299— src/PersistentCollection.php:299-316 | src/PersistentCollection.php:321-338 — 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 (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) src/Cache/Persister/Collection/AbstractCollectionPersister.php:49— src/Cache/Persister/Collection/AbstractCollectionPersister.php:49-63 | src/Cache/Persister/Entity/AbstractEntityPersister.php:69-81 — 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.
Edited copy of a member (13 corresponding lines) src/Query/SqlWalker.php:2258— src/Query/SqlWalker.php:2258-2270 | src/Query/SqlWalker.php:2278-2292 — 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.
Edited copy of a member (13 corresponding lines) src/Cache/Persister/Entity/ReadWriteCachedEntityPersister.php:69— src/Cache/Persister/Entity/ReadWriteCachedEntityPersister.php:69-86 | src/Cache/Persister/Entity/ReadWriteCachedEntityPersister.php:91-103 — 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.
Edited copy of a member (13 corresponding lines) src/Persisters/Collection/ManyToManyPersister.php:180— src/Persisters/Collection/ManyToManyPersister.php:180-194 | src/Persisters/Collection/ManyToManyPersister.php:199-211 — 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 copy of a member (4 corresponding lines) · ×4
Edited copy of a member (4 corresponding lines) src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:27— src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:27-30 | src/Mapping/PropertyAccessors/RawValuePropertyAccessor.php:26-29 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/Query/SqlWalker.php:151— src/Query/SqlWalker.php:151-155 | src/Persisters/Collection/AbstractCollectionPersister.php:29-32 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/Persisters/Collection/ManyToManyPersister.php:172— src/Persisters/Collection/ManyToManyPersister.php:172-175 | src/Persisters/Collection/OneToManyPersister.php:106-109 — These two members are one piece of code written twice and then edited apart: 4 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 (4 corresponding lines) src/Internal/StronglyConnectedComponents.php:87— src/Internal/StronglyConnectedComponents.php:87-90 | src/Internal/TopologicalSort.php:60-63 — These two members are one piece of code written twice and then edited apart: 4 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 (14 lines × 2) src/Query/Parser.php:906— src/Query/Parser.php:906-919 | src/Query/Parser.php:963-976 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (14 lines × 2) src/UnitOfWork.php:2155— src/UnitOfWork.php:2155-2168 | src/UnitOfWork.php:2196-2209 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UnitOfWork.php:2155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Mapping/ManyToManyOwningSideMapping.php:64— src/Mapping/ManyToManyOwningSideMapping.php:64-77 | src/Mapping/ManyToManyOwningSideMapping.php:79-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/Query/AST/Functions/LowerFunction.php:25— src/Query/AST/Functions/LowerFunction.php:25-38 | src/Query/AST/Functions/UpperFunction.php:25-38 — before extracting anything, compare `src/Query/AST/Functions/LowerFunction.php` and `src/Query/AST/Functions/UpperFunction.php` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Query/AST/Functions/LowerFunction.php:25` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/Mapping/Driver/XmlDriver.php:512— src/Mapping/Driver/XmlDriver.php:512-523 | src/Mapping/Driver/XmlDriver.php:605-618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Mapping/Driver/XmlDriver.php:525` calls `isset` and `src/Mapping/Driver/XmlDriver.php:620` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/Persisters/Entity/BasicEntityPersister.php:1095— src/Persisters/Entity/BasicEntityPersister.php:1095-1106 | src/Persisters/Entity/BasicEntityPersister.php:1865-1876 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Persisters/Entity/BasicEntityPersister.php:1095` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/QueryBuilder.php:417— src/QueryBuilder.php:417-428 | src/QueryBuilder.php:474-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/QueryBuilder.php:417` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/UnitOfWork.php:708— src/UnitOfWork.php:708-719 | src/UnitOfWork.php:1093-1104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UnitOfWork.php:708` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Mapping/DiscriminatorColumnMapping.php:50— src/Mapping/DiscriminatorColumnMapping.php:50-60 | src/Mapping/FieldMapping.php:124-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/DiscriminatorColumnMapping.php:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Persisters/Entity/BasicEntityPersister.php:522— src/Persisters/Entity/BasicEntityPersister.php:522-532 | src/Persisters/Entity/BasicEntityPersister.php:1052-1062 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/AbstractQuery.php:334— src/AbstractQuery.php:334-344 | src/QueryBuilder.php:511-521 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/Mapping/AssociationOverrides.php:26— src/Mapping/AssociationOverrides.php:26-36 | src/Mapping/AttributeOverrides.php:26-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) src/Cache/Persister/Entity/AbstractEntityPersister.php:157— src/Cache/Persister/Entity/AbstractEntityPersister.php:157-165 | src/Cache/Persister/Entity/AbstractEntityPersister.php:405-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Cache/Persister/Entity/AbstractEntityPersister.php:416` calls `storeJoinedAssociations` and `src/Cache/Persister/Entity/AbstractEntityPersister.php:167` 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 (9 lines × 2) src/Cache/Persister/Entity/AbstractEntityPersister.php:483— src/Cache/Persister/Entity/AbstractEntityPersister.php:483-491 | src/Cache/Persister/Entity/AbstractEntityPersister.php:514-522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/Mapping/Driver/XmlDriver.php:780— src/Mapping/Driver/XmlDriver.php:780-788 | src/Mapping/Driver/XmlDriver.php:855-863 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:780` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/Query/Parser.php:1044— src/Query/Parser.php:1044-1052 | src/Query/Parser.php:1793-1801 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/Query/SqlWalker.php:1021— src/Query/SqlWalker.php:1021-1026 | src/Query/SqlWalker.php:1038-1043 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/Query/SqlWalker.php:1767— src/Query/SqlWalker.php:1767-1772 | src/Query/SqlWalker.php:1782-1787 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/Query/AST/Functions/AbsFunction.php:30— src/Query/AST/Functions/AbsFunction.php:30-35 | src/Query/AST/Functions/SqrtFunction.php:33-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/Query/AST/Functions/BitAndFunction.php:24— src/Query/AST/Functions/BitAndFunction.php:24-29 | src/Query/AST/Functions/BitOrFunction.php:24-29 — before extracting anything, compare `src/Query/AST/Functions/BitAndFunction.php` and `src/Query/AST/Functions/BitOrFunction.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) src/Query/Parser.php:848— src/Query/Parser.php:848-855 | src/Query/Parser.php:1401-1413 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/Query/SqlWalker.php:1767— src/Query/SqlWalker.php:1767-1774 | src/Query/SqlWalker.php:1782-1789 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) src/Cache/DefaultCache.php:120— src/Cache/DefaultCache.php:120-127 | src/Cache/DefaultCache.php:132-139 — These two members are one piece of code written twice and then edited apart: 8 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 (9 corresponding lines) · ×3
Edited copy of a member (9 corresponding lines) src/Persisters/Entity/BasicEntityPersister.php:880— src/Persisters/Entity/BasicEntityPersister.php:880-891 | src/Persisters/Entity/BasicEntityPersister.php:959-967 — 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) src/Persisters/Entity/BasicEntityPersister.php:994— src/Persisters/Entity/BasicEntityPersister.php:994-1002 | src/Persisters/Entity/BasicEntityPersister.php:1015-1026 — 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) src/Mapping/ClassMetadata.php:990— src/Mapping/ClassMetadata.php:990-998 | src/Mapping/ClassMetadata.php:1015-1023 — 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) src/Query/Parser.php:2118— src/Query/Parser.php:2118-2131 | src/Query/Parser.php:2140-2154 — 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) src/Query/Parser.php:3481— src/Query/Parser.php:3481-3494 | src/Query/Parser.php:3520-3533 — 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) src/QueryBuilder.php:947— src/QueryBuilder.php:947-960 | src/QueryBuilder.php:988-1001 — 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 (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) src/Mapping/DiscriminatorColumnMapping.php:50— src/Mapping/DiscriminatorColumnMapping.php:50-67 | src/Mapping/FieldMapping.php:124-139 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) src/Query/Parser.php:2403— src/Query/Parser.php:2403-2418 | src/Query/Parser.php:2426-2441 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) src/AbstractQuery.php:484— src/AbstractQuery.php:484-499 | src/AbstractQuery.php:517-532 — These two members are one piece of code written twice and then edited apart: 16 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) · ×3
Edited copy of a member (7 corresponding lines) src/Persisters/Entity/BasicEntityPersister.php:292— src/Persisters/Entity/BasicEntityPersister.php:292-298 | src/Persisters/Entity/JoinedSubclassPersister.php:511-517 — 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.
Edited copy of a member (7 corresponding lines) src/AbstractQuery.php:285— src/AbstractQuery.php:285-291 | src/QueryBuilder.php:564-570 — 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.
Edited copy of a member (7 corresponding lines) src/Mapping/PropertyAccessors/EmbeddablePropertyAccessor.php:48— src/Mapping/PropertyAccessors/EmbeddablePropertyAccessor.php:48-56 | src/Mapping/PropertyAccessors/EnumPropertyAccessor.php:33-39 — 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.
Duplicated block (13 lines × 2) src/Mapping/Driver/XmlDriver.php:419— src/Mapping/Driver/XmlDriver.php:419-431 | src/Mapping/Driver/XmlDriver.php:556-568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:419` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/Query/Expr.php:396— src/Query/Expr.php:396-408 | src/Query/Expr.php:419-431 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/Query/SqlWalker.php:1444— src/Query/SqlWalker.php:1444-1456 | src/Query/SqlWalker.php:1479-1491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/Cache/Persister/Entity/AbstractEntityPersister.php:353— src/Cache/Persister/Entity/AbstractEntityPersister.php:353-360 | src/Cache/Persister/Entity/AbstractEntityPersister.php:445-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/Query/AST/Functions/BitAndFunction.php:34— src/Query/AST/Functions/BitAndFunction.php:34-41 | src/Query/AST/Functions/BitOrFunction.php:34-41 — before extracting anything, compare `src/Query/AST/Functions/BitAndFunction.php` and `src/Query/AST/Functions/BitOrFunction.php` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/Tools/Event/GenerateSchemaEventArgs.php:40— src/Tools/Event/GenerateSchemaEventArgs.php:40-47 | src/Tools/Event/GenerateSchemaTableEventArgs.php:49-56 — 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 (31 lines × 2) src/Persisters/Entity/JoinedSubclassPersister.php:427— src/Persisters/Entity/JoinedSubclassPersister.php:427-457 | src/Persisters/Entity/SingleTablePersister.php:64-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Persisters/Entity/JoinedSubclassPersister.php:427` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Persisters/Entity/JoinedSubclassPersister.php:424` calls `getSQLTableAlias` and `src/Persisters/Entity/SingleTablePersister.php:61` 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 (31 lines × 2) src/Tools/Pagination/CountOutputWalker.php:79— src/Tools/Pagination/CountOutputWalker.php:79-109 | src/Tools/Pagination/LimitSubqueryOutputWalker.php:517-547 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/Pagination/CountOutputWalker.php:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Tools/Pagination/LimitSubqueryOutputWalker.php:549` calls `count`, `RuntimeException` and `src/Tools/Pagination/CountOutputWalker.php:111` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) src/Mapping/Driver/AttributeDriver.php:130— src/Mapping/Driver/AttributeDriver.php:130-146 | src/Mapping/Driver/AttributeDriver.php:175-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/AttributeDriver.php:130` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Mapping/Driver/XmlDriver.php:171— src/Mapping/Driver/XmlDriver.php:171-187 | src/Mapping/Driver/XmlDriver.php:214-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Mapping/Driver/XmlDriver.php:355— src/Mapping/Driver/XmlDriver.php:355-369 | src/Mapping/Driver/XmlDriver.php:457-471 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/Tools/SchemaTool.php:209— src/Tools/SchemaTool.php:209-223 | src/Tools/SchemaTool.php:526-540 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/SchemaTool.php:209` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/Cache/Persister/Collection/ReadWriteCachedCollectionPersister.php:29— src/Cache/Persister/Collection/ReadWriteCachedCollectionPersister.php:29-41 | src/Cache/Persister/Collection/ReadWriteCachedCollectionPersister.php:46-58 | src/Cache/Persister/Entity/ReadWriteCachedEntityPersister.php:52-64 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 3) src/Mapping/ManyToManyOwningSideMapping.php:148— src/Mapping/ManyToManyOwningSideMapping.php:148-160 | src/Mapping/ManyToManyOwningSideMapping.php:187-199 | src/Mapping/ToOneOwningSideMapping.php:164-176 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 2) src/Mapping/Driver/AttributeDriver.php:384— src/Mapping/Driver/AttributeDriver.php:384-393 | src/Mapping/Driver/AttributeDriver.php:461-470 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/Tools/Pagination/CursorPaginator.php:134— src/Tools/Pagination/CursorPaginator.php:134-143 | src/Tools/Pagination/PaginatorQuery.php:161-170 — 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–10 lines × 2) src/Persisters/Collection/OneToManyPersister.php:87— src/Persisters/Collection/OneToManyPersister.php:87-96 | src/Persisters/Collection/OneToManyPersister.php:140-148 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) src/Query/Parser.php:1780— src/Query/Parser.php:1780-1789 | src/Query/Parser.php:1795-1803 — 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 × 3) src/Cache/Persister/Entity/AbstractEntityPersister.php:312— src/Cache/Persister/Entity/AbstractEntityPersister.php:312-318 | src/Cache/Persister/Entity/AbstractEntityPersister.php:351-357 | src/Cache/Persister/Entity/AbstractEntityPersister.php:443-449 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Cache/Persister/Entity/AbstractEntityPersister.php:312` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/Tools/Console/Command/ClearCache/MetadataCommand.php:23— src/Tools/Console/Command/ClearCache/MetadataCommand.php:23-29 | src/Tools/Console/Command/ClearCache/ResultCommand.php:23-43 | src/Tools/Console/Command/SchemaTool/CreateCommand.php:24-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/Console/Command/SchemaTool/CreateCommand.php:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption docs/en/cookbook/generated-columns/Person.php:11— No encryption usage (Laravel's Crypt facade or encrypt() helper, an Eloquent 'encrypted' cast, openssl_encrypt, libsodium's sodium_crypto_secretbox/aead, defuse/php-encryption, phpseclib, CipherSweet) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
XmlDriver.loadMetadataForClass (cyclomatic 140) src/Mapping/Driver/XmlDriver.php:82— XmlDriver.loadMetadataForClass has cyclomatic complexity 140 (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.
AttributeDriver.loadMetadataForClass (cyclomatic 95) src/Mapping/Driver/AttributeDriver.php:82— AttributeDriver.loadMetadataForClass has cyclomatic complexity 95 (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.
UnitOfWork.createEntity (cyclomatic 68) src/UnitOfWork.php:2480— UnitOfWork.createEntity 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.
SchemaValidator.validateClass (cyclomatic 59) src/Tools/SchemaValidator.php:109— SchemaValidator.validateClass has cyclomatic complexity 59 (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.
ObjectHydrator.hydrateRowData (cyclomatic 52) src/Internal/Hydration/ObjectHydrator.php:322— ObjectHydrator.hydrateRowData 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.
UnitOfWork.computeChangeSet (cyclomatic 49) src/UnitOfWork.php:600— UnitOfWork.computeChangeSet has cyclomatic complexity 49 (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.
ClassMetadata._validateAndCompleteAssociationMapping (cyclomatic 48) src/Mapping/ClassMetadata.php:1308— ClassMetadata._validateAndCompleteAssociationMapping has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SchemaTool.getSchemaFromMetadata (cyclomatic 43) src/Tools/SchemaTool.php:198— SchemaTool.getSchemaFromMetadata has cyclomatic complexity 43 (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.
SchemaTool.experimentalGetSchemaFromMetadata (cyclomatic 43) src/Tools/SchemaTool.php:523— SchemaTool.experimentalGetSchemaFromMetadata has cyclomatic complexity 43 (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.
ArrayHydrator.hydrateRowData (cyclomatic 38) src/Internal/Hydration/ArrayHydrator.php:63— ArrayHydrator.hydrateRowData 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.
ManyToManyOwningSideMapping.fromMappingArrayAndNamingStrategy (cyclomatic 31) src/Mapping/ManyToManyOwningSideMapping.php:62— ManyToManyOwningSideMapping.fromMappingArrayAndNamingStrategy 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.
SqlWalker.walkJoinAssociationDeclaration (cyclomatic 28) src/Query/SqlWalker.php:934— SqlWalker.walkJoinAssociationDeclaration has cyclomatic complexity 28 (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.
SqlWalker.walkSelectExpression (cyclomatic 28) src/Query/SqlWalker.php:1279— SqlWalker.walkSelectExpression has cyclomatic complexity 28 (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.
ClassMetadataFactory.doLoadMetadata (cyclomatic 27) src/Mapping/ClassMetadataFactory.php:132— ClassMetadataFactory.doLoadMetadata 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.
Lexer.getType (cyclomatic 27) src/Query/Lexer.php:59— Lexer.getType has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Parser.SelectExpression (cyclomatic 27) src/Query/Parser.php:2187— Parser.SelectExpression has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SqlWalker.walkSelectClause (cyclomatic 27) src/Query/SqlWalker.php:680— SqlWalker.walkSelectClause 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.
AbstractHydrator.gatherRowData (cyclomatic 26) src/Internal/Hydration/AbstractHydrator.php:277— AbstractHydrator.gatherRowData has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SchemaTool.gatherColumn (cyclomatic 26) src/Tools/SchemaTool.php:905— SchemaTool.gatherColumn has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UnitOfWork.commit (cyclomatic 26) src/UnitOfWork.php:366— UnitOfWork.commit has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassMetadata.validateAndCompleteFieldMapping (cyclomatic 25) src/Mapping/ClassMetadata.php:1214— ClassMetadata.validateAndCompleteFieldMapping 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.
SchemaTool.gatherRelationJoinColumns (cyclomatic 25) src/Tools/SchemaTool.php:1207— SchemaTool.gatherRelationJoinColumns 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.
BasicEntityPersister.getSelectColumnsSQL (cyclomatic 23) src/Persisters/Entity/BasicEntityPersister.php:1261— BasicEntityPersister.getSelectColumnsSQL 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.
SimpleObjectHydrator.hydrateRowData (cyclomatic 22) src/Internal/Hydration/SimpleObjectHydrator.php:73— SimpleObjectHydrator.hydrateRowData 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.
DefaultQueryCache.put (cyclomatic 21) src/Cache/DefaultQueryCache.php:200— DefaultQueryCache.put 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.
EntityManager.find (cyclomatic 21) src/EntityManager.php:276— EntityManager.find 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.
BasicEntityPersister.prepareUpdateData (cyclomatic 21) src/Persisters/Entity/BasicEntityPersister.php:595— BasicEntityPersister.prepareUpdateData 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.
Parser.SimpleConditionalExpression (cyclomatic 21) src/Query/Parser.php:2510— Parser.SimpleConditionalExpression 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.
UnitOfWork.recomputeSingleEntityChangeSet (cyclomatic 20) src/UnitOfWork.php:1058— UnitOfWork.recomputeSingleEntityChangeSet 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.
XmlDriver.columnToArray (cyclomatic 19) src/Mapping/Driver/XmlDriver.php:829— XmlDriver.columnToArray has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ToOneOwningSideMapping.fromMappingArrayAndName (cyclomatic 19) src/Mapping/ToOneOwningSideMapping.php:99— ToOneOwningSideMapping.fromMappingArrayAndName 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.
QueryExpressionVisitor.walkComparison (cyclomatic 18) src/Query/QueryExpressionVisitor.php:82— QueryExpressionVisitor.walkComparison 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.
UnitOfWork.computeDeleteExecutionOrder (cyclomatic 18) src/UnitOfWork.php:1375— UnitOfWork.computeDeleteExecutionOrder 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.
DefaultEntityHydrator.buildCacheEntry (cyclomatic 17) src/Cache/DefaultEntityHydrator.php:37— DefaultEntityHydrator.buildCacheEntry 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.
DefaultQueryCache.get (cyclomatic 17) src/Cache/DefaultQueryCache.php:57— DefaultQueryCache.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.
ClassMetadata.__sleep (cyclomatic 17) src/Mapping/ClassMetadata.php:735— ClassMetadata.__sleep has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BasicEntityPersister.getSelectConditionStatementSQL (cyclomatic 17) src/Persisters/Entity/BasicEntityPersister.php:1630— BasicEntityPersister.getSelectConditionStatementSQL 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.
JoinedSubclassPersister.getSelectColumnsSQL (cyclomatic 17) src/Persisters/Entity/JoinedSubclassPersister.php:365— JoinedSubclassPersister.getSelectColumnsSQL 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.
JoinedSubclassPersister.getInsertColumnList (cyclomatic 17) src/Persisters/Entity/JoinedSubclassPersister.php:463— JoinedSubclassPersister.getInsertColumnList has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
SchemaValidator.validatePropertiesTypes (cyclomatic 17) src/Tools/SchemaValidator.php:337— SchemaValidator.validatePropertiesTypes has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LegacyReflectionFields.offsetGet (cyclomatic 16) src/Mapping/LegacyReflectionFields.php:53— LegacyReflectionFields.offsetGet 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.
SqlWalker.walkObjectExpression (cyclomatic 16) src/Query/SqlWalker.php:1418— SqlWalker.walkObjectExpression 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.
QueryBuilder.add (cyclomatic 16) src/QueryBuilder.php:628— QueryBuilder.add 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.
Hotspot: src/Tools/SchemaTool.php src/Tools/SchemaTool.php:198— src/Tools/SchemaTool.php changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in SchemaTool.getSchemaFromMetadata at line 198. 3 of those changes were fix/bug commits, and the other 9 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-09..2026-11-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-09 14:42:13 +01:00' --until='2026-11-07 14:42:13 +01:00' --full-history --no-merges -- src/Tools/SchemaTool.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.
XmlDriver.loadMetadataForClass (cognitive 353) src/Mapping/Driver/XmlDriver.php:82— XmlDriver.loadMetadataForClass has cognitive complexity 353 (threshold 15). Drivers by points: if/else 91 (232 pts), loops 25 (74 pts), ternaries 12 (39 pts), boolean chains 8 (nesting depth added 217). 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.
AttributeDriver.loadMetadataForClass (cognitive 217) src/Mapping/Driver/AttributeDriver.php:82— AttributeDriver.loadMetadataForClass has cognitive complexity 217 (threshold 15). Drivers by points: if/else 68 (162 pts), loops 17 (47 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 127). 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.
ObjectHydrator.hydrateRowData (cognitive 172) src/Internal/Hydration/ObjectHydrator.php:322— ObjectHydrator.hydrateRowData has cognitive complexity 172 (threshold 15). Drivers by points: if/else 45 (141 pts), ternaries 5 (18 pts), boolean chains 8, loops 3 (5 pts) (nesting depth added 111). 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.
UnitOfWork.createEntity (cognitive 133) src/UnitOfWork.php:2480— UnitOfWork.createEntity has cognitive complexity 133 (threshold 15). Drivers by points: if/else 35 (88 pts), boolean chains 28, match/switch 3 (9 pts), loops 4 (8 pts) (nesting depth added 63). 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.
SchemaValidator.validateClass (cognitive 124) src/Tools/SchemaValidator.php:109— SchemaValidator.validateClass has cognitive complexity 124 (threshold 15). Drivers by points: if/else 29 (87 pts), loops 8 (23 pts), boolean chains 14 (nesting depth added 73). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaTool.getSchemaFromMetadata (cognitive 123) src/Tools/SchemaTool.php:198— SchemaTool.getSchemaFromMetadata has cognitive complexity 123 (threshold 15). Drivers by points: if/else 24 (71 pts), loops 14 (42 pts), ternaries 2 (8 pts), boolean chains 2 (nesting depth added 81). 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.
SchemaTool.experimentalGetSchemaFromMetadata (cognitive 123) src/Tools/SchemaTool.php:523— SchemaTool.experimentalGetSchemaFromMetadata has cognitive complexity 123 (threshold 15). Drivers by points: if/else 24 (72 pts), loops 14 (41 pts), ternaries 2 (8 pts), boolean chains 2 (nesting depth added 81). 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.
UnitOfWork.computeChangeSet (cognitive 116) src/UnitOfWork.php:600— UnitOfWork.computeChangeSet has cognitive complexity 116 (threshold 15). Drivers by points: if/else 33 (95 pts), loops 5 (11 pts), boolean chains 10 (nesting depth added 68). 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.
ArrayHydrator.hydrateRowData (cognitive 100) src/Internal/Hydration/ArrayHydrator.php:63— ArrayHydrator.hydrateRowData has cognitive complexity 100 (threshold 15). Drivers by points: if/else 25 (63 pts), ternaries 7 (26 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 59). 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.
ClassMetadata._validateAndCompleteAssociationMapping (cognitive 57) src/Mapping/ClassMetadata.php:1308— ClassMetadata._validateAndCompleteAssociationMapping has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (35 pts), boolean chains 16, ternaries 3 (5 pts), match/switch 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.
SqlWalker.walkSelectClause (cognitive 55) src/Query/SqlWalker.php:680— SqlWalker.walkSelectClause has cognitive complexity 55 (threshold 15). Drivers by points: if/else 11 (27 pts), loops 6 (16 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManyToManyOwningSideMapping.fromMappingArrayAndNamingStrategy (cognitive 52) src/Mapping/ManyToManyOwningSideMapping.php:62— ManyToManyOwningSideMapping.fromMappingArrayAndNamingStrategy has cognitive complexity 52 (threshold 15). Drivers by points: if/else 19 (37 pts), loops 4 (6 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassMetadataFactory.doLoadMetadata (cognitive 45) src/Mapping/ClassMetadataFactory.php:132— ClassMetadataFactory.doLoadMetadata has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 6, loops 1 (2 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractHydrator.gatherRowData (cognitive 44) src/Internal/Hydration/AbstractHydrator.php:277— AbstractHydrator.gatherRowData has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (28 pts), loops 6, boolean chains 5, ternaries 1 (3 pts), match/switch 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.
DebugUnitOfWorkListener.dumpIdentityMap (cognitive 43) src/Tools/DebugUnitOfWorkListener.php:46— DebugUnitOfWorkListener.dumpIdentityMap has cognitive complexity 43 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 5 (18 pts), boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.getSelectColumnsSQL (cognitive 42) src/Persisters/Entity/BasicEntityPersister.php:1261— BasicEntityPersister.getSelectColumnsSQL has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 6 (12 pts), boolean chains 5 (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.
DefaultQueryCache.put (cognitive 41) src/Cache/DefaultQueryCache.php:200— DefaultQueryCache.put has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlWalker.walkJoinAssociationDeclaration (cognitive 41) src/Query/SqlWalker.php:934— SqlWalker.walkJoinAssociationDeclaration has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (22 pts), ternaries 4 (7 pts), loops 3 (6 pts), boolean chains 5, match/switch 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.
SimpleObjectHydrator.hydrateRowData (cognitive 39) src/Internal/Hydration/SimpleObjectHydrator.php:73— SimpleObjectHydrator.hydrateRowData has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnitOfWork.computeDeleteExecutionOrder (cognitive 39) src/UnitOfWork.php:1375— UnitOfWork.computeDeleteExecutionOrder has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultEntityHydrator.buildCacheEntry (cognitive 38) src/Cache/DefaultEntityHydrator.php:37— DefaultEntityHydrator.buildCacheEntry has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 4 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaTool.gatherRelationJoinColumns (cognitive 38) src/Tools/SchemaTool.php:1207— SchemaTool.gatherRelationJoinColumns has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (29 pts), boolean chains 3, loops 3, ternaries 1 (2 pts), match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultQueryCache.get (cognitive 37) src/Cache/DefaultQueryCache.php:57— DefaultQueryCache.get has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 4 (8 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.prepareUpdateData (cognitive 37) src/Persisters/Entity/BasicEntityPersister.php:595— BasicEntityPersister.prepareUpdateData has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6, ternaries 2 (6 pts), loops 2 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToOneOwningSideMapping.fromMappingArrayAndName (cognitive 36) src/Mapping/ToOneOwningSideMapping.php:99— ToOneOwningSideMapping.fromMappingArrayAndName has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnitOfWork.recomputeSingleEntityChangeSet (cognitive 35) src/UnitOfWork.php:1058— UnitOfWork.recomputeSingleEntityChangeSet has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3 (6 pts), boolean chains 4 (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.
DatabaseDriver.loadMetadataForClass (cognitive 34) src/Mapping/Driver/DatabaseDriver.php:172— DatabaseDriver.loadMetadataForClass has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 5 (14 pts), ternaries 1 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassMetadata.validateAndCompleteFieldMapping (cognitive 32) src/Mapping/ClassMetadata.php:1214— ClassMetadata.validateAndCompleteFieldMapping has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 7 (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.
BasicEntityPersister.getSelectConditionStatementSQL (cognitive 31) src/Persisters/Entity/BasicEntityPersister.php:1630— BasicEntityPersister.getSelectConditionStatementSQL has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 5, loops 1, ternaries 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.
UnitOfWork.commit (cognitive 31) src/UnitOfWork.php:366— UnitOfWork.commit has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 5 (8 pts), boolean chains 6, error handling 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Parser.SimpleConditionalExpression (cognitive 30) src/Query/Parser.php:2510— Parser.SimpleConditionalExpression has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 4, loops 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaTool.getDropSchemaSQL (cognitive 30) src/Tools/SchemaTool.php:1452— SchemaTool.getDropSchemaSQL has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EntityManager.find (cognitive 29) src/EntityManager.php:276— EntityManager.find has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (24 pts), match/switch 2 (3 pts), loops 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.
SqlWalker.walkSelectExpression (cognitive 29) src/Query/SqlWalker.php:1279— SqlWalker.walkSelectExpression has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 5 (10 pts), match/switch 1 (nesting depth added 14). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SchemaTool.gatherColumn (cognitive 29) src/Tools/SchemaTool.php:905— SchemaTool.gatherColumn has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 9, ternaries 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.
JoinedSubclassPersister.getSelectColumnsSQL (cognitive 28) src/Persisters/Entity/JoinedSubclassPersister.php:365— JoinedSubclassPersister.getSelectColumnsSQL has cognitive complexity 28 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 4 (9 pts), ternaries 3 (5 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.
SqlWalker.walkObjectExpression (cognitive 28) src/Query/SqlWalker.php:1418— SqlWalker.walkObjectExpression has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (2 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.
ClassMetadataFactory.validateRuntimeMetadata (cognitive 26) src/Mapping/ClassMetadataFactory.php:260— ClassMetadataFactory.validateRuntimeMetadata has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 5, loops 1 (3 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.
BasicEntityPersister.loadOneToOneEntity (cognitive 26) src/Persisters/Entity/BasicEntityPersister.php:764— BasicEntityPersister.loadOneToOneEntity has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JoinedSubclassPersister.executeInserts (cognitive 26) src/Persisters/Entity/JoinedSubclassPersister.php:99— JoinedSubclassPersister.executeInserts has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 6 (12 pts), ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.getOrderBySQL (cognitive 25) src/Persisters/Entity/BasicEntityPersister.php:1200— BasicEntityPersister.getOrderBySQL has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (9 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.
Parser.processDeferredPathExpressions (cognitive 25) src/Query/Parser.php:727— Parser.processDeferredPathExpressions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 2 (6 pts), boolean chains 1, loops 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.
QueryBuilder.add (cognitive 25) src/QueryBuilder.php:628— QueryBuilder.add has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, loops 1 (2 pts), ternaries 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.
SqlWalker.generateDiscriminatorColumnConditionSQL (cognitive 24) src/Query/SqlWalker.php:407— SqlWalker.generateDiscriminatorColumnConditionSQL has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 4 (9 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LegacyReflectionFields.offsetGet (cognitive 23) src/Mapping/LegacyReflectionFields.php:53— LegacyReflectionFields.offsetGet has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 10). 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.
BasicEntityPersister.getSelectConditionStatementColumnSQL (cognitive 23) src/Persisters/Entity/BasicEntityPersister.php:1715— BasicEntityPersister.getSelectConditionStatementColumnSQL has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (6 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiTableUpdateExecutor.__construct (cognitive 23) src/Query/Exec/MultiTableUpdateExecutor.php:43— MultiTableUpdateExecutor.__construct has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CountOutputWalker.createSqlForFinalizer (cognitive 23) src/Tools/Pagination/CountOutputWalker.php:56— CountOutputWalker.createSqlForFinalizer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (7 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.
JoinedSubclassPersister.getInsertColumnList (cognitive 22) src/Persisters/Entity/JoinedSubclassPersister.php:463— JoinedSubclassPersister.getInsertColumnList has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (8 pts), loops 2 (5 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlWalker.walkCollectionMemberExpression (cognitive 22) src/Query/SqlWalker.php:1931— SqlWalker.walkCollectionMemberExpression has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 4 (8 pts), ternaries 3 (5 pts), match/switch 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.
LimitSubqueryOutputWalker.getSQLIdentifier (cognitive 22) src/Tools/Pagination/LimitSubqueryOutputWalker.php:507— LimitSubqueryOutputWalker.getSQLIdentifier has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (7 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.
ManyToManyPersister.loadCriteria (cognitive 21) src/Persisters/Collection/ManyToManyPersister.php:217— ManyToManyPersister.loadCriteria has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 4 (5 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.getInsertColumnList (cognitive 21) src/Persisters/Entity/BasicEntityPersister.php:1481— BasicEntityPersister.getInsertColumnList has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProxyFactory.getProxyFactory (cognitive 21) src/Proxy/ProxyFactory.php:372— ProxyFactory.getProxyFactory has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 2 (6 pts), loops 4 (5 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.
SchemaTool.gatherRelationsSql (cognitive 21) src/Tools/SchemaTool.php:1053— SchemaTool.gatherRelationsSql has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (9 pts), boolean chains 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.
ClassMetadataFactory.addInheritedIndexes (cognitive 20) src/Mapping/ClassMetadataFactory.php:518— ClassMetadataFactory.addInheritedIndexes has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 2 (4 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.
XmlDriver.parseOptions (cognitive 20) src/Mapping/Driver/XmlDriver.php:687— XmlDriver.parseOptions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnitOfWork.computeAssociationChanges (cognitive 20) src/UnitOfWork.php:903— UnitOfWork.computeAssociationChanges has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (2 pts), boolean chains 1, loops 1, 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.
BasicEntityPersister.deleteJoinTableRecords (cognitive 19) src/Persisters/Entity/BasicEntityPersister.php:509— BasicEntityPersister.deleteJoinTableRecords has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (5 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.expandCriteriaParameters (cognitive 19) src/Persisters/Entity/BasicEntityPersister.php:897— BasicEntityPersister.expandCriteriaParameters has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaValidator.validatePropertiesTypes (cognitive 19) src/Tools/SchemaValidator.php:337— SchemaValidator.validatePropertiesTypes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (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.
UnitOfWork.getEntityState (cognitive 19) src/UnitOfWork.php:1733— UnitOfWork.getEntityState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnitOfWork.eagerLoadCollections (cognitive 19) src/UnitOfWork.php:2861— UnitOfWork.eagerLoadCollections has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 4 (8 pts), boolean chains 1 (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.
PersisterHelper.getTypeOfColumn (cognitive 19) src/Utility/PersisterHelper.php:85— PersisterHelper.getTypeOfColumn has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (6 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.
ObjectHydrator.prepare (cognitive 18) src/Internal/Hydration/ObjectHydrator.php:54— ObjectHydrator.prepare has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassMetadata.wakeupReflection (cognitive 18) src/Mapping/ClassMetadata.php:838— ClassMetadata.wakeupReflection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 3 (5 pts), loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassMetadata.setDiscriminatorColumn (cognitive 18) src/Mapping/ClassMetadata.php:2214— ClassMetadata.setDiscriminatorColumn has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 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.
XmlDriver.columnToArray (cognitive 18) src/Mapping/Driver/XmlDriver.php:829— XmlDriver.columnToArray has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 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.
SqlWalker.generateOrderedCollectionOrderByItems (cognitive 18) src/Query/SqlWalker.php:362— SqlWalker.generateOrderedCollectionOrderByItems has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 2 (7 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DebugEntityListenersDoctrineCommand.execute (cognitive 18) src/Tools/Console/Command/Debug/DebugEntityListenersDoctrineCommand.php:47— DebugEntityListenersDoctrineCommand.execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DebugEventManagerDoctrineCommand.execute (cognitive 18) src/Tools/Console/Command/Debug/DebugEventManagerDoctrineCommand.php:46— DebugEventManagerDoctrineCommand.execute has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (7 pts), loops 2 (3 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.
IdentifierFlattener.flattenIdentifier (cognitive 18) src/Utility/IdentifierFlattener.php:46— IdentifierFlattener.flattenIdentifier has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), boolean chains 3 (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.
ClassMetadata.__sleep (cognitive 17) src/Mapping/ClassMetadata.php:735— ClassMetadata.__sleep has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16 (17 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassMetadataFactory.completeIdGeneratorMapping (cognitive 17) src/Mapping/ClassMetadataFactory.php:572— ClassMetadataFactory.completeIdGeneratorMapping has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeDriver.getMethodCallbacks (cognitive 17) src/Mapping/Driver/AttributeDriver.php:646— AttributeDriver.getMethodCallbacks has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SingleTablePersister.getSelectColumnsSQL (cognitive 17) src/Persisters/Entity/SingleTablePersister.php:35— SingleTablePersister.getSelectColumnsSQL has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 3 (7 pts), boolean chains 2 (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.
ProxyFactory.__construct (cognitive 17) src/Proxy/ProxyFactory.php:151— ProxyFactory.__construct has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.processDeferredNewObjectExpressions (cognitive 17) src/Query/Parser.php:603— Parser.processDeferredNewObjectExpressions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, 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.
ResultSetMappingBuilder.addAllClassFields (cognitive 17) src/Query/ResultSetMappingBuilder.php:111— ResultSetMappingBuilder.addAllClassFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlWalker.walkNewObject (cognitive 17) src/Query/SqlWalker.php:1560— SqlWalker.walkNewObject has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 3 (8 pts), match/switch 2 (5 pts), if/else 1 (3 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.
DatabaseDriver.reverseEngineerMappingFromDatabase (cognitive 16) src/Mapping/Driver/DatabaseDriver.php:273— DatabaseDriver.reverseEngineerMappingFromDatabase has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicEntityPersister.updateTable (cognitive 16) src/Persisters/Entity/BasicEntityPersister.php:401— BasicEntityPersister.updateTable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 2 (4 pts), loops 2, 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.
SizeFunction.getSql (cognitive 16) src/Query/AST/Functions/SizeFunction.php:27— SizeFunction.getSql has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 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.
SqlWalker.walkJoin (cognitive 16) src/Query/SqlWalker.php:1155— SqlWalker.walkJoin has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, ternaries 2 (3 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlWalker.walkWhereClause (cognitive 16) src/Query/SqlWalker.php:1818— SqlWalker.walkWhereClause has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (3 pts), 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.
QueryBuilder.addCriteria (cognitive 16) src/QueryBuilder.php:1271— QueryBuilder.addCriteria has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (5 pts), ternaries 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.
CursorPaginator.paginate (cognitive 16) src/Tools/Pagination/CursorPaginator.php:95— CursorPaginator.paginate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LimitSubqueryWalker.validate (cognitive 16) src/Tools/Pagination/LimitSubqueryWalker.php:101— LimitSubqueryWalker.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UnitOfWork.computeInsertExecutionOrder (cognitive 16) src/UnitOfWork.php:1292— UnitOfWork.computeInsertExecutionOrder has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (4 pts), boolean chains 3 (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.
Change coupling: EntityManagerDecorator.php ↔ EntityManager.php src/Decorator/EntityManagerDecorator.php:1— `src/Decorator/EntityManagerDecorator.php` and `src/EntityManager.php` change together 88% of the time (23 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 23 shared commits counted here, the most recent 3 are `9930cece` Deprecate passing null as lock mode; `b20a66dc` Leverage event manager interfaces; `7ef1f0a3` Phpcs fixes — run `git show` on any of them.
Near-duplicate member pair (267 shared lines) src/Tools/SchemaTool.php:200— src/Tools/SchemaTool.php:200-513 | src/Tools/SchemaTool.php:526-853 — These two members are variants of one another: 267 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) src/Tools/Pagination/CountOutputWalker.php:58— src/Tools/Pagination/CountOutputWalker.php:58-123 | src/Tools/Pagination/LimitSubqueryOutputWalker.php:515-560 — These two members are one piece of code written twice and then edited apart: 46 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 (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) src/Cache/Persister/Entity/AbstractEntityPersister.php:305— src/Cache/Persister/Entity/AbstractEntityPersister.php:305-337 | src/Cache/Persister/Entity/AbstractEntityPersister.php:349-373 — These two members are one piece of code written twice and then edited apart: 25 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) src/Cache/Persister/Entity/AbstractEntityPersister.php:476— src/Cache/Persister/Entity/AbstractEntityPersister.php:476-499 | src/Cache/Persister/Entity/AbstractEntityPersister.php:507-530 — These two members are one piece of code written twice and then edited apart: 24 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) src/Persisters/Collection/ManyToManyPersister.php:432— src/Persisters/Collection/ManyToManyPersister.php:432-453 | src/Persisters/Collection/ManyToManyPersister.php:479-502 — These two members are one piece of code written twice and then edited apart: 22 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 (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) src/UnitOfWork.php:2150— src/UnitOfWork.php:2150-2181 | src/UnitOfWork.php:2191-2222 — These two members are one piece of code written twice and then edited apart: 32 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) src/Cache/DefaultCacheFactory.php:68— src/Cache/DefaultCacheFactory.php:68-88 | src/Cache/DefaultCacheFactory.php:96-116 — These two members are one piece of code written twice and then edited apart: 21 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) src/Cache/Persister/Entity/NonStrictReadWriteCachedEntityPersister.php:16— src/Cache/Persister/Entity/NonStrictReadWriteCachedEntityPersister.php:16-42 | src/Cache/Persister/Entity/ReadWriteCachedEntityPersister.php:25-47 — These two members are one piece of code written twice and then edited apart: 23 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 (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) src/Query/AST/Functions/ConcatFunction.php:40— src/Query/AST/Functions/ConcatFunction.php:40-56 | src/Query/AST/Functions/LocateFunction.php:44-60 | src/Query/AST/Functions/SubstringFunction.php:40-56 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) src/QueryBuilder.php:417— src/QueryBuilder.php:417-433 | src/QueryBuilder.php:474-490 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) src/Tools/Console/Command/ClearCache/MetadataCommand.php:34— src/Tools/Console/Command/ClearCache/MetadataCommand.php:34-50 | src/Tools/Console/Command/ClearCache/QueryCommand.php:33-52 | src/Tools/Console/Command/ClearCache/ResultCommand.php:48-63 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) src/AbstractQuery.php:736— src/AbstractQuery.php:736-754 | src/AbstractQuery.php:772-786 — 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 copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) src/Query/Parser.php:2641— src/Query/Parser.php:2641-2660 | src/Query/Parser.php:3046-3059 | src/Query/Parser.php:3299-3313 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×1
Edited copies of one member (5 members, 7+ corresponding lines) src/Tools/Console/Command/ClearCache/CollectionRegionCommand.php:25— src/Tools/Console/Command/ClearCache/CollectionRegionCommand.php:25-56 | src/Tools/Console/Command/ClearCache/EntityRegionCommand.php:25-55 | src/Tools/Console/Command/ClearCache/QueryRegionCommand.php:25-54 | src/Tools/Console/Command/SchemaTool/DropCommand.php:25-45 | src/Tools/Console/Command/ValidateSchemaCommand.php:25-31 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 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 5 times and the copies 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) src/Query/Parser.php:1303— src/Query/Parser.php:1303-1314 | src/Query/Parser.php:1322-1333 | src/Query/Parser.php:1380-1392 | src/Query/Parser.php:2078-2093 — 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 copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) src/Cache/Persister/Collection/AbstractCollectionPersister.php:143— src/Cache/Persister/Collection/AbstractCollectionPersister.php:143-151 | src/Cache/Persister/Collection/NonStrictReadWriteCachedCollectionPersister.php:38-43 | src/Cache/Persister/Collection/ReadWriteCachedCollectionPersister.php:63-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) src/PersistentCollection.php:343— src/PersistentCollection.php:343-352 | src/PersistentCollection.php:357-363 | src/PersistentCollection.php:531-537 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 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 3 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) src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:39— src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:39-49 | src/Mapping/PropertyAccessors/RawValuePropertyAccessor.php:41-51 — 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 (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) src/Internal/StronglyConnectedComponents.php:111— src/Internal/StronglyConnectedComponents.php:111-115 | src/Internal/TopologicalSort.php:97-103 — 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 (133–134 lines × 2) src/Tools/SchemaTool.php:308— src/Tools/SchemaTool.php:308-440 | src/Tools/SchemaTool.php:632-765 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/SchemaTool.php:308` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (76–78 lines × 2) src/Tools/SchemaTool.php:228— src/Tools/SchemaTool.php:228-303 | src/Tools/SchemaTool.php:546-623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/SchemaTool.php:228` 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 (43 lines × 2) src/Tools/SchemaTool.php:451— src/Tools/SchemaTool.php:451-493 | src/Tools/SchemaTool.php:785-827 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/SchemaTool.php:451` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) src/Tools/Pagination/CursorWalker.php:106— src/Tools/Pagination/CursorWalker.php:106-135 | src/Tools/Pagination/WhereInWalker.php:85-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/Pagination/CursorWalker.php:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27–28 lines × 2) src/Internal/Hydration/ArrayHydrator.php:190— src/Internal/Hydration/ArrayHydrator.php:190-217 | src/Internal/Hydration/ObjectHydrator.php:538-564 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Internal/Hydration/ArrayHydrator.php:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (28 lines × 2) src/Query/Parser.php:570— src/Query/Parser.php:570-597 | src/Query/Parser.php:688-715 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Query/Parser.php:570` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–26 lines × 2) src/Mapping/Driver/XmlDriver.php:328— src/Mapping/Driver/XmlDriver.php:328-353 | src/Mapping/Driver/XmlDriver.php:438-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:328` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (23 lines × 2) src/Mapping/ManyToManyOwningSideMapping.php:142— src/Mapping/ManyToManyOwningSideMapping.php:142-164 | src/Mapping/ManyToManyOwningSideMapping.php:181-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/ManyToManyOwningSideMapping.php:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) src/Query/SqlWalker.php:987— src/Query/SqlWalker.php:987-1008 | src/Query/SqlWalker.php:1042-1063 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Query/SqlWalker.php:987` 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 (21 lines × 2) src/Persisters/Entity/BasicEntityPersister.php:322— src/Persisters/Entity/BasicEntityPersister.php:322-342 | src/Persisters/Entity/JoinedSubclassPersister.php:551-571 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Persisters/Entity/BasicEntityPersister.php:322` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (17–18 lines × 2) src/Query/SqlWalker.php:644— src/Query/SqlWalker.php:644-661 | src/Query/SqlWalker.php:852-868 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/PersistentCollection.php:301— src/PersistentCollection.php:301-316 | src/PersistentCollection.php:323-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–17 lines × 2) src/Persisters/Collection/ManyToManyPersister.php:439— src/Persisters/Collection/ManyToManyPersister.php:439-453 | src/Persisters/Collection/ManyToManyPersister.php:486-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–14 lines × 2) src/Mapping/Driver/XmlDriver.php:198— src/Mapping/Driver/XmlDriver.php:198-208 | src/Mapping/Driver/XmlDriver.php:234-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–14 lines × 2) src/Mapping/Driver/XmlDriver.php:390— src/Mapping/Driver/XmlDriver.php:390-403 | src/Mapping/Driver/XmlDriver.php:487-499 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Mapping/Driver/XmlDriver.php:390` 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, `src/Mapping/Driver/XmlDriver.php:405` calls `isset`, `getCascadeMappings` and `src/Mapping/Driver/XmlDriver.php:501` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12–14 lines × 2) src/Query/Exec/MultiTableDeleteExecutor.php:88— src/Query/Exec/MultiTableDeleteExecutor.php:88-99 | src/Query/Exec/MultiTableUpdateExecutor.php:127-140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Query/Exec/MultiTableDeleteExecutor.php:88` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–13 lines × 2) src/Tools/Pagination/CountWalker.php:44— src/Tools/Pagination/CountWalker.php:44-56 | src/Tools/Pagination/WhereInWalker.php:54-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Tools/Pagination/CountWalker.php:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Tools/Pagination/CountWalker.php:40` calls `_getQuery`, `getHint` and `src/Tools/Pagination/WhereInWalker.php:52` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) src/Mapping/Driver/XmlDriver.php:521— src/Mapping/Driver/XmlDriver.php:521-531 | src/Mapping/Driver/XmlDriver.php:612-622 | src/Mapping/Driver/XmlDriver.php:883-893 — 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) src/Persisters/Entity/JoinedSubclassPersister.php:350— src/Persisters/Entity/JoinedSubclassPersister.php:350-357 | src/Persisters/Entity/JoinedSubclassPersister.php:584-591 | src/Persisters/Entity/JoinedSubclassPersister.php:598-605 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Persisters/Entity/JoinedSubclassPersister.php:350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 2) src/Query/AST/Functions/DateAddFunction.php:29— src/Query/AST/Functions/DateAddFunction.php:29-61 | src/Query/AST/Functions/DateSubFunction.php:22-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/Mapping/Driver/DatabaseDriver.php:602— src/Mapping/Driver/DatabaseDriver.php:602-606 | src/Tools/SchemaTool.php:1599-1603 — 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.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Swallowed exception (empty catch) src/Tools/SchemaTool.php:1414— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated predicate src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php:39— `$object instanceof InternalProxy && ! $object` appears character-identically in 2 files — src/Mapping/PropertyAccessors/ObjectCastPropertyAccessor.php, src/Mapping/PropertyAccessors/RawValuePropertyAccessor.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Persisters/Collection/ManyToManyPersister.php:256— `$operator === Comparison::IN || $operator === Comparison::NIN` appears character-identically in 2 files — src/Persisters/Collection/ManyToManyPersister.php, src/Persisters/Entity/BasicEntityPersister.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Internal/Hydration/AbstractHydrator.php:307— `$value !== null && isset($cacheKeyInfo['enumType'])` appears character-identically in 2 files — src/Internal/Hydration/AbstractHydrator.php, src/Internal/Hydration/SimpleObjectHydrator.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Persisters/Collection/ManyToManyPersister.php:254— `$value === null && ($operator === Comparison::EQ || $operator === Comparison::NEQ)` appears character-identically in 2 files — src/Persisters/Collection/ManyToManyPersister.php, src/Persisters/Entity/BasicEntityPersister.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Mapping/Driver/AttributeDriver.php:141— `isset($index['columns'], $index['fields']) || ( ! isset($index['columns']) && ! isset($index['fields']) )` appears character-identically in 2 files — src/Mapping/Driver/AttributeDriver.php, src/Mapping/Driver/XmlDriver.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Internal/Hydration/ObjectHydrator.php:533— `isset($this->hints[Query::HINT_INTERNAL_ITERATION]) && $this` appears character-identically in 2 files — src/Internal/Hydration/ObjectHydrator.php, src/Internal/Hydration/SimpleObjectHydrator.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.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (an Eloquent model's prunable() for model:prune, or a command that deletes rows past their retention — PruneOld… / PurgeExpired…).
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: src/Tools/Console/Command/GenerateProxiesCommand.php, src/Mapping/JoinTableMapping.php, src/Cache/Persister/CompatOrderings.php. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 5 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (9 single-owned of 126 analysed files in total, 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; 126 of the 472 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/Tools/Pagination/PaginatorQuery.php, src/Tools/Pagination/Cursor.php, src/Mapping/LegacyReflectionFields.php, src/Tools/Console/Command/Debug/DebugEntityListenersDoctrineCommand.php, src/Query/AST/Functions/IdentityFunction.php, src/Utility/IdentifierFlattener.php.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (48130 LoC, 467 module-visible types across 46 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D27 · Navigability· High interface indirection · ×1
High interface indirection — 38 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P1 · CI/CD gates· CI build step not evidenced · ×1
CI build step not evidenced — A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
P3 · Security & performance tooling· Dependabot does not watch composer · ×1
Dependabot does not watch composer REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `composer`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· PHP static analysis does not check null everywhere · ×1
PHP static analysis does not check null everywhere — 0/2 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
Skipped (documented): testCompositeCollectionMemberExpression tests/Tests/ORM/Functional/CompositePrimaryKeyTest.php:136— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testUsingTimeRelatedDefaultExpressionCausesAnOrmDeprecationAndNoDbalDeprecation tests/Tests/ORM/Functional/DefaultTimeExpressionTest.php:29— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testNoDeprecationsAreTrownWhenTheyCannotBeAddressed tests/Tests/ORM/Functional/DefaultTimeExpressionTest.php:58— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testUsingDefaultExpressionInstancesCausesNoDeprecation tests/Tests/ORM/Functional/DefaultTimeExpressionTest.php:94— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testUsingTimeRelatedDefaultExpressionCausesAnOrmDeprecationAndNoDbalDeprecation tests/Tests/ORM/Functional/DefaultTimeExpressionXmlTest.php:24— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testUsingDefaultExpressionInstancesCausesNoDeprecationXmlDriver tests/Tests/ORM/Functional/DefaultTimeExpressionXmlTest.php:57— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testEnumWithNonMatchingDatabaseValueThrowsException tests/Tests/ORM/Functional/EnumTest.php:431— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testLockPessimisticWrite tests/Tests/ORM/Functional/Locking/LockTest.php:228— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testRefreshWithLockPessimisticWrite tests/Tests/ORM/Functional/Locking/LockTest.php:259— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testLockPessimisticRead tests/Tests/ORM/Functional/Locking/LockTest.php:290— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testPartialObjectProxyLoadedChangeset tests/Tests/ORM/Functional/PartialObjectsTest.php:23— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testPartialObjectLazyInitDoesNotOverwriteChangedProperty tests/Tests/ORM/Functional/PartialObjectsTest.php:74— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testFindWithProxyName tests/Tests/ORM/Functional/ProxiesLikeEntitiesTest.php:110— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testJoinPartialObjectHydration tests/Tests/ORM/Functional/QueryTest.php:112— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testCommonPersistenceProxy tests/Tests/ORM/Functional/ReferenceProxyTest.php:242— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testGetCreateSchemaSql4 tests/Tests/ORM/Functional/SchemaTool/MySqlSchemaToolTest.php:198— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testPersistLazyGhost tests/Tests/ORM/Functional/StandardEntityPersisterTest.php:116— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testGetEntityState tests/Tests/ORM/Functional/Ticket/DDC117Test.php:421— Skipped with a documented reason — a deferral, not lazy debt: reported incomplete at run time by markTestIncomplete()
Skipped (documented): testColumnAliasUsesPlatformIdentifierFolding tests/Tests/ORM/Functional/Ticket/DDC12272Test.php:20— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testColumnAliasUsesIdentifierFoldingForEveryPlatform tests/Tests/ORM/Functional/Ticket/DDC12272Test.php:40— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testColumnAliasUsesLegacyFoldingWithoutIdentifierFoldingApi tests/Tests/ORM/Functional/Ticket/DDC12272Test.php:56— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testColumnAliasUsesLegacyPostgreSQLFoldingWithoutIdentifierFoldingApi tests/Tests/ORM/Functional/Ticket/DDC12272Test.php:71— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testIssue tests/Tests/ORM/Functional/Ticket/DDC1695Test.php:20— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testPassColumnOptionsToJoinColumns tests/Tests/ORM/Functional/Ticket/DDC2182Test.php:18— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
Skipped (documented): testLockCTIClass tests/Tests/ORM/Functional/Ticket/DDC933Test.php:30— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by markTestSkipped()
+ 28 more in this group — see findings.md.
D10 · Test Quality· No assertions (declared) · ×23
No assertions (declared): testBulkUpdateNonScalarParameterDDC1341 tests/Tests/ORM/Functional/ClassTableInheritanceTest.php:329— 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): testSelfReferenceWithApplicationGeneratedIdMayBeNotNullable tests/Tests/ORM/Functional/GH7877Test.php:24— 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): testCrossReferenceWithApplicationGeneratedIdMayBeNotNullable tests/Tests/ORM/Functional/GH7877Test.php:35— 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): testNullableForeignKeysMakeInsertOrderLessRelevant tests/Tests/ORM/Functional/GH7877Test.php:54— 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): testLockVersionedEntity tests/Tests/ORM/Functional/Locking/LockTest.php:37— 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): testLockWorksWithProxy tests/Tests/ORM/Functional/Locking/OptimisticTest.php:186— 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): testIssue tests/Tests/ORM/Functional/Ticket/DDC588Test.php:24— 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): testInheritedReadOnlyPropertyValueCanBeSet tests/Tests/ORM/Functional/Ticket/GH10049/GH10049Test.php:23— 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): testDeletes tests/Tests/ORM/Functional/Ticket/GH10531Test.php:69— 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): testDeletes tests/Tests/ORM/Functional/Ticket/GH10532Test.php:70— 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): testInitializeObjectNoOpForNonManagedObjects tests/Tests/ORM/Functional/Ticket/GH12172Test.php:25— 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): testInitializeObjectNoOpForCustomNonEntityClass tests/Tests/ORM/Functional/Ticket/GH12172Test.php:34— 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): testInitializeObjectWithValidEntityClassDoesNotBreakMetadataLoading tests/Tests/ORM/Functional/Ticket/GH12172Test.php:52— 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): testInitializeObjectNoOpForNonManagedObjectsWithMappingDriverChain tests/Tests/ORM/Functional/Ticket/GH12172Test.php:82— 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): testToManyAssociationOnBaseClassAllowedWhenThereAreMappedSuperclassesAsChildren tests/Tests/ORM/Functional/Ticket/GH8415ToManyAssociationTest.php:13— 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): testDiscriminatorMapWithSeveralLevelsIsSupported tests/Tests/ORM/Functional/Ticket/GH8914Test.php:23— 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): testIssue tests/Tests/ORM/Functional/Ticket/GH9192Test.php:21— 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): testCanRemoveEntityWithReadonlyId tests/Tests/ORM/Functional/Ticket/GH9538Test.php:24— 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): testDisablingXmlValidationIsPossible tests/Tests/ORM/Mapping/XmlMappingDriverTest.php:329— 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): testDisablingXmlValidationIsPossible tests/Tests/ORM/ORMSetupTest.php:67— 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): testMatch tests/Tests/ORM/Query/ParserTest.php:47— 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): testItPrintsTheSql tests/Tests/ORM/Tools/Console/Command/SchemaTool/CreateCommandTest.php:13— 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): testItPrintsTheSql tests/Tests/ORM/Tools/Console/Command/SchemaTool/DropCommandTest.php:14— 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 114 file(s) — `src/Cache/AssociationCacheEntry.php`, `src/Cache/CacheKey.php`, `src/Cache/CollectionCacheEntry.php`, `src/Cache/CollectionCacheKey.php`, `src/Cache/DefaultCache.php`, … (+109 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 01a1d6da-5dfb-7925-9f7e-a3419a3ff540 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 38 · Warnings: 384 · Recommendations: 19 · Info: 76 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 13-11-2026 @ 21:39 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.