Public report of rectorphp/rector, published 14 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, 14 November 2026, 00:28 UTC · Survey ID cd_d91e910b28744ec394a4d3490ffdae90
rectorphp/rector
Measured 14 November 2026, 00:25 UTC, at code version 0350e33
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 110,871 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 39
Findings by how serious they are
77 critical408 serious48 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
14 November 2026, 00:25 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 ▸
36of 36 dimensions measured by tools.
524of 533 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
36dimensions across 5 lenses, read from 110,871 lines of product code in 1 project.
rectorphp/rector falls short of our standard for production because we found no logging, tracing or health checks in the code. It scores 52 out of 100 and is rated Adequate, and 72 of its 77 critical findings are security problems.
Production Readiness, at 39, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 10 points. Recording design decisions comes next, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 64.
Fifty-seven passwords or keys are open to anyone who can read the repository. Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and five sets of files in separate parts keep changing together, which points to hidden dependencies. Replacing each exposed password or key, pinning each tool to an exact version and making the hidden dependencies explicit would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access, and limiting each secret to its own step would deal with the secret exposed to more of the pipeline than needed.
The product code is 110,871 lines, about €110,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 39 to 70, the lowest score rated Strong, the score would rise from 52 to about 64.
Code composition: what the lines of code are
Product code 100%Tests 0%
New since the last survey: 115 findings
These 115 critical or serious findings weren't in the previous survey, on 25 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Edited copy of a member (49 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php
Code Duplication · Edited copy of a member (42 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php
Code Duplication · Edited copy of a member (27 corresponding lines) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php
Code Duplication · Edited copy of a member (41 corresponding lines) rules/DeadCode/Rector/MethodCall/RemoveNullArgOnNullDefaultParamRector.php
Code Duplication · Edited copy of a member (35 corresponding lines) rules/Php81/Rector/Property/ReadOnlyPropertyRector.php
Code Duplication · Edited copy of a member (36 corresponding lines) rules/TypeDeclarationDocblocks/Rector/ClassMethod/DocblockGetterReturnArrayFromPropertyDocblockVarRector.php
Code Duplication · Edited copy of a member (28 corresponding lines) rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php
Code Duplication · Edited copy of a member (20 corresponding lines) rules/Php80/Rector/NotIdentical/MbStrContainsRector.php
Code Duplication · Edited copy of a member (23 corresponding lines) rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php
Code Duplication · Edited copy of a member (22 corresponding lines) src/PhpParser/AstResolver.php
Code Duplication · Edited copy of a member (24 corresponding lines) rules/CodeQuality/Rector/FuncCall/SimplifyInArrayValuesRector.php
Code Duplication · Edited copy of a member (22 corresponding lines) rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php
Code Duplication · Edited copy of a member (24 corresponding lines) rules/DeadCode/Rector/BinaryOp/RemoveRedundantTypeCheckRector.php
Code Duplication · Edited copy of a member (7 corresponding lines) src/ChangesReporting/Output/GitlabOutputFormatter.php
Code Duplication · Edited copy of a member (13 corresponding lines) rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php
Code Duplication · Edited copy of a member (15 corresponding lines) rules/Php81/NodeFactory/EnumFactory.php
Code Duplication · Edited copy of a member (23 corresponding lines) src/BetterPhpDocParser/PhpDocManipulator/PhpDocTypeChanger.php
Code Duplication · Edited copy of a member (21 corresponding lines) rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php
Code Duplication · Edited copy of a member (19 corresponding lines) rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php
Code Duplication · Edited copy of a member (22 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeDeclarationRector.php
Code Duplication · Edited copy of a member (20 corresponding lines) rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromCast.php
Code Duplication · Edited copy of a member (19 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php
Code Duplication · Edited copy of a member (21 corresponding lines) src/BetterPhpDocParser/PhpDocManipulator/PhpDocClassRenamer.php
Code Duplication · Edited copy of a member (21 corresponding lines) src/NodeManipulator/ClassMethodPropertyFetchManipulator.php
Code Duplication · Edited copy of a member (21 corresponding lines) rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php
Code Duplication · Edited copy of a member (21 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictConstantReturnRector.php
Code Duplication · Edited copy of a member (24 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveTestsOverriddenPrivateMethodParameterRector.php
Code Duplication · Edited copy of a member (25 corresponding lines) rules/TypeDeclaration/Rector/ClassLike/AddVoidReturnTypeWhereNoReturnRector.php
Code Duplication · Edited copy of a member (21 corresponding lines) rules/CodingStyle/Rector/FuncCall/CallUserFuncToMethodCallRector.php
Code Duplication · Edited copy of a member (18 corresponding lines) rules/TypeDeclaration/Rector/Class_/PropertyTypeFromStrictSetterGetterRector.php
Code Duplication · Edited copy of a member (19 corresponding lines) rules/Php72/Rector/FuncCall/StringsAssertNakedRector.php
Code Duplication · Edited copy of a member (19 corresponding lines) rules/CodeQuality/Rector/New_/NewStaticToNewSelfRector.php
Code Duplication · Edited copy of a member (23 corresponding lines) rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php
Code Duplication · Edited copy of a member (20 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php
Code Duplication · Edited copy of a member (16 corresponding lines) rules/CodeQuality/Rector/FuncCall/IsAWithStringWithThirdArgumentRector.php
Code Duplication · Edited copies of one member (3 members, 22+ corresponding lines) rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php
Code Duplication · Edited copy of a member (15 corresponding lines) rules/Php74/Rector/FuncCall/ArrayKeyExistsOnPropertyRector.php
Code Duplication · Edited copy of a member (15 corresponding lines) rules/Php80/NodeAnalyzer/PromotedPropertyCandidateResolver.php
Code Duplication · Edited copy of a member (11 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php
Code Duplication · Edited copy of a member (15 corresponding lines) rules/TypeDeclaration/TypeInferer/PropertyTypeInferer/GetterTypeDeclarationPropertyTypeInferer.php
Code Duplication · Edited copy of a member (11 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php
Code Duplication · Edited copies of one member (5 members, 16+ corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php
Code Duplication · Edited copy of a member (8 corresponding lines) src/Reporting/MissConfigurationReporter.php
Code Duplication · Edited copy of a member (10 corresponding lines) rules/Php70/Rector/Ternary/TernaryToSpaceshipRector.php
Code Duplication · Edited copy of a member (14 corresponding lines) rules/Php81/Rector/FuncCall/NullToStrictIntPregSlitFuncCallLimitArgRector.php
Code Duplication · Edited copy of a member (13 corresponding lines) src/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php
Code Duplication · Edited copy of a member (18 corresponding lines) src/VendorLocker/NodeVendorLocker/ClassMethodParamVendorLockResolver.php
Code Duplication · Edited copy of a member (13 corresponding lines) rules/DeadCode/Rector/If_/ReduceAlwaysFalseIfOrRector.php
Code Duplication · Edited copy of a member (12 corresponding lines) rules/Php80/Rector/Class_/ClassPropertyAssignToConstructorPromotionRector.php
Code Duplication · Edited copy of a member (17 corresponding lines) src/NodeAnalyzer/CallLikeArgumentNameAdder.php
Code Duplication · Edited copy of a member (16 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/CallTypesResolver.php
Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) rules/Removing/Rector/ClassMethod/ArgumentRemoverRector.php
Code Duplication · Edited copy of a member (11 corresponding lines) rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php
Code Duplication · Edited copy of a member (14 corresponding lines) rules/CodingStyle/Rector/Assign/SplitDoubleAssignRector.php
Code Duplication · Edited copy of a member (10 corresponding lines) rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php
Code Duplication · Edited copy of a member (10 corresponding lines) src/PhpParser/AstResolver.php
Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) rules/CodeQuality/Rector/Switch_/SingularSwitchToIfRector.php
Code Duplication · Edited copy of a member (7 corresponding lines) rules/TypeDeclarationDocblocks/NodeFinder/ArrayDimFetchFinder.php
Code Duplication · Edited copy of a member (10 corresponding lines) src/StaticTypeMapper/PhpDocParser/IdentifierPhpDocTypeMapper.php
Code Duplication · Edited copy of a member (10 corresponding lines) src/PhpParser/NodeVisitor/ByRefNodeVisitor.php
Code Duplication · Edited copy of a member (14 corresponding lines) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php
Code Duplication · Edited copy of a member (13 corresponding lines) src/BetterPhpDocParser/ValueObject/PhpDoc/DoctrineAnnotation/AbstractValuesAwareNode.php
Code Duplication · Edited copy of a member (10 corresponding lines) src/Reporting/DeprecatedRulesReporter.php
Code Duplication · Edited copy of a member (10 corresponding lines) rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php
Code Duplication · Edited copy of a member (12 corresponding lines) rules/CodeQuality/Rector/Class_/InlineConstructorDefaultToPropertyRector.php
Code Duplication · Edited copy of a member (8 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/StrictReturnNewArrayResolver.php
Code Duplication · Edited copy of a member (13 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php
Code Duplication · Edited copy of a member (11 corresponding lines) src/NodeManipulator/IfManipulator.php
Code Duplication · Edited copy of a member (12 corresponding lines) rules/Php80/NodeAnalyzer/PromotedPropertyResolver.php
Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveMixedDocblockOverruledByNativeTypeRector.php
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php
Code Duplication · Edited copy of a member (9 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveUselessReturnTagRector.php
Code Duplication · Edited copy of a member (8 corresponding lines) rules/CodeQuality/Rector/Catch_/ThrowWithPreviousExceptionRector.php
Code Duplication · Edited copy of a member (8 corresponding lines) rules/DeadCode/Rector/Expression/SimplifyMirrorAssignRector.php
Code Duplication · Edited copy of a member (7 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php
Code Duplication · Edited copy of a member (11 corresponding lines) src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php
Code Duplication · Edited copy of a member (7 corresponding lines) rules/DeadCode/PhpDoc/DeadParamTagValueNodeAnalyzer.php
Code Duplication · Edited copy of a member (9 corresponding lines) rules/Php83/Rector/ClassConst/AddTypeToConstRector.php
Code Duplication · Edited copy of a member (6 corresponding lines) rules/Renaming/ValueObject/MethodCallRename.php
Code Duplication · Edited copy of a member (8 corresponding lines) rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php
Code Duplication · Edited copy of a member (7 corresponding lines) rules/CodeQuality/Rector/Foreach_/ForeachToInArrayRector.php
Code Duplication · Edited copy of a member (5 corresponding lines) src/StaticTypeMapper/ValueObject/Type/AliasedObjectType.php
Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) rules/Arguments/ValueObject/ArgumentAdder.php
Code Duplication · Edited copy of a member (1 corresponding lines) rules/Php80/Rector/Class_/AnnotationToAttributeRector.php
Code Duplication · Edited copy of a member (6 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php
Code Duplication · Edited copy of a member (3 corresponding lines) src/PhpAttribute/NodeFactory/PhpAttributeGroupFactory.php
Code Duplication · Edited copy of a member (5 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php
Code Duplication · Edited copy of a member (4 corresponding lines) rules/Php81/Rector/Class_/MyCLabsClassToEnumRector.php
Code Duplication · Edited copy of a member (5 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 31 findings
These 31 critical or serious findings were in the previous survey, on 25 October 2026, and are gone from this one.
€36,000 to €180,000, for 592 to 1,878 hours of work, about 0.7 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 110,871 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
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 10 points · Medium effort · Observability
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json.
Raises the score by about 3 points · Low effort · ADR Quality
3
Resolve the 55 High secret finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (10), REDACTED (6).
Raises the score by about 3 points · Medium effort · Secrets (history)
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 39 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Of all the actions in this report, it raises the score most for the work it takes: about 10 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
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.
527 modules, with 1796 dependencies between them. 6 loops run through 56 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 487 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.
NodeNameResolver uses NodeAnalyzer, so a change to NodeAnalyzer can break NodeNameResolver, while a change to NodeNameResolver can't break NodeAnalyzer.
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.
BetterPhpDocParser.PhpDocInfo uses StaticTypeMapper, so a change to StaticTypeMapper can break BetterPhpDocParser.PhpDocInfo, while a change to BetterPhpDocParser.PhpDocInfo can't break StaticTypeMapper.
Position
Below the diagonal: BetterPhpDocParser.PhpDocInfo uses a module listed above it, which is the healthy direction.
NodeTypeResolver uses NodeNameResolver, so a change to NodeNameResolver can break NodeTypeResolver, while a change to NodeTypeResolver can't break NodeNameResolver.
Position
Below the diagonal: NodeTypeResolver uses a module listed above it, which is the healthy direction.
13→30 NodeTypeResolver uses NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in NodeTypeResolver uses a type in NodeAnalyzer.
NodeTypeResolver uses NodeAnalyzer, so a change to NodeAnalyzer can break NodeTypeResolver, while a change to NodeTypeResolver can't break NodeAnalyzer.
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.
Privatization.NodeManipulator uses NodeNameResolver, so a change to NodeNameResolver can break Privatization.NodeManipulator, while a change to Privatization.NodeManipulator can't break NodeNameResolver.
Position
Below the diagonal: Privatization.NodeManipulator uses a module listed above it, which is the healthy direction.
Comments.NodeDocBlock uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break Comments.NodeDocBlock, while a change to Comments.NodeDocBlock can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: Comments.NodeDocBlock uses a module listed above it, which is the healthy direction.
PhpParser.Node uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break PhpParser.Node, while a change to PhpParser.Node can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: PhpParser.Node uses a module listed above it, which is the healthy direction.
PhpParser.Node uses NodeNameResolver, so a change to NodeNameResolver can break PhpParser.Node, while a change to PhpParser.Node can't break NodeNameResolver.
Position
Below the diagonal: PhpParser.Node uses a module listed above it, which is the healthy direction.
PhpParser.Node uses StaticTypeMapper, so a change to StaticTypeMapper can break PhpParser.Node, while a change to PhpParser.Node can't break StaticTypeMapper.
Position
Below the diagonal: PhpParser.Node uses a module listed above it, which is the healthy direction.
PhpParser.Node uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break PhpParser.Node, while a change to PhpParser.Node can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: PhpParser.Node uses a module listed above it, which is the healthy direction.
BetterPhpDocParser.PhpDocManipulator uses StaticTypeMapper, so a change to StaticTypeMapper can break BetterPhpDocParser.PhpDocManipulator, while a change to BetterPhpDocParser.PhpDocManipulator can't break StaticTypeMapper.
Position
Below the diagonal: BetterPhpDocParser.PhpDocManipulator uses a module listed above it, which is the healthy direction.
BetterPhpDocParser.PhpDocManipulator uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break BetterPhpDocParser.PhpDocManipulator, while a change to BetterPhpDocParser.PhpDocManipulator can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: BetterPhpDocParser.PhpDocManipulator uses a module listed above it, which is the healthy direction.
BetterPhpDocParser.PhpDocManipulator uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break BetterPhpDocParser.PhpDocManipulator, while a change to BetterPhpDocParser.PhpDocManipulator can't break Comments.NodeDocBlock.
Position
Below the diagonal: BetterPhpDocParser.PhpDocManipulator uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses NodeTypeResolver.PHPStan.Type, so a change to NodeTypeResolver.PHPStan.Type can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break NodeTypeResolver.PHPStan.Type.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses PhpParser.Comparing, so a change to PhpParser.Comparing can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break PhpParser.Comparing.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses NodeNameResolver, so a change to NodeNameResolver can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break NodeNameResolver.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses NodeTypeResolver, so a change to NodeTypeResolver can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break NodeTypeResolver.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
Php80.NodeAnalyzer uses PhpParser.Node, so a change to PhpParser.Node can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break PhpParser.Node.
Position
Below the diagonal: Php80.NodeAnalyzer uses a module listed above it, which is the healthy direction.
19→30 Php80.NodeAnalyzer uses NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in Php80.NodeAnalyzer uses a type in NodeAnalyzer.
Php80.NodeAnalyzer uses NodeAnalyzer, so a change to NodeAnalyzer can break Php80.NodeAnalyzer, while a change to Php80.NodeAnalyzer can't break NodeAnalyzer.
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.
PhpParser.Node.Value uses NodeNameResolver, so a change to NodeNameResolver can break PhpParser.Node.Value, while a change to PhpParser.Node.Value can't break NodeNameResolver.
Position
Below the diagonal: PhpParser.Node.Value uses a module listed above it, which is the healthy direction.
PhpParser.Node.Value uses NodeTypeResolver, so a change to NodeTypeResolver can break PhpParser.Node.Value, while a change to PhpParser.Node.Value can't break NodeTypeResolver.
Position
Below the diagonal: PhpParser.Node.Value uses a module listed above it, which is the healthy direction.
PhpParser.Node.Value uses Reflection, so a change to Reflection can break PhpParser.Node.Value, while a change to PhpParser.Node.Value can't break Reflection.
Position
Below the diagonal: PhpParser.Node.Value uses a module listed above it, which is the healthy direction.
21→30 PhpParser.Node.Value uses NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in PhpParser.Node.Value uses a type in NodeAnalyzer.
PhpParser.Node.Value uses NodeAnalyzer, so a change to NodeAnalyzer can break PhpParser.Node.Value, while a change to PhpParser.Node.Value can't break NodeAnalyzer.
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.
ValueObject.Application uses PhpParser.Node, so a change to PhpParser.Node can break ValueObject.Application, while a change to ValueObject.Application can't break PhpParser.Node.
Position
Below the diagonal: ValueObject.Application uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses NodeNameResolver, so a change to NodeNameResolver can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break NodeNameResolver.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses NodeTypeResolver, so a change to NodeTypeResolver can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break NodeTypeResolver.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses PhpParser.Node, so a change to PhpParser.Node can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break PhpParser.Node.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses Reflection, so a change to Reflection can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break Reflection.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses PhpParser, so a change to PhpParser can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break PhpParser.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
DeadCode.NodeAnalyzer uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break PhpParser.Node.Value.
Position
Below the diagonal: DeadCode.NodeAnalyzer uses a module listed above it, which is the healthy direction.
23→30 DeadCode.NodeAnalyzer uses NodeAnalyzerpart of a loop✕
Connections
3 pairs of types, where a type in DeadCode.NodeAnalyzer uses a type in NodeAnalyzer.
DeadCode.NodeAnalyzer uses NodeAnalyzer, so a change to NodeAnalyzer can break DeadCode.NodeAnalyzer, while a change to DeadCode.NodeAnalyzer can't break NodeAnalyzer.
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.
DeadCode.PhpDoc.TagRemover uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break DeadCode.PhpDoc.TagRemover, while a change to DeadCode.PhpDoc.TagRemover can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: DeadCode.PhpDoc.TagRemover uses a module listed above it, which is the healthy direction.
DeadCode.PhpDoc.TagRemover uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break DeadCode.PhpDoc.TagRemover, while a change to DeadCode.PhpDoc.TagRemover can't break Comments.NodeDocBlock.
Position
Below the diagonal: DeadCode.PhpDoc.TagRemover uses a module listed above it, which is the healthy direction.
DeadCode.PhpDoc.TagRemover uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break DeadCode.PhpDoc.TagRemover, while a change to DeadCode.PhpDoc.TagRemover can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: DeadCode.PhpDoc.TagRemover uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses NodeNameResolver, so a change to NodeNameResolver can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break NodeNameResolver.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses NodeTypeResolver, so a change to NodeTypeResolver can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break NodeTypeResolver.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses PhpParser.Node, so a change to PhpParser.Node can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break PhpParser.Node.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses Reflection, so a change to Reflection can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break Reflection.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
PhpParser.NodeFinder uses PhpParser, so a change to PhpParser can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break PhpParser.
Position
Below the diagonal: PhpParser.NodeFinder uses a module listed above it, which is the healthy direction.
25→30 PhpParser.NodeFinder uses NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in PhpParser.NodeFinder uses a type in NodeAnalyzer.
PhpParser.NodeFinder uses NodeAnalyzer, so a change to NodeAnalyzer can break PhpParser.NodeFinder, while a change to PhpParser.NodeFinder can't break NodeAnalyzer.
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.
TypeDeclaration.TypeInferer uses NodeTypeResolver.PHPStan.Type, so a change to NodeTypeResolver.PHPStan.Type can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break NodeTypeResolver.PHPStan.Type.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses NodeTypeResolver, so a change to NodeTypeResolver can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break NodeTypeResolver.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses PhpParser.Node, so a change to PhpParser.Node can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break PhpParser.Node.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses Reflection, so a change to Reflection can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break Reflection.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break Php80.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break PhpParser.Node.Value.
Position
Below the diagonal: TypeDeclaration.TypeInferer uses a module listed above it, which is the healthy direction.
26→27 TypeDeclaration.TypeInferer uses TypeDeclaration.NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in TypeDeclaration.TypeInferer uses a type in TypeDeclaration.NodeAnalyzer.
TypeDeclaration.TypeInferer uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break TypeDeclaration.NodeAnalyzer.
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→28 TypeDeclaration.TypeInferer uses TypeDeclaration.AlreadyAssignDetectorpart of a loop✕
Connections
3 pairs of types, where a type in TypeDeclaration.TypeInferer uses a type in TypeDeclaration.AlreadyAssignDetector.
TypeDeclaration.TypeInferer uses TypeDeclaration.AlreadyAssignDetector, so a change to TypeDeclaration.AlreadyAssignDetector can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break TypeDeclaration.AlreadyAssignDetector.
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→30 TypeDeclaration.TypeInferer uses NodeAnalyzerpart of a loop✕
Connections
2 pairs of types, where a type in TypeDeclaration.TypeInferer uses a type in NodeAnalyzer.
TypeDeclaration.TypeInferer uses NodeAnalyzer, so a change to NodeAnalyzer can break TypeDeclaration.TypeInferer, while a change to TypeDeclaration.TypeInferer can't break NodeAnalyzer.
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.
TypeDeclaration.NodeAnalyzer uses NodeTypeResolver.PHPStan.Type, so a change to NodeTypeResolver.PHPStan.Type can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break NodeTypeResolver.PHPStan.Type.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses PhpParser.Comparing, so a change to PhpParser.Comparing can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break PhpParser.Comparing.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses NodeNameResolver, so a change to NodeNameResolver can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break NodeNameResolver.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses StaticTypeMapper, so a change to StaticTypeMapper can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break StaticTypeMapper.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses NodeTypeResolver, so a change to NodeTypeResolver can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break NodeTypeResolver.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break Comments.NodeDocBlock.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses PhpParser.Node, so a change to PhpParser.Node can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break PhpParser.Node.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses Reflection, so a change to Reflection can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break Reflection.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break Php80.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break PhpParser.Node.Value.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.NodeAnalyzer uses TypeDeclaration.TypeInferer, so a change to TypeDeclaration.TypeInferer can break TypeDeclaration.NodeAnalyzer, while a change to TypeDeclaration.NodeAnalyzer can't break TypeDeclaration.TypeInferer.
Position
Below the diagonal: TypeDeclaration.NodeAnalyzer uses a module listed above it, which is the healthy direction.
TypeDeclaration.AlreadyAssignDetector uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break TypeDeclaration.AlreadyAssignDetector, while a change to TypeDeclaration.AlreadyAssignDetector can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: TypeDeclaration.AlreadyAssignDetector uses a module listed above it, which is the healthy direction.
TypeDeclaration.AlreadyAssignDetector uses PhpParser.Comparing, so a change to PhpParser.Comparing can break TypeDeclaration.AlreadyAssignDetector, while a change to TypeDeclaration.AlreadyAssignDetector can't break PhpParser.Comparing.
Position
Below the diagonal: TypeDeclaration.AlreadyAssignDetector uses a module listed above it, which is the healthy direction.
TypeDeclaration.AlreadyAssignDetector uses NodeTypeResolver, so a change to NodeTypeResolver can break TypeDeclaration.AlreadyAssignDetector, while a change to TypeDeclaration.AlreadyAssignDetector can't break NodeTypeResolver.
Position
Below the diagonal: TypeDeclaration.AlreadyAssignDetector uses a module listed above it, which is the healthy direction.
TypeDeclaration.AlreadyAssignDetector uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break TypeDeclaration.AlreadyAssignDetector, while a change to TypeDeclaration.AlreadyAssignDetector can't break TypeDeclaration.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.AlreadyAssignDetector uses a module listed above it, which is the healthy direction.
28→30 TypeDeclaration.AlreadyAssignDetector uses NodeAnalyzerpart of a loop✕
Connections
1 pair of types, where a type in TypeDeclaration.AlreadyAssignDetector uses a type in NodeAnalyzer.
TypeDeclaration.AlreadyAssignDetector uses NodeAnalyzer, so a change to NodeAnalyzer can break TypeDeclaration.AlreadyAssignDetector, while a change to TypeDeclaration.AlreadyAssignDetector can't break NodeAnalyzer.
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.
NodeManipulator uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break NodeManipulator, while a change to NodeManipulator can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses PhpParser.Comparing, so a change to PhpParser.Comparing can break NodeManipulator, while a change to NodeManipulator can't break PhpParser.Comparing.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses NodeNameResolver, so a change to NodeNameResolver can break NodeManipulator, while a change to NodeManipulator can't break NodeNameResolver.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break NodeManipulator, while a change to NodeManipulator can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses NodeTypeResolver, so a change to NodeTypeResolver can break NodeManipulator, while a change to NodeManipulator can't break NodeTypeResolver.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses PhpParser.Node, so a change to PhpParser.Node can break NodeManipulator, while a change to NodeManipulator can't break PhpParser.Node.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break NodeManipulator, while a change to NodeManipulator can't break Php80.NodeAnalyzer.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break NodeManipulator, while a change to NodeManipulator can't break PhpParser.Node.Value.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses DeadCode.NodeAnalyzer, so a change to DeadCode.NodeAnalyzer can break NodeManipulator, while a change to NodeManipulator can't break DeadCode.NodeAnalyzer.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses PhpParser.NodeFinder, so a change to PhpParser.NodeFinder can break NodeManipulator, while a change to NodeManipulator can't break PhpParser.NodeFinder.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break NodeManipulator, while a change to NodeManipulator can't break TypeDeclaration.NodeAnalyzer.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
NodeManipulator uses TypeDeclaration.AlreadyAssignDetector, so a change to TypeDeclaration.AlreadyAssignDetector can break NodeManipulator, while a change to NodeManipulator can't break TypeDeclaration.AlreadyAssignDetector.
Position
Below the diagonal: NodeManipulator uses a module listed above it, which is the healthy direction.
29→30 NodeManipulator uses NodeAnalyzerpart of a loop✕
Connections
4 pairs of types, where a type in NodeManipulator uses a type in NodeAnalyzer.
NodeAnalyzer uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break NodeAnalyzer, while a change to NodeAnalyzer can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
NodeAnalyzer uses PhpParser.Comparing, so a change to PhpParser.Comparing can break NodeAnalyzer, while a change to NodeAnalyzer can't break PhpParser.Comparing.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
NodeAnalyzer uses NodeNameResolver, so a change to NodeNameResolver can break NodeAnalyzer, while a change to NodeAnalyzer can't break NodeNameResolver.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
NodeAnalyzer uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break NodeAnalyzer, while a change to NodeAnalyzer can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
NodeAnalyzer uses NodeTypeResolver, so a change to NodeTypeResolver can break NodeAnalyzer, while a change to NodeAnalyzer can't break NodeTypeResolver.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
NodeAnalyzer uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break NodeAnalyzer, while a change to NodeAnalyzer can't break Php80.NodeAnalyzer.
Position
Below the diagonal: NodeAnalyzer uses a module listed above it, which is the healthy direction.
Application uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break Application, while a change to Application can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: Application uses a module listed above it, which is the healthy direction.
Application uses ValueObject.Application, so a change to ValueObject.Application can break Application, while a change to Application can't break ValueObject.Application.
Position
Below the diagonal: Application uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses NodeTypeResolver.PHPStan.Type, so a change to NodeTypeResolver.PHPStan.Type can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break NodeTypeResolver.PHPStan.Type.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses NodeNameResolver, so a change to NodeNameResolver can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break NodeNameResolver.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses StaticTypeMapper, so a change to StaticTypeMapper can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break StaticTypeMapper.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses NodeTypeResolver, so a change to NodeTypeResolver can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break NodeTypeResolver.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses PhpParser.Node, so a change to PhpParser.Node can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break PhpParser.Node.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses PhpParser, so a change to PhpParser can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break PhpParser.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses ValueObject.Application, so a change to ValueObject.Application can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break ValueObject.Application.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses TypeDeclaration.TypeInferer, so a change to TypeDeclaration.TypeInferer can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break TypeDeclaration.TypeInferer.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break TypeDeclaration.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses NodeManipulator, so a change to NodeManipulator can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break NodeManipulator.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
TypeDeclaration.TypeInferer.PropertyTypeInferer uses NodeAnalyzer, so a change to NodeAnalyzer can break TypeDeclaration.TypeInferer.PropertyTypeInferer, while a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can't break NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.TypeInferer.PropertyTypeInferer uses a module listed above it, which is the healthy direction.
Rector uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break Rector, while a change to Rector can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: Rector uses a module listed above it, which is the healthy direction.
Rector uses ValueObject.Application, so a change to ValueObject.Application can break Rector, while a change to Rector can't break ValueObject.Application.
Position
Below the diagonal: Rector uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses Configuration.Deprecation.Contract, so a change to Configuration.Deprecation.Contract can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break Configuration.Deprecation.Contract.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses RuleDoc, so a change to RuleDoc can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break RuleDoc.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses VersionBonding.Contract, so a change to VersionBonding.Contract can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break VersionBonding.Contract.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses PhpParser.Node, so a change to PhpParser.Node can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break PhpParser.Node.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break PhpParser.Node.Value.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses DeadCode.PhpDoc.TagRemover, so a change to DeadCode.PhpDoc.TagRemover can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break DeadCode.PhpDoc.TagRemover.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses NodeManipulator, so a change to NodeManipulator can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break NodeManipulator.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
CodeQuality.Rector.If_ uses Rector, so a change to Rector can break CodeQuality.Rector.If_, while a change to CodeQuality.Rector.If_ can't break Rector.
Position
Below the diagonal: CodeQuality.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Configuration.Deprecation.Contract, so a change to Configuration.Deprecation.Contract can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Configuration.Deprecation.Contract.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses RuleDoc, so a change to RuleDoc can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break RuleDoc.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses VersionBonding.Contract, so a change to VersionBonding.Contract can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break VersionBonding.Contract.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses StaticTypeMapper, so a change to StaticTypeMapper can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break StaticTypeMapper.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Privatization.NodeManipulator, so a change to Privatization.NodeManipulator can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Privatization.NodeManipulator.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Comments.NodeDocBlock.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses PhpParser.Node, so a change to PhpParser.Node can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break PhpParser.Node.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Reflection, so a change to Reflection can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Reflection.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Php80.NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break PhpParser.Node.Value.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses DeadCode.NodeAnalyzer, so a change to DeadCode.NodeAnalyzer can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break DeadCode.NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses DeadCode.PhpDoc.TagRemover, so a change to DeadCode.PhpDoc.TagRemover can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break DeadCode.PhpDoc.TagRemover.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses PhpParser.NodeFinder, so a change to PhpParser.NodeFinder can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break PhpParser.NodeFinder.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses NodeManipulator, so a change to NodeManipulator can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break NodeManipulator.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses NodeAnalyzer, so a change to NodeAnalyzer can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.ClassMethod uses Rector, so a change to Rector can break DeadCode.Rector.ClassMethod, while a change to DeadCode.Rector.ClassMethod can't break Rector.
Position
Below the diagonal: DeadCode.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses PhpParser.Node, so a change to PhpParser.Node can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break PhpParser.Node.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses Reflection, so a change to Reflection can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break Reflection.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break Php80.NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses DeadCode.NodeAnalyzer, so a change to DeadCode.NodeAnalyzer can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break DeadCode.NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses TypeDeclaration.AlreadyAssignDetector, so a change to TypeDeclaration.AlreadyAssignDetector can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break TypeDeclaration.AlreadyAssignDetector.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses NodeManipulator, so a change to NodeManipulator can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break NodeManipulator.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
DeadCode.Rector.If_ uses NodeAnalyzer, so a change to NodeAnalyzer can break DeadCode.Rector.If_, while a change to DeadCode.Rector.If_ can't break NodeAnalyzer.
Position
Below the diagonal: DeadCode.Rector.If_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses Contract.Rector, so a change to Contract.Rector can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break Contract.Rector.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses VersionBonding.Contract, so a change to VersionBonding.Contract can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break VersionBonding.Contract.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses StaticTypeMapper, so a change to StaticTypeMapper can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break StaticTypeMapper.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break Comments.NodeDocBlock.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses PhpParser.Node, so a change to PhpParser.Node can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break PhpParser.Node.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses Reflection, so a change to Reflection can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break Reflection.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses Php80.NodeAnalyzer, so a change to Php80.NodeAnalyzer can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break Php80.NodeAnalyzer.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break PhpParser.Node.Value.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses TypeDeclaration.TypeInferer, so a change to TypeDeclaration.TypeInferer can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break TypeDeclaration.TypeInferer.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
Php80.Rector.Class_ uses NodeAnalyzer, so a change to NodeAnalyzer can break Php80.Rector.Class_, while a change to Php80.Rector.Class_ can't break NodeAnalyzer.
Position
Below the diagonal: Php80.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses Configuration.Deprecation.Contract, so a change to Configuration.Deprecation.Contract can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Configuration.Deprecation.Contract.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses Contract.Rector, so a change to Contract.Rector can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Contract.Rector.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses NodeTypeResolver.PHPStan.Type, so a change to NodeTypeResolver.PHPStan.Type can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break NodeTypeResolver.PHPStan.Type.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses Php, so a change to Php can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Php.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses PhpDocParser.NodeTraverser, so a change to PhpDocParser.NodeTraverser can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break PhpDocParser.NodeTraverser.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
45 pairs of types, where a type in TypeDeclaration.Rector.ClassMethod uses a type in RuleDoc. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
TypeDeclaration.Rector.ClassMethod uses RuleDoc, so a change to RuleDoc can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break RuleDoc.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in TypeDeclaration.Rector.ClassMethod uses a type in VersionBonding.Contract. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
TypeDeclaration.Rector.ClassMethod uses VersionBonding.Contract, so a change to VersionBonding.Contract can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break VersionBonding.Contract.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses StaticTypeMapper, so a change to StaticTypeMapper can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break StaticTypeMapper.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Comments.NodeDocBlock.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses PhpParser.Node, so a change to PhpParser.Node can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break PhpParser.Node.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses Reflection, so a change to Reflection can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Reflection.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break PhpParser.Node.Value.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses PhpParser.NodeFinder, so a change to PhpParser.NodeFinder can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break PhpParser.NodeFinder.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses TypeDeclaration.TypeInferer, so a change to TypeDeclaration.TypeInferer can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break TypeDeclaration.TypeInferer.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break TypeDeclaration.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.ClassMethod uses NodeAnalyzer, so a change to NodeAnalyzer can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
42 pairs of types, where a type in TypeDeclaration.Rector.ClassMethod uses a type in Rector. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
TypeDeclaration.Rector.ClassMethod uses Rector, so a change to Rector can break TypeDeclaration.Rector.ClassMethod, while a change to TypeDeclaration.Rector.ClassMethod can't break Rector.
Position
Below the diagonal: TypeDeclaration.Rector.ClassMethod uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses RuleDoc, so a change to RuleDoc can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break RuleDoc.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses VersionBonding.Contract, so a change to VersionBonding.Contract can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break VersionBonding.Contract.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses StaticTypeMapper, so a change to StaticTypeMapper can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break StaticTypeMapper.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break Comments.NodeDocBlock.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses PhpParser.Node, so a change to PhpParser.Node can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break PhpParser.Node.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses Reflection, so a change to Reflection can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break Reflection.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break PhpParser.Node.Value.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses DeadCode.PhpDoc.TagRemover, so a change to DeadCode.PhpDoc.TagRemover can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break DeadCode.PhpDoc.TagRemover.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses TypeDeclaration.TypeInferer, so a change to TypeDeclaration.TypeInferer can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break TypeDeclaration.TypeInferer.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses TypeDeclaration.NodeAnalyzer, so a change to TypeDeclaration.NodeAnalyzer can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break TypeDeclaration.NodeAnalyzer.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses TypeDeclaration.AlreadyAssignDetector, so a change to TypeDeclaration.AlreadyAssignDetector can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break TypeDeclaration.AlreadyAssignDetector.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses TypeDeclaration.TypeInferer.PropertyTypeInferer, so a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break TypeDeclaration.TypeInferer.PropertyTypeInferer.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Class_ uses Rector, so a change to Rector can break TypeDeclaration.Rector.Class_, while a change to TypeDeclaration.Rector.Class_ can't break Rector.
Position
Below the diagonal: TypeDeclaration.Rector.Class_ uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses Configuration.Deprecation.Contract, so a change to Configuration.Deprecation.Contract can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break Configuration.Deprecation.Contract.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses Contract.Rector, so a change to Contract.Rector can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break Contract.Rector.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses RuleDoc, so a change to RuleDoc can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break RuleDoc.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses VersionBonding.Contract, so a change to VersionBonding.Contract can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break VersionBonding.Contract.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses StaticTypeMapper, so a change to StaticTypeMapper can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break StaticTypeMapper.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses BetterPhpDocParser.PhpDocInfo, so a change to BetterPhpDocParser.PhpDocInfo can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break BetterPhpDocParser.PhpDocInfo.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses Comments.NodeDocBlock, so a change to Comments.NodeDocBlock can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break Comments.NodeDocBlock.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses Reflection, so a change to Reflection can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break Reflection.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses BetterPhpDocParser.PhpDocManipulator, so a change to BetterPhpDocParser.PhpDocManipulator can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break BetterPhpDocParser.PhpDocManipulator.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses PhpParser.Node.Value, so a change to PhpParser.Node.Value can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break PhpParser.Node.Value.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses DeadCode.PhpDoc.TagRemover, so a change to DeadCode.PhpDoc.TagRemover can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break DeadCode.PhpDoc.TagRemover.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses TypeDeclaration.AlreadyAssignDetector, so a change to TypeDeclaration.AlreadyAssignDetector can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break TypeDeclaration.AlreadyAssignDetector.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses TypeDeclaration.TypeInferer.PropertyTypeInferer, so a change to TypeDeclaration.TypeInferer.PropertyTypeInferer can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break TypeDeclaration.TypeInferer.PropertyTypeInferer.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
TypeDeclaration.Rector.Property uses Rector, so a change to Rector can break TypeDeclaration.Rector.Property, while a change to TypeDeclaration.Rector.Property can't break Rector.
Position
Below the diagonal: TypeDeclaration.Rector.Property uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A07:2025 — Authentication Failures
58
High / Critical
A05:2025 — Injection
15
High / Critical
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Resolve the 55 High secret finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (10), REDACTED (6); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
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 — 77
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 — 408
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 — 48
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 36 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 — 36 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, 524 of 533 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.php) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (193 contributor(s) across 20000 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 192 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (110871 LoC, 1197 module-visible types across 526 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised PHP container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
P7 Outbound HTTP resilience — not measured this run — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. The PHP source it reads makes no outbound call, and the rest of this repository's production source is , which it does not read yet — the calls may well be there — a gap in this analyzer's language reach, not a finding about the code.
S1 Web-Security Posture — not measured this run — 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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
52 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PHPStanNodeScopeResolver.fillScope at 60. A further 2 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 CarbonCallFactory.createModifyMethodCall at 21 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: rules/Carbon/NodeFactory/CarbonCallFactory.php (CarbonCallFactory.createModifyMethodCall at 21), src/PhpParser/Enum/NodeGroup.php (NodeGroup.isStmtAwareNode at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 47 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with PHPStanNodeScopeResolver.fillScope (cyclomatic 60), RectorConfigBuilder.__invoke (cyclomatic 42), MergePhpstanDocTagIntoNativeRector.refactor (cyclomatic 31). — 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 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
+ 149 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with RemoveArgumentFromDefaultParentCallRector.refactor (cognitive 72), PHPStanNodeScopeResolver.fillScope (cognitive 66). — 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 2 together lifts Cognitive Complexity from 6.0 to about 6.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.8 / 10Stronggated by 5 serious findings✓ 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 5 TooManyMethods finding(s) in God Classes — start with RectorConfig.php, RectorConfigBuilder.php, PhpDocInfo.php. — One of this dimension's main actionable groups (5 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.
73 duplicated block group(s) detected. 4.8 % of the production lines (5,374 of 110,871) are in a reported copy. A further 92 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 66 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SetUpAssignedPropertyTyper.php, CallLikeArgumentNameAdder.php, ArrowFunctionAndClosureFirstClassCallableGuard.php. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 7 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with TernaryToSpaceshipRector.php, ArgumentAdderRector.php, AstResolver.php. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with RepeatedAndNotEqualToNotInArrayRector.php, PhpDocClassRenamer.php, ClassMethodPropertyFetchManipulator.php. — One of this dimension's main actionable groups (6 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 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with NodeFactory.php, MatchSwitchAnalyzer.php, SwitchAnalyzer.php. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d6_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 11 Hotspot finding(s) in Churn × Complexity Hotspots — start with PHPStanNodeScopeResolver.php, RectorConfigBuilder.php, BetterStandardPrinter.php. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 deducted task-comment markers across 110871 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with ReflectionResolver.php, GitHubOutputFormatter.php. — One of this dimension's main actionable groups (2 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 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with composer.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.4 / 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.
40 % of calls cross a namespace and 0 % go through an interface, but 19 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
Scattered collaborators
What to do
Resolve the 1 Scattered collaborators 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: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
57 finding(s): 0 critical, 57 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 55 High secret finding(s) in Secrets (history) — start with REDACTED (10), REDACTED (10), REDACTED (6). — One of this dimension's main actionable groups (55 issue-level).
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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).
15 finding(s): 0 critical, 14 high, 1 medium, 0 low. 13 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.
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).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
No action in Static Analysis (SAST) — all 13 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 (13 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 anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 549 of the 1254 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with php84.php, ConfigurationFactory.php, php83.php. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 Change coupling finding(s) in Change Coupling — start with ProcessCommand.php, ForeachToArrayAllRector.php, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with VersionResolver.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 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 1 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?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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
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?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 4 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.
D36 Supply-chain Provenance & Signing — 8 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
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 — 39 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~163 lines of test source are present (.php) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .php test runner
D12 Dependency Hygiene — Not scored — 1 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
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
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 — not scored — this repository shows none of the 3 signals this lens looks for
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 2 current-state document(s) make no claim of a kind M4 checks.
P7 Outbound HTTP resilience — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: php84.php ↔ PhpVersionFeature.php config/set/php84.php:1— `config/set/php84.php` (context config) and `src/ValueObject/PhpVersionFeature.php` (context ValueObject) sit in DIFFERENT parts of the tree yet change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `70f40591` Updated Rector to commit dc677e1b15aaa2015959d62b3db812aecb4dedf1; `e6a737e1` Updated Rector to commit d5a995460f98b81cf51438f92e8b8b4364bcfea0; `306b6f62` Updated Rector to commit 096678dc6b7ebea98cb687cf24662b9490e1b383 — run `git show` on any of them.
Boundary-crossing change coupling: ConfigurationFactory.php ↔ ProcessConfigureDecorator.php src/Configuration/ConfigurationFactory.php:1— `src/Configuration/ConfigurationFactory.php` (context Configuration) and `src/Console/ProcessConfigureDecorator.php` (context Console) sit in DIFFERENT parts of the tree yet change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `1547cf11` Updated Rector to commit 27c5f897750ebb175a96e894d13041c31a2c054d; `c7eef3b7` Updated Rector to commit 0ee1347fda56433334b34f2298c14ae493cee30a; `7a207676` Updated Rector to commit 0c3d4f4e3c5c3eb7eabc0f7097bd7efaea657439 — run `git show` on any of them.
Boundary-crossing change coupling: php83.php ↔ PhpVersionFeature.php config/set/php83.php:1— `config/set/php83.php` (context config) and `src/ValueObject/PhpVersionFeature.php` (context ValueObject) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `064c784e` Updated Rector to commit a72065d1676018c9fa346f11ff0cdd2dd7bbe27d; `4366ff8d` Updated Rector to commit 9f3665ae712294588cb9f1d1001c6efc1ad8683b; `36801f8f` Updated Rector to commit 2a5e822a045365728e20dbfdca16936f497b5837 — run `git show` on any of them.
Boundary-crossing change coupling: ClassNameImportSkipper.php ↔ NameImportingPostRector.php rules/CodingStyle/ClassNameImport/ClassNameImportSkipper.php:1— `rules/CodingStyle/ClassNameImport/ClassNameImportSkipper.php` (context rules) and `src/PostRector/Rector/NameImportingPostRector.php` (context PostRector) sit in DIFFERENT parts of the tree yet change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `2d115a2c` Updated Rector to commit b2213fdb4431413ab027e9f83ffb97e0cb8d838f; `155105e7` Updated Rector to commit 52e95e83fcca59cb53d96fa664d8839b42c90ed9; `2da17746` Updated Rector to commit 363ae1bd444c365e38aef1cfcd69324b734c3c9c (at that commit the file was still `packages/PostRector/Rector/NameImportingPostRector.php`) — run `git show` on any of them.
Boundary-crossing change coupling: php85.php ↔ PhpVersionFeature.php config/set/php85.php:1— `config/set/php85.php` (context config) and `src/ValueObject/PhpVersionFeature.php` (context ValueObject) sit in DIFFERENT parts of the tree yet change together 50% of the time (13 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `3fd17418` Updated Rector to commit 6a3101644b93c439234f00d00a4bde62467e3b75; `72228d41` Updated Rector to commit 815e30915b029e87f9d58adcd1ef070d485ab5f5; `a40557f7` Updated Rector to commit ade4c813058020138d73b110f091a2fbee415536 — run `git show` on any of them.
Hotspot: src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php:144— src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 60 in PHPStanNodeScopeResolver.fillScope at line 144. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Configuration/RectorConfigBuilder.php src/Configuration/RectorConfigBuilder.php:151— src/Configuration/RectorConfigBuilder.php changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in RectorConfigBuilder.__invoke at line 151. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- src/Configuration/RectorConfigBuilder.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/PhpParser/Printer/BetterStandardPrinter.php src/PhpParser/Printer/BetterStandardPrinter.php:400— src/PhpParser/Printer/BetterStandardPrinter.php changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BetterStandardPrinter.wrapBinaryOpWithBrackets at line 400. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- src/PhpParser/Printer/BetterStandardPrinter.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php:80— rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in MergePhpstanDocTagIntoNativeRector.refactor at line 80. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php:53— rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in ObjectTypeSpecifier.narrowToFullyQualifiedOrAliasedObjectType at line 53. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php:113— rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AddParamBasedOnParentClassMethodRector.refactor at line 113. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php:103— rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in StrictArrayParamDimFetchRector.refactor at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php:94— rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ArrayToFirstClassCallableRector.refactor at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Application/ChangedNodeScopeRefresher.php src/Application/ChangedNodeScopeRefresher.php:146— src/Application/ChangedNodeScopeRefresher.php changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ChangedNodeScopeRefresher.resolveStmts at line 146. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- src/Application/ChangedNodeScopeRefresher.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/Privatization/TypeManipulator/TypeNormalizer.php rules/Privatization/TypeManipulator/TypeNormalizer.php:69— rules/Privatization/TypeManipulator/TypeNormalizer.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in TypeNormalizer.generalizeConstantTypes at line 69. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/Privatization/TypeManipulator/TypeNormalizer.php`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:51— rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ArrowFunctionAndClosureFirstClassCallableGuard.shouldSkip at line 51. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 21:48:06 +00:00' --until='2026-11-13 21:48:06 +00:00' --full-history --no-merges -- rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.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.
Duplicated block (8 lines × 2) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:133— rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:133-140 | rules/TypeDeclarationDocblocks/NodeAnalyzer/ConstructorAssignedTypeResolver.php:45-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/NodeAnalyzer/CallLikeArgumentNameAdder.php:63— src/NodeAnalyzer/CallLikeArgumentNameAdder.php:63-70 | src/NodeAnalyzer/CallLikeArgumentNameAdder.php:125-132 — 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/NodeAnalyzer/CallLikeArgumentNameAdder.php:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:186— rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:186-193 | src/NodeAnalyzer/ArgsAnalyzer.php:24-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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) rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php:185— rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php:185-192 | rules/DeadCode/Rector/ClassMethod/RemoveUnusedConstructorParamRector.php:106-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) rules/Php80/NodeFactory/MatchFactory.php:77— rules/Php80/NodeFactory/MatchFactory.php:77-84 | rules/Php80/Rector/Switch_/ChangeSwitchToMatchRector.php:230-237 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:66— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:66-73 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:63-70 — before extracting anything, compare `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php` and `rules/Php84/NodeFactory/ForeachToArrayFindFactory.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) rules/TypeDeclaration/Rector/Closure/AddClosureVoidReturnTypeWhereNoReturnRector.php:53— rules/TypeDeclaration/Rector/Closure/AddClosureVoidReturnTypeWhereNoReturnRector.php:53-60 | rules/TypeDeclaration/Rector/Function_/AddFunctionVoidReturnTypeWhereNoReturnRector.php:53-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/StaticTypeMapper/ValueObject/Type/FullyQualifiedObjectType.php:60— src/StaticTypeMapper/ValueObject/Type/FullyQualifiedObjectType.php:60-67 | src/StaticTypeMapper/ValueObject/Type/NonExistingObjectType.php:18-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The 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) rules/Php80/NodeAnalyzer/SwitchAnalyzer.php:112— rules/Php80/NodeAnalyzer/SwitchAnalyzer.php:112-119 | src/PhpParser/Node/FileNode.php:187-194 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The 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) rules/Renaming/ValueObject/RenameClassAndConstFetch.php:29— rules/Renaming/ValueObject/RenameClassAndConstFetch.php:29-36 | rules/Renaming/ValueObject/RenameStaticMethod.php:31-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.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×7
Edited copy of a member (10 corresponding lines) rules/Php70/Rector/Ternary/TernaryToSpaceshipRector.php:96— rules/Php70/Rector/Ternary/TernaryToSpaceshipRector.php:96-105 | rules/Php70/Rector/Ternary/TernaryToSpaceshipRector.php:112-121 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php:335— rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php:335-347 | rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php:351-360 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/PhpParser/AstResolver.php:166— src/PhpParser/AstResolver.php:166-179 | src/PhpParser/AstResolver.php:272-281 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/StaticTypeMapper/PhpDocParser/IdentifierPhpDocTypeMapper.php:127— src/StaticTypeMapper/PhpDocParser/IdentifierPhpDocTypeMapper.php:127-140 | src/StaticTypeMapper/PhpDocParser/IdentifierPhpDocTypeMapper.php:147-156 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/PhpParser/NodeVisitor/ByRefNodeVisitor.php:105— src/PhpParser/NodeVisitor/ByRefNodeVisitor.php:105-114 | src/PhpParser/NodeVisitor/ByRefNodeVisitor.php:121-133 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) src/Reporting/DeprecatedRulesReporter.php:23— src/Reporting/DeprecatedRulesReporter.php:23-32 | src/Reporting/DeprecatedRulesReporter.php:37-46 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:100— rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:100-109 | rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:116-125 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×6
Edited copy of a member (21 corresponding lines) rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:123— rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:123-143 | rules/CodeQuality/Rector/BooleanOr/RepeatedOrEqualToInArrayRector.php:128-148 — 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.
Edited copy of a member (21 corresponding lines) src/BetterPhpDocParser/PhpDocManipulator/PhpDocClassRenamer.php:54— src/BetterPhpDocParser/PhpDocManipulator/PhpDocClassRenamer.php:54-83 | src/BetterPhpDocParser/PhpDocManipulator/PhpDocClassRenamer.php:132-152 — 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.
Edited copy of a member (21 corresponding lines) src/NodeManipulator/ClassMethodPropertyFetchManipulator.php:93— src/NodeManipulator/ClassMethodPropertyFetchManipulator.php:93-115 | src/PhpParser/NodeFinder/PropertyFetchFinder.php:119-139 — 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.
Edited copy of a member (21 corresponding lines) rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php:116— rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php:116-139 | rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php:159-179 — 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.
Edited copy of a member (21 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictConstantReturnRector.php:95— rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictConstantReturnRector.php:95-115 | rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictTypedPropertyRector.php:103-124 — 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.
Edited copy of a member (21 corresponding lines) rules/CodingStyle/Rector/FuncCall/CallUserFuncToMethodCallRector.php:61— rules/CodingStyle/Rector/FuncCall/CallUserFuncToMethodCallRector.php:61-82 | rules/Php72/Rector/FuncCall/StringifyDefineRector.php:69-89 — 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.
Duplicated block (12 lines × 2) rules/CodeQuality/Rector/FuncCall/SimplifyInArrayValuesRector.php:33— rules/CodeQuality/Rector/FuncCall/SimplifyInArrayValuesRector.php:33-44 | rules/CodeQuality/Rector/FuncCall/SingleInArrayToCompareRector.php:80-91 — 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 (12 lines × 2) rules/CodeQuality/Rector/If_/SimplifyIfNullableReturnRector.php:101— rules/CodeQuality/Rector/If_/SimplifyIfNullableReturnRector.php:101-112 | rules/CodeQuality/Rector/If_/SimplifyIfReturnBoolRector.php:78-89 — 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 `rules/CodeQuality/Rector/If_/SimplifyIfNullableReturnRector.php:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) rules/Php80/Rector/NotIdentical/MbStrContainsRector.php:91— rules/Php80/Rector/NotIdentical/MbStrContainsRector.php:91-102 | rules/Php80/Rector/NotIdentical/StrContainsRector.php:96-107 — before extracting anything, compare `rules/Php80/Rector/NotIdentical/MbStrContainsRector.php` and `rules/Php80/Rector/NotIdentical/StrContainsRector.php` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:86— rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:86-97 | rules/TypeDeclaration/Rector/Class_/ScalarTypedPropertyFromJMSSerializerAttributeTypeRector.php:92-103 — before extracting anything, compare `rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php` and `rules/TypeDeclaration/Rector/Class_/ScalarTypedPropertyFromJMSSerializerAttributeTypeRector.php` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) rules/TypeDeclaration/Rector/FuncCall/AddArrayFunctionClosureParamTypeRector.php:58— rules/TypeDeclaration/Rector/FuncCall/AddArrayFunctionClosureParamTypeRector.php:58-69 | rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php:61-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/Rector/FuncCall/AddArrayFunctionClosureParamTypeRector.php:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/NodeManipulator/ClassMethodPropertyFetchManipulator.php:52— src/NodeManipulator/ClassMethodPropertyFetchManipulator.php:52-63 | src/NodeManipulator/ClassMethodPropertyFetchManipulator.php:96-107 — 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 lines × 2) rules/Php80/Rector/FuncCall/GetHeadersArgumentFormatRector.php:50— rules/Php80/Rector/FuncCall/GetHeadersArgumentFormatRector.php:50-60 | rules/Php80/Rector/FuncCall/VersionCompareFuncCallArgumentRector.php:55-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) rules/Php83/Rector/FuncCall/CombineHostPortLdapUriRector.php:55— rules/Php83/Rector/FuncCall/CombineHostPortLdapUriRector.php:55-65 | rules/Php83/Rector/FuncCall/DynamicClassConstFetchRector.php:41-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:196— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:196-206 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:142-152 — before extracting anything, compare `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php` and `rules/Php84/NodeFactory/ForeachToArrayFindFactory.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php:51— rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php:51-61 | rules/TypeDeclaration/Rector/ClassMethod/ReturnNullableTypeRector.php:99-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `rules/TypeDeclaration/Rector/ClassMethod/ReturnNullableTypeRector.php:98` calls `fetch` and `rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php:50` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php:83— rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php:83-93 | rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictScalarReturnsRector.php:81-91 — before extracting anything, compare `rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php` and `rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictScalarReturnsRector.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromAssignsParamToParamReferenceRector.php:97— rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromAssignsParamToParamReferenceRector.php:97-107 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromDimFetchAccessRector.php:104-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 `rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromAssignsParamToParamReferenceRector.php:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:74— rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:74-80 | rules/CodingStyle/Rector/Stmt/NewlineAfterStatementRector.php:82-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:74` 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/Reporting/MissConfigurationReporter.php:48— src/Reporting/MissConfigurationReporter.php:48-54 | src/Reporting/MissConfigurationReporter.php:64-70 — 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) rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:95— rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:95-101 | rules/CodeQuality/Rector/BooleanOr/RepeatedOrEqualToInArrayRector.php:100-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) rules/CodeQuality/Rector/If_/ExplicitNullableObjectInstanceRector.php:218— rules/CodeQuality/Rector/If_/ExplicitNullableObjectInstanceRector.php:218-224 | rules/DeadCode/Rector/BinaryOp/RemoveRedundantTypeCheckRector.php:177-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:113— rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:113-119 | rules/TypeDeclaration/Rector/Class_/ScalarTypedPropertyFromJMSSerializerAttributeTypeRector.php:119-125 — before extracting anything, compare `rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php` and `rules/TypeDeclaration/Rector/Class_/ScalarTypedPropertyFromJMSSerializerAttributeTypeRector.php` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/NodeTypeResolver/NodeTypeResolver.php:292— src/NodeTypeResolver/NodeTypeResolver.php:292-298 | src/NodeTypeResolver/PHPStan/TypeHasher.php:45-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
TooManyMethods: RectorConfig src/Config/RectorConfig.php:29— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RectorConfigBuilder src/Configuration/RectorConfigBuilder.php:41— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PhpDocInfo src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php:44— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: NodeFactory src/PhpParser/Node/NodeFactory.php:65— 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.
TooManyMethods: BetterStandardPrinter src/PhpParser/Printer/BetterStandardPrinter.php:50— 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.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×5
Edited copy of a member (7 corresponding lines) src/ChangesReporting/Output/GitlabOutputFormatter.php:79— src/ChangesReporting/Output/GitlabOutputFormatter.php:79-85 | src/ChangesReporting/Output/GitlabOutputFormatter.php:103-112 — 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) rules/TypeDeclarationDocblocks/NodeFinder/ArrayDimFetchFinder.php:112— rules/TypeDeclarationDocblocks/NodeFinder/ArrayDimFetchFinder.php:112-118 | rules/TypeDeclarationDocblocks/NodeFinder/ArrayDimFetchFinder.php:132-138 — 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) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:68— rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:68-74 | rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/SubstrMatchAndRefactor.php:65-71 — 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) rules/DeadCode/PhpDoc/DeadParamTagValueNodeAnalyzer.php:63— rules/DeadCode/PhpDoc/DeadParamTagValueNodeAnalyzer.php:63-71 | rules/DeadCode/PhpDoc/DeadReturnTagValueNodeAnalyzer.php:60-66 — 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) rules/CodeQuality/Rector/Foreach_/ForeachToInArrayRector.php:169— rules/CodeQuality/Rector/Foreach_/ForeachToInArrayRector.php:169-176 | rules/CodeQuality/Rector/If_/ConsecutiveNullCompareReturnsToNullCoalesceQueueRector.php:143-149 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:51— rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:51-63 | rules/Php70/NodeAnalyzer/BattleshipTernaryAnalyzer.php:74-86 — 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/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php:43— src/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php:43-55 | src/StaticTypeMapper/PhpParser/UnionTypeNodeMapper.php:56-72 — 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) rules/DeadCode/Rector/If_/ReduceAlwaysFalseIfOrRector.php:68— rules/DeadCode/Rector/If_/ReduceAlwaysFalseIfOrRector.php:68-80 | rules/DeadCode/Rector/If_/RemoveAlwaysTrueIfConditionRector.php:184-196 — 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/BetterPhpDocParser/ValueObject/PhpDoc/DoctrineAnnotation/AbstractValuesAwareNode.php:100— src/BetterPhpDocParser/ValueObject/PhpDoc/DoctrineAnnotation/AbstractValuesAwareNode.php:100-112 | src/BetterPhpDocParser/ValueObject/PhpDoc/DoctrineAnnotation/CurlyListNode.php:35-47 — 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) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:139— rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:139-155 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanStrictReturnsRector.php:141-153 — 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 (11 corresponding lines) · ×5
Edited copy of a member (11 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:54— rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:54-64 | rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:45-55 — 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.
Edited copy of a member (11 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:68— rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:68-81 | rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:85-95 — 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.
Edited copy of a member (11 corresponding lines) rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php:119— rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php:119-132 | rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php:162-172 — 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.
Edited copy of a member (11 corresponding lines) src/NodeManipulator/IfManipulator.php:45— src/NodeManipulator/IfManipulator.php:45-55 | rules/Php70/Rector/If_/IfToSpaceshipRector.php:175-185 — 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.
Edited copy of a member (11 corresponding lines) src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php:441— src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php:441-453 | src/BetterPhpDocParser/PhpDocNodeFinder/PhpDocNodeByTypeFinder.php:20-30 — 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 (8 corresponding lines) · ×5
Edited copy of a member (8 corresponding lines) src/Reporting/MissConfigurationReporter.php:47— src/Reporting/MissConfigurationReporter.php:47-54 | src/Reporting/MissConfigurationReporter.php:63-70 — 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) rules/TypeDeclaration/NodeAnalyzer/StrictReturnNewArrayResolver.php:224— rules/TypeDeclaration/NodeAnalyzer/StrictReturnNewArrayResolver.php:224-231 | rules/CodeQuality/Rector/Equal/UseIdenticalOverEqualWithSameTypeRector.php:90-98 — 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) rules/CodeQuality/Rector/Catch_/ThrowWithPreviousExceptionRector.php:203— rules/CodeQuality/Rector/Catch_/ThrowWithPreviousExceptionRector.php:203-210 | rules/Php84/Rector/FuncCall/AddEscapeArgumentRector.php:91-98 — 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) rules/DeadCode/Rector/Expression/SimplifyMirrorAssignRector.php:43— rules/DeadCode/Rector/Expression/SimplifyMirrorAssignRector.php:43-50 | rules/Php72/Rector/Unset_/UnsetCastRector.php:66-73 — 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) rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php:174— rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php:174-182 | src/NodeTypeResolver/NodeTypeResolver.php:401-408 — 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 (5 corresponding lines) · ×5
Edited copy of a member (5 corresponding lines) src/StaticTypeMapper/ValueObject/Type/AliasedObjectType.php:36— src/StaticTypeMapper/ValueObject/Type/AliasedObjectType.php:36-40 | src/StaticTypeMapper/ValueObject/Type/FullyQualifiedObjectType.php:48-52 — 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.
Edited copy of a member (5 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php:164— rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php:164-168 | src/NodeAnalyzer/DoctrineEntityAnalyzer.php:30-34 — 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.
Edited copy of a member (5 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:53— rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:53-57 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanStrictReturnsRector.php:61-66 — 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.
Edited copy of a member (5 corresponding lines) rules/Renaming/Rector/PropertyFetch/RenamePropertyRector.php:110— rules/Renaming/Rector/PropertyFetch/RenamePropertyRector.php:110-114 | src/Reflection/ClassModifierChecker.php:20-24 — 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.
Edited copy of a member (5 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictTypedPropertyRector.php:58— rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictTypedPropertyRector.php:58-63 | rules/TypeDeclaration/Rector/Class_/ReturnTypeFromStrictTernaryRector.php:54-58 — 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 (14 lines × 2) rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:112— rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:112-125 | rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:189-202 — 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 `rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:112` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php:175— rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php:175-188 | rules/Php70/Rector/Ternary/TernaryToNullCoalescingRector.php:157-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php:175` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) rules/EarlyReturn/Rector/If_/ChangeIfElseValueAssignToEarlyReturnRector.php:81— rules/EarlyReturn/Rector/If_/ChangeIfElseValueAssignToEarlyReturnRector.php:81-94 | rules/Php70/Rector/StmtsAwareInterface/IfIssetToCoalescingRector.php:70-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/EarlyReturn/Rector/If_/ChangeIfElseValueAssignToEarlyReturnRector.php:81` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php:145— rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php:145-158 | rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictScalarReturnsRector.php:92-105 — before extracting anything, compare `rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php` and `rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictScalarReturnsRector.php` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php:62— rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php:62-75 | rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayReduceRector.php:70-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:137— rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:137-149 | rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:198-210 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:137` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:61— rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:61-73 | rules/Php81/Rector/MethodCall/SpatieEnumMethodCallToEnumConstRector.php:58-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:179— rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:179-191 | rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:237-249 — 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 `rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php:78— rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php:78-90 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/NarrowArrayCollectionUnionReturnDocblockRector.php:87-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) rules/TypeDeclaration/Rector/Closure/ClosureReturnTypeFromAssertInstanceOfRector.php:103— rules/TypeDeclaration/Rector/Closure/ClosureReturnTypeFromAssertInstanceOfRector.php:103-115 | rules/TypeDeclaration/Rector/Closure/ClosureReturnTypeRector.php:63-75 — 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 `rules/TypeDeclaration/Rector/Closure/ClosureReturnTypeFromAssertInstanceOfRector.php:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) rules/CodingStyle/Rector/FuncCall/CallUserFuncToMethodCallRector.php:61— rules/CodingStyle/Rector/FuncCall/CallUserFuncToMethodCallRector.php:61-69 | rules/Php72/Rector/FuncCall/StringifyDefineRector.php:69-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) rules/DeadCode/Rector/StmtsAwareInterface/RemoveDeadInstanceOfAssertRector.php:132— rules/DeadCode/Rector/StmtsAwareInterface/RemoveDeadInstanceOfAssertRector.php:132-140 | rules/Php74/Rector/StaticCall/ExportToReflectionFunctionRector.php:93-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:73— rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php:73-81 | rules/Php80/ValueObjectFactory/StrStartsWithFactory.php:12-20 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:128— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:128-136 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:118-126 — before extracting anything, compare `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php` and `rules/Php84/NodeFactory/ForeachToArrayFindFactory.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:128` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstReturnsRector.php:128— rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstReturnsRector.php:128-136 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanStrictReturnsRector.php:183-191 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.
Change coupling: ProcessCommand.php ↔ WorkerCommand.php src/Console/Command/ProcessCommand.php:1— `src/Console/Command/ProcessCommand.php` and `src/Console/Command/WorkerCommand.php` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `61e9fc33` Updated Rector to commit 3da7c7296690b22c5e4a150659c8a0c8c599087e; `2c3da2b6` Updated Rector to commit 1a19a3450852b3e048689560e8ddc95d12e28863; `724521df` Updated Rector to commit 5d1b2c61f95ca5bc9b6a89eca0796dd8149ba233 — run `git show` on any of them.
Change coupling: ForeachToArrayAllRector.php ↔ ForeachToArrayAnyRector.php rules/Php84/Rector/Foreach_/ForeachToArrayAllRector.php:1— `rules/Php84/Rector/Foreach_/ForeachToArrayAllRector.php` and `rules/Php84/Rector/Foreach_/ForeachToArrayAnyRector.php` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `a6b4c3e0` Updated Rector to commit 6d8240575626342682a62f2c6f016f1579cca59e; `6ef2168c` Updated Rector to commit 0b70133f43cd354afe4e985133180a325dbab464; `03076912` Updated Rector to commit 91df93193d271308ebee81c66297decffd9feaed — run `git show` on any of them.
Change coupling: REDACTED ↔ ProcessConfigureDecorator.php REDACTED:1— `REDACTED` and `src/Console/ProcessConfigureDecorator.php` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `0c0fb34f` Updated Rector to commit cddd74ee001a655ef49163a8607bfc918702c940; `0c189c26` Updated Rector to commit 9342d9b3c1b43ee0453aa7907e62c49e761421fc; `1547cf11` Updated Rector to commit 27c5f897750ebb175a96e894d13041c31a2c054d — run `git show` on any of them.
Change coupling: ConsoleOutputFormatter.php ↔ JsonOutputFormatter.php src/ChangesReporting/Output/ConsoleOutputFormatter.php:1— `src/ChangesReporting/Output/ConsoleOutputFormatter.php` and `src/ChangesReporting/Output/JsonOutputFormatter.php` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `ea37cb5b` Updated Rector to commit 7f0688c1e4b5aaa6d75cbc458db35b4b6988f9c0; `3f02794d` Updated Rector to commit 27078e79628cb14866b69dc6b8c2181fbec1d4c6 (at that commit the files were still `packages/ChangesReporting/Output/ConsoleOutputFormatter.php` and `packages/ChangesReporting/Output/JsonOutputFormatter.php`); `18916795` Updated Rector to commit 701278e9882f33c2977753be99b08dd7aaf93997 (at that commit the files were still `packages/ChangesReporting/Output/ConsoleOutputFormatter.php` and `packages/ChangesReporting/Output/JsonOutputFormatter.php`) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) rules/Php81/NodeFactory/EnumFactory.php:70— rules/Php81/NodeFactory/EnumFactory.php:70-84 | rules/Php81/NodeFactory/EnumFactory.php:88-102 — 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.
Edited copy of a member (15 corresponding lines) rules/Php74/Rector/FuncCall/ArrayKeyExistsOnPropertyRector.php:59— rules/Php74/Rector/FuncCall/ArrayKeyExistsOnPropertyRector.php:59-74 | rules/Php74/Rector/FuncCall/FilterVarToAddSlashesRector.php:48-62 — 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.
Edited copy of a member (15 corresponding lines) rules/Php80/NodeAnalyzer/PromotedPropertyCandidateResolver.php:168— rules/Php80/NodeAnalyzer/PromotedPropertyCandidateResolver.php:168-182 | src/PhpParser/AstResolver.php:187-204 — 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.
Edited copy of a member (15 corresponding lines) rules/TypeDeclaration/TypeInferer/PropertyTypeInferer/GetterTypeDeclarationPropertyTypeInferer.php:36— rules/TypeDeclaration/TypeInferer/PropertyTypeInferer/GetterTypeDeclarationPropertyTypeInferer.php:36-50 | rules/TypeDeclaration/TypeInferer/PropertyTypeInferer/SetterTypeDeclarationPropertyTypeInferer.php:36-54 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×4
Edited copy of a member (19 corresponding lines) rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php:167— rules/DeadCode/Rector/Plus/RemoveDeadZeroAndOneOperationRector.php:167-188 | rules/Php70/Rector/Ternary/TernaryToNullCoalescingRector.php:152-170 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:78— rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:78-96 | rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/SubstrMatchAndRefactor.php:75-93 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) rules/Php72/Rector/FuncCall/StringsAssertNakedRector.php:64— rules/Php72/Rector/FuncCall/StringsAssertNakedRector.php:64-84 | rules/Php80/Rector/FuncCall/VersionCompareFuncCallArgumentRector.php:55-73 — These two members are one piece of code written twice and then edited apart: 19 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 (19 corresponding lines) rules/CodeQuality/Rector/New_/NewStaticToNewSelfRector.php:54— rules/CodeQuality/Rector/New_/NewStaticToNewSelfRector.php:54-72 | rules/Php55/Rector/ClassConstFetch/StaticToSelfOnFinalClassRector.php:54-74 — These two members are one piece of code written twice and then edited apart: 19 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.
Low cohesion: NodeFactory (LCOM4 11) src/PhpParser/Node/NodeFactory.php:65— NodeFactory's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MatchSwitchAnalyzer (LCOM4 5) rules/Php80/NodeAnalyzer/MatchSwitchAnalyzer.php:21— MatchSwitchAnalyzer'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: SwitchAnalyzer (LCOM4 4) rules/Php80/NodeAnalyzer/SwitchAnalyzer.php:16— SwitchAnalyzer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ExprAnalyzer (LCOM4 4) src/NodeAnalyzer/ExprAnalyzer.php:59— ExprAnalyzer's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) rules/Php80/Rector/NotIdentical/MbStrContainsRector.php:83— rules/Php80/Rector/NotIdentical/MbStrContainsRector.php:83-102 | rules/Php80/Rector/NotIdentical/StrContainsRector.php:85-107 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromCast.php:50— rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromCast.php:50-69 | rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromStrictNativeCall.php:56-79 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php:76— rules/TypeDeclaration/Rector/ClassMethod/NarrowBoolDocblockReturnTypeRector.php:76-95 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/NarrowArrayCollectionUnionReturnDocblockRector.php:86-106 — These two members are one piece of code written twice and then edited apart: 20 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) · ×3
Edited copy of a member (23 corresponding lines) rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:69— rules/CodeQuality/Rector/BooleanAnd/RepeatedAndNotEqualToNotInArrayRector.php:69-91 | rules/CodeQuality/Rector/BooleanOr/RepeatedOrEqualToInArrayRector.php:68-96 — 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.
Edited copy of a member (23 corresponding lines) src/BetterPhpDocParser/PhpDocManipulator/PhpDocTypeChanger.php:75— src/BetterPhpDocParser/PhpDocManipulator/PhpDocTypeChanger.php:75-101 | src/BetterPhpDocParser/PhpDocManipulator/PhpDocTypeChanger.php:130-152 — 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.
Edited copy of a member (23 corresponding lines) rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php:179— rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php:179-201 | rules/Php86/Rector/Class_/ConstructorReadonlyAssignToDefaultRector.php:123-145 — 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 copy of a member (22 corresponding lines) · ×3
Edited copy of a member (22 corresponding lines) src/PhpParser/AstResolver.php:97— src/PhpParser/AstResolver.php:97-118 | src/PhpParser/AstResolver.php:211-239 — 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.
Edited copy of a member (22 corresponding lines) rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:61— rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:61-84 | rules/Php81/Rector/MethodCall/SpatieEnumMethodCallToEnumConstRector.php:58-79 — 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.
Edited copy of a member (22 corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeDeclarationRector.php:91— rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeDeclarationRector.php:91-118 | rules/TypeDeclaration/Rector/ClassMethod/AddReturnTypeDeclarationRector.php:93-114 — 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 (24 corresponding lines) · ×3
Edited copy of a member (24 corresponding lines) rules/CodeQuality/Rector/FuncCall/SimplifyInArrayValuesRector.php:33— rules/CodeQuality/Rector/FuncCall/SimplifyInArrayValuesRector.php:33-56 | rules/CodeQuality/Rector/FuncCall/SingleInArrayToCompareRector.php:80-109 — 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.
Edited copy of a member (24 corresponding lines) rules/DeadCode/Rector/BinaryOp/RemoveRedundantTypeCheckRector.php:95— rules/DeadCode/Rector/BinaryOp/RemoveRedundantTypeCheckRector.php:95-124 | rules/DeadCode/Rector/BinaryOp/RemoveRedundantTypeCheckRector.php:131-154 — 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.
Edited copy of a member (24 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveTestsOverriddenPrivateMethodParameterRector.php:91— rules/DeadCode/Rector/ClassMethod/RemoveTestsOverriddenPrivateMethodParameterRector.php:91-114 | rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeBasedOnPHPUnitDataProviderRector.php:103-126 — 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 (14 corresponding lines) · ×3
Edited copy of a member (14 corresponding lines) rules/Php81/Rector/FuncCall/NullToStrictIntPregSlitFuncCallLimitArgRector.php:63— rules/Php81/Rector/FuncCall/NullToStrictIntPregSlitFuncCallLimitArgRector.php:63-76 | rules/Php85/Rector/FuncCall/ArrayKeyExistsNullToEmptyStringRector.php:48-64 — 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) rules/CodingStyle/Rector/Assign/SplitDoubleAssignRector.php:56— rules/CodingStyle/Rector/Assign/SplitDoubleAssignRector.php:56-69 | rules/Php80/Rector/Property/NestedAnnotationToAttributeRector.php:111-126 — 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) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:97— rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:97-110 | rules/DeadCode/Rector/ClassMethod/RemoveUnusedPrivateMethodParameterRector.php:65-81 — 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 (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) rules/Php80/Rector/Class_/ClassPropertyAssignToConstructorPromotionRector.php:442— rules/Php80/Rector/Class_/ClassPropertyAssignToConstructorPromotionRector.php:442-456 | rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:272-283 — 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) rules/CodeQuality/Rector/Class_/InlineConstructorDefaultToPropertyRector.php:154— rules/CodeQuality/Rector/Class_/InlineConstructorDefaultToPropertyRector.php:154-166 | src/NodeManipulator/ClassDependencyManipulator.php:246-257 — 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) rules/Php80/NodeAnalyzer/PromotedPropertyResolver.php:17— rules/Php80/NodeAnalyzer/PromotedPropertyResolver.php:17-28 | src/PhpParser/AstResolver.php:285-297 — 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.
Duplicated block (6 lines × 2) rules/Transform/ValueObject/FuncCallToMethodCall.php:27— rules/Transform/ValueObject/FuncCallToMethodCall.php:27-32 | rules/Transform/ValueObject/FuncCallToStaticCall.php:26-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:152— rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:152-157 | rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromGetRepositoryDocblockRector.php:210-215 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/BetterPhpDocParser/PhpDocNodeFinder/PhpDocNodeByTypeFinder.php:38— src/BetterPhpDocParser/PhpDocNodeFinder/PhpDocNodeByTypeFinder.php:38-43 | src/PhpParser/Node/BetterNodeFinder.php:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
TodoComment src/Reflection/ReflectionResolver.php:195— // todo: support NullsafeMethodCall — 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/ChangesReporting/Output/GitHubOutputFormatter.php:93— // TODO: Should be removed once github will have fixed it issue. — 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) · ×2
Edited copy of a member (18 corresponding lines) rules/TypeDeclaration/Rector/Class_/PropertyTypeFromStrictSetterGetterRector.php:249— rules/TypeDeclaration/Rector/Class_/PropertyTypeFromStrictSetterGetterRector.php:249-266 | rules/TypeDeclarationDocblocks/NodeAnalyzer/ConstructorAssignedTypeResolver.php:37-58 — 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/VendorLocker/NodeVendorLocker/ClassMethodParamVendorLockResolver.php:33— src/VendorLocker/NodeVendorLocker/ClassMethodParamVendorLockResolver.php:33-50 | src/VendorLocker/NodeVendorLocker/ClassMethodReturnTypeOverrideGuard.php:45-65 — 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 (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) rules/CodeQuality/Rector/FuncCall/IsAWithStringWithThirdArgumentRector.php:51— rules/CodeQuality/Rector/FuncCall/IsAWithStringWithThirdArgumentRector.php:51-66 | rules/Php73/Rector/FuncCall/StringifyStrNeedlesRector.php:53-72 — 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) rules/TypeDeclaration/NodeAnalyzer/CallTypesResolver.php:52— rules/TypeDeclaration/NodeAnalyzer/CallTypesResolver.php:52-67 | rules/TypeDeclaration/NodeAnalyzer/CallTypesResolver.php:75-91 — 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 (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveUselessReturnTagRector.php:78— rules/DeadCode/Rector/ClassMethod/RemoveUselessReturnTagRector.php:78-87 | rules/DeadCode/Rector/Property/RemoveUselessVarTagRector.php:66-74 — 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) rules/Php83/Rector/ClassConst/AddTypeToConstRector.php:151— rules/Php83/Rector/ClassConst/AddTypeToConstRector.php:151-159 | rules/Privatization/VisibilityGuard/ClassMethodVisibilityGuard.php:33-42 — 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 (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) rules/Renaming/ValueObject/MethodCallRename.php:25— rules/Renaming/ValueObject/MethodCallRename.php:25-30 | rules/Renaming/ValueObject/MethodCallRenameWithArrayKey.php:33-39 — These two members are one piece of code written twice and then edited apart: 6 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 (6 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:61— rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:61-67 | rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromGetRepositoryDocblockRector.php:62-67 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:265— rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:265-274 | rules/Php80/Rector/Property/NestedAnnotationToAttributeRector.php:149-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php:43— src/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php:43-52 | src/StaticTypeMapper/PhpParser/UnionTypeNodeMapper.php:56-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/StaticTypeMapper/PhpParser/IntersectionTypeNodeMapper.php:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) rules/CodeQuality/Rector/Expression/TernaryFalseExpressionToIfRector.php:20— rules/CodeQuality/Rector/Expression/TernaryFalseExpressionToIfRector.php:20-54 | rules/CodeQuality/Rector/FuncCall/SetTypeToCastRector.php:20-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/Expression/TernaryFalseExpressionToIfRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (33 lines × 2) rules/CodeQuality/Rector/FuncCall/CallUserFuncWithArrowFunctionToInlineRector.php:20— rules/CodeQuality/Rector/FuncCall/CallUserFuncWithArrowFunctionToInlineRector.php:20-52 | rules/CodingStyle/Rector/FuncCall/ArraySpreadInsteadOfArrayMergeRector.php:20-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/FuncCall/CallUserFuncWithArrowFunctionToInlineRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (36 lines × 2) rules/TypeDeclaration/Rector/ClassMethod/AddReturnArrayDocblockBasedOnArrayMapRector.php:21— rules/TypeDeclaration/Rector/ClassMethod/AddReturnArrayDocblockBasedOnArrayMapRector.php:21-58 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockBasedOnArrayMapRector.php:21-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/Rector/ClassMethod/AddReturnArrayDocblockBasedOnArrayMapRector.php:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (36 lines × 2) src/BetterPhpDocParser/NodeDecorator/ArrayItemClassNameDecorator.php:27— src/BetterPhpDocParser/NodeDecorator/ArrayItemClassNameDecorator.php:27-69 | src/BetterPhpDocParser/NodeDecorator/PhpDocTagGenericUsesDecorator.php:30-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/BetterPhpDocParser/NodeDecorator/ArrayItemClassNameDecorator.php:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
PHPStanNodeScopeResolver.fillScope (cyclomatic 60) src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php:144— PHPStanNodeScopeResolver.fillScope has cyclomatic complexity 60 (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.
RectorConfigBuilder.__invoke (cyclomatic 42) src/Configuration/RectorConfigBuilder.php:151— RectorConfigBuilder.__invoke has cyclomatic complexity 42 (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.
MergePhpstanDocTagIntoNativeRector.refactor (cyclomatic 31) rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php:80— MergePhpstanDocTagIntoNativeRector.refactor 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.
ThrowWithPreviousExceptionRector.refactorThrow (cyclomatic 29) rules/CodeQuality/Rector/Catch_/ThrowWithPreviousExceptionRector.php:107— ThrowWithPreviousExceptionRector.refactorThrow has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.refactor (cyclomatic 29) rules/TypeDeclaration/Rector/ClassMethod/AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.php:87— AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.refactor has cyclomatic complexity 29 (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.
DateFuncCallToCarbonRector.refactor (cyclomatic 28) rules/Carbon/Rector/FuncCall/DateFuncCallToCarbonRector.php:61— DateFuncCallToCarbonRector.refactor 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.
NodeFactory.createArrayItem (cyclomatic 27) src/PhpParser/Node/NodeFactory.php:357— NodeFactory.createArrayItem has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ContextNodeVisitor.enterNode (cyclomatic 26) src/PhpParser/NodeVisitor/ContextNodeVisitor.php:70— ContextNodeVisitor.enterNode 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.
RemoveArgumentFromDefaultParentCallRector.refactor (cyclomatic 25) rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:97— RemoveArgumentFromDefaultParentCallRector.refactor 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.
TypeNormalizer.generalizeConstantTypes (cyclomatic 25) rules/Privatization/TypeManipulator/TypeNormalizer.php:69— TypeNormalizer.generalizeConstantTypes 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.
EregToPcreTransformer._ere2pcre (cyclomatic 24) rules/Php70/EregToPcreTransformer.php:93— EregToPcreTransformer._ere2pcre has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RemoveNonExistingVarAnnotationRector.refactor (cyclomatic 22) rules/DeadCode/Rector/Node/RemoveNonExistingVarAnnotationRector.php:106— RemoveNonExistingVarAnnotationRector.refactor 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.
RectorConfigBuilder.withAttributesSets (cyclomatic 22) src/Configuration/RectorConfigBuilder.php:328— RectorConfigBuilder.withAttributesSets has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SimpleNodeDumper.dumpSingleNode (cyclomatic 22) src/CustomRules/SimpleNodeDumper.php:131— SimpleNodeDumper.dumpSingleNode 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.
DeadVarTagValueNodeAnalyzer.isDead (cyclomatic 21) rules/DeadCode/PhpDoc/DeadVarTagValueNodeAnalyzer.php:45— DeadVarTagValueNodeAnalyzer.isDead has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoveDoubleAssignRector.refactor (cyclomatic 21) rules/DeadCode/Rector/Assign/RemoveDoubleAssignRector.php:55— RemoveDoubleAssignRector.refactor 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.
PreparedValueToEarlyReturnRector.refactor (cyclomatic 21) rules/EarlyReturn/Rector/Return_/PreparedValueToEarlyReturnRector.php:95— PreparedValueToEarlyReturnRector.refactor 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.
ObjectTypeSpecifier.narrowToFullyQualifiedOrAliasedObjectType (cyclomatic 21) rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php:53— ObjectTypeSpecifier.narrowToFullyQualifiedOrAliasedObjectType 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.
UnusedImportRemovingPostRector.enterNode (cyclomatic 21) src/PostRector/Rector/UnusedImportRemovingPostRector.php:44— UnusedImportRemovingPostRector.enterNode 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.
ClassPropertyAssignToConstructorPromotionRector.refactor (cyclomatic 20) rules/Php80/Rector/Class_/ClassPropertyAssignToConstructorPromotionRector.php:190— ClassPropertyAssignToConstructorPromotionRector.refactor 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.
StrictArrayParamDimFetchRector.refactor (cyclomatic 20) rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php:103— StrictArrayParamDimFetchRector.refactor 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.
ScalarStringToTypeMapper.mapScalarStringToType (cyclomatic 20) src/StaticTypeMapper/Mapper/ScalarStringToTypeMapper.php:41— ScalarStringToTypeMapper.mapScalarStringToType has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ArrowFunctionAndClosureFirstClassCallableGuard.shouldSkip (cyclomatic 19) rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:51— ArrowFunctionAndClosureFirstClassCallableGuard.shouldSkip 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.
ArrayToFirstClassCallableRector.refactor (cyclomatic 19) rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php:94— ArrayToFirstClassCallableRector.refactor 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.
InlineArrayReturnAssignRector.refactor (cyclomatic 18) rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php:69— InlineArrayReturnAssignRector.refactor 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.
CallCollectionAnalyzer.isExists (cyclomatic 18) rules/DeadCode/NodeAnalyzer/CallCollectionAnalyzer.php:37— CallCollectionAnalyzer.isExists 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.
LivingCodeManipulator.keepLivingCodeFromExpr (cyclomatic 18) rules/DeadCode/NodeManipulator/LivingCodeManipulator.php:55— LivingCodeManipulator.keepLivingCodeFromExpr has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoveUselessAssignFromPropertyPromotionRector.refactor (cyclomatic 18) rules/DeadCode/Rector/ClassMethod/RemoveUselessAssignFromPropertyPromotionRector.php:52— RemoveUselessAssignFromPropertyPromotionRector.refactor 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.
ChangeSwitchToMatchRector.refactor (cyclomatic 18) rules/Php80/Rector/Switch_/ChangeSwitchToMatchRector.php:97— ChangeSwitchToMatchRector.refactor 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.
ExprAnalyzer.isBoolExpr (cyclomatic 18) src/NodeAnalyzer/ExprAnalyzer.php:69— ExprAnalyzer.isBoolExpr has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExprAnalyzer.isExprWithExprPropertyWrappable (cyclomatic 18) src/NodeAnalyzer/ExprAnalyzer.php:88— ExprAnalyzer.isExprWithExprPropertyWrappable has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExplicitReturnNullRector.refactor (cyclomatic 17) rules/CodeQuality/Rector/ClassMethod/ExplicitReturnNullRector.php:105— ExplicitReturnNullRector.refactor 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.
LocallyCalledStaticMethodToNonStaticRector.refactorClassMethod (cyclomatic 17) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:112— LocallyCalledStaticMethodToNonStaticRector.refactorClassMethod 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.
RemoveUnusedVariableAssignRector.resolvedAssignedVariablesByStmtPosition (cyclomatic 17) rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php:231— RemoveUnusedVariableAssignRector.resolvedAssignedVariablesByStmtPosition 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.
AddReturnDocblockForArrayDimAssignedObjectRector.isVariableExclusivelyArrayDimAssigned (cyclomatic 17) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForArrayDimAssignedObjectRector.php:153— AddReturnDocblockForArrayDimAssignedObjectRector.isVariableExclusivelyArrayDimAssigned 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.
BetterStandardPrinter.wrapBinaryOpWithBrackets (cyclomatic 17) src/PhpParser/Printer/BetterStandardPrinter.php:400— BetterStandardPrinter.wrapBinaryOpWithBrackets 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.
ConvertStaticToSelfRector.shouldSkip (cyclomatic 16) rules/CodeQuality/Rector/Class_/ConvertStaticToSelfRector.php:103— ConvertStaticToSelfRector.shouldSkip 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.
ForeachToInArrayRector.refactor (cyclomatic 16) rules/CodeQuality/Rector/Foreach_/ForeachToInArrayRector.php:73— ForeachToInArrayRector.refactor 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.
MakeInheritedMethodVisibilitySameAsParentRector.refactor (cyclomatic 16) rules/CodingStyle/Rector/ClassMethod/MakeInheritedMethodVisibilitySameAsParentRector.php:79— MakeInheritedMethodVisibilitySameAsParentRector.refactor 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.
RemoveUselessTernaryRector.refactor (cyclomatic 16) rules/DeadCode/Rector/Ternary/RemoveUselessTernaryRector.php:58— RemoveUselessTernaryRector.refactor has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SwitchExprsResolver.resolve (cyclomatic 16) rules/Php80/NodeResolver/SwitchExprsResolver.php:21— SwitchExprsResolver.resolve 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.
AddParamBasedOnParentClassMethodRector.refactor (cyclomatic 16) rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php:113— AddParamBasedOnParentClassMethodRector.refactor 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.
AddTypeToConstRector.refactor (cyclomatic 16) rules/Php83/Rector/ClassConst/AddTypeToConstRector.php:85— AddTypeToConstRector.refactor 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.
AddEscapeArgumentRector.refactor (cyclomatic 16) rules/Php84/Rector/FuncCall/AddEscapeArgumentRector.php:41— AddEscapeArgumentRector.refactor 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.
ArrayFirstLastRector.refactorArrayValuesPattern (cyclomatic 16) rules/Php85/Rector/ArrayDimFetch/ArrayFirstLastRector.php:95— ArrayFirstLastRector.refactorArrayValuesPattern 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.
ArrayCallbackParamTypeResolver.refactorFirstParamType (cyclomatic 16) rules/TypeDeclaration/NodeAnalyzer/ArrayCallbackParamTypeResolver.php:49— ArrayCallbackParamTypeResolver.refactorFirstParamType has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AddReturnDocblockForScalarArrayFromAssignsRector.resolveScalarArrayTypeForVariable (cyclomatic 16) rules/TypeDeclaration/Rector/ClassMethod/AddReturnDocblockForScalarArrayFromAssignsRector.php:176— AddReturnDocblockForScalarArrayFromAssignsRector.resolveScalarArrayTypeForVariable 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.
AddClosureParamTypeFromIterableMethodCallRector.refactor (cyclomatic 16) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeFromIterableMethodCallRector.php:94— AddClosureParamTypeFromIterableMethodCallRector.refactor 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.
TypedPropertyFromAssignsRector.refactor (cyclomatic 16) rules/TypeDeclaration/Rector/Property/TypedPropertyFromAssignsRector.php:149— TypedPropertyFromAssignsRector.refactor 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.
ChangedNodeScopeRefresher.resolveStmts (cyclomatic 16) src/Application/ChangedNodeScopeRefresher.php:146— ChangedNodeScopeRefresher.resolveStmts has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DoctrineAnnotationDecorator.createValue (cyclomatic 16) src/BetterPhpDocParser/NodeDecorator/DoctrineAnnotationDecorator.php:157— DoctrineAnnotationDecorator.createValue 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.
ExprAnalyzer.isNonTypedFromParam (cyclomatic 16) src/NodeAnalyzer/ExprAnalyzer.php:102— ExprAnalyzer.isNonTypedFromParam has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoveArgumentFromDefaultParentCallRector.refactor (cognitive 72) rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:97— RemoveArgumentFromDefaultParentCallRector.refactor has cognitive complexity 72 (threshold 15). Drivers by points: if/else 20 (62 pts), loops 4 (10 pts) (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PHPStanNodeScopeResolver.fillScope (cognitive 66) src/NodeTypeResolver/PHPStan/Scope/PHPStanNodeScopeResolver.php:144— PHPStanNodeScopeResolver.fillScope has cognitive complexity 66 (threshold 15). Drivers by points: if/else 30 (36 pts), boolean chains 28, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TypeNormalizer.generalizeConstantTypes (cognitive 54) rules/Privatization/TypeManipulator/TypeNormalizer.php:69— TypeNormalizer.generalizeConstantTypes has cognitive complexity 54 (threshold 15). Drivers by points: if/else 19 (42 pts), loops 2 (6 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 29). 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.
RemoveNonExistingVarAnnotationRector.refactor (cognitive 46) rules/DeadCode/Rector/Node/RemoveNonExistingVarAnnotationRector.php:106— RemoveNonExistingVarAnnotationRector.refactor has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (36 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RectorConfigBuilder.__invoke (cognitive 46) src/Configuration/RectorConfigBuilder.php:151— RectorConfigBuilder.__invoke has cognitive complexity 46 (threshold 15). Drivers by points: if/else 33 (36 pts), loops 5 (6 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
MergePhpstanDocTagIntoNativeRector.refactor (cognitive 39) rules/TypeDeclarationDocblocks/Rector/Property/MergePhpstanDocTagIntoNativeRector.php:80— MergePhpstanDocTagIntoNativeRector.refactor has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 12, loops 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateFuncCallToCarbonRector.refactor (cognitive 38) rules/Carbon/Rector/FuncCall/DateFuncCallToCarbonRector.php:61— DateFuncCallToCarbonRector.refactor has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 12 (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.
CallCollectionAnalyzer.isExists (cognitive 37) rules/DeadCode/NodeAnalyzer/CallCollectionAnalyzer.php:37— CallCollectionAnalyzer.isExists has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 5, loops 2 (5 pts), ternaries 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddParamFromDimFetchKeyUseRector.refactor (cognitive 37) rules/TypeDeclaration/Rector/ClassMethod/AddParamFromDimFetchKeyUseRector.php:90— AddParamFromDimFetchKeyUseRector.refactor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddReturnDocblockForArrayDimAssignedObjectRector.isVariableExclusivelyArrayDimAssigned (cognitive 34) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForArrayDimAssignedObjectRector.php:153— AddReturnDocblockForArrayDimAssignedObjectRector.isVariableExclusivelyArrayDimAssigned has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 4 (nesting depth added 18). 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.
UnusedImportRemovingPostRector.enterNode (cognitive 33) src/PostRector/Rector/UnusedImportRemovingPostRector.php:44— UnusedImportRemovingPostRector.enterNode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 4 (7 pts), boolean chains 5, loops 2 (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.
ThrowWithPreviousExceptionRector.refactorThrow (cognitive 32) rules/CodeQuality/Rector/Catch_/ThrowWithPreviousExceptionRector.php:107— ThrowWithPreviousExceptionRector.refactorThrow has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 10, ternaries 3 (8 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.
RemoveDoubleAssignRector.refactor (cognitive 32) rules/DeadCode/Rector/Assign/RemoveDoubleAssignRector.php:55— RemoveDoubleAssignRector.refactor has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 5, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PreparedValueToEarlyReturnRector.refactor (cognitive 32) rules/EarlyReturn/Rector/Return_/PreparedValueToEarlyReturnRector.php:95— PreparedValueToEarlyReturnRector.refactor has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 7, 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.
ChangeSwitchToMatchRector.refactor (cognitive 32) rules/Php80/Rector/Switch_/ChangeSwitchToMatchRector.php:97— ChangeSwitchToMatchRector.refactor has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveUnusedVariableAssignRector.resolvedAssignedVariablesByStmtPosition (cognitive 31) rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php:231— RemoveUnusedVariableAssignRector.resolvedAssignedVariablesByStmtPosition has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveParentCallWithoutParentRector.refactor (cognitive 31) rules/DeadCode/Rector/StaticCall/RemoveParentCallWithoutParentRector.php:82— RemoveParentCallWithoutParentRector.refactor has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 2 (3 pts), boolean chains 2 (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.
EregToPcreTransformer._ere2pcre (cognitive 31) rules/Php70/EregToPcreTransformer.php:93— EregToPcreTransformer._ere2pcre has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 3, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObjectTypeSpecifier.narrowToFullyQualifiedOrAliasedObjectType (cognitive 31) rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php:53— ObjectTypeSpecifier.narrowToFullyQualifiedOrAliasedObjectType has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.refactor (cognitive 30) rules/TypeDeclaration/Rector/ClassMethod/AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.php:87— AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.refactor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 4, loops 2, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
InlineArrayReturnAssignRector.refactor (cognitive 29) rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php:69— InlineArrayReturnAssignRector.refactor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (5 pts), boolean chains 1, error handling 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.
ForeachToInArrayRector.refactor (cognitive 29) rules/CodeQuality/Rector/Foreach_/ForeachToInArrayRector.php:73— ForeachToInArrayRector.refactor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MakeInheritedMethodVisibilitySameAsParentRector.refactor (cognitive 29) rules/CodingStyle/Rector/ClassMethod/MakeInheritedMethodVisibilitySameAsParentRector.php:79— MakeInheritedMethodVisibilitySameAsParentRector.refactor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 3 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeValueResolver.resolve (cognitive 29) rules/Php80/Rector/Class_/AttributeValueResolver.php:19— AttributeValueResolver.resolve has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (26 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ClassPropertyAssignToConstructorPromotionRector.refactor (cognitive 29) rules/Php80/Rector/Class_/ClassPropertyAssignToConstructorPromotionRector.php:190— ClassPropertyAssignToConstructorPromotionRector.refactor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnnotationToAttributeIntegerValueCaster.castAttributeTypes (cognitive 29) src/PhpAttribute/NodeFactory/AnnotationToAttributeIntegerValueCaster.php:32— AnnotationToAttributeIntegerValueCaster.castAttributeTypes has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (3 pts), ternaries 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.
AddTypeToConstRector.refactor (cognitive 28) rules/Php83/Rector/ClassConst/AddTypeToConstRector.php:85— AddTypeToConstRector.refactor has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColonAfterSwitchCaseRector.refactor (cognitive 28) rules/Php85/Rector/Switch_/ColonAfterSwitchCaseRector.php:42— ColonAfterSwitchCaseRector.refactor has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContextNodeVisitor.enterNode (cognitive 28) src/PhpParser/NodeVisitor/ContextNodeVisitor.php:70— ContextNodeVisitor.enterNode has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 9, loops 2 (4 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoveDefaultValueFromAssignedPropertyRector.refactor (cognitive 27) rules/DeadCode/Rector/Property/RemoveDefaultValueFromAssignedPropertyRector.php:82— RemoveDefaultValueFromAssignedPropertyRector.refactor has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimplifyForeachToCoalescingRector.refactor (cognitive 26) rules/CodeQuality/Rector/Foreach_/SimplifyForeachToCoalescingRector.php:55— SimplifyForeachToCoalescingRector.refactor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (25 pts), 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.
SimplifyIfNullableReturnRector.refactor (cognitive 26) rules/CodeQuality/Rector/If_/SimplifyIfNullableReturnRector.php:99— SimplifyIfNullableReturnRector.refactor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EregToPcreTransformer.processSquareBracket (cognitive 26) rules/Php70/EregToPcreTransformer.php:206— EregToPcreTransformer.processSquareBracket has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 7, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwitchExprsResolver.resolve (cognitive 26) rules/Php80/NodeResolver/SwitchExprsResolver.php:21— SwitchExprsResolver.resolve has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 3 (5 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.
ClassMethodArrayDocblockParamFromLocalCallsRector.refactor (cognitive 26) rules/TypeDeclarationDocblocks/Rector/Class_/ClassMethodArrayDocblockParamFromLocalCallsRector.php:95— ClassMethodArrayDocblockParamFromLocalCallsRector.refactor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RectorNodeTraverser.traverseArray (cognitive 26) src/PhpParser/NodeTraverser/RectorNodeTraverser.php:82— RectorNodeTraverser.traverseArray has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 3 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddParamBasedOnParentClassMethodRector.refactor (cognitive 25) rules/Php80/Rector/ClassMethod/AddParamBasedOnParentClassMethodRector.php:113— AddParamBasedOnParentClassMethodRector.refactor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 2, 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.
KnownMagicClassMethodTypeRector.refactor (cognitive 25) rules/TypeDeclaration/Rector/ClassMethod/KnownMagicClassMethodTypeRector.php:68— KnownMagicClassMethodTypeRector.refactor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StrictArrayParamDimFetchRector.refactor (cognitive 25) rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php:103— StrictArrayParamDimFetchRector.refactor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddParamArrayDocblockFromDimFetchAccessRector.refactor (cognitive 25) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromDimFetchAccessRector.php:95— AddParamArrayDocblockFromDimFetchAccessRector.refactor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NewlineBeforeNewAssignSetRector.resolveCurrentStmtVariableName (cognitive 24) rules/CodingStyle/Rector/ClassMethod/NewlineBeforeNewAssignSetRector.php:108— NewlineBeforeNewAssignSetRector.resolveCurrentStmtVariableName has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (5 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 14). 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.
AnnotationToAttributeRector.processDoctrineAnnotationClasses (cognitive 24) rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:259— AnnotationToAttributeRector.processDoctrineAnnotationClasses has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypedPropertyFromAssignsRector.refactor (cognitive 24) rules/TypeDeclaration/Rector/Property/TypedPropertyFromAssignsRector.php:149— TypedPropertyFromAssignsRector.refactor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 3, 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.
ConsecutiveNullCompareReturnsToNullCoalesceQueueRector.refactor (cognitive 23) rules/CodeQuality/Rector/If_/ConsecutiveNullCompareReturnsToNullCoalesceQueueRector.php:80— ConsecutiveNullCompareReturnsToNullCoalesceQueueRector.refactor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 2, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FixClassCaseSensitivityVarDocblockRector.resolveExistingClassName (cognitive 23) rules/CodeQuality/Rector/Property/FixClassCaseSensitivityVarDocblockRector.php:123— FixClassCaseSensitivityVarDocblockRector.resolveExistingClassName has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddReturnDocblockForScalarArrayFromAssignsRector.resolveScalarArrayTypeForVariable (cognitive 23) rules/TypeDeclaration/Rector/ClassMethod/AddReturnDocblockForScalarArrayFromAssignsRector.php:176— AddReturnDocblockForScalarArrayFromAssignsRector.resolveScalarArrayTypeForVariable has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddReturnTypeFromTryCatchTypeRector.refactor (cognitive 23) rules/TypeDeclaration/Rector/ClassMethod/AddReturnTypeFromTryCatchTypeRector.php:97— AddReturnTypeFromTryCatchTypeRector.refactor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 3 (4 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.
AddArrayFunctionClosureParamTypeRector.refactor (cognitive 23) rules/TypeDeclaration/Rector/FuncCall/AddArrayFunctionClosureParamTypeRector.php:56— AddArrayFunctionClosureParamTypeRector.refactor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddArrowFunctionParamArrayWhereDimFetchRector.refactor (cognitive 23) rules/TypeDeclaration/Rector/FuncCall/AddArrowFunctionParamArrayWhereDimFetchRector.php:59— AddArrowFunctionParamArrayWhereDimFetchRector.refactor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DoctrineAnnotationDecorator.decorate (cognitive 23) src/BetterPhpDocParser/NodeDecorator/DoctrineAnnotationDecorator.php:72— DoctrineAnnotationDecorator.decorate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, 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.
SimpleNodeDumper.dumpSingleNode (cognitive 23) src/CustomRules/SimpleNodeDumper.php:131— SimpleNodeDumper.dumpSingleNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, 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.
RectorNodeTraverser.traverseNode (cognitive 23) src/PhpParser/NodeTraverser/RectorNodeTraverser.php:39— RectorNodeTraverser.traverseNode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (3 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.
InlineConstructorDefaultToPropertyRector.refactor (cognitive 22) rules/CodeQuality/Rector/Class_/InlineConstructorDefaultToPropertyRector.php:89— InlineConstructorDefaultToPropertyRector.refactor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IssetOnPropertyObjectToPropertyExistsRector.refactor (cognitive 22) rules/CodeQuality/Rector/Isset_/IssetOnPropertyObjectToPropertyExistsRector.php:90— IssetOnPropertyObjectToPropertyExistsRector.refactor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeadVarTagValueNodeAnalyzer.isDead (cognitive 22) rules/DeadCode/PhpDoc/DeadVarTagValueNodeAnalyzer.php:45— DeadVarTagValueNodeAnalyzer.isDead has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (16 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.
RemoveUselessAssignFromPropertyPromotionRector.refactor (cognitive 22) rules/DeadCode/Rector/ClassMethod/RemoveUselessAssignFromPropertyPromotionRector.php:52— RemoveUselessAssignFromPropertyPromotionRector.refactor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, loops 3 (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.
RemoveDuplicatedCaseInSwitchRector.removeDuplicatedCases (cognitive 22) rules/DeadCode/Rector/Switch_/RemoveDuplicatedCaseInSwitchRector.php:91— RemoveDuplicatedCaseInSwitchRector.removeDuplicatedCases has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (7 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.
SleepToSerializeRector.refactor (cognitive 22) rules/Php85/Rector/Class_/SleepToSerializeRector.php:84— SleepToSerializeRector.refactor has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SetUpAssignedPropertyTyper.refactorClass (cognitive 22) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:72— SetUpAssignedPropertyTyper.refactorClass has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 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.
ObjectTypeSpecifier.matchShortenedObjectType (cognitive 22) rules/TypeDeclaration/PHPStan/ObjectTypeSpecifier.php:161— ObjectTypeSpecifier.matchShortenedObjectType has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (3 pts), 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.
LocalVariableScopeNodeVisitor.enterNode (cognitive 22) src/PhpParser/NodeVisitor/LocalVariableScopeNodeVisitor.php:34— LocalVariableScopeNodeVisitor.enterNode has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (7 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.
InlineArrayReturnAssignRector.areAssignExclusiveToDimFetchVariable (cognitive 21) rules/CodeQuality/Rector/ClassMethod/InlineArrayReturnAssignRector.php:134— InlineArrayReturnAssignRector.areAssignExclusiveToDimFetchVariable has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PrivateMethodParamRemover.removeCallerArgs (cognitive 21) rules/DeadCode/NodeManipulator/PrivateMethodParamRemover.php:89— PrivateMethodParamRemover.removeCallerArgs has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (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.
Php4ConstructorRector.refactor (cognitive 21) rules/Php70/Rector/ClassMethod/Php4ConstructorRector.php:78— Php4ConstructorRector.refactor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 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.
IfIssetToCoalescingRector.refactor (cognitive 21) rules/Php70/Rector/StmtsAwareInterface/IfIssetToCoalescingRector.php:68— IfIssetToCoalescingRector.refactor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnnotationToAttributeRector.resolveTrailingComment (cognitive 21) rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:316— AnnotationToAttributeRector.resolveTrailingComment has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeachToArrayAnyAllFactory.refactorBooleanAssignmentPattern (cognitive 21) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:85— ForeachToArrayAnyAllFactory.refactorBooleanAssignmentPattern has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeachToArrayFindFactory.createArrayFindAssign (cognitive 21) rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:75— ForeachToArrayFindFactory.createArrayFindAssign has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayFirstLastRector.refactorArrayValuesPattern (cognitive 21) rules/Php85/Rector/ArrayDimFetch/ArrayFirstLastRector.php:95— ArrayFirstLastRector.refactorArrayValuesPattern has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StrictTypeSafetyChecker.areArgsSafe (cognitive 21) rules/TypeDeclaration/NodeAnalyzer/StrictTypeSafetyChecker.php:110— StrictTypeSafetyChecker.areArgsSafe has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypedPropertyFromStrictConstructorRector.refactor (cognitive 21) rules/TypeDeclaration/Rector/Property/TypedPropertyFromStrictConstructorRector.php:123— TypedPropertyFromStrictConstructorRector.refactor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (20 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.
OnlyRuleResolver.resolve (cognitive 21) src/Configuration/OnlyRuleResolver.php:27— OnlyRuleResolver.resolve has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RectorConfigBuilder.withAttributesSets (cognitive 21) src/Configuration/RectorConfigBuilder.php:328— RectorConfigBuilder.withAttributesSets has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12, boolean chains 9. 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.
NodeFactory.createArrayItem (cognitive 21) src/PhpParser/Node/NodeFactory.php:357— NodeFactory.createArrayItem has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 16, if/else 5. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LocallyCalledStaticMethodToNonStaticRector.refactorClassMethod (cognitive 20) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:112— LocallyCalledStaticMethodToNonStaticRector.refactorClassMethod has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ClosureFromCallableToFirstClassCallableRector.refactor (cognitive 20) rules/CodingStyle/Rector/FuncCall/ClosureFromCallableToFirstClassCallableRector.php:44— ClosureFromCallableToFirstClassCallableRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LivingCodeManipulator.keepLivingCodeFromExpr (cognitive 20) rules/DeadCode/NodeManipulator/LivingCodeManipulator.php:55— LivingCodeManipulator.keepLivingCodeFromExpr has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
RemoveUnusedForeachKeyRector.refactor (cognitive 20) rules/DeadCode/Rector/Foreach_/RemoveUnusedForeachKeyRector.php:79— RemoveUnusedForeachKeyRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveNextSameValueConditionRector.refactor (cognitive 20) rules/DeadCode/Rector/Stmt/RemoveNextSameValueConditionRector.php:78— RemoveNextSameValueConditionRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 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.
PrivatizeFinalClassPropertyRector.refactor (cognitive 20) rules/Privatization/Rector/Property/PrivatizeFinalClassPropertyRector.php:68— PrivatizeFinalClassPropertyRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MergeDateTimePropertyTypeDeclarationRector.refactor (cognitive 20) rules/TypeDeclaration/Rector/Class_/MergeDateTimePropertyTypeDeclarationRector.php:66— MergeDateTimePropertyTypeDeclarationRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypedPropertyFromDocblockSetUpDefinedRector.refactor (cognitive 20) rules/TypeDeclaration/Rector/Class_/TypedPropertyFromDocblockSetUpDefinedRector.php:107— TypedPropertyFromDocblockSetUpDefinedRector.refactor has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 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.
ScalarStringToTypeMapper.mapScalarStringToType (cognitive 20) src/StaticTypeMapper/Mapper/ScalarStringToTypeMapper.php:41— ScalarStringToTypeMapper.mapScalarStringToType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18 (19 pts), loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VariableDimFetchAssignResolver.resolveFromStmtsAndVariable (cognitive 19) rules/CodeQuality/NodeAnalyzer/VariableDimFetchAssignResolver.php:35— VariableDimFetchAssignResolver.resolveFromStmtsAndVariable has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExplicitReturnNullRector.refactor (cognitive 19) rules/CodeQuality/Rector/ClassMethod/ExplicitReturnNullRector.php:105— ExplicitReturnNullRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 3, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ArrowFunctionAndClosureFirstClassCallableGuard.shouldSkip (cognitive 19) rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:51— ArrowFunctionAndClosureFirstClassCallableGuard.shouldSkip has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 2, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RemoveUnusedPrivateMethodRector.refactor (cognitive 19) rules/DeadCode/Rector/ClassMethod/RemoveUnusedPrivateMethodRector.php:89— RemoveUnusedPrivateMethodRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveNullNamedArgOnNullDefaultParamRector.refactor (cognitive 19) rules/DeadCode/Rector/MethodCall/RemoveNullNamedArgOnNullDefaultParamRector.php:79— RemoveNullNamedArgOnNullDefaultParamRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveConditionExactReturnRector.refactor (cognitive 19) rules/DeadCode/Rector/Stmt/RemoveConditionExactReturnRector.php:66— RemoveConditionExactReturnRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveUnusedVariableInCatchRector.refactor (cognitive 19) rules/Php80/Rector/Catch_/RemoveUnusedVariableInCatchRector.php:78— RemoveUnusedVariableInCatchRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), ternaries 1 (3 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.
ArrayToFirstClassCallableRector.refactor (cognitive 19) rules/Php81/Rector/Array_/ArrayToFirstClassCallableRector.php:94— ArrayToFirstClassCallableRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 4 (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.
AddEscapeArgumentRector.refactor (cognitive 19) rules/Php84/Rector/FuncCall/AddEscapeArgumentRector.php:41— AddEscapeArgumentRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4 (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.
AddClosureParamTypeFromIterableMethodCallRector.refactor (cognitive 19) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeFromIterableMethodCallRector.php:94— AddClosureParamTypeFromIterableMethodCallRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 2, ternaries 1 (2 pts), boolean chains 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.
PropertyGetterFinder.find (cognitive 19) rules/TypeDeclarationDocblocks/NodeFinder/PropertyGetterFinder.php:23— PropertyGetterFinder.find has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
DocblockVarArrayFromPropertyDefaultsRector.refactor (cognitive 19) rules/TypeDeclarationDocblocks/Rector/Class_/DocblockVarArrayFromPropertyDefaultsRector.php:72— DocblockVarArrayFromPropertyDefaultsRector.refactor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 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.
FileProcessor.processFile (cognitive 19) src/Application/FileProcessor.php:91— FileProcessor.processFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RectorRegistry.sortByPrecededRule (cognitive 19) src/Application/RectorRegistry.php:150— RectorRegistry.sortByPrecededRule has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5 (8 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.
ProcessCommand.execute (cognitive 19) src/Console/Command/ProcessCommand.php:128— ProcessCommand.execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 4 (8 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeTypeResolver.getType (cognitive 19) src/NodeTypeResolver/NodeTypeResolver.php:177— NodeTypeResolver.getType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ValueResolver.getValue (cognitive 19) src/PhpParser/Node/Value/ValueResolver.php:93— ValueResolver.getValue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConvertStaticToSelfRector.shouldSkip (cognitive 18) rules/CodeQuality/Rector/Class_/ConvertStaticToSelfRector.php:103— ConvertStaticToSelfRector.shouldSkip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (8 pts), match/switch 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimplifyUselessVariableRector.refactor (cognitive 18) rules/CodeQuality/Rector/FunctionLike/SimplifyUselessVariableRector.php:70— SimplifyUselessVariableRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 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.
RemoveUnusedPromotedPropertyRector.refactor (cognitive 18) rules/DeadCode/Rector/ClassMethod/RemoveUnusedPromotedPropertyRector.php:120— RemoveUnusedPromotedPropertyRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveOverriddenAssignBeforeIfElseRector.refactor (cognitive 18) rules/DeadCode/Rector/If_/RemoveOverriddenAssignBeforeIfElseRector.php:96— RemoveOverriddenAssignBeforeIfElseRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RandomFunctionRector.refactor (cognitive 18) rules/Php70/Rector/FuncCall/RandomFunctionRector.php:48— RandomFunctionRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 2, loops 1 (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.
PromotedPropertyCandidateResolver.matchPropertyPromotionCandidate (cognitive 18) rules/Php80/NodeAnalyzer/PromotedPropertyCandidateResolver.php:120— PromotedPropertyCandidateResolver.matchPropertyPromotionCandidate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 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.
PropertyTypeFromStrictSetterGetterRector.refactor (cognitive 18) rules/TypeDeclaration/Rector/Class_/PropertyTypeFromStrictSetterGetterRector.php:122— PropertyTypeFromStrictSetterGetterRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypedPropertyFromCreateMockAssignRector.refactor (cognitive 18) rules/TypeDeclaration/Rector/Class_/TypedPropertyFromCreateMockAssignRector.php:84— TypedPropertyFromCreateMockAssignRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (17 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.
TypedStaticPropertyInBehatContextRector.refactor (cognitive 18) rules/TypeDeclaration/Rector/Class_/TypedStaticPropertyInBehatContextRector.php:75— TypedStaticPropertyInBehatContextRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddClosureParamTypeForArrayMapRector.refactor (cognitive 18) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php:60— AddClosureParamTypeForArrayMapRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddReturnDocblockForCommonObjectDenominatorRector.refactor (cognitive 18) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForCommonObjectDenominatorRector.php:117— AddReturnDocblockForCommonObjectDenominatorRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocblockGetterReturnArrayFromPropertyDocblockVarRector.refactor (cognitive 18) rules/TypeDeclarationDocblocks/Rector/ClassMethod/DocblockGetterReturnArrayFromPropertyDocblockVarRector.php:91— DocblockGetterReturnArrayFromPropertyDocblockVarRector.refactor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DoctrineAnnotationDecorator.createValue (cognitive 18) src/BetterPhpDocParser/NodeDecorator/DoctrineAnnotationDecorator.php:157— DoctrineAnnotationDecorator.createValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, ternaries 2 (5 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeTypeResolver.isObjectType (cognitive 18) src/NodeTypeResolver/NodeTypeResolver.php:134— NodeTypeResolver.isObjectType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
WorkerCommandLineFactory.mirrorCommandOptions (cognitive 18) src/Parallel/Command/WorkerCommandLineFactory.php:155— WorkerCommandLineFactory.mirrorCommandOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 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.
UseAliasNameMatcher.match (cognitive 18) src/PhpAttribute/UseAliasNameMatcher.php:20— UseAliasNameMatcher.match has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 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.
UnusedImportRemovingPostRector.isUseImportUsed (cognitive 18) src/PostRector/Rector/UnusedImportRemovingPostRector.php:203— UnusedImportRemovingPostRector.isUseImportUsed has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1, 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.
StaticTypeMapper.styleTypeNode (cognitive 18) src/StaticTypeMapper/StaticTypeMapper.php:131— StaticTypeMapper.styleTypeNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (7 pts), loops 2 (5 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocallyCalledStaticMethodToNonStaticRector.isClassMethodCalledInAnotherStaticClassMethod (cognitive 17) rules/CodeQuality/Rector/ClassMethod/LocallyCalledStaticMethodToNonStaticRector.php:179— LocallyCalledStaticMethodToNonStaticRector.isClassMethodCalledInAnotherStaticClassMethod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OptionalParametersAfterRequiredRector.processParam (cognitive 17) rules/CodeQuality/Rector/ClassMethod/OptionalParametersAfterRequiredRector.php:129— OptionalParametersAfterRequiredRector.processParam has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimplifyIfNotNullReturnRector.refactor (cognitive 17) rules/CodeQuality/Rector/If_/SimplifyIfNotNullReturnRector.php:62— SimplifyIfNotNullReturnRector.refactor 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.
NumberCompareToMaxFuncCallRector.refactor (cognitive 17) rules/CodeQuality/Rector/Ternary/NumberCompareToMaxFuncCallRector.php:53— NumberCompareToMaxFuncCallRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NoDiscardCallAnalyzer.isNoDiscardCall (cognitive 17) rules/DeadCode/NodeAnalyzer/NoDiscardCallAnalyzer.php:37— NoDiscardCallAnalyzer.isNoDiscardCall has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveEmptyClassMethodRector.refactor (cognitive 17) rules/DeadCode/Rector/ClassMethod/RemoveEmptyClassMethodRector.php:84— RemoveEmptyClassMethodRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveNullArgOnNullDefaultParamRector.refactor (cognitive 17) rules/DeadCode/Rector/MethodCall/RemoveNullArgOnNullDefaultParamRector.php:80— RemoveNullArgOnNullDefaultParamRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForeachToArrayAnyAllFactory.refactorEarlyReturnPattern (cognitive 17) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:141— ForeachToArrayAnyAllFactory.refactorEarlyReturnPattern has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WrapReturnRector.refactor (cognitive 17) rules/Transform/Rector/ClassMethod/WrapReturnRector.php:60— WrapReturnRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddParamTypeSplFixedArrayRector.refactor (cognitive 17) rules/TypeDeclaration/Rector/FunctionLike/AddParamTypeSplFixedArrayRector.php:89— AddParamTypeSplFixedArrayRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypedPropertyFromStrictSetUpRector.refactor (cognitive 17) rules/TypeDeclaration/Rector/Property/TypedPropertyFromStrictSetUpRector.php:93— TypedPropertyFromStrictSetUpRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReturnStrictTypeAnalyzer.collectStrictReturnTypes (cognitive 17) rules/TypeDeclaration/TypeAnalyzer/ReturnStrictTypeAnalyzer.php:61— ReturnStrictTypeAnalyzer.collectStrictReturnTypes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 6, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddVarArrayDocblockFromDimFetchAssignRector.refactor (cognitive 17) rules/TypeDeclarationDocblocks/Rector/Class_/AddVarArrayDocblockFromDimFetchAssignRector.php:97— AddVarArrayDocblockFromDimFetchAssignRector.refactor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ApplicationFileProcessor.processFiles (cognitive 17) REDACTED:150— ApplicationFileProcessor.processFiles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExprAnalyzer.isBoolExpr (cognitive 17) src/NodeAnalyzer/ExprAnalyzer.php:69— ExprAnalyzer.isBoolExpr has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 17. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExprAnalyzer.isExprWithExprPropertyWrappable (cognitive 17) src/NodeAnalyzer/ExprAnalyzer.php:88— ExprAnalyzer.isExprWithExprPropertyWrappable has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 14, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParentClassMethodTypeOverrideGuard.resolveParentClassMethod (cognitive 17) src/VendorLocker/ParentClassMethodTypeOverrideGuard.php:120— ParentClassMethodTypeOverrideGuard.resolveParentClassMethod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpVersionedFilter.filter (cognitive 17) src/VersionBonding/PhpVersionedFilter.php:35— PhpVersionedFilter.filter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArgumentAdderRector.shouldSkipParameter (cognitive 16) rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php:218— ArgumentAdderRector.shouldSkipParameter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrowFunctionAndClosureFirstClassCallableGuard.isNotUsingSameParamsForArgs (cognitive 16) rules/CodingStyle/Guard/ArrowFunctionAndClosureFirstClassCallableGuard.php:212— ArrowFunctionAndClosureFirstClassCallableGuard.isNotUsingSameParamsForArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FunctionFirstClassCallableRector.refactor (cognitive 16) rules/CodingStyle/Rector/FuncCall/FunctionFirstClassCallableRector.php:59— FunctionFirstClassCallableRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (3 pts), boolean chains 2, loops 2, error handling 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.
RemoveUselessAliasInUseStatementRector.refactor (cognitive 16) rules/CodingStyle/Rector/Stmt/RemoveUselessAliasInUseStatementRector.php:41— RemoveUselessAliasInUseStatementRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OverriddenParameterResolver.resolve (cognitive 16) rules/DeadCode/NodeCollector/OverriddenParameterResolver.php:42— OverriddenParameterResolver.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RemoveArgumentFromDefaultParentCallRector.hasParentStaticCall (cognitive 16) rules/DeadCode/Rector/ClassMethod/RemoveArgumentFromDefaultParentCallRector.php:187— RemoveArgumentFromDefaultParentCallRector.hasParentStaticCall has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NarrowObjectReturnTypeRector.refactor (cognitive 16) rules/TypeDeclaration/Rector/ClassMethod/NarrowObjectReturnTypeRector.php:123— NarrowObjectReturnTypeRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NumericReturnTypeFromStrictScalarReturnsRector.refactor (cognitive 16) rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictScalarReturnsRector.php:78— NumericReturnTypeFromStrictScalarReturnsRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PropertyTypeFromStrictSetterGetterRector.decorateDefaultExpr (cognitive 16) rules/TypeDeclaration/Rector/Class_/PropertyTypeFromStrictSetterGetterRector.php:215— PropertyTypeFromStrictSetterGetterRector.decorateDefaultExpr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (16 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.
DataProviderNodes.getClassMethods (cognitive 16) rules/TypeDeclaration/ValueObject/DataProviderNodes.php:50— DataProviderNodes.getClassMethods has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 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.
AddParamArrayDocblockFromAssignsParamToParamReferenceRector.refactor (cognitive 16) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromAssignsParamToParamReferenceRector.php:81— AddParamArrayDocblockFromAssignsParamToParamReferenceRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddReturnDocblockForJsonArrayRector.isJsonDecodeToArray (cognitive 16) rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForJsonArrayRector.php:121— AddReturnDocblockForJsonArrayRector.isJsonDecodeToArray has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (16 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.
DocblockVarArrayFromGetterReturnRector.refactor (cognitive 16) rules/TypeDeclarationDocblocks/Rector/Class_/DocblockVarArrayFromGetterReturnRector.php:88— DocblockVarArrayFromGetterReturnRector.refactor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhpDocInfoPrinter.replaceOpaqueChildren (cognitive 16) src/BetterPhpDocParser/Printer/PhpDocInfoPrinter.php:138— PhpDocInfoPrinter.replaceOpaqueChildren has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (5 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExprAnalyzer.isNonTypedFromParam (cognitive 16) src/NodeAnalyzer/ExprAnalyzer.php:102— ExprAnalyzer.isNonTypedFromParam has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassDependencyManipulator.addPromotedProperty (cognitive 16) src/NodeManipulator/ClassDependencyManipulator.php:203— ClassDependencyManipulator.addPromotedProperty has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (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.
BetterStandardPrinter.wrapBinaryOpWithBrackets (cognitive 16) src/PhpParser/Printer/BetterStandardPrinter.php:400— BetterStandardPrinter.wrapBinaryOpWithBrackets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 7. 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.
RectorConfigValidator.ensureRectorRulesExist (cognitive 16) src/Validation/RectorConfigValidator.php:27— RectorConfigValidator.ensureRectorRulesExist has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 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.
Near-duplicate member pair (41 shared lines) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:87— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:87-136 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:77-126 — These two members are variants of one another: 41 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 (49 corresponding lines) · ×1
Edited copy of a member (49 corresponding lines) rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:74— rules/TypeDeclaration/NodeAnalyzer/SetUpAssignedPropertyTyper.php:74-124 | rules/TypeDeclaration/Rector/Class_/TypedPropertyFromDocblockSetUpDefinedRector.php:110-158 — These two members are one piece of code written twice and then edited apart: 49 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 (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php:92— rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php:92-136 | rules/DeadCode/Rector/ClassMethod/RemoveUselessUnionReturnDocblockRector.php:80-121 — These two members are one piece of code written twice and then edited apart: 42 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 (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:185— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:185-211 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:130-160 — These two members are one piece of code written twice and then edited apart: 27 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) rules/DeadCode/Rector/MethodCall/RemoveNullArgOnNullDefaultParamRector.php:82— rules/DeadCode/Rector/MethodCall/RemoveNullArgOnNullDefaultParamRector.php:82-122 | rules/DeadCode/Rector/MethodCall/RemoveNullNamedArgOnNullDefaultParamRector.php:81-127 — These two members are one piece of code written twice and then edited apart: 41 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 (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:157— rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:157-191 | rules/Php81/Rector/Property/ReadOnlyPropertyRector.php:214-249 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) rules/TypeDeclarationDocblocks/Rector/ClassMethod/DocblockGetterReturnArrayFromPropertyDocblockVarRector.php:93— rules/TypeDeclarationDocblocks/Rector/ClassMethod/DocblockGetterReturnArrayFromPropertyDocblockVarRector.php:93-129 | rules/TypeDeclarationDocblocks/Rector/Class_/DocblockVarArrayFromGetterReturnRector.php:90-125 — These two members are one piece of code written twice and then edited apart: 36 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:82— rules/TypeDeclaration/Rector/Class_/ObjectTypedPropertyFromJMSSerializerAttributeTypeRector.php:82-109 | rules/TypeDeclaration/Rector/Class_/ScalarTypedPropertyFromJMSSerializerAttributeTypeRector.php:88-115 — These two members are one piece of code written twice and then edited apart: 28 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) rules/TypeDeclaration/Rector/ClassLike/AddVoidReturnTypeWhereNoReturnRector.php:74— rules/TypeDeclaration/Rector/ClassLike/AddVoidReturnTypeWhereNoReturnRector.php:74-100 | rules/TypeDeclaration/Rector/Class_/AddTestsVoidReturnTypeWhereNoReturnRector.php:70-94 — 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 copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php:44— rules/TypeDeclaration/NodeManipulator/AddUnionReturnType.php:44-67 | rules/TypeDeclaration/Rector/ClassMethod/ReturnNullableTypeRector.php:91-115 | rules/TypeDeclaration/Rector/Closure/ClosureReturnTypeFromAssertInstanceOfRector.php:94-115 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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, 16+ corresponding lines) · ×1
Edited copies of one member (5 members, 16+ corresponding lines) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:102— rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:102-117 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstReturnsRector.php:95-110 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanStrictReturnsRector.php:103-123 | rules/TypeDeclaration/Rector/ClassMethod/StringReturnTypeFromStrictScalarReturnsRector.php:88-106 | rules/TypeDeclaration/Rector/ClassMethod/StringReturnTypeFromStrictStringReturnsRector.php:90-110 — These 5 members are one piece of code written 5 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 5 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/NodeAnalyzer/CallLikeArgumentNameAdder.php:146— src/NodeAnalyzer/CallLikeArgumentNameAdder.php:146-162 | src/PhpParser/NodeVisitor/CallLikeReflectionNodeVisitor.php:140-156 — 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, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) rules/Removing/Rector/ClassMethod/ArgumentRemoverRector.php:63— rules/Removing/Rector/ClassMethod/ArgumentRemoverRector.php:63-77 | rules/Renaming/Rector/ClassConstFetch/RenameClassConstFetchRector.php:51-65 | rules/Transform/Rector/StaticCall/StaticCallToFuncCallRector.php:41-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) rules/CodeQuality/Rector/Switch_/SingularSwitchToIfRector.php:102— rules/CodeQuality/Rector/Switch_/SingularSwitchToIfRector.php:102-119 | src/NodeAnalyzer/TerminatedNodeAnalyzer.php:124-136 | src/NodeAnalyzer/TerminatedNodeAnalyzer.php:176-193 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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 (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) rules/DeadCode/Rector/ClassMethod/RemoveMixedDocblockOverruledByNativeTypeRector.php:100— rules/DeadCode/Rector/ClassMethod/RemoveMixedDocblockOverruledByNativeTypeRector.php:100-131 | rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php:160-173 | src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php:275-285 | src/BetterPhpDocParser/PhpDocManipulator/PhpDocTagRemover.php:38-52 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 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, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php:110— rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayMapRector.php:110-118 | rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeForArrayReduceRector.php:114-126 | rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeFromVariableCallRector.php:165-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) rules/Arguments/ValueObject/ArgumentAdder.php:45— rules/Arguments/ValueObject/ArgumentAdder.php:45-52 | rules/Arguments/ValueObject/ArgumentAdderWithoutDefaultValue.php:38-44 | rules/Arguments/ValueObject/ReplaceArgumentDefaultValue.php:43-48 — 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 copy of a member (1 corresponding lines) · ×1
Edited copy of a member (1 corresponding lines) rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:154— rules/Php80/Rector/Class_/AnnotationToAttributeRector.php:154-154 | rules/Transform/Rector/Attribute/AttributeKeyToClassConstFetchRector.php:71-71 — These two members are one piece of code written twice and then edited apart: 1 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 (3 corresponding lines) · ×1
Edited copy of a member (3 corresponding lines) src/PhpAttribute/NodeFactory/PhpAttributeGroupFactory.php:113— src/PhpAttribute/NodeFactory/PhpAttributeGroupFactory.php:113-117 | src/PhpAttribute/NodeFactory/PhpNestedAttributeGroupFactory.php:103-105 — These two members are one piece of code written twice and then edited apart: 3 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) · ×1
Edited copy of a member (4 corresponding lines) rules/Php81/Rector/Class_/MyCLabsClassToEnumRector.php:60— rules/Php81/Rector/Class_/MyCLabsClassToEnumRector.php:60-63 | rules/Php81/Rector/Class_/SpatieEnumClassToEnumRector.php:75-78 — 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 (20 lines × 2) rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:85— rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:85-104 | rules/CodingStyle/Rector/Stmt/NewlineAfterStatementRector.php:90-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodingStyle/Rector/ClassLike/NewlineBetweenClassLikeStmtsRector.php:85` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php:92— rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php:92-110 | rules/DeadCode/Rector/ClassMethod/RemoveUselessUnionReturnDocblockRector.php:80-98 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:100— rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:100-116 | rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:120-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:87— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:87-102 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:77-92 — before extracting anything, compare `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php` and `rules/Php84/NodeFactory/ForeachToArrayFindFactory.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (3–16 lines × 3) rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:111— rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:111-126 | rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:171-173 | rules/Php84/NodeFactory/ForeachToArrayFindFactory.php:101-116 — before extracting anything, compare `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php` and `rules/Php84/NodeFactory/ForeachToArrayFindFactory.php` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:111` 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 × 3) rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:103— rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:103-114 | rules/Php81/Rector/MethodCall/MyCLabsMethodCallToEnumConstRector.php:123-134 | rules/Php81/Rector/MethodCall/SpatieEnumMethodCallToEnumConstRector.php:90-101 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 2) src/PhpParser/AstResolver.php:100— src/PhpParser/AstResolver.php:100-110 | src/PhpParser/AstResolver.php:218-227 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/PhpParser/AstResolver.php:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 4) rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:103— rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:103-112 | rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanStrictReturnsRector.php:104-113 | rules/TypeDeclaration/Rector/ClassMethod/NumericReturnTypeFromStrictReturnsRector.php:88-97 | rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictTypedCallRector.php:136-145 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rules/TypeDeclaration/Rector/ClassMethod/BoolReturnTypeFromBooleanConstAndStrictReturnsRector.php:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–9 lines × 3) rules/CodingStyle/Rector/Stmt/NewlineAfterStatementRector.php:79— rules/CodingStyle/Rector/Stmt/NewlineAfterStatementRector.php:79-86 | rules/Php72/Rector/FuncCall/ParseStrWithResultArgumentRector.php:60-67 | rules/Php73/Rector/FuncCall/ArrayKeyFirstLastRector.php:101-109 — 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 `rules/CodingStyle/Rector/Stmt/NewlineAfterStatementRector.php:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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 (33 lines × 13) rules/CodeQuality/Rector/Class_/CompleteDynamicPropertiesRector.php:20— rules/CodeQuality/Rector/Class_/CompleteDynamicPropertiesRector.php:20-57 | rules/CodeQuality/Rector/Class_/DynamicDocBlockPropertyToNativePropertyRector.php:20-58 | rules/CodeQuality/Rector/Class_/InnerFunctionToPrivateMethodRector.php:20-62 | rules/DeadCode/Rector/ClassLike/RemoveTypedPropertyNonMockDocblockRector.php:20-52 | rules/DeadCode/Rector/ClassMethod/RemoveParentDelegatingConstructorRector.php:20-62 | rules/Naming/Rector/Class_/RenamePropertyToMatchTypeRector.php:20-62 | rules/Php83/Rector/ClassMethod/AddOverrideAttributeToOverriddenMethodsRector.php:22-75 | rules/Php84/Rector/Class_/PropertyHookRector.php:22-64 | rules/TypeDeclaration/Rector/ClassMethod/ParamTypeByParentCallTypeRector.php:20-66 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddParamArrayDocblockFromDataProviderRector.php:20-71 | rules/TypeDeclarationDocblocks/Rector/Class_/AddReturnArrayDocblockFromDataProviderParamRector.php:20-70 | rules/TypeDeclarationDocblocks/Rector/Class_/AddReturnDocblockDataProviderRector.php:20-76 | rules/Unambiguous/Rector/Class_/RemoveReturnThisFromSetterClassMethodRector.php:20-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 13 times. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/Class_/CompleteDynamicPropertiesRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24 lines × 9) rules/CodeQuality/Rector/Foreach_/ForeachItemsAssignToEmptyArrayToAssignRector.php:20— rules/CodeQuality/Rector/Foreach_/ForeachItemsAssignToEmptyArrayToAssignRector.php:20-55 | rules/CodeQuality/Rector/Foreach_/UnusedForeachValueToArrayKeysRector.php:20-58 | rules/CodeQuality/Rector/StmtsAwareInterface/MoveInnerFunctionToTopLevelRector.php:20-56 | rules/EarlyReturn/Rector/If_/ChangeNestedIfsToEarlyReturnRector.php:20-63 | rules/EarlyReturn/Rector/Return_/ReturnBinaryOrToEarlyReturnRector.php:20-52 | rules/EarlyReturn/Rector/StmtsAwareInterface/ReturnEarlyIfVariableRector.php:20-57 | rules/Naming/Rector/Foreach_/RenameForeachValueVariableToMatchExprVariableRector.php:20-58 | rules/Php73/Rector/FuncCall/JsonThrowOnErrorRector.php:22-45 | rules/Php85/Rector/StmtsAwareInterface/SequentialAssignmentsToPipeOperatorRector.php:24-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/Foreach_/ForeachItemsAssignToEmptyArrayToAssignRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (31 lines × 5) rules/CodeQuality/Rector/If_/CombineIfRector.php:20— rules/CodeQuality/Rector/If_/CombineIfRector.php:20-58 | rules/CodeQuality/Rector/If_/ShortenElseIfRector.php:20-62 | rules/CodeQuality/Rector/If_/SimplifyIfElseToTernaryRector.php:20-56 | rules/CodingStyle/Rector/If_/NullableCompareToNullRector.php:20-50 | rules/EarlyReturn/Rector/If_/ChangeOrIfContinueToMultiContinueRector.php:20-69 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/If_/CombineIfRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (37 lines × 2) rules/CodeQuality/Rector/If_/ExplicitBoolCompareRector.php:22— rules/CodeQuality/Rector/If_/ExplicitBoolCompareRector.php:22-58 | rules/CodeQuality/Rector/If_/ObjectExplicitBoolCompareRector.php:22-58 — 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 `rules/CodeQuality/Rector/If_/ExplicitBoolCompareRector.php:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (44 lines × 2) rules/CodeQuality/Rector/Switch_/SwitchTrueToIfRector.php:20— rules/CodeQuality/Rector/Switch_/SwitchTrueToIfRector.php:20-69 | rules/CodeQuality/Rector/Switch_/SwitchTrueToMatchRector.php:20-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `rules/CodeQuality/Rector/Switch_/SwitchTrueToIfRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (30 lines × 3) rules/CodingStyle/Rector/ClassMethod/BinaryOpStandaloneAssignsToDirectRector.php:22— rules/CodingStyle/Rector/ClassMethod/BinaryOpStandaloneAssignsToDirectRector.php:22-51 | rules/DeadCode/Rector/FunctionLike/RemoveDeadReturnRector.php:22-64 | rules/TypeDeclaration/Rector/ClassMethod/StrictStringParamConcatRector.php:24-60 — 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 `rules/CodingStyle/Rector/ClassMethod/BinaryOpStandaloneAssignsToDirectRector.php:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (33 lines × 5) rules/DeadCode/Rector/ClassMethod/RemoveDuplicatedReturnSelfDocblockRector.php:20— rules/DeadCode/Rector/ClassMethod/RemoveDuplicatedReturnSelfDocblockRector.php:20-55 | rules/Naming/Rector/ClassMethod/RenameParamToMatchTypeRector.php:20-52 | rules/Naming/Rector/ClassMethod/RenameVariableToMatchNewTypeRector.php:20-54 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForDimFetchArrayFromAssignsRector.php:20-72 | rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockFromMethodCallDocblockRector.php:20-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `rules/DeadCode/Rector/ClassMethod/RemoveDuplicatedReturnSelfDocblockRector.php:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (39 lines × 2) rules/Naming/Rector/Assign/RenameVariableToMatchMethodCallReturnTypeRector.php:22— rules/Naming/Rector/Assign/RenameVariableToMatchMethodCallReturnTypeRector.php:22-64 | rules/Naming/Rector/Foreach_/RenameForeachValueVariableToMatchMethodCallReturnTypeRector.php:22-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Naming/Rector/Assign/RenameVariableToMatchMethodCallReturnTypeRector.php:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (25 lines × 4) rules/Transform/Rector/Class_/AddInterfaceByTraitRector.php:21— rules/Transform/Rector/Class_/AddInterfaceByTraitRector.php:21-47 | rules/Transform/Rector/Class_/MergeInterfacesRector.php:21-45 | rules/Transform/Rector/FuncCall/FuncCallToMethodCallRector.php:22-64 | rules/Transform/Rector/StaticCall/StaticCallToMethodCallRector.php:22-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `rules/Transform/Rector/Class_/AddInterfaceByTraitRector.php:21` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/NodeTypeResolver/NodeTypeResolver/NameTypeResolver.php:52— src/NodeTypeResolver/NodeTypeResolver/NameTypeResolver.php:52-56 | src/Reflection/ReflectionResolver.php:84-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) rules/Php80/NodeAnalyzer/PhpAttributeAnalyzer.php:49— rules/Php80/NodeAnalyzer/PhpAttributeAnalyzer.php:49-56 | src/NodeTypeResolver/NodeTypeResolver.php:125-132 | src/PhpParser/Comparing/NodeComparator.php:49-56 | src/PhpParser/Node/Value/ValueResolver.php:139-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) src/NodeNameResolver/NodeNameResolver/ClassConstNameResolver.php:24— src/NodeNameResolver/NodeNameResolver/ClassConstNameResolver.php:24-28 | src/NodeNameResolver/NodeNameResolver/PropertyNameResolver.php:24-28 | src/NodeNameResolver/NodeNameResolver/UseNameResolver.php:24-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Duplicated predicate rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:200— `!$assignmentStmt instanceof Expression || !$assignmentStmt` appears character-identically in 2 files — rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php, rules/Php84/NodeFactory/ForeachToArrayFindFactory.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/NodeCollector/NodeAnalyzer/ArrayCallableMethodMatcher.php:147— `!$classReflection instanceof ClassReflection || !$classReflection` appears character-identically in 5 files — src/NodeCollector/NodeAnalyzer/ArrayCallableMethodMatcher.php, src/NodeTypeResolver/NodeTypeResolver/NameTypeResolver.php, src/NodeTypeResolver/TypeComparator/TypeComparator.php, src/PhpParser/Node/Value/ValueResolver.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 rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php:189— `!$firstStmt instanceof If_ || count($firstStmt->stmts) !== 2` appears character-identically in 2 files — rules/Php84/NodeFactory/ForeachToArrayAnyAllFactory.php, rules/Php84/NodeFactory/ForeachToArrayFindFactory.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 rules/TypeDeclaration/NodeAnalyzer/ReturnFilter/ExclusiveNativeCallLikeReturnMatcher.php:37— `!$functionLikeReflection instanceof FunctionReflection && !$functionLikeReflection instanceof MethodReflection` appears character-identically in 2 files — rules/TypeDeclaration/NodeAnalyzer/ReturnFilter/ExclusiveNativeCallLikeReturnMatcher.php, src/PhpParser/NodeVisitor/CallLikeReflectionNodeVisitor.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 rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForArrayDimAssignedObjectRector.php:118— `!$onlyReturnWithExpr instanceof Return_ || !$onlyReturnWithExpr` appears character-identically in 2 files — rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForArrayDimAssignedObjectRector.php, rules/TypeDeclarationDocblocks/Rector/ClassMethod/AddReturnDocblockForCommonObjectDenominatorRector.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 rules/DeadCode/NodeManipulator/PrivateMethodParamRemover.php:172— `!$subNode instanceof MethodCall && !$subNode instanceof StaticCall` appears character-identically in 2 files — rules/DeadCode/NodeManipulator/PrivateMethodParamRemover.php, src/PhpParser/NodeFinder/LocalMethodCallFinder.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 rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php:54— `$binaryOp instanceof Identical || $binaryOp instanceof Equal` appears character-identically in 4 files — rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrncmpMatchAndRefactor.php, rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/StrposMatchAndRefactor.php, rules/Php80/MatchAndRefactor/StrStartsWithMatchAndRefactor/SubstrMatchAndRefactor.php, rules/Php80/Rector/Identical/StrEndsWithRector.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 rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeDeclarationRector.php:141— `$classLike instanceof Class_ && $classLike` appears character-identically in 2 files — rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeDeclarationRector.php, src/Application/ChangedNodeScopeRefresher.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 rules/DeadCode/NodeAnalyzer/SafeLeftTypeBooleanAndOrAnalyzer.php:62— `$classReflection instanceof ClassReflection && $classReflection` appears character-identically in 7 files — rules/DeadCode/NodeAnalyzer/SafeLeftTypeBooleanAndOrAnalyzer.php, rules/DeadCode/Rector/ClassMethod/RemoveReturnTagIncompatibleWithNativeTypeRector.php, rules/DeadCode/Rector/If_/RemoveAlwaysTrueIfConditionRector.php, rules/DeadCode/Rector/If_/RemoveDeadInstanceOfRector.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 rules/Php83/Rector/ClassConst/AddTypeToConstRector.php:175— `$expr instanceof ConstFetch || $expr instanceof ClassConstFetch` appears character-identically in 2 files — rules/Php83/Rector/ClassConst/AddTypeToConstRector.php, rules/Php86/Rector/Class_/ConstructorReadonlyAssignToDefaultRector.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 rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromCast.php:53— `$functionLike instanceof ClassMethod && $this` appears character-identically in 4 files — rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromCast.php, rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php, rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromStrictNativeCall.php, rules/TypeDeclaration/Rector/Class_/ReturnTypeFromStrictTernaryRector.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 rules/CodeQuality/Rector/Foreach_/SimplifyForeachToCoalescingRector.php:170— `$nextStmt instanceof Return_ && $nextStmt` appears character-identically in 2 files — rules/CodeQuality/Rector/Foreach_/SimplifyForeachToCoalescingRector.php, rules/Php80/NodeFactory/MatchFactory.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 rules/CodeQuality/Rector/If_/ExplicitNullableObjectInstanceRector.php:110— `$node instanceof BooleanAnd || $node instanceof BooleanOr` appears character-identically in 2 files — rules/CodeQuality/Rector/If_/ExplicitNullableObjectInstanceRector.php, src/PhpParser/Printer/BetterStandardPrinter.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 rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php:95— `$node instanceof Class_ || $node instanceof FunctionLike` appears character-identically in 5 files — rules/TypeDeclaration/NodeManipulator/AddReturnTypeFromParam.php, rules/TypeDeclaration/Rector/ClassMethod/StrictArrayParamDimFetchRector.php, rules/TypeDeclaration/Rector/FunctionLike/AddClosureParamTypeFromVariableCallRector.php, src/PhpParser/NodeTraverser/SimpleNodeTraverser.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 rules/Naming/VariableRenamer.php:57— `$node instanceof Class_ || $node instanceof Function_` appears character-identically in 4 files — rules/Naming/VariableRenamer.php, rules/TypeDeclaration/Rector/ClassMethod/AddParamTypeFromPropertyTypeRector.php, src/NodeAnalyzer/ParamAnalyzer.php, src/NodeManipulator/PropertyFetchAssignManipulator.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 rules/Php80/Rector/NotIdentical/MbStrContainsRector.php:99— `$node instanceof Identical || $node instanceof Equal` appears character-identically in 2 files — rules/Php80/Rector/NotIdentical/MbStrContainsRector.php, rules/Php80/Rector/NotIdentical/StrContainsRector.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 rules/CodeQuality/Rector/Identical/SimplifyConditionsRector.php:78— `$node instanceof Identical || $node instanceof NotIdentical` appears character-identically in 2 files — rules/CodeQuality/Rector/Identical/SimplifyConditionsRector.php, rules/CodeQuality/Rector/If_/ExplicitNullableObjectInstanceRector.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 rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php:113— `$node instanceof MethodCall || $node instanceof StaticCall` appears character-identically in 2 files — rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php, rules/Removing/Rector/ClassMethod/ArgumentRemoverRector.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/NodeTypeResolver/PhpDocNodeVisitor/ClassRenamePhpDocNodeVisitor.php:107— `$objectType instanceof ShortenedObjectType || $objectType instanceof AliasedObjectType` appears character-identically in 3 files — src/NodeTypeResolver/PhpDocNodeVisitor/ClassRenamePhpDocNodeVisitor.php, src/PhpParser/Node/NullableObjectToInstanceofFactory.php, src/Reflection/ReflectionResolver.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 rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictFluentReturnRector.php:108— `$returnType instanceof ObjectType && $returnType` appears character-identically in 2 files — rules/TypeDeclaration/Rector/ClassMethod/ReturnTypeFromStrictFluentReturnRector.php, rules/TypeDeclaration/Rector/Class_/ReturnTypeFromMockObjectRector.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 rules/CodingStyle/ClassNameImport/ClassNameImportContext.php:92— `$stmt instanceof Namespace_ || $stmt instanceof FileNode` appears character-identically in 2 files — rules/CodingStyle/ClassNameImport/ClassNameImportContext.php, rules/CodingStyle/ClassNameImport/UseImportsTraverser.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 rules/CodeQuality/Rector/Switch_/SingularSwitchToIfRector.php:109— `$subNode instanceof Class_ || $subNode instanceof FunctionLike` appears character-identically in 2 files — rules/CodeQuality/Rector/Switch_/SingularSwitchToIfRector.php, src/PhpParser/Node/BetterNodeFinder.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 rules/DeadCode/NodeAnalyzer/IsClassMethodUsedAnalyzer.php:193— `$subNode instanceof Class_ || $subNode instanceof Function_` appears character-identically in 3 files — rules/DeadCode/NodeAnalyzer/IsClassMethodUsedAnalyzer.php, rules/DeadCode/Rector/Assign/RemoveUnusedVariableAssignRector.php, rules/TypeDeclaration/Rector/ClassMethod/AddParamArrayDocblockBasedOnCallableNativeFuncCallRector.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 rules/CodeQuality/Rector/ClassMethod/ExplicitReturnNullRector.php:122— `$subNode instanceof Class_ || $subNode instanceof Function_ || $subNode instanceof Closure` appears character-identically in 6 files — rules/CodeQuality/Rector/ClassMethod/ExplicitReturnNullRector.php, rules/DeadCode/Rector/ClassMethod/RemoveUselessReturnExprInConstructRector.php, rules/Php52/Rector/Switch_/ContinueToBreakInSwitchRector.php, rules/Php71/Rector/Assign/AssignArrayToStringRector.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 rules/TypeDeclaration/TypeInferer/SilentVoidResolver.php:79— `$subNode instanceof Yield_ || $subNode instanceof YieldFrom` appears character-identically in 2 files — rules/TypeDeclaration/TypeInferer/SilentVoidResolver.php, src/PhpParser/Node/BetterNodeFinder.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.
No ADRs found composer.json:7— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `composer.json` makes this repository a deployable product (line 7).
Scattered collaborators — 40 % of calls cross a namespace and only 19 % of collaborators are co-located — group each feature's code into a vertical slice so a call's collaborators sit together.
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.
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 — This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
Silent fallback default on parse failure src/BetterPhpDocParser/PhpDocInfo/PhpDocInfo.php:507— `resolveInlineGenericUsesReferenceClassNames` returns `[]` when `InvalidArgumentException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the docblock, and the row stops firing.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
0
—
Run 01a1d772-4e5e-7d3f-9a73-d92aab62c430 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 77 · Warnings: 408 · Recommendations: 48 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 00:25 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.