Public report of boa-dev/boa, published 27 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 27 October 2026, 13:10 UTC · Survey ID cd_e97c10e944b641fe828998b62f9fb1dd
boa-dev/boa
Measured 27 October 2026, 13:09 UTC, at code version 64c209f
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreStrong
CriticalWeakAdequateStrongExemplary
Down 4 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: 206,906 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 2.1 person-years · Weakest lens: Code Health, 68
Findings by how serious they are
7 critical1157 serious113 minor
11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
27 October 2026, 13:09 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
61of 61 dimensions measured by tools.
1250of 1277 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
61dimensions across 6 lenses, read from 206,906 lines of product code in 16 projects.
boa-dev/boa meets our standard for a preview release. It scores 73 out of 100 and is rated Strong, and two of its seven critical findings are security problems in its automatic dependency updates and in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is recording design decisions, worth about 5 points. Handling the errors the code catches and ignores comes next, worth about 4 points.
One automatic update takes new releases before a bad one can be spotted. Five parts of the code are no longer understood by anyone working on it. Setting a waiting period for automatic updates and having someone learn the forgotten files would close both risks. Correcting the flagged pipeline settings would fix the weakness in the build pipeline's configuration.
The product code is 206,906 lines, about €310,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.
Exception handling · Swallowed exception (caught, then discarded) core/runtime/assets/harness.js
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 18 findings
These 18 critical or serious findings were in the previous survey, on 13 October 2026, and are gone from this one.
€100,000 to €520,000, for 1,729 to 5,484 hours of work, about 2.1 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×1.1 at a score of 73. 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: 206,906 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: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 5 points · Low effort · ADR Quality
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 10,412 lines over the last 90 days, which is about 42,226 lines a year. At that pace, the extra work comes to an estimated 2.1 to 14.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
537 modules, with 2681 dependencies between them. 4 loops run through 195 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 497 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.
boa_engine.value.conversions.try_from_js uses boa_engine.value, so a change to boa_engine.value can break boa_engine.value.conversions.try_from_js, while a change to boa_engine.value.conversions.try_from_js can't break boa_engine.value.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→28 boa_engine.value.conversions.try_from_js uses boa_engine.contextpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value.conversions.try_from_js uses a type in boa_engine.context.
boa_engine.value.conversions.try_from_js uses boa_engine.context, so a change to boa_engine.context can break boa_engine.value.conversions.try_from_js, while a change to boa_engine.value.conversions.try_from_js can't break boa_engine.context.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→5 boa_engine.vm.opcode uses boa_engine.vm.opcode.binary_ops.macro_definedpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.vm.opcode uses a type in boa_engine.vm.opcode.binary_ops.macro_defined.
boa_engine.vm.opcode uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.vm.opcode, while a change to boa_engine.vm.opcode can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→30 boa_engine.vm.opcode uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.vm.opcode uses a type in boa_engine.builtins.intl.number_format.
boa_engine.vm.opcode uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.vm.opcode, while a change to boa_engine.vm.opcode can't break boa_engine.builtins.intl.number_format.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in boa_interner.sym uses a type in boa_gc.trace.
The types involved
boa_interner.sym.Sym → boa_gc.trace.Trace
Direction
boa_interner.sym uses boa_gc.trace, so a change to boa_gc.trace can break boa_interner.sym, while a change to boa_interner.sym can't break boa_gc.trace.
Position
Below the diagonal: boa_interner.sym uses a module listed above it, which is the healthy direction.
4→13 boa_interner.sym uses boa_internerpart of a loop✕
Connections
1 pair of types, where a type in boa_interner.sym uses a type in boa_interner.
The types involved
boa_interner.sym.Sym → boa_interner.Interner
Direction
boa_interner.sym uses boa_interner, so a change to boa_interner can break boa_interner.sym, while a change to boa_interner.sym can't break boa_interner.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→15 boa_interner.sym uses boa_ast.visitorpart of a loop✕
Connections
1 pair of types, where a type in boa_interner.sym uses a type in boa_ast.visitor.
The types involved
boa_interner.sym.Sym → boa_ast.visitor.VisitWith
Direction
boa_interner.sym uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_interner.sym, while a change to boa_interner.sym can't break boa_ast.visitor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→26 boa_interner.sym uses boa_stringpart of a loop✕
Connections
1 pair of types, where a type in boa_interner.sym uses a type in boa_string.
The types involved
boa_interner.sym.Sym → boa_string.JsString
Direction
boa_interner.sym uses boa_string, so a change to boa_string can break boa_interner.sym, while a change to boa_interner.sym can't break boa_string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→34 boa_interner.sym uses boa_ast.expression.identifierpart of a loop✕
Connections
1 pair of types, where a type in boa_interner.sym uses a type in boa_ast.expression.identifier.
boa_interner.sym uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_interner.sym, while a change to boa_interner.sym can't break boa_ast.expression.identifier.
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.
boa_engine.vm.opcode.binary_ops.macro_defined uses boa_engine.vm.opcode, so a change to boa_engine.vm.opcode can break boa_engine.vm.opcode.binary_ops.macro_defined, while a change to boa_engine.vm.opcode.binary_ops.macro_defined can't break boa_engine.vm.opcode.
Position
Below the diagonal: boa_engine.vm.opcode.binary_ops.macro_defined uses a module listed above it, which is the healthy direction.
5→28 boa_engine.vm.opcode.binary_ops.macro_defined uses boa_engine.contextpart of a loop✕
Connections
19 pairs of types, where a type in boa_engine.vm.opcode.binary_ops.macro_defined uses a type in boa_engine.context.
boa_engine.vm.opcode.binary_ops.macro_defined uses boa_engine.context, so a change to boa_engine.context can break boa_engine.vm.opcode.binary_ops.macro_defined, while a change to boa_engine.vm.opcode.binary_ops.macro_defined can't break boa_engine.context.
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.
boa_gc.cell uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_gc.cell, while a change to boa_gc.cell can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_gc.cell uses a module listed above it, which is the healthy direction.
6→25 boa_gc.cell uses boa_engine.builtins.iterable.iterator_helper.droppart of a loop✕
Connections
2 pairs of types, where a type in boa_gc.cell uses a type in boa_engine.builtins.iterable.iterator_helper.drop.
boa_gc.cell uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_gc.cell, while a change to boa_gc.cell can't break boa_engine.builtins.iterable.iterator_helper.drop.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→30 boa_gc.cell uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
6 pairs of types, where a type in boa_gc.cell uses a type in boa_engine.builtins.intl.number_format.
boa_gc.cell uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_gc.cell, while a change to boa_gc.cell can't break boa_engine.builtins.intl.number_format.
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.
boa_gc.pointers.gc uses boa_gc.trace, so a change to boa_gc.trace can break boa_gc.pointers.gc, while a change to boa_gc.pointers.gc can't break boa_gc.trace.
Position
Below the diagonal: boa_gc.pointers.gc uses a module listed above it, which is the healthy direction.
boa_gc.pointers.gc uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_gc.pointers.gc, while a change to boa_gc.pointers.gc can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_gc.pointers.gc uses a module listed above it, which is the healthy direction.
7→25 boa_gc.pointers.gc uses boa_engine.builtins.iterable.iterator_helper.droppart of a loop✕
Connections
2 pairs of types, where a type in boa_gc.pointers.gc uses a type in boa_engine.builtins.iterable.iterator_helper.drop.
boa_gc.pointers.gc uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_gc.pointers.gc, while a change to boa_gc.pointers.gc can't break boa_engine.builtins.iterable.iterator_helper.drop.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→30 boa_gc.pointers.gc uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
2 pairs of types, where a type in boa_gc.pointers.gc uses a type in boa_engine.builtins.intl.number_format.
boa_gc.pointers.gc uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_gc.pointers.gc, while a change to boa_gc.pointers.gc can't break boa_engine.builtins.intl.number_format.
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.
boa_string.str uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_string.str, while a change to boa_string.str can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_string.str uses a module listed above it, which is the healthy direction.
8→12 boa_string.str uses boa_engine.builtins.stringpart of a loop✕
Connections
1 pair of types, where a type in boa_string.str uses a type in boa_engine.builtins.string.
boa_string.str uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_string.str, while a change to boa_string.str can't break boa_engine.builtins.string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 boa_string.str uses boa_stringpart of a loop✕
Connections
1 pair of types, where a type in boa_string.str uses a type in boa_string.
The types involved
boa_string.str.JsStr → boa_string.JsString
Direction
boa_string.str uses boa_string, so a change to boa_string can break boa_string.str, while a change to boa_string.str can't break boa_string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 boa_string.str uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
1 pair of types, where a type in boa_string.str uses a type in boa_engine.builtins.intl.number_format.
boa_string.str uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_string.str, while a change to boa_string.str can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.property uses boa_string.str, so a change to boa_string.str can break boa_engine.property, while a change to boa_engine.property can't break boa_string.str.
Position
Below the diagonal: boa_engine.property uses a module listed above it, which is the healthy direction.
9→11 boa_engine.property uses boa_engine.valuepart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.property uses a type in boa_engine.value.
boa_engine.property uses boa_engine.value, so a change to boa_engine.value can break boa_engine.property, while a change to boa_engine.property can't break boa_engine.value.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→22 boa_engine.property uses boa_engine.object.builtins.jsfunctionpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.property uses a type in boa_engine.object.builtins.jsfunction.
boa_engine.property uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.property, while a change to boa_engine.property can't break boa_engine.object.builtins.jsfunction.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→26 boa_engine.property uses boa_stringpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.property uses a type in boa_string.
boa_engine.property uses boa_string, so a change to boa_string can break boa_engine.property, while a change to boa_engine.property can't break boa_string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→30 boa_engine.property uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.property uses a type in boa_engine.builtins.intl.number_format.
boa_engine.property uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.property, while a change to boa_engine.property can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.realm uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.realm, while a change to boa_engine.realm can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_engine.realm uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in boa_engine.realm uses a type in boa_gc.pointers.gc.
The types involved
boa_engine.realm.Inner → boa_gc.pointers.gc.Gc
boa_engine.realm.Realm → boa_gc.pointers.gc.Gc
Direction
boa_engine.realm uses boa_gc.pointers.gc, so a change to boa_gc.pointers.gc can break boa_engine.realm, while a change to boa_engine.realm can't break boa_gc.pointers.gc.
Position
Below the diagonal: boa_engine.realm uses a module listed above it, which is the healthy direction.
10→20 boa_engine.realm uses boa_engine.object.jsobjectpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.realm uses a type in boa_engine.object.jsobject.
boa_engine.realm uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.realm, while a change to boa_engine.realm can't break boa_engine.object.jsobject.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→23 boa_engine.realm uses boa_engine.context.intrinsicspart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.realm uses a type in boa_engine.context.intrinsics.
boa_engine.realm uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.realm, while a change to boa_engine.realm can't break boa_engine.context.intrinsics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→27 boa_engine.realm uses boa_ast.scopepart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.realm uses a type in boa_ast.scope.
The types involved
boa_engine.realm.Inner → boa_ast.scope.Scope
boa_engine.realm.Realm → boa_ast.scope.Scope
Direction
boa_engine.realm uses boa_ast.scope, so a change to boa_ast.scope can break boa_engine.realm, while a change to boa_engine.realm can't break boa_ast.scope.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→28 boa_engine.realm uses boa_engine.contextpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.realm uses a type in boa_engine.context.
boa_engine.realm uses boa_engine.context, so a change to boa_engine.context can break boa_engine.realm, while a change to boa_engine.realm can't break boa_engine.context.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→30 boa_engine.realm uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.realm uses a type in boa_engine.builtins.intl.number_format.
boa_engine.realm uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.realm, while a change to boa_engine.realm can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.value uses boa_engine.value.conversions.try_from_js, so a change to boa_engine.value.conversions.try_from_js can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.value.conversions.try_from_js.
Position
Below the diagonal: boa_engine.value uses a module listed above it, which is the healthy direction.
boa_engine.value uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_engine.value uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in boa_engine.value uses a type in boa_string.str.
The types involved
boa_engine.value.JsValue → boa_string.str.JsStr
Direction
boa_engine.value uses boa_string.str, so a change to boa_string.str can break boa_engine.value, while a change to boa_engine.value can't break boa_string.str.
Position
Below the diagonal: boa_engine.value uses a module listed above it, which is the healthy direction.
boa_engine.value uses boa_engine.property, so a change to boa_engine.property can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.property.
Position
Below the diagonal: boa_engine.value uses a module listed above it, which is the healthy direction.
11→12 boa_engine.value uses boa_engine.builtins.stringpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value uses a type in boa_engine.builtins.string.
boa_engine.value uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.builtins.string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→20 boa_engine.value uses boa_engine.object.jsobjectpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value uses a type in boa_engine.object.jsobject.
boa_engine.value uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.object.jsobject.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→22 boa_engine.value uses boa_engine.object.builtins.jsfunctionpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.value uses a type in boa_engine.object.builtins.jsfunction.
boa_engine.value uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.object.builtins.jsfunction.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→24 boa_engine.value uses boa_engine.builtins.iterablepart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value uses a type in boa_engine.builtins.iterable.
boa_engine.value uses boa_engine.builtins.iterable, so a change to boa_engine.builtins.iterable can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.builtins.iterable.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→26 boa_engine.value uses boa_stringpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value uses a type in boa_string.
The types involved
boa_engine.value.JsValue → boa_string.JsString
Direction
boa_engine.value uses boa_string, so a change to boa_string can break boa_engine.value, while a change to boa_engine.value can't break boa_string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→28 boa_engine.value uses boa_engine.contextpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.value uses a type in boa_engine.context.
boa_engine.value uses boa_engine.context, so a change to boa_engine.context can break boa_engine.value, while a change to boa_engine.value can't break boa_engine.context.
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.
boa_engine.builtins.string uses boa_engine.value.conversions.try_from_js, so a change to boa_engine.value.conversions.try_from_js can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.value.conversions.try_from_js.
Position
Below the diagonal: boa_engine.builtins.string uses a module listed above it, which is the healthy direction.
boa_engine.builtins.string uses boa_string.str, so a change to boa_string.str can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_string.str.
Position
Below the diagonal: boa_engine.builtins.string uses a module listed above it, which is the healthy direction.
boa_engine.builtins.string uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins.string uses a module listed above it, which is the healthy direction.
boa_engine.builtins.string uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins.string uses a module listed above it, which is the healthy direction.
12→20 boa_engine.builtins.string uses boa_engine.object.jsobjectpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.string uses a type in boa_engine.object.jsobject.
boa_engine.builtins.string uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.object.jsobject.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→23 boa_engine.builtins.string uses boa_engine.context.intrinsicspart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.string uses a type in boa_engine.context.intrinsics.
boa_engine.builtins.string uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.context.intrinsics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→26 boa_engine.builtins.string uses boa_stringpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.builtins.string uses a type in boa_string.
boa_engine.builtins.string uses boa_string, so a change to boa_string can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_string.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→28 boa_engine.builtins.string uses boa_engine.contextpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.builtins.string uses a type in boa_engine.context.
boa_engine.builtins.string uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.context.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→29 boa_engine.builtins.string uses boa_engine.builtinspart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.builtins.string uses a type in boa_engine.builtins.
boa_engine.builtins.string uses boa_engine.builtins, so a change to boa_engine.builtins can break boa_engine.builtins.string, while a change to boa_engine.builtins.string can't break boa_engine.builtins.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in boa_interner uses a type in boa_interner.sym.
The types involved
boa_interner.Interner → boa_interner.sym.Sym
Direction
boa_interner uses boa_interner.sym, so a change to boa_interner.sym can break boa_interner, while a change to boa_interner can't break boa_interner.sym.
Position
Below the diagonal: boa_interner uses a module listed above it, which is the healthy direction.
boa_interner uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_interner, while a change to boa_interner can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_interner uses a module listed above it, which is the healthy direction.
13→30 boa_interner uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
1 pair of types, where a type in boa_interner uses a type in boa_engine.builtins.intl.number_format.
boa_interner uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_interner, while a change to boa_interner can't break boa_engine.builtins.intl.number_format.
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.
boa_ast.statement uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.statement, while a change to boa_ast.statement can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.statement uses a module listed above it, which is the healthy direction.
boa_ast.statement uses boa_interner, so a change to boa_interner can break boa_ast.statement, while a change to boa_ast.statement can't break boa_interner.
Position
Below the diagonal: boa_ast.statement uses a module listed above it, which is the healthy direction.
14→15 boa_ast.statement uses boa_ast.visitorpart of a loop✕
Connections
1 pair of types, where a type in boa_ast.statement uses a type in boa_ast.visitor.
boa_ast.statement uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.statement, while a change to boa_ast.statement can't break boa_ast.visitor.
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.
14→36 boa_ast.statement uses boa_ast.expressionpart of a loop✕
Connections
1 pair of types, where a type in boa_ast.statement uses a type in boa_ast.expression.
boa_ast.statement uses boa_ast.expression, so a change to boa_ast.expression can break boa_ast.statement, while a change to boa_ast.statement can't break boa_ast.expression.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2 pairs of types, where a type in boa_ast.visitor uses a type in boa_interner.sym.
The types involved
boa_ast.visitor.NodeRef → boa_interner.sym.Sym
boa_ast.visitor.NodeRefMut → boa_interner.sym.Sym
Direction
boa_ast.visitor uses boa_interner.sym, so a change to boa_interner.sym can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_interner.sym.
Position
Below the diagonal: boa_ast.visitor uses a module listed above it, which is the healthy direction.
boa_ast.visitor uses boa_ast.statement, so a change to boa_ast.statement can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_ast.statement.
Position
Below the diagonal: boa_ast.visitor uses a module listed above it, which is the healthy direction.
15→16 boa_ast.visitor uses boa_ast.function.parameterspart of a loop✕
Connections
4 pairs of types, where a type in boa_ast.visitor uses a type in boa_ast.function.parameters.
boa_ast.visitor uses boa_ast.function.parameters, so a change to boa_ast.function.parameters can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_ast.function.parameters.
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.
15→17 boa_ast.visitor uses boa_ast.function.classpart of a loop✕
Connections
8 pairs of types, where a type in boa_ast.visitor uses a type in boa_ast.function.class.
boa_ast.visitor uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_ast.function.class.
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.
15→34 boa_ast.visitor uses boa_ast.expression.identifierpart of a loop✕
Connections
2 pairs of types, where a type in boa_ast.visitor uses a type in boa_ast.expression.identifier.
boa_ast.visitor uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_ast.expression.identifier.
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.
15→36 boa_ast.visitor uses boa_ast.expressionpart of a loop✕
Connections
2 pairs of types, where a type in boa_ast.visitor uses a type in boa_ast.expression.
boa_ast.visitor uses boa_ast.expression, so a change to boa_ast.expression can break boa_ast.visitor, while a change to boa_ast.visitor can't break boa_ast.expression.
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.
boa_ast.function.parameters uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.function.parameters, while a change to boa_ast.function.parameters can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.function.parameters uses a module listed above it, which is the healthy direction.
boa_ast.function.parameters uses boa_interner, so a change to boa_interner can break boa_ast.function.parameters, while a change to boa_ast.function.parameters can't break boa_interner.
Position
Below the diagonal: boa_ast.function.parameters uses a module listed above it, which is the healthy direction.
boa_ast.function.parameters uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.function.parameters, while a change to boa_ast.function.parameters can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.function.parameters uses a module listed above it, which is the healthy direction.
16→36 boa_ast.function.parameters uses boa_ast.expressionpart of a loop✕
Connections
1 pair of types, where a type in boa_ast.function.parameters uses a type in boa_ast.expression.
boa_ast.function.parameters uses boa_ast.expression, so a change to boa_ast.expression can break boa_ast.function.parameters, while a change to boa_ast.function.parameters can't break boa_ast.expression.
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.
boa_ast.function.class uses boa_interner.sym, so a change to boa_interner.sym can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_interner.sym.
Position
Below the diagonal: boa_ast.function.class uses a module listed above it, which is the healthy direction.
boa_ast.function.class uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.function.class uses a module listed above it, which is the healthy direction.
boa_ast.function.class uses boa_interner, so a change to boa_interner can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_interner.
Position
Below the diagonal: boa_ast.function.class uses a module listed above it, which is the healthy direction.
boa_ast.function.class uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.function.class uses a module listed above it, which is the healthy direction.
boa_ast.function.class uses boa_ast.function.parameters, so a change to boa_ast.function.parameters can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.function.parameters.
Position
Below the diagonal: boa_ast.function.class uses a module listed above it, which is the healthy direction.
17→27 boa_ast.function.class uses boa_ast.scopepart of a loop✕
Connections
6 pairs of types, where a type in boa_ast.function.class uses a type in boa_ast.scope.
boa_ast.function.class uses boa_ast.scope, so a change to boa_ast.scope can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.scope.
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.
17→32 boa_ast.function.class uses boa_ast.positionpart of a loop✕
Connections
7 pairs of types, where a type in boa_ast.function.class uses a type in boa_ast.position.
boa_ast.function.class uses boa_ast.position, so a change to boa_ast.position can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.position.
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.
17→34 boa_ast.function.class uses boa_ast.expression.identifierpart of a loop✕
Connections
2 pairs of types, where a type in boa_ast.function.class uses a type in boa_ast.expression.identifier.
boa_ast.function.class uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.expression.identifier.
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.
17→36 boa_ast.function.class uses boa_ast.expressionpart of a loop✕
Connections
4 pairs of types, where a type in boa_ast.function.class uses a type in boa_ast.expression.
boa_ast.function.class uses boa_ast.expression, so a change to boa_ast.expression can break boa_ast.function.class, while a change to boa_ast.function.class can't break boa_ast.expression.
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.
boa_engine.builtins.function uses boa_gc.trace, so a change to boa_gc.trace can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_gc.trace.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_gc.pointers.gc, so a change to boa_gc.pointers.gc can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_gc.pointers.gc.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_string.str, so a change to boa_string.str can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_string.str.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_engine.property, so a change to boa_engine.property can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.property.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
boa_engine.builtins.function uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_ast.function.class.
Position
Below the diagonal: boa_engine.builtins.function uses a module listed above it, which is the healthy direction.
18→19 boa_engine.builtins.function uses boa_engine.objectpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.function uses a type in boa_engine.object.
boa_engine.builtins.function uses boa_engine.object, so a change to boa_engine.object can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.object.
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.
18→20 boa_engine.builtins.function uses boa_engine.object.jsobjectpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.builtins.function uses a type in boa_engine.object.jsobject.
boa_engine.builtins.function uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.object.jsobject.
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.
18→22 boa_engine.builtins.function uses boa_engine.object.builtins.jsfunctionpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.function uses a type in boa_engine.object.builtins.jsfunction.
boa_engine.builtins.function uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.object.builtins.jsfunction.
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.
18→23 boa_engine.builtins.function uses boa_engine.context.intrinsicspart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.function uses a type in boa_engine.context.intrinsics.
boa_engine.builtins.function uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.context.intrinsics.
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.
18→28 boa_engine.builtins.function uses boa_engine.contextpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.builtins.function uses a type in boa_engine.context.
boa_engine.builtins.function uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.context.
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.
18→29 boa_engine.builtins.function uses boa_engine.builtinspart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.builtins.function uses a type in boa_engine.builtins.
boa_engine.builtins.function uses boa_engine.builtins, so a change to boa_engine.builtins can break boa_engine.builtins.function, while a change to boa_engine.builtins.function can't break boa_engine.builtins.
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.
boa_engine.object uses boa_gc.trace, so a change to boa_gc.trace can break boa_engine.object, while a change to boa_engine.object can't break boa_gc.trace.
Position
Below the diagonal: boa_engine.object uses a module listed above it, which is the healthy direction.
boa_engine.object uses boa_engine.property, so a change to boa_engine.property can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.property.
Position
Below the diagonal: boa_engine.object uses a module listed above it, which is the healthy direction.
boa_engine.object uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.object uses a module listed above it, which is the healthy direction.
boa_engine.object uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_engine.object, while a change to boa_engine.object can't break boa_ast.function.class.
Position
Below the diagonal: boa_engine.object uses a module listed above it, which is the healthy direction.
boa_engine.object uses boa_engine.builtins.function, so a change to boa_engine.builtins.function can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.builtins.function.
Position
Below the diagonal: boa_engine.object uses a module listed above it, which is the healthy direction.
19→20 boa_engine.object uses boa_engine.object.jsobjectpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object uses a type in boa_engine.object.jsobject.
boa_engine.object uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.object.jsobject.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→22 boa_engine.object uses boa_engine.object.builtins.jsfunctionpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.object uses a type in boa_engine.object.builtins.jsfunction.
boa_engine.object uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.object.builtins.jsfunction.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→23 boa_engine.object uses boa_engine.context.intrinsicspart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object uses a type in boa_engine.context.intrinsics.
boa_engine.object uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.context.intrinsics.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→26 boa_engine.object uses boa_stringpart of a loop✕
Connections
4 pairs of types, where a type in boa_engine.object uses a type in boa_string.
boa_engine.object uses boa_engine.context, so a change to boa_engine.context can break boa_engine.object, while a change to boa_engine.object can't break boa_engine.context.
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.
boa_engine.object.jsobject uses boa_engine.value.conversions.try_from_js, so a change to boa_engine.value.conversions.try_from_js can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.value.conversions.try_from_js.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_gc.cell, so a change to boa_gc.cell can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_gc.cell.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_gc.pointers.gc, so a change to boa_gc.pointers.gc can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_gc.pointers.gc.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_engine.property, so a change to boa_engine.property can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.property.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_engine.value, so a change to boa_engine.value can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.value.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_ast.function.class.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
boa_engine.object.jsobject uses boa_engine.object, so a change to boa_engine.object can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.object.
Position
Below the diagonal: boa_engine.object.jsobject uses a module listed above it, which is the healthy direction.
20→22 boa_engine.object.jsobject uses boa_engine.object.builtins.jsfunctionpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.object.builtins.jsfunction.
boa_engine.object.jsobject uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.object.builtins.jsfunction.
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.
20→23 boa_engine.object.jsobject uses boa_engine.context.intrinsicspart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.context.intrinsics.
boa_engine.object.jsobject uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.context.intrinsics.
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.
20→24 boa_engine.object.jsobject uses boa_engine.builtins.iterablepart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.builtins.iterable.
boa_engine.object.jsobject uses boa_engine.builtins.iterable, so a change to boa_engine.builtins.iterable can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.builtins.iterable.
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.
20→25 boa_engine.object.jsobject uses boa_engine.builtins.iterable.iterator_helper.droppart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.builtins.iterable.iterator_helper.drop.
boa_engine.object.jsobject uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.builtins.iterable.iterator_helper.drop.
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.
20→26 boa_engine.object.jsobject uses boa_stringpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_string.
boa_engine.object.jsobject uses boa_string, so a change to boa_string can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_string.
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.
20→28 boa_engine.object.jsobject uses boa_engine.contextpart of a loop✕
Connections
1 pair of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.context.
boa_engine.object.jsobject uses boa_engine.context, so a change to boa_engine.context can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.context.
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.
20→30 boa_engine.object.jsobject uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.object.jsobject uses a type in boa_engine.builtins.intl.number_format.
boa_engine.object.jsobject uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.object.jsobject, while a change to boa_engine.object.jsobject can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.error uses boa_gc.trace, so a change to boa_gc.trace can break boa_engine.error, while a change to boa_engine.error can't break boa_gc.trace.
Position
Below the diagonal: boa_engine.error uses a module listed above it, which is the healthy direction.
boa_engine.error uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_engine.error uses a module listed above it, which is the healthy direction.
boa_engine.error uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.error uses a module listed above it, which is the healthy direction.
boa_engine.error uses boa_engine.value, so a change to boa_engine.value can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.value.
Position
Below the diagonal: boa_engine.error uses a module listed above it, which is the healthy direction.
boa_engine.error uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.error uses a module listed above it, which is the healthy direction.
21→28 boa_engine.error uses boa_engine.contextpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.error uses a type in boa_engine.context.
boa_engine.error uses boa_engine.context, so a change to boa_engine.context can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.context.
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.
21→30 boa_engine.error uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
6 pairs of types, where a type in boa_engine.error uses a type in boa_engine.builtins.intl.number_format.
boa_engine.error uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.error, while a change to boa_engine.error can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.object.builtins.jsfunction uses boa_engine.value.conversions.try_from_js, so a change to boa_engine.value.conversions.try_from_js can break boa_engine.object.builtins.jsfunction, while a change to boa_engine.object.builtins.jsfunction can't break boa_engine.value.conversions.try_from_js.
Position
Below the diagonal: boa_engine.object.builtins.jsfunction uses a module listed above it, which is the healthy direction.
boa_engine.object.builtins.jsfunction uses boa_engine.value, so a change to boa_engine.value can break boa_engine.object.builtins.jsfunction, while a change to boa_engine.object.builtins.jsfunction can't break boa_engine.value.
Position
Below the diagonal: boa_engine.object.builtins.jsfunction uses a module listed above it, which is the healthy direction.
boa_engine.object.builtins.jsfunction uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.object.builtins.jsfunction, while a change to boa_engine.object.builtins.jsfunction can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.object.builtins.jsfunction uses a module listed above it, which is the healthy direction.
22→28 boa_engine.object.builtins.jsfunction uses boa_engine.contextpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.object.builtins.jsfunction uses a type in boa_engine.context.
boa_engine.object.builtins.jsfunction uses boa_engine.context, so a change to boa_engine.context can break boa_engine.object.builtins.jsfunction, while a change to boa_engine.object.builtins.jsfunction can't break boa_engine.context.
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.
boa_engine.context.intrinsics uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.context.intrinsics, while a change to boa_engine.context.intrinsics can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.context.intrinsics uses a module listed above it, which is the healthy direction.
boa_engine.context.intrinsics uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.context.intrinsics, while a change to boa_engine.context.intrinsics can't break boa_engine.object.builtins.jsfunction.
Position
Below the diagonal: boa_engine.context.intrinsics uses a module listed above it, which is the healthy direction.
23→24 boa_engine.context.intrinsics uses boa_engine.builtins.iterablepart of a loop✕
Connections
1 pair of types, where a type in boa_engine.context.intrinsics uses a type in boa_engine.builtins.iterable.
boa_engine.context.intrinsics uses boa_engine.builtins.iterable, so a change to boa_engine.builtins.iterable can break boa_engine.context.intrinsics, while a change to boa_engine.context.intrinsics can't break boa_engine.builtins.iterable.
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.
boa_engine.builtins.iterable uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins.iterable uses a module listed above it, which is the healthy direction.
boa_engine.builtins.iterable uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins.iterable uses a module listed above it, which is the healthy direction.
boa_engine.builtins.iterable uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.builtins.iterable uses a module listed above it, which is the healthy direction.
boa_engine.builtins.iterable uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.context.intrinsics.
Position
Below the diagonal: boa_engine.builtins.iterable uses a module listed above it, which is the healthy direction.
24→28 boa_engine.builtins.iterable uses boa_engine.contextpart of a loop✕
Connections
3 pairs of types, where a type in boa_engine.builtins.iterable uses a type in boa_engine.context.
boa_engine.builtins.iterable uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.context.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→29 boa_engine.builtins.iterable uses boa_engine.builtinspart of a loop✕
Connections
1 pair of types, where a type in boa_engine.builtins.iterable uses a type in boa_engine.builtins.
boa_engine.builtins.iterable uses boa_engine.builtins, so a change to boa_engine.builtins can break boa_engine.builtins.iterable, while a change to boa_engine.builtins.iterable can't break boa_engine.builtins.
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.
boa_engine.builtins.iterable.iterator_helper.drop uses boa_engine.builtins.iterable, so a change to boa_engine.builtins.iterable can break boa_engine.builtins.iterable.iterator_helper.drop, while a change to boa_engine.builtins.iterable.iterator_helper.drop can't break boa_engine.builtins.iterable.
Position
Below the diagonal: boa_engine.builtins.iterable.iterator_helper.drop uses a module listed above it, which is the healthy direction.
boa_string uses boa_engine.value.conversions.try_from_js, so a change to boa_engine.value.conversions.try_from_js can break boa_string, while a change to boa_string can't break boa_engine.value.conversions.try_from_js.
Position
Below the diagonal: boa_string uses a module listed above it, which is the healthy direction.
boa_string uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_string, while a change to boa_string can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_string uses a module listed above it, which is the healthy direction.
boa_string uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_string, while a change to boa_string can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_string uses a module listed above it, which is the healthy direction.
boa_string uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_string, while a change to boa_string can't break boa_engine.builtins.iterable.iterator_helper.drop.
Position
Below the diagonal: boa_string uses a module listed above it, which is the healthy direction.
26→28 boa_string uses boa_engine.contextpart of a loop✕
Connections
1 pair of types, where a type in boa_string uses a type in boa_engine.context.
The types involved
boa_string.JsString → boa_engine.context.Context
Direction
boa_string uses boa_engine.context, so a change to boa_engine.context can break boa_string, while a change to boa_string can't break boa_engine.context.
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 boa_string uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
1 pair of types, where a type in boa_string uses a type in boa_engine.builtins.intl.number_format.
boa_string uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_string, while a change to boa_string can't break boa_engine.builtins.intl.number_format.
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.
boa_ast.scope uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_ast.scope, while a change to boa_ast.scope can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.context uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_engine.value, so a change to boa_engine.value can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.value.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_interner, so a change to boa_interner can break boa_engine.context, while a change to boa_engine.context can't break boa_interner.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_engine.error, so a change to boa_engine.error can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.error.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.context.intrinsics.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.builtins.iterable.iterator_helper.drop.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in boa_engine.context uses a type in boa_string.
The types involved
boa_engine.context.Context → boa_string.JsString
Direction
boa_engine.context uses boa_string, so a change to boa_string can break boa_engine.context, while a change to boa_engine.context can't break boa_string.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
boa_engine.context uses boa_ast.scope, so a change to boa_ast.scope can break boa_engine.context, while a change to boa_engine.context can't break boa_ast.scope.
Position
Below the diagonal: boa_engine.context uses a module listed above it, which is the healthy direction.
28→30 boa_engine.context uses boa_engine.builtins.intl.number_formatpart of a loop✕
Connections
2 pairs of types, where a type in boa_engine.context uses a type in boa_engine.builtins.intl.number_format.
boa_engine.context uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.context, while a change to boa_engine.context can't break boa_engine.builtins.intl.number_format.
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.
boa_engine.builtins uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins, while a change to boa_engine.builtins can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins uses a module listed above it, which is the healthy direction.
boa_engine.builtins uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins, while a change to boa_engine.builtins can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins uses a module listed above it, which is the healthy direction.
boa_engine.builtins uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins, while a change to boa_engine.builtins can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.builtins uses a module listed above it, which is the healthy direction.
boa_engine.builtins uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins, while a change to boa_engine.builtins can't break boa_engine.context.intrinsics.
Position
Below the diagonal: boa_engine.builtins uses a module listed above it, which is the healthy direction.
boa_engine.builtins uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins, while a change to boa_engine.builtins can't break boa_engine.context.
Position
Below the diagonal: boa_engine.builtins uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_gc.trace, so a change to boa_gc.trace can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_gc.trace.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.object.builtins.jsfunction.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.context.intrinsics.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_string, so a change to boa_string can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_string.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.context.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.intl.number_format uses boa_engine.builtins, so a change to boa_engine.builtins can break boa_engine.builtins.intl.number_format, while a change to boa_engine.builtins.intl.number_format can't break boa_engine.builtins.
Position
Below the diagonal: boa_engine.builtins.intl.number_format uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_gc.trace, so a change to boa_gc.trace can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_gc.trace.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.value, so a change to boa_engine.value can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.value.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.error, so a change to boa_engine.error can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.error.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.object.builtins.jsfunction, so a change to boa_engine.object.builtins.jsfunction can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.object.builtins.jsfunction.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.context.intrinsics, so a change to boa_engine.context.intrinsics can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.context.intrinsics.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.builtins.iterable, so a change to boa_engine.builtins.iterable can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.builtins.iterable.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.context, so a change to boa_engine.context can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.context.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_engine.builtins.promise uses boa_engine.builtins, so a change to boa_engine.builtins can break boa_engine.builtins.promise, while a change to boa_engine.builtins.promise can't break boa_engine.builtins.
Position
Below the diagonal: boa_engine.builtins.promise uses a module listed above it, which is the healthy direction.
boa_ast.position uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_ast.position, while a change to boa_ast.position can't break boa_engine.builtins.intl.number_format.
Position
Below the diagonal: boa_ast.position uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.vm.opcode.binary_ops.macro_defined, so a change to boa_engine.vm.opcode.binary_ops.macro_defined can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.vm.opcode.binary_ops.macro_defined.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_gc.cell, so a change to boa_gc.cell can break boa_engine.module, while a change to boa_engine.module can't break boa_gc.cell.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in boa_engine.module uses a type in boa_gc.pointers.gc.
The types involved
boa_engine.module.Module → boa_gc.pointers.gc.Gc
Direction
boa_engine.module uses boa_gc.pointers.gc, so a change to boa_gc.pointers.gc can break boa_engine.module, while a change to boa_engine.module can't break boa_gc.pointers.gc.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.realm, so a change to boa_engine.realm can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.realm.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.value, so a change to boa_engine.value can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.value.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_interner, so a change to boa_interner can break boa_engine.module, while a change to boa_engine.module can't break boa_interner.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.object.jsobject, so a change to boa_engine.object.jsobject can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.object.jsobject.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.context, so a change to boa_engine.context can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.context.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.builtins.intl.number_format, so a change to boa_engine.builtins.intl.number_format can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.builtins.intl.number_format.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_engine.module uses boa_engine.builtins.promise, so a change to boa_engine.builtins.promise can break boa_engine.module, while a change to boa_engine.module can't break boa_engine.builtins.promise.
Position
Below the diagonal: boa_engine.module uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_interner.sym, so a change to boa_interner.sym can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_interner.sym.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_interner, so a change to boa_interner can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_interner.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_string, so a change to boa_string can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_string.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_ast.expression.identifier uses boa_ast.position, so a change to boa_ast.position can break boa_ast.expression.identifier, while a change to boa_ast.expression.identifier can't break boa_ast.position.
Position
Below the diagonal: boa_ast.expression.identifier uses a module listed above it, which is the healthy direction.
boa_parser.lexer.cursor uses boa_ast.position, so a change to boa_ast.position can break boa_parser.lexer.cursor, while a change to boa_parser.lexer.cursor can't break boa_ast.position.
Position
Below the diagonal: boa_parser.lexer.cursor uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.expression, while a change to boa_ast.expression can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_interner, so a change to boa_interner can break boa_ast.expression, while a change to boa_ast.expression can't break boa_interner.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.expression, while a change to boa_ast.expression can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_ast.expression, while a change to boa_ast.expression can't break boa_ast.function.class.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_ast.position, so a change to boa_ast.position can break boa_ast.expression, while a change to boa_ast.expression can't break boa_ast.position.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.expression uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_ast.expression, while a change to boa_ast.expression can't break boa_ast.expression.identifier.
Position
Below the diagonal: boa_ast.expression uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_interner, so a change to boa_interner can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_interner.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_ast.function.parameters, so a change to boa_ast.function.parameters can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_ast.function.parameters.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_ast.function.class.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_ast.scope, so a change to boa_ast.scope can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_ast.scope.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_ast.scope_analyzer uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_ast.scope_analyzer, while a change to boa_ast.scope_analyzer can't break boa_ast.expression.identifier.
Position
Below the diagonal: boa_ast.scope_analyzer uses a module listed above it, which is the healthy direction.
boa_parser.parser uses boa_interner, so a change to boa_interner can break boa_parser.parser, while a change to boa_parser.parser can't break boa_interner.
Position
Below the diagonal: boa_parser.parser uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in boa_parser.parser uses a type in boa_ast.scope.
The types involved
boa_parser.parser.Parser → boa_ast.scope.Scope
Direction
boa_parser.parser uses boa_ast.scope, so a change to boa_ast.scope can break boa_parser.parser, while a change to boa_parser.parser can't break boa_ast.scope.
Position
Below the diagonal: boa_parser.parser uses a module listed above it, which is the healthy direction.
boa_parser.parser uses boa_ast.position, so a change to boa_ast.position can break boa_parser.parser, while a change to boa_parser.parser can't break boa_ast.position.
Position
Below the diagonal: boa_parser.parser uses a module listed above it, which is the healthy direction.
boa_parser.parser uses boa_parser.lexer.cursor, so a change to boa_parser.lexer.cursor can break boa_parser.parser, while a change to boa_parser.parser can't break boa_parser.lexer.cursor.
Position
Below the diagonal: boa_parser.parser uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_interner.sym, so a change to boa_interner.sym can break boa_ast.operations, while a change to boa_ast.operations can't break boa_interner.sym.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_engine.builtins.string, so a change to boa_engine.builtins.string can break boa_ast.operations, while a change to boa_ast.operations can't break boa_engine.builtins.string.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_interner, so a change to boa_interner can break boa_ast.operations, while a change to boa_ast.operations can't break boa_interner.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.statement, so a change to boa_ast.statement can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.statement.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.visitor, so a change to boa_ast.visitor can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.visitor.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.function.parameters, so a change to boa_ast.function.parameters can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.function.parameters.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.function.class.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.position, so a change to boa_ast.position can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.position.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.expression.identifier.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_ast.operations uses boa_ast.expression, so a change to boa_ast.expression can break boa_ast.operations, while a change to boa_ast.operations can't break boa_ast.expression.
Position
Below the diagonal: boa_ast.operations uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_engine.vm.opcode, so a change to boa_engine.vm.opcode can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_engine.vm.opcode.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_interner.sym, so a change to boa_interner.sym can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_interner.sym.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_gc.pointers.gc, so a change to boa_gc.pointers.gc can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_gc.pointers.gc.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_interner, so a change to boa_interner can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_interner.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.statement, so a change to boa_ast.statement can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.statement.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.function.parameters, so a change to boa_ast.function.parameters can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.function.parameters.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.function.class, so a change to boa_ast.function.class can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.function.class.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_engine.builtins.function, so a change to boa_engine.builtins.function can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_engine.builtins.function.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_engine.builtins.iterable.iterator_helper.drop, so a change to boa_engine.builtins.iterable.iterator_helper.drop can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_engine.builtins.iterable.iterator_helper.drop.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_string, so a change to boa_string can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_string.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.scope, so a change to boa_ast.scope can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.scope.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.position, so a change to boa_ast.position can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.position.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.expression.identifier, so a change to boa_ast.expression.identifier can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.expression.identifier.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.expression, so a change to boa_ast.expression can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.expression.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
boa_engine.bytecompiler uses boa_ast.scope_analyzer, so a change to boa_ast.scope_analyzer can break boa_engine.bytecompiler, while a change to boa_engine.bytecompiler can't break boa_ast.scope_analyzer.
Position
Below the diagonal: boa_engine.bytecompiler uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 68% · Adequate · gated by X3 ·
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
A03:2025 — Software Supply Chain Failures
8
Medium
A05:2025 — Injection
3
High / Critical
Roadmap
Begin by addressing the missing architectural decision records and resolving swallowed exceptions to ensure robust error handling and clear design rationale. Next, update the README to clearly explain how to run the test suite, improving onboarding and verification processes. Finally, resolve the five orphaned knowledge findings, prioritizing mod.rs, utils.rs, and position.rs, to maintain codebase relevance and reduce technical debt.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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.
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.
Reconcile the README with reality: tests/fuzz/README.md links to `fuzz/fuzz_targets/common.rs`, but `tests/fuzz/fuzz/fuzz_targets/common.rs` does not exist.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 7
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 — 1157
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 — 113
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 61 of 61 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 61 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, 1250 of 1277 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (.github/codecov.yml) and a coverage step in CI (`cargo tarpaulin`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 158 test files), but it was not re-run: its build outgrew the 12 GB scratch ceiling (12.001 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust 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.
Repo exclusion declarations: 22 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
75 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClassElement::parse at 92. A further 27 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 Visitor::visit at 103 — they are counted neither in the figure above nor in this dimension's score. 12 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: core/ast/src/visitor.rs (Visitor::visit at 103), core/ast/src/punctuator/mod.rs (Punctuator::as_str at 57), core/ast/src/keyword/mod.rs (Keyword::from_str at 40), core/ast/src/expression/mod.rs (Expression::to_no_indent_string at 33), core/engine/src/builtins/date/mod.rs (Date::to_utc_string at 24), and 7 more not listed here. 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.
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with ClassElement::parse (cyclomatic 92). — Refactoring it lifts Cyclomatic Complexity from 6.1 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 63 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with ClassElement::parse (cognitive 168). — Refactoring it lifts Cognitive Complexity from 5.5 to about 5.8/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.1 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 51 FileTooLong finding(s) in God Classes — start with mod.rs (33), operations.rs (2), class.rs (2). — One of this dimension's main actionable groups (51 warning-level).
Resolve the 50 MethodTooLong finding(s) in God Classes — start with mod.rs (27), code_block.rs (2), source.rs (2). — One of this dimension's main actionable groups (50 warning-level).
Resolve the 26 ClassTooLong finding(s) in God Classes — start with mod.rs (19), builtin.rs, source.rs. — One of this dimension's main actionable groups (26 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
537 duplicated block group(s) detected. A further 37 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 174 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 40 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with mod.rs (25), scope_analyzer.rs (3), class.rs (2). — One of this dimension's main actionable groups (40 warning-level).
Resolve the 38 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with mod.rs (22), class.rs (3), declarations.rs (2). — One of this dimension's main actionable groups (38 warning-level).
Resolve the 27 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with mod.rs (18), scope_analyzer.rs (2), jsobject.rs (2). — One of this dimension's main actionable groups (27 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.0 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
16 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 12 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: boa_icu_provider · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with mod.rs (7), jump_control.rs. — One of this dimension's main actionable groups (8 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1728 test methods: 1687 unit, 40 integration, 0 BDD, 1 e2e. The Rust suite contributes 1728 `#[test]` function(s) across 158 file(s) declaring at least one; its unit/integration split is Cargo's own — 17 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
9 outdated, 0 yanked direct Cargo dependencies. 107 of 110 direct crates were graded against crates.io (0 not published there, 3 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: fixed_decimal · ×9
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 461 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Unlicense OR MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), code_block.rs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
24 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is core/engine/src/builtins/typed_array/builtin_uint8.rs. Counted over 520 of the 662 production source files in this repository: 141 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
163 deducted task-comment markers across 206906 LoC (0.1/KLoC) → score 9.8. 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 161 TodoComment finding(s) in Explicit Debt — start with mod.rs (106), lib.rs (9), options.rs (4). — One of this dimension's main actionable groups (161 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with lib.rs, globals.rs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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. 17 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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
2 of 16 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
3 finding(s): 0 critical, 2 high, 1 medium, 0 low. semgrep hit a parse error in 9 file(s) — `cli/src/main.rs` (line 652, line 677, line 834), `core/engine/src/builtins/finalization_registry/mod.rs` (line 182, line 189), `core/engine/src/module/source.rs` (line 612), `core/engine/src/native_function/mod.rs` (line 209), `core/runtime/src/fetch/request.rs` (line 272, line 288, line 317), … (+4 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
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 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_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.
90 of 521 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is core/parser/src/parser/statement/mod.rs. Counted over 521 of the 662 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 5 Orphaned knowledge finding(s) in Knowledge Freshness — start with mod.rs (3), utils.rs, position.rs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 85 Orphaned file finding(s) in Knowledge Freshness — start with mod.rs (28), tests.rs (11), import.rs (2). — One of this dimension's main actionable groups (85 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Change coupling finding(s) in Change Coupling — start with mod.rs (4), map_iterator.rs, function.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 6 Change-coupling hub finding(s) in Change Coupling — start with mod.rs (5), code_block.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with mod.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
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 1 platform declaration(s) and 0 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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
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.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
151 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 13 of 18 project(s) that lack one — worth up to 1.4 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
tests/fuzz/README.md links to `fuzz/fuzz_targets/common.rs`, but `tests/fuzz/fuzz/fuzz_targets/common.rs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tests/fuzz/README.md:5
What to do
Reconcile the README with reality: tests/fuzz/README.md links to `fuzz/fuzz_targets/common.rs`, but `tests/fuzz/fuzz/fuzz_targets/common.rs` does not exist.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cli`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — core/runtime/assets/harness.js:54
What to do
Swallowed exception (caught, then discarded)
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.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 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 — 54 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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.
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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves 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, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) 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 Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~15677 lines of test source are present (.rs) 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 — the .rs suite was found but not re-run
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 is measured on C# only; JavaScript, Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .rs, 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
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (204 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
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
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
S1 Web-Security Posture — No web surface: 576 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Orphaned knowledge core/parser/src/parser/statement/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/parser/src/parser/expression/primary/object_initializer/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge core/engine/src/builtins/date/utils.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/parser/src/parser/expression/mod.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge core/ast/src/position.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
TodoComment tests/wpt/src/lib.rs:380— // TODO: The console-log-large-array.any.js test is too slow. — 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 tests/wpt/src/lib.rs:395— // TODO: re-enable those when better encoding and options are supported. — 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 tests/wpt/src/fetcher/mod.rs:15— // TODO: Look into what NodeJS or other browserless runtimes do for WPT tests. — 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 tests/tester/src/read.rs:171— // TODO: iterate in parallel — 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 tests/tester/src/exec/mod.rs:283— // TODO: timeout — 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 tests/fuzz/fuzz_targets/common.rs:36— // TODO arbitrary strings literals? — 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 core/wintertc/src/url/mod.rs:9— //! # TODO — 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 core/wintertc/src/fetch/mod.rs:9— //! # TODO — 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 core/wintertc/src/events/mod.rs:10— //! # TODO — 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 core/wintertc/src/encoding/mod.rs:10— //! # TODO — 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 core/wintertc/src/abort/mod.rs:9— //! # TODO — 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 core/string/src/lib.rs:1001— // TODO: remove [`str::JsSliceIndex`] and rename this when `JsStr` is no more. — 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 core/runtime/src/test262.rs:227— // TODO: improve initialization of this by using a `[[HostDefined]]` field on `Context`. — 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 core/runtime/src/fetch/mod.rs:39— // TODO: consider implementing an async version of this. — 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 core/runtime/src/fetch/mod.rs:247— // TODO(#4688): Replace this manual `[Symbol.iterator]` wiring once `#[boa(class)]`
TodoComment core/runtime/src/fetch/request.rs:21— // TODO: This class does not contain all fields that are defined in the spec. — 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 core/runtime/src/fetch/request.rs:100— // TODO: add more support types. — 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 core/runtime/src/fetch/response.rs:321— // TODO: handle other BodyInit types: Blob, FormData, URLSearchParams. — 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 core/runtime/src/fetch/response.rs:485— // TODO: track the full URL list to implement this properly. — 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 core/parser/src/parser/tests/format/expression.rs:67— // TODO: `let a = await fn()` is invalid syntax as of writing. It should be tested here once implemented. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment core/parser/src/parser/tests/format/statement.rs:14— // TODO: Once block labels are implemented, this should be tested: — 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 core/parser/src/parser/statement/mod.rs:119— // TODO: add BreakableStatement and divide Whiles, fors and so on to another place. — 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 core/parser/src/parser/statement/mod.rs:329— // TODO: should store directives in some place — 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 core/parser/src/parser/statement/mod.rs:658— // TODO: Currently parses only BindingIdentifier. — 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.
FileTooLong: bytecompiler/mod.rs core/engine/src/bytecompiler/mod.rs— FileTooLong — 1860 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: ByteCompiler (2 blocks, 496-2841). The bar is 500 significant lines; this is 1360 over it, 3.72× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/scope_analyzer.rs core/ast/src/scope_analyzer.rs— FileTooLong — 1632 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1132 over it, 3.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: array/mod.rs core/engine/src/builtins/array/mod.rs— FileTooLong — 1617 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 86% of them inside a single declaration: Array (6 blocks, 61-3336). The bar is 500 significant lines; this is 1117 over it, 3.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: operations/mod.rs core/ast/src/operations/mod.rs— FileTooLong — 1572 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1072 over it, 3.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: typed_array/builtin.rs core/engine/src/builtins/typed_array/builtin.rs— FileTooLong — 1519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: BuiltinTypedArray (4 blocks, 37-3170). The bar is 500 significant lines; this is 1019 over it, 3.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: promise/mod.rs core/engine/src/builtins/promise/mod.rs— FileTooLong — 1296 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: Promise (5 blocks, 84-2565). The bar is 500 significant lines; this is 796 over it, 2.59× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: zoneddatetime/mod.rs core/engine/src/builtins/temporal/zoneddatetime/mod.rs— FileTooLong — 1221 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: ZonedDateTime (8 blocks, 57-1875). The bar is 500 significant lines; this is 721 over it, 2.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: module/source.rs core/engine/src/module/source.rs— FileTooLong — 1205 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: SourceTextModule (3 blocks, 253-2037). The bar is 500 significant lines; this is 705 over it, 2.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: string/mod.rs core/engine/src/builtins/string/mod.rs— FileTooLong — 1173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: String (5 blocks, 64-2635). The bar is 500 significant lines; this is 673 over it, 2.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: plain_date_time/mod.rs core/engine/src/builtins/temporal/plain_date_time/mod.rs— FileTooLong — 984 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 79% of them inside a single declaration: PlainDateTime (8 blocks, 59-1605). The bar is 500 significant lines; this is 484 over it, 1.97× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: regexp/mod.rs core/engine/src/builtins/regexp/mod.rs— FileTooLong — 973 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: RegExp (6 blocks, 42-2107). The bar is 500 significant lines; this is 473 over it, 1.95× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: date/mod.rs core/engine/src/builtins/date/mod.rs— FileTooLong — 906 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: Date (5 blocks, 50-1912). The bar is 500 significant lines; this is 406 over it, 1.81× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: class_decl/mod.rs core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs— FileTooLong — 879 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 64% of them inside a single declaration: ClassElement (3 blocks, 507-1299). The bar is 500 significant lines; this is 379 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: vm/code_block.rs core/engine/src/vm/code_block.rs— FileTooLong — 877 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: CodeBlock (4 blocks, 127-1079). The bar is 500 significant lines; this is 377 over it, 1.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: context/intrinsics.rs core/engine/src/context/intrinsics.rs— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: error/mod.rs core/engine/src/error/mod.rs— FileTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 241 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: plain_date/mod.rs core/engine/src/builtins/temporal/plain_date/mod.rs— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: PlainDate (8 blocks, 60-1271). The bar is 500 significant lines; this is 235 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: duration/mod.rs core/engine/src/builtins/temporal/duration/mod.rs— FileTooLong — 721 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 76% of them inside a single declaration: Duration (8 blocks, 45-1159). The bar is 500 significant lines; this is 221 over it, 1.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: builtins/jstypedarray.rs core/engine/src/object/builtins/jstypedarray.rs— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: JsTypedArray (4 blocks, 20-973). The bar is 500 significant lines; this is 219 over it, 1.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: number_format/options.rs core/engine/src/builtins/intl/number_format/options.rs— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 216 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: opcode/mod.rs core/engine/src/vm/opcode/mod.rs— FileTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 192 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: object/operations.rs core/engine/src/object/operations.rs— FileTooLong — 672 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: JsObject (56-1330). The bar is 500 significant lines; this is 172 over it, 1.34× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: statement/mod.rs core/parser/src/parser/statement/mod.rs— FileTooLong — 671 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 171 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: object/mod.rs core/engine/src/builtins/object/mod.rs— FileTooLong — 666 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: OrdinaryObject (4 blocks, 50-1430). The bar is 500 significant lines; this is 166 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: internal_methods/mod.rs core/engine/src/object/internal_methods/mod.rs— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: ClassElement.parse core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:535— MethodTooLong — parse runs 547 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 447 over it, 5.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.compile_class core/engine/src/bytecompiler/class.rs:82— MethodTooLong — compile_class runs 476 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 376 over it, 4.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CodeBlock.instruction_operands core/engine/src/vm/code_block.rs:378— MethodTooLong — instruction_operands runs 475 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 375 over it, 4.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CodeBlock.to_graph core/engine/src/vm/flowgraph/mod.rs:24— MethodTooLong — to_graph runs 374 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 274 over it, 3.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ZonedDateTime.init core/engine/src/builtins/temporal/zoneddatetime/mod.rs:74— MethodTooLong — init runs 256 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.compile_expr_impl core/engine/src/bytecompiler/expression/mod.rs:90— MethodTooLong — compile_expr_impl runs 241 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PropertyDefinition.parse core/parser/src/parser/expression/primary/object_initializer/mod.rs:175— MethodTooLong — parse runs 229 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.compile_assign core/engine/src/bytecompiler/expression/assign.rs:15— MethodTooLong — compile_assign runs 210 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 110 over it, 2.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SourceTextModule.initialize_environment core/engine/src/module/source.rs:1591— MethodTooLong — initialize_environment runs 207 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PlainDateTime.init core/engine/src/builtins/temporal/plain_date_time/mod.rs:78— MethodTooLong — init runs 201 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 101 over it, 2.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.compile_update core/engine/src/bytecompiler/expression/update.rs:13— MethodTooLong — compile_update runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.compile_declaration_pattern_impl core/engine/src/bytecompiler/declaration/declaration_pattern.rs:12— MethodTooLong — compile_declaration_pattern_impl runs 189 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MemberExpression.parse core/parser/src/parser/expression/left_hand_side/member.rs:63— MethodTooLong — parse runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CoverParenthesizedExpressionAndArrowParameterList.parse core/parser/src/parser/expression/primary/mod.rs:312— MethodTooLong — parse runs 172 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Eval.perform_eval core/engine/src/builtins/eval/mod.rs:73— MethodTooLong — perform_eval runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ForStatement.parse core/parser/src/parser/statement/iteration/for_statement.rs:79— MethodTooLong — parse runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ObjectBindingPattern.parse core/parser/src/parser/statement/mod.rs:516— MethodTooLong — parse runs 158 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BuiltInFunctionObject.create_dynamic_function core/engine/src/builtins/function/mod.rs:394— MethodTooLong — create_dynamic_function runs 156 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PlainDate.init core/engine/src/builtins/temporal/plain_date/mod.rs:75— MethodTooLong — init runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LeftHandSideExpression.parse core/parser/src/parser/expression/left_hand_side/mod.rs:76— MethodTooLong — parse runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SourceTextModule.inner_evaluate core/engine/src/module/source.rs:1177— MethodTooLong — inner_evaluate runs 150 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Promise.perform_promise_all_keyed core/engine/src/builtins/promise/mod.rs:1190— MethodTooLong — perform_promise_all_keyed runs 144 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ByteCompiler.function_declaration_instantiation core/engine/src/bytecompiler/declarations.rs:876— MethodTooLong — function_declaration_instantiation runs 140 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PrimaryExpression.parse core/parser/src/parser/expression/primary/mod.rs:96— MethodTooLong — parse runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NumberFormat.new core/engine/src/builtins/intl/number_format/mod.rs:303— MethodTooLong — new runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (9 lines × 2) core/ast/src/scope_analyzer.rs:851— core/ast/src/scope_analyzer.rs:851-859 | core/ast/src/scope_analyzer.rs:862-870 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/ast/src/scope_analyzer.rs:1495— core/ast/src/scope_analyzer.rs:1495-1503 | core/ast/src/scope_analyzer.rs:1506-1514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/ast/src/scope_analyzer.rs:1632— core/ast/src/scope_analyzer.rs:1632-1640 | core/ast/src/scope_analyzer.rs:1657-1665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/builtins/async_generator/mod.rs:74— core/engine/src/builtins/async_generator/mod.rs:74-82 | core/engine/src/builtins/iterable/async_from_sync_iterator.rs:30-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) core/engine/src/builtins/string/mod.rs:899— core/engine/src/builtins/string/mod.rs:899-908 | core/engine/src/builtins/string/mod.rs:965-973 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1838— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1838-1846 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2214-2222 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:545— core/engine/src/builtins/temporal/plain_month_day/mod.rs:545-553 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:843-851 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1131— core/engine/src/builtins/typed_array/builtin.rs:1131-1139 | core/engine/src/builtins/typed_array/builtin.rs:1270-1278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/bytecompiler/class.rs:225— core/engine/src/bytecompiler/class.rs:225-234 | core/engine/src/bytecompiler/class.rs:285-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/bytecompiler/class.rs:641— core/engine/src/bytecompiler/class.rs:641-649 | core/engine/src/bytecompiler/class.rs:657-665 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/bytecompiler/declarations.rs:510— core/engine/src/bytecompiler/declarations.rs:510-518 | core/engine/src/bytecompiler/declarations.rs:783-791 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/bytecompiler/mod.rs:1031— core/engine/src/bytecompiler/mod.rs:1031-1039 | core/engine/src/bytecompiler/mod.rs:1068-1076 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/object/shape/shared_shape/forward_transition.rs:58— core/engine/src/object/shape/shared_shape/forward_transition.rs:58-66 | core/engine/src/object/shape/shared_shape/forward_transition.rs:70-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/value/display/array.rs:12— core/engine/src/value/display/array.rs:12-20 | core/engine/src/value/display/array.rs:80-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/parser/src/lexer/regex.rs:215— core/parser/src/lexer/regex.rs:215-223 | core/parser/src/lexer/regex.rs:247-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/parser/src/parser/expression/primary/class_expression/mod.rs:54— core/parser/src/parser/expression/primary/class_expression/mod.rs:54-62 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:81-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:430— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:430-438 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:449-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:915— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:915-923 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1018-1026 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/runtime/src/fetch/headers.rs:111— core/runtime/src/fetch/headers.rs:111-119 | core/runtime/src/fetch/headers.rs:121-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/runtime/src/url.rs:207— core/runtime/src/url.rs:207-215 | core/runtime/src/url.rs:217-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/object/builtins/jsarray.rs:309— core/engine/src/object/builtins/jsarray.rs:309-317 | core/engine/src/object/builtins/jstypedarray.rs:274-282 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) core/engine/src/object/builtins/jsfinalization_registry.rs:23— core/engine/src/object/builtins/jsfinalization_registry.rs:23-31 | core/engine/src/object/builtins/jstypedarray.rs:31-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) core/engine/src/builtins/intl/plural_rules/mod.rs:208— core/engine/src/builtins/intl/plural_rules/mod.rs:208-216 | core/engine/src/builtins/intl/plural_rules/mod.rs:302-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:289— core/engine/src/builtins/temporal/instant/mod.rs:289-299 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:812-820 — `core/engine/src/builtins/temporal/instant/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) core/engine/src/builtins/map/mod.rs:459— core/engine/src/builtins/map/mod.rs:459-468 | core/engine/src/builtins/map/mod.rs:659-667 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/ast/src/function/class.rs:125— core/ast/src/function/class.rs:125-135 | core/ast/src/function/class.rs:301-311 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/ast/src/function/class.rs:142— core/ast/src/function/class.rs:142-152 | core/ast/src/function/class.rs:320-330 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/ast/src/operations/mod.rs:194— core/ast/src/operations/mod.rs:194-204 | core/ast/src/operations/mod.rs:209-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/ast/src/scope_analyzer.rs:216— core/ast/src/scope_analyzer.rs:216-226 | core/ast/src/scope_analyzer.rs:248-258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/array_buffer/mod.rs:331— core/engine/src/builtins/array_buffer/mod.rs:331-341 | core/engine/src/builtins/array_buffer/shared.rs:100-110 — before extracting anything, compare `core/engine/src/builtins/array_buffer/mod.rs` and `core/engine/src/builtins/array_buffer/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) core/engine/src/builtins/async_generator/mod.rs:598— core/engine/src/builtins/async_generator/mod.rs:598-608 | core/engine/src/builtins/async_generator/mod.rs:629-639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/date/utils.rs:343— core/engine/src/builtins/date/utils.rs:343-353 | core/engine/src/builtins/date/utils.rs:371-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/json/mod.rs:696— core/engine/src/builtins/json/mod.rs:696-706 | core/engine/src/builtins/json/mod.rs:799-809 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/json/mod.rs:969— core/engine/src/builtins/json/mod.rs:969-979 | core/engine/src/builtins/json/mod.rs:1128-1138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/json/mod.rs:1023— core/engine/src/builtins/json/mod.rs:1023-1033 | core/engine/src/builtins/json/mod.rs:1160-1170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/math/mod.rs:673— core/engine/src/builtins/math/mod.rs:673-683 | core/engine/src/builtins/math/mod.rs:711-721 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/promise/mod.rs:1255— core/engine/src/builtins/promise/mod.rs:1255-1265 | core/engine/src/builtins/promise/mod.rs:1337-1347 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/string/mod.rs:1034— core/engine/src/builtins/string/mod.rs:1034-1044 | core/engine/src/builtins/string/mod.rs:1161-1171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/string/mod.rs:1498— core/engine/src/builtins/string/mod.rs:1498-1508 | core/engine/src/builtins/string/mod.rs:2244-2254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:353— core/engine/src/builtins/temporal/instant/mod.rs:353-363 | core/engine/src/builtins/temporal/instant/mod.rs:386-396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1262— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1262-1272 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1290-1300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/temporal/plain_time/mod.rs:576— core/engine/src/builtins/temporal/plain_time/mod.rs:576-586 | core/engine/src/builtins/temporal/plain_time/mod.rs:606-616 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/builtins/typed_array/builtin_uint8.rs:40— core/engine/src/builtins/typed_array/builtin_uint8.rs:40-50 | core/engine/src/builtins/typed_array/builtin_uint8.rs:151-161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/bytecompiler/declarations.rs:75— core/engine/src/bytecompiler/declarations.rs:75-85 | core/engine/src/bytecompiler/declarations.rs:401-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/bytecompiler/declarations.rs:1133— core/engine/src/bytecompiler/declarations.rs:1133-1143 | core/engine/src/bytecompiler/declarations.rs:1168-1180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/bytecompiler/mod.rs:2486— core/engine/src/bytecompiler/mod.rs:2486-2496 | core/engine/src/bytecompiler/mod.rs:2567-2577 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/bytecompiler/statement/try.rs:31— core/engine/src/bytecompiler/statement/try.rs:31-41 | core/engine/src/bytecompiler/statement/try.rs:46-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/object/operations.rs:452— core/engine/src/object/operations.rs:452-462 | core/engine/src/object/operations.rs:508-518 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/optimizer/pass/constant_folding.rs:178— core/engine/src/optimizer/pass/constant_folding.rs:178-188 | core/engine/src/optimizer/pass/constant_folding.rs:204-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) core/engine/src/vm/opcode/get/name.rs:66— core/engine/src/vm/opcode/get/name.rs:66-76 | core/engine/src/vm/opcode/get/property.rs:45-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) core/ast/src/scope_analyzer.rs:995— core/ast/src/scope_analyzer.rs:995-1004 | core/ast/src/scope_analyzer.rs:1608-1617 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/ast/src/scope_analyzer.rs:1930— core/ast/src/scope_analyzer.rs:1930-1939 | core/ast/src/scope_analyzer.rs:2400-2409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/date/mod.rs:538— core/engine/src/builtins/date/mod.rs:538-547 | core/engine/src/builtins/date/mod.rs:829-838 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/date/mod.rs:1409— core/engine/src/builtins/date/mod.rs:1409-1418 | core/engine/src/builtins/date/mod.rs:1687-1696 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/date/utils.rs:1014— core/engine/src/builtins/date/utils.rs:1014-1023 | core/engine/src/builtins/date/utils.rs:1026-1035 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/promise/mod.rs:1320— core/engine/src/builtins/promise/mod.rs:1320-1329 | core/engine/src/builtins/promise/mod.rs:1393-1402 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:1225— core/engine/src/builtins/temporal/plain_date/mod.rs:1225-1234 | core/engine/src/builtins/temporal/plain_date/mod.rs:1246-1255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:383— core/engine/src/builtins/temporal/plain_month_day/mod.rs:383-392 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:404-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/temporal/plain_time/mod.rs:471— core/engine/src/builtins/temporal/plain_time/mod.rs:471-480 | core/engine/src/builtins/temporal/plain_time/mod.rs:500-509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/temporal/plain_year_month/mod.rs:764— core/engine/src/builtins/temporal/plain_year_month/mod.rs:764-773 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:785-794 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:795— core/engine/src/builtins/typed_array/builtin.rs:795-804 | core/engine/src/builtins/typed_array/builtin.rs:1366-1375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/bytecompiler/mod.rs:956— core/engine/src/bytecompiler/mod.rs:956-965 | core/engine/src/bytecompiler/mod.rs:987-996 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/bytecompiler/statement/try.rs:133— core/engine/src/bytecompiler/statement/try.rs:133-142 | core/engine/src/bytecompiler/statement/try.rs:163-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/object/jsobject.rs:215— core/engine/src/object/jsobject.rs:215-224 | core/engine/src/object/jsobject.rs:1115-1124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/vm/opcode/environment/mod.rs:187— core/engine/src/vm/opcode/environment/mod.rs:187-196 | core/engine/src/vm/opcode/new/mod.rs:52-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.
Duplicated block (10 lines × 2) core/engine/src/vm/opcode/generator/mod.rs:27— core/engine/src/vm/opcode/generator/mod.rs:27-36 | core/engine/src/vm/opcode/generator/mod.rs:73-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/icu_provider/src/lib.rs:58— core/icu_provider/src/lib.rs:58-67 | core/icu_provider/src/lib.rs:79-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/parser/src/parser/expression/mod.rs:268— core/parser/src/parser/expression/mod.rs:268-278 | core/parser/src/parser/expression/mod.rs:287-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/parser/src/parser/expression/mod.rs:579— core/parser/src/parser/expression/mod.rs:579-588 | core/parser/src/parser/expression/mod.rs:599-608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:917— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:917-926 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1153-1162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/engine/src/object/builtins/jsweakmap.rs:28— core/engine/src/object/builtins/jsweakmap.rs:28-37 | core/engine/src/object/builtins/jsweakset.rs:28-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:743— core/engine/src/builtins/temporal/instant/mod.rs:743-755 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1285-1294 — `core/engine/src/builtins/temporal/instant/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) core/engine/src/builtins/map/mod.rs:259— core/engine/src/builtins/map/mod.rs:259-268 | core/engine/src/builtins/map/mod.rs:607-618 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:102— core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:102-111 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:841-851 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) core/engine/src/builtins/array/mod.rs:2827— core/engine/src/builtins/array/mod.rs:2827-2836 | core/engine/src/builtins/array/mod.rs:2924-2933 — 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.
ClassTooLong: ByteCompiler core/engine/src/bytecompiler/mod.rs:496— ClassTooLong — 1519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 152 methods, 2 blocks, lines 496-2841. The bar is 400 significant lines; this is 1119 over it, 3.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BuiltinTypedArray core/engine/src/builtins/typed_array/builtin.rs:35— ClassTooLong — 1445 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 49 methods, 4 blocks, lines 37-3170. The bar is 400 significant lines; this is 1045 over it, 3.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Array core/engine/src/builtins/array/mod.rs:61— ClassTooLong — 1390 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 55 methods, 6 blocks, lines 61-3336. The bar is 400 significant lines; this is 990 over it, 3.48× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Promise core/engine/src/builtins/promise/mod.rs:84— ClassTooLong — 1058 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 5 blocks, lines 84-2565. The bar is 400 significant lines; this is 658 over it, 2.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: String core/engine/src/builtins/string/mod.rs:62— ClassTooLong — 1051 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 54 methods, 5 blocks, lines 64-2635. The bar is 400 significant lines; this is 651 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RegExp core/engine/src/builtins/regexp/mod.rs:42— ClassTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 33 methods, 6 blocks, lines 42-2107. The bar is 400 significant lines; this is 543 over it, 2.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ZonedDateTime core/engine/src/builtins/temporal/zoneddatetime/mod.rs:57— ClassTooLong — 934 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 51 methods, 8 blocks, lines 57-1875. The bar is 400 significant lines; this is 534 over it, 2.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SourceTextModule core/engine/src/module/source.rs:253— ClassTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 3 blocks, lines 253-2037. The bar is 400 significant lines; this is 482 over it, 2.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Date core/engine/src/builtins/date/mod.rs:48— ClassTooLong — 878 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods, 5 blocks, lines 50-1912. The bar is 400 significant lines; this is 478 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PlainDateTime core/engine/src/builtins/temporal/plain_date_time/mod.rs:59— ClassTooLong — 780 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 42 methods, 8 blocks, lines 59-1605. The bar is 400 significant lines; this is 380 over it, 1.95× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CodeBlock core/engine/src/vm/code_block.rs:127— ClassTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 4 blocks, lines 127-1079. The bar is 400 significant lines; this is 325 over it, 1.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OrdinaryObject core/engine/src/builtins/object/mod.rs:48— ClassTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 36 methods, 4 blocks, lines 50-1430. The bar is 400 significant lines; this is 204 over it, 1.51× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PlainDate core/engine/src/builtins/temporal/plain_date/mod.rs:60— ClassTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 34 methods, 8 blocks, lines 60-1271. The bar is 400 significant lines; this is 171 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ClassElement core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:507— ClassTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 3 blocks, lines 507-1299. The bar is 400 significant lines; this is 165 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Duration core/engine/src/builtins/temporal/duration/mod.rs:45— ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 27 methods, 8 blocks, lines 45-1159. The bar is 400 significant lines; this is 149 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.
ClassTooLong: Json core/engine/src/builtins/json/mod.rs:200— ClassTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 3 blocks, lines 202-1242. The bar is 400 significant lines; this is 118 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BindingCollectorVisitor core/ast/src/scope_analyzer.rs:577— ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 3 blocks, lines 577-1222. The bar is 400 significant lines; this is 91 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DataView core/engine/src/builtins/dataview/mod.rs:39— ClassTooLong — 481 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 6 blocks, lines 39-1136. The bar is 400 significant lines; this is 81 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JsValue core/engine/src/value/mod.rs:118— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 131 methods, 3 blocks, lines 120-1747. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: NumberFormat core/engine/src/builtins/intl/number_format/mod.rs:115— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 6 methods, 8 blocks, lines 115-922. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Number core/engine/src/builtins/number/mod.rs:47— ClassTooLong — 442 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 22 methods, 4 blocks, lines 49-941. The bar is 400 significant lines; this is 42 over it, 1.11× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: StandardConstructors core/engine/src/context/intrinsics.rs:126— ClassTooLong — 441 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 63 methods, 3 blocks, lines 126-1080. The bar is 400 significant lines; this is 41 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JsTypedArray core/engine/src/object/builtins/jstypedarray.rs:20— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 41 methods, 4 blocks, lines 20-973. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JsString core/string/src/lib.rs:138— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 43 methods, 28 blocks, lines 138-998. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Set core/engine/src/builtins/set/mod.rs:120— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 4 blocks, lines 122-1109. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
boa_engine::builtins::string::get_substitution (cognitive 63) core/engine/src/builtins/string/mod.rs:2643— boa_engine::builtins::string::get_substitution has cognitive complexity 63 (threshold 15). Drivers by points: if/else 14 (47 pts), match/switch 2 (9 pts), loops 2 (6 pts), boolean chains 1 (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
boa_engine::bytecompiler::declarations::prepare_eval_declaration_instantiation (cognitive 53) core/engine/src/bytecompiler/declarations.rs:194— boa_engine::bytecompiler::declarations::prepare_eval_declaration_instantiation has cognitive complexity 53 (threshold 15). Drivers by points: if/else 13 (42 pts), loops 3 (7 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 34). 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.
boa_engine::object::internal_methods::validate_and_apply_property_descriptor (cognitive 47) core/engine/src/object/internal_methods/mod.rs:1026— boa_engine::object::internal_methods::validate_and_apply_property_descriptor has cognitive complexity 47 (threshold 15). Drivers by points: if/else 19 (36 pts), match/switch 3 (7 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::value::display::value::log_value_to (cognitive 45) core/engine/src/value/display/value.rs:28— boa_engine::value::display::value::log_value_to has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (29 pts), match/switch 5 (15 pts), boolean chains 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
boa_engine::builtins::uri::decode (cognitive 40) core/engine/src/builtins/uri/mod.rs:366— boa_engine::builtins::uri::decode has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 2 (5 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::builtins::array::from_async::from_async_iterator (cognitive 34) core/engine/src/builtins/array/from_async.rs:245— boa_engine::builtins::array::from_async::from_async_iterator has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 5 (13 pts), loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::bytecompiler::declarations::global_declaration_instantiation_context (cognitive 33) core/engine/src/bytecompiler/declarations.rs:57— boa_engine::bytecompiler::declarations::global_declaration_instantiation_context has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (24 pts), loops 4 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). 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.
boa_engine::value::display::value::log_value_compact (cognitive 29) core/engine/src/value/display/value.rs:184— boa_engine::value::display::value::log_value_compact has cognitive complexity 29 (threshold 15). Drivers by points: if/else 17 (22 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
boa_engine::value::display::array::log_array_to (cognitive 28) core/engine/src/value/display/array.rs:6— boa_engine::value::display::array::log_array_to has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 2 (9 pts), loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::builtins::array::array_exotic_define_own_property (cognitive 26) core/engine/src/builtins/array/mod.rs:3448— boa_engine::builtins::array::array_exotic_define_own_property has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (24 pts), boolean chains 1, match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
boa_engine::builtins::intl::date_time_format::create_date_time_format (cognitive 23) core/engine/src/builtins/intl/date_time_format/mod.rs:599— boa_engine::builtins::intl::date_time_format::create_date_time_format has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 4 (6 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
boa_engine::builtins::proxy::proxy_exotic_get_own_property (cognitive 23) core/engine/src/builtins/proxy/mod.rs:468— boa_engine::builtins::proxy::proxy_exotic_get_own_property has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 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.
boa_engine::builtins::proxy::proxy_exotic_own_property_keys (cognitive 23) core/engine/src/builtins/proxy/mod.rs:1032— boa_engine::builtins::proxy::proxy_exotic_own_property_keys has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4, match/switch 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::builtins::typed_array::base64::decode_mut (cognitive 23) REDACTED:36— boa_engine::builtins::typed_array::base64::decode_mut has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (5 pts), match/switch 4 (5 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.
boa_engine::object::internal_methods::ordinary_set (cognitive 23) core/engine/src/object/internal_methods/mod.rs:810— boa_engine::object::internal_methods::ordinary_set has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::builtins::number::globals::parse_int (cognitive 22) core/engine/src/builtins/number/globals.rs:156— boa_engine::builtins::number::globals::parse_int 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, 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.
boa_engine::value::display::arguments::log_arguments_to (cognitive 21) core/engine/src/value/display/arguments.rs:19— boa_engine::value::display::arguments::log_arguments_to has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 2 (9 pts), 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.
boa_engine::vm::opcode::get::property::get_by_value (cognitive 20) core/engine/src/vm/opcode/get/property.rs:82— boa_engine::vm::opcode::get::property::get_by_value has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 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.
boa_engine::builtins::proxy::proxy_exotic_define_own_property (cognitive 18) core/engine/src/builtins/proxy/mod.rs:596— boa_engine::builtins::proxy::proxy_exotic_define_own_property has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::module::source::async_module_execution_fulfilled (cognitive 18) core/engine/src/module/source.rs:2043— boa_engine::module::source::async_module_execution_fulfilled has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), match/switch 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.
boa_engine::builtins::function::arguments::arguments_exotic_define_own_property (cognitive 17) core/engine/src/builtins/function/arguments.rs:322— boa_engine::builtins::function::arguments::arguments_exotic_define_own_property has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_engine::builtins::typed_array::builtin::compare_typed_array_elements (cognitive 17) core/engine/src/builtins/typed_array/builtin.rs:3184— boa_engine::builtins::typed_array::builtin::compare_typed_array_elements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
boa_engine::vm::opcode::set::property::set_by_name (cognitive 17) core/engine/src/vm/opcode/set/property.rs:15— boa_engine::vm::opcode::set::property::set_by_name has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 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.
boa_engine::builtins::array::array_set_length (cognitive 16) core/engine/src/builtins/array/mod.rs:3565— boa_engine::builtins::array::array_set_length has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Duplicated block (12 lines × 2) core/ast/src/function/arrow_function.rs:120— core/ast/src/function/arrow_function.rs:120-131 | core/ast/src/function/async_arrow_function.rs:121-132 — before extracting anything, compare `core/ast/src/function/arrow_function.rs` and `core/ast/src/function/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 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 (12 lines × 2) core/engine/src/builtins/array_buffer/mod.rs:968— core/engine/src/builtins/array_buffer/mod.rs:968-979 | core/engine/src/builtins/array_buffer/shared.rs:593-604 — before extracting anything, compare `core/engine/src/builtins/array_buffer/mod.rs` and `core/engine/src/builtins/array_buffer/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 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 (12 lines × 2) core/engine/src/builtins/date/mod.rs:1195— core/engine/src/builtins/date/mod.rs:1195-1206 | core/engine/src/builtins/date/mod.rs:1257-1268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/iterable/iterator_constructor.rs:443— core/engine/src/builtins/iterable/iterator_constructor.rs:443-454 | core/engine/src/builtins/iterable/iterator_constructor.rs:517-528 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:1011— core/engine/src/builtins/temporal/plain_date/mod.rs:1011-1022 | core/engine/src/builtins/temporal/plain_date/mod.rs:1042-1053 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:874— core/engine/src/builtins/typed_array/builtin.rs:874-885 | core/engine/src/builtins/typed_array/builtin.rs:946-957 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:910— core/engine/src/builtins/typed_array/builtin.rs:910-921 | core/engine/src/builtins/typed_array/builtin.rs:982-993 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1172— core/engine/src/builtins/typed_array/builtin.rs:1172-1183 | core/engine/src/builtins/typed_array/builtin.rs:1307-1318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1731— core/engine/src/builtins/typed_array/builtin.rs:1731-1742 | core/engine/src/builtins/typed_array/builtin.rs:1750-1761 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/typed_array/object.rs:568— core/engine/src/builtins/typed_array/object.rs:568-579 | core/engine/src/builtins/typed_array/object.rs:610-621 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/bytecompiler/mod.rs:778— core/engine/src/bytecompiler/mod.rs:778-789 | core/engine/src/bytecompiler/mod.rs:805-816 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/bytecompiler/mod.rs:2473— core/engine/src/bytecompiler/mod.rs:2473-2484 | core/engine/src/bytecompiler/mod.rs:2553-2564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/property/mod.rs:308— core/engine/src/property/mod.rs:308-319 | core/engine/src/property/mod.rs:389-400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/vm/opcode/define/class/getter.rs:150— core/engine/src/vm/opcode/define/class/getter.rs:150-161 | core/engine/src/vm/opcode/define/class/setter.rs:153-164 — before extracting anything, compare `core/engine/src/vm/opcode/define/class/getter.rs` and `core/engine/src/vm/opcode/define/class/setter.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 (12 lines × 2) core/engine/src/vm/opcode/define/class/method.rs:121— core/engine/src/vm/opcode/define/class/method.rs:121-132 | core/engine/src/vm/opcode/define/class/method.rs:170-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/vm/opcode/templates/mod.rs:61— core/engine/src/vm/opcode/templates/mod.rs:61-72 | core/engine/src/vm/opcode/templates/mod.rs:74-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/object/builtins/jsarray.rs:151— core/engine/src/object/builtins/jsarray.rs:151-162 | core/engine/src/object/builtins/jstypedarray.rs:222-233 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) core/engine/src/object/builtins/jstypedarray.rs:781— core/engine/src/object/builtins/jstypedarray.rs:781-792 | core/engine/src/object/builtins/jstypedarray.rs:807-818 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/builtins/object/mod.rs:583— core/engine/src/builtins/object/mod.rs:583-594 | core/engine/src/builtins/object/mod.rs:604-615 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) cli/src/debug/limits.rs:125— cli/src/debug/limits.rs:125-136 | cli/src/debug/optimizer.rs:67-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) core/engine/src/object/builtins/jsarray.rs:177— core/engine/src/object/builtins/jsarray.rs:177-188 | core/engine/src/object/builtins/jsarray.rs:203-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/engine/src/object/builtins/jstypedarray.rs:548— core/engine/src/object/builtins/jstypedarray.rs:548-559 | core/engine/src/object/builtins/jstypedarray.rs:656-667 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) core/parser/src/parser/expression/primary/mod.rs:614— core/parser/src/parser/expression/primary/mod.rs:614-625 | core/parser/src/parser/expression/primary/mod.rs:627-638 — 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.
TooManyMethods: ByteCompiler core/engine/src/bytecompiler/mod.rs:496— TooManyMethods — 152 methods, declared across 26 files: bytecompiler/mod.rs (76), bytecompiler/jump_control.rs (17), expression/binary.rs (5), statement/loop.rs (5), +22 more file(s). The bar is 30 methods; this is 122 over it, 5.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsValue core/engine/src/value/mod.rs:118— TooManyMethods — 131 methods, declared across 10 files: value/mod.rs (69), value/operations.rs (39), value/equality.rs (8), object/operations.rs (6), +6 more file(s). The bar is 30 methods; this is 101 over it, 4.37× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsObject core/engine/src/object/jsobject.rs:62— TooManyMethods — 90 methods, declared across 4 files: object/jsobject.rs (41), object/operations.rs (33), internal_methods/mod.rs (14), iterable/mod.rs (2). The bar is 30 methods; this is 60 over it, 3.00× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Context core/engine/src/context/mod.rs:96— TooManyMethods — 77 methods, declared across 3 files: context/mod.rs (57), vm/mod.rs (11), runtime/mod.rs (9). The bar is 30 methods; this is 47 over it, 2.57× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Array core/engine/src/builtins/array/mod.rs:61— TooManyMethods — 55 methods, declared across 2 files: array/mod.rs (54), array/from_async.rs (1). The bar is 30 methods; this is 25 over it, 1.83× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: String core/engine/src/builtins/string/mod.rs:62— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: ZonedDateTime core/engine/src/builtins/temporal/zoneddatetime/mod.rs:57— TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsDate core/engine/src/object/builtins/jsdate.rs:38— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: BuiltinTypedArray core/engine/src/builtins/typed_array/builtin.rs:35— 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: JsString core/string/src/lib.rs:138— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: PlainDateTime core/engine/src/builtins/temporal/plain_date_time/mod.rs:59— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsTypedArray core/engine/src/object/builtins/jstypedarray.rs:20— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Date core/engine/src/builtins/date/mod.rs:48— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Math core/engine/src/builtins/math/mod.rs:27— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NanBoxedValue core/engine/src/value/inner/nan_boxed.rs:325— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OrdinaryObject core/engine/src/builtins/object/mod.rs:48— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: PlainDate core/engine/src/builtins/temporal/plain_date/mod.rs:60— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: RegExp core/engine/src/builtins/regexp/mod.rs:42— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: Url core/runtime/src/url.rs:649— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsBigInt core/engine/src/bigint.rs:30— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: JsArray core/engine/src/object/builtins/jsarray.rs:14— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
Duplicated block (8 lines × 2) core/ast/src/scope_analyzer.rs:107— core/ast/src/scope_analyzer.rs:107-114 | core/ast/src/scope_analyzer.rs:127-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/ast/src/scope_analyzer.rs:228— core/ast/src/scope_analyzer.rs:228-235 | core/ast/src/scope_analyzer.rs:260-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/array/mod.rs:1207— core/engine/src/builtins/array/mod.rs:1207-1214 | core/engine/src/builtins/array/mod.rs:1216-1223 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/atomics/mod.rs:244— core/engine/src/builtins/atomics/mod.rs:244-251 | core/engine/src/builtins/atomics/mod.rs:292-299 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/dataview/mod.rs:451— core/engine/src/builtins/dataview/mod.rs:451-458 | core/engine/src/builtins/dataview/mod.rs:793-800 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/generator/mod.rs:267— core/engine/src/builtins/generator/mod.rs:267-274 | core/engine/src/builtins/generator/mod.rs:347-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/context/mod.rs:674— core/engine/src/context/mod.rs:674-681 | core/engine/src/context/mod.rs:829-836 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/object/property_map.rs:391— core/engine/src/object/property_map.rs:391-398 | core/engine/src/object/property_map.rs:402-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/object/property_map.rs:422— core/engine/src/object/property_map.rs:422-429 | core/engine/src/object/property_map.rs:431-438 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/object/property_map.rs:920— core/engine/src/object/property_map.rs:920-927 | core/engine/src/object/property_map.rs:1035-1042 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/object/property_map.rs:933— core/engine/src/object/property_map.rs:933-940 | core/engine/src/object/property_map.rs:1048-1055 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1088— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1088-1095 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1181-1188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/runtime/src/fetch/response.rs:295— core/runtime/src/fetch/response.rs:295-302 | core/runtime/src/fetch/response.rs:311-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/array_buffer/mod.rs:652— core/engine/src/builtins/array_buffer/mod.rs:652-660 | core/engine/src/builtins/typed_array/object.rs:200-207 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/engine/src/builtins/set/mod.rs:293— core/engine/src/builtins/set/mod.rs:293-300 | core/engine/src/builtins/set/mod.rs:357-365 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/array/mod.rs:952— core/engine/src/builtins/array/mod.rs:952-959 | core/engine/src/builtins/array/mod.rs:2600-2608 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:321— core/engine/src/builtins/temporal/instant/mod.rs:321-329 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:836-843 — `core/engine/src/builtins/temporal/instant/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) core/engine/src/builtins/dataview/mod.rs:373— core/engine/src/builtins/dataview/mod.rs:373-380 | core/engine/src/builtins/typed_array/builtin.rs:2908-2915 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:611— core/engine/src/builtins/temporal/plain_date_time/mod.rs:611-618 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:629-636 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) core/macros/src/lib.rs:527— core/macros/src/lib.rs:527-534 | core/macros/src/lib.rs:662-669 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) core/engine/src/builtins/weak_map/mod.rs:305— core/engine/src/builtins/weak_map/mod.rs:305-312 | core/engine/src/builtins/weak_map/mod.rs:360-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) core/ast/src/scope_analyzer.rs:2393— core/ast/src/scope_analyzer.rs:2393-2401 | core/engine/src/bytecompiler/declarations.rs:243-251 | core/engine/src/bytecompiler/declarations.rs:651-659 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) core/engine/src/builtins/date/mod.rs:1407— core/engine/src/builtins/date/mod.rs:1407-1415 | core/engine/src/builtins/date/mod.rs:1685-1693 | core/engine/src/builtins/date/mod.rs:1723-1731 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1413— core/engine/src/builtins/temporal/plain_date/mod.rs:1413-1421 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1738-1747 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2109-2118 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_year_month/mod.rs:632— core/engine/src/builtins/temporal/plain_year_month/mod.rs:632-640 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:667-675 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:702-710 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1400— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1400-1408 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1431-1439 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1539-1547 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/bytecompiler/mod.rs:283— core/engine/src/bytecompiler/mod.rs:283-291 | core/engine/src/bytecompiler/mod.rs:298-306 | core/engine/src/bytecompiler/mod.rs:313-321 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/vm/opcode/call/mod.rs:107— core/engine/src/vm/opcode/call/mod.rs:107-115 | core/engine/src/vm/opcode/environment/mod.rs:186-194 | core/engine/src/vm/opcode/new/mod.rs:51-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) core/parser/src/parser/function/mod.rs:493— core/parser/src/parser/function/mod.rs:493-501 | core/parser/src/parser/mod.rs:422-430 | core/parser/src/parser/statement/mod.rs:965-973 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9 lines × 3) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:764— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:764-772 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:872-880 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:974-982 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/duration/mod.rs:334— core/engine/src/builtins/temporal/duration/mod.rs:334-344 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:195-203 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:300-308 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:710— core/engine/src/builtins/temporal/plain_date_time/mod.rs:710-719 | core/engine/src/builtins/temporal/plain_time/mod.rs:322-331 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:720-728 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:736— core/engine/src/builtins/temporal/plain_date_time/mod.rs:736-745 | core/engine/src/builtins/temporal/plain_time/mod.rs:348-357 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:743-751 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:684— core/engine/src/builtins/temporal/plain_date_time/mod.rs:684-693 | core/engine/src/builtins/temporal/plain_time/mod.rs:296-305 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:697-705 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:788— core/engine/src/builtins/temporal/plain_date_time/mod.rs:788-797 | core/engine/src/builtins/temporal/plain_time/mod.rs:400-409 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:789-797 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:762— core/engine/src/builtins/temporal/plain_date_time/mod.rs:762-771 | core/engine/src/builtins/temporal/plain_time/mod.rs:374-383 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:766-774 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:658— core/engine/src/builtins/temporal/plain_date_time/mod.rs:658-667 | core/engine/src/builtins/temporal/plain_time/mod.rs:270-279 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:674-682 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:72— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:72-80 | core/parser/src/parser/expression/primary/function_expression/mod.rs:71-79 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:76-84 — `core/parser/src/parser/expression/primary/async_function_expression/mod.rs` and `core/parser/src/parser/expression/primary/function_expression/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 81 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) core/engine/src/builtins/intl/locale/mod.rs:424— core/engine/src/builtins/intl/locale/mod.rs:424-432 | core/engine/src/builtins/intl/locale/mod.rs:448-456 | core/engine/src/builtins/intl/locale/mod.rs:658-666 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:996— core/engine/src/builtins/temporal/plain_date_time/mod.rs:996-1004 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:520-528 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1068-1076 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 172 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) core/engine/src/builtins/async_generator/mod.rs:601— core/engine/src/builtins/async_generator/mod.rs:601-614 | core/engine/src/vm/opcode/await/mod.rs:91-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) core/engine/src/builtins/intl/date_time_format/mod.rs:1233— core/engine/src/builtins/intl/date_time_format/mod.rs:1233-1246 | core/engine/src/builtins/intl/number_format/mod.rs:947-960 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/number_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 137 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) core/engine/src/builtins/intl/number_format/mod.rs:824— core/engine/src/builtins/intl/number_format/mod.rs:824-837 | core/engine/src/builtins/intl/plural_rules/mod.rs:363-376 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) core/engine/src/builtins/temporal/duration/mod.rs:1100— core/engine/src/builtins/temporal/duration/mod.rs:1100-1113 | core/engine/src/builtins/temporal/duration/mod.rs:1130-1143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:394— core/engine/src/builtins/temporal/plain_date_time/mod.rs:394-407 | core/engine/src/builtins/temporal/plain_time/mod.rs:194-207 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1193— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1193-1206 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1227-1240 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1401— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1401-1414 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1432-1445 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/bytecompiler/mod.rs:1621— core/engine/src/bytecompiler/mod.rs:1621-1634 | core/engine/src/bytecompiler/mod.rs:1671-1684 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/value/display/array.rs:46— core/engine/src/value/display/array.rs:46-59 | core/engine/src/value/display/array.rs:113-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/vm/mod.rs:956— core/engine/src/vm/mod.rs:956-969 | core/engine/src/vm/mod.rs:989-1002 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/vm/opcode/await/mod.rs:63— core/engine/src/vm/opcode/await/mod.rs:63-76 | core/engine/src/vm/opcode/await/mod.rs:102-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/vm/opcode/define/class/getter.rs:27— core/engine/src/vm/opcode/define/class/getter.rs:27-40 | core/engine/src/vm/opcode/define/class/getter.rs:84-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/engine/src/vm/opcode/define/class/setter.rs:27— core/engine/src/vm/opcode/define/class/setter.rs:27-40 | core/engine/src/vm/opcode/define/class/setter.rs:85-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/parser/src/parser/expression/update.rs:97— core/parser/src/parser/expression/update.rs:97-110 | core/parser/src/parser/expression/update.rs:125-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/parser/src/parser/function/mod.rs:353— core/parser/src/parser/function/mod.rs:353-366 | core/parser/src/parser/function/mod.rs:369-382 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/wintertc/src/timers/mod.rs:88— core/wintertc/src/timers/mod.rs:88-101 | core/wintertc/src/timers/mod.rs:140-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) core/parser/src/parser/expression/left_hand_side/call.rs:161— core/parser/src/parser/expression/left_hand_side/call.rs:161-174 | core/parser/src/parser/expression/left_hand_side/member.rs:275-288 — before extracting anything, compare `core/parser/src/parser/expression/left_hand_side/call.rs` and `core/parser/src/parser/expression/left_hand_side/member.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1435— core/engine/src/builtins/typed_array/builtin.rs:1435-1448 | core/engine/src/builtins/typed_array/builtin.rs:1509-1522 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/ast/src/operations/mod.rs:2463— core/ast/src/operations/mod.rs:2463-2475 | core/ast/src/operations/mod.rs:2481-2493 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/builtins/iterable/iterator_constructor.rs:252— core/engine/src/builtins/iterable/iterator_constructor.rs:252-264 | core/engine/src/builtins/iterable/iterator_constructor.rs:310-322 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1460— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1460-1472 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1484-1496 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:354— core/engine/src/builtins/temporal/plain_month_day/mod.rs:354-366 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:735-747 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) core/engine/src/builtins/temporal/plain_time/mod.rs:783— core/engine/src/builtins/temporal/plain_time/mod.rs:783-795 | core/engine/src/builtins/temporal/plain_time/mod.rs:807-819 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/builtins/typed_array/builtin_uint8.rs:269— core/engine/src/builtins/typed_array/builtin_uint8.rs:269-281 | core/engine/src/builtins/typed_array/builtin_uint8.rs:534-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/bytecompiler/mod.rs:943— core/engine/src/bytecompiler/mod.rs:943-955 | core/engine/src/bytecompiler/mod.rs:971-983 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/bytecompiler/statement/try.rs:90— core/engine/src/bytecompiler/statement/try.rs:90-102 | core/engine/src/bytecompiler/statement/try.rs:129-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/object/jsobject.rs:241— core/engine/src/object/jsobject.rs:241-253 | core/engine/src/object/jsobject.rs:1080-1092 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/value/operations.rs:135— core/engine/src/value/operations.rs:135-147 | core/engine/src/value/operations.rs:189-201 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/macros/src/value.rs:219— core/macros/src/value.rs:219-231 | core/macros/src/value.rs:250-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/parser/src/parser/expression/assignment/arrow_function.rs:199— core/parser/src/parser/expression/assignment/arrow_function.rs:199-211 | core/parser/src/parser/expression/assignment/async_arrow_function.rs:192-204 — before extracting anything, compare `core/parser/src/parser/expression/assignment/arrow_function.rs` and `core/parser/src/parser/expression/assignment/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:357— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:357-369 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:387-399 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/parser/src/parser/statement/mod.rs:780— core/parser/src/parser/statement/mod.rs:780-792 | core/parser/src/parser/statement/mod.rs:839-852 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/ast/src/function/arrow_function.rs:47— core/ast/src/function/arrow_function.rs:47-59 | core/ast/src/function/async_arrow_function.rs:48-60 — before extracting anything, compare `core/ast/src/function/arrow_function.rs` and `core/ast/src/function/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:666— core/engine/src/builtins/typed_array/builtin.rs:666-678 | core/engine/src/builtins/typed_array/builtin.rs:2222-2234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) core/engine/src/builtins/temporal/duration/mod.rs:1315— core/engine/src/builtins/temporal/duration/mod.rs:1315-1327 | core/engine/src/builtins/temporal/duration/mod.rs:1363-1375 — 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) core/ast/src/scope_analyzer.rs:449— core/ast/src/scope_analyzer.rs:449-455 | core/ast/src/scope_analyzer.rs:458-464 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) core/ast/src/scope_analyzer.rs:1019— core/ast/src/scope_analyzer.rs:1019-1025 | core/ast/src/scope_analyzer.rs:1086-1092 — 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) core/engine/src/builtins/array_buffer/utils.rs:439— core/engine/src/builtins/array_buffer/utils.rs:439-445 | core/engine/src/builtins/array_buffer/utils.rs:517-523 — 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) core/engine/src/builtins/map/mod.rs:45— core/engine/src/builtins/map/mod.rs:45-51 | core/engine/src/builtins/set/mod.rs:127-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) core/engine/src/vm/code_block.rs:1095— core/engine/src/vm/code_block.rs:1095-1101 | core/engine/src/vm/code_block.rs:1163-1169 — 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) core/engine/src/vm/opcode/call/mod.rs:420— core/engine/src/vm/opcode/call/mod.rs:420-426 | core/engine/src/vm/opcode/call/mod.rs:437-443 — 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) core/runtime/src/fetch/request.rs:290— core/runtime/src/fetch/request.rs:290-296 | core/runtime/src/fetch/response.rs:528-535 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) core/runtime/src/url.rs:493— core/runtime/src/url.rs:493-499 | core/runtime/src/url.rs:576-582 — 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) core/ast/src/expression/yield.rs:84— core/ast/src/expression/yield.rs:84-90 | core/ast/src/statement/return.rs:66-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) core/ast/src/expression/yield.rs:95— core/ast/src/expression/yield.rs:95-101 | core/ast/src/statement/return.rs:77-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) core/ast/src/statement/iteration/break.rs:61— core/ast/src/statement/iteration/break.rs:61-67 | core/ast/src/statement/iteration/continue.rs:59-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 (7 lines × 2) core/ast/src/statement/iteration/break.rs:72— core/ast/src/statement/iteration/break.rs:72-78 | core/ast/src/statement/iteration/continue.rs:70-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) core/engine/src/object/builtins/jsmap.rs:407— core/engine/src/object/builtins/jsmap.rs:407-413 | core/engine/src/object/builtins/jsset.rs:140-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) core/engine/src/object/builtins/jsweakmap.rs:136— core/engine/src/object/builtins/jsweakmap.rs:136-142 | core/engine/src/object/builtins/jsweakset.rs:80-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) core/engine/src/builtins/array/mod.rs:1403— core/engine/src/builtins/array/mod.rs:1403-1409 | core/engine/src/builtins/array/mod.rs:1819-1827 — 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) core/engine/src/builtins/array/mod.rs:1353— core/engine/src/builtins/array/mod.rs:1353-1359 | core/engine/src/builtins/array/mod.rs:2534-2542 — 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) core/engine/src/builtins/map/map_iterator.rs:108— core/engine/src/builtins/map/map_iterator.rs:108-114 | core/engine/src/builtins/set/set_iterator.rs:107-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
ByteCompiler::compile_update (cognitive 88) core/engine/src/bytecompiler/expression/update.rs:13— ByteCompiler::compile_update has cognitive complexity 88 (threshold 15). Drivers by points: if/else 31 (74 pts), match/switch 5 (12 pts), boolean chains 2 (nesting depth added 50). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_lexical_decl (cognitive 73) core/engine/src/bytecompiler/mod.rs:2218— ByteCompiler::compile_lexical_decl has cognitive complexity 73 (threshold 15). Drivers by points: if/else 20 (52 pts), match/switch 5 (13 pts), loops 4 (8 pts) (nesting depth added 44). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_class (cognitive 68) core/engine/src/bytecompiler/class.rs:82— ByteCompiler::compile_class has cognitive complexity 68 (threshold 15). Drivers by points: if/else 22 (41 pts), match/switch 10 (24 pts), loops 3 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ByteCompiler::compile_declaration_pattern_impl (cognitive 66) core/engine/src/bytecompiler/declaration/declaration_pattern.rs:12— ByteCompiler::compile_declaration_pattern_impl has cognitive complexity 66 (threshold 15). Drivers by points: if/else 7 (24 pts), loops 7 (22 pts), match/switch 6 (20 pts) (nesting depth added 46). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::function_declaration_instantiation (cognitive 65) core/engine/src/bytecompiler/declarations.rs:876— ByteCompiler::function_declaration_instantiation has cognitive complexity 65 (threshold 15). Drivers by points: if/else 25 (46 pts), loops 6 (9 pts), boolean chains 6, match/switch 2 (4 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ByteCompiler::compile_expr_impl (cognitive 62) core/engine/src/bytecompiler/expression/mod.rs:90— ByteCompiler::compile_expr_impl has cognitive complexity 62 (threshold 15). Drivers by points: if/else 21 (35 pts), loops 7 (16 pts), match/switch 5 (11 pts) (nesting depth added 29). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_assign (cognitive 37) core/engine/src/bytecompiler/expression/assign.rs:15— ByteCompiler::compile_assign has cognitive complexity 37 (threshold 15). Drivers by points: match/switch 8 (22 pts), if/else 9 (15 pts) (nesting depth added 20). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_stmt (cognitive 32) core/engine/src/bytecompiler/statement/mod.rs:19— ByteCompiler::compile_stmt has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 4, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::call (cognitive 31) core/engine/src/bytecompiler/mod.rs:2635— ByteCompiler::call has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 5 (8 pts), loops 2 (4 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ByteCompiler::eval_declaration_instantiation (cognitive 29) core/engine/src/bytecompiler/declarations.rs:615— ByteCompiler::eval_declaration_instantiation has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 7 (10 pts), match/switch 2 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ByteCompiler::compile_for_loop (cognitive 29) core/engine/src/bytecompiler/statement/loop.rs:18— ByteCompiler::compile_for_loop has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 5 (12 pts), match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ByteCompiler::compile_object_literal (cognitive 26) core/engine/src/bytecompiler/expression/object_literal.rs:11— ByteCompiler::compile_object_literal has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 3 (9 pts), boolean chains 1, loops 1 (nesting depth added 16). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_for_of_loop (cognitive 19) core/engine/src/bytecompiler/statement/loop.rs:269— ByteCompiler::compile_for_of_loop has cognitive complexity 19 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 7, boolean chains 1 (nesting depth added 7). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::global_declaration_instantiation (cognitive 18) core/engine/src/bytecompiler/declarations.rs:374— ByteCompiler::global_declaration_instantiation has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 6 (7 pts), match/switch 2 (4 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.
ByteCompiler::compile_optional_item_kind (cognitive 17) core/engine/src/bytecompiler/mod.rs:2100— ByteCompiler::compile_optional_item_kind has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (6 pts), match/switch 2 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ByteCompiler::compile_statement_list (cognitive 16) core/engine/src/bytecompiler/mod.rs:1732— ByteCompiler::compile_statement_list has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 2 (7 pts), loops 3 (6 pts), if/else 2, 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.
FunctionTooLong: boa_ast::operations::check_labels core/ast/src/operations/mod.rs:1434— FunctionTooLong — boa_ast::operations::check_labels runs 220 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_ast::operations::contains core/ast/src/operations/mod.rs:77— FunctionTooLong — boa_ast::operations::contains runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::object::internal_methods::validate_and_apply_property_descriptor core/engine/src/object/internal_methods/mod.rs:1026— FunctionTooLong — boa_engine::object::internal_methods::validate_and_apply_property_descriptor runs 147 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::temporal::zoneddatetime::to_zoned_date_time_fields core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2103— FunctionTooLong — boa_engine::builtins::temporal::zoneddatetime::to_zoned_date_time_fields runs 134 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::array::from_async::from_async_iterator core/engine/src/builtins/array/from_async.rs:245— FunctionTooLong — boa_engine::builtins::array::from_async::from_async_iterator runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::intl::date_time_format::create_date_time_format core/engine/src/builtins/intl/date_time_format/mod.rs:599— FunctionTooLong — boa_engine::builtins::intl::date_time_format::create_date_time_format runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::typed_array::base64::decode_mut REDACTED:36— FunctionTooLong — boa_engine::builtins::typed_array::base64::decode_mut runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_ast::scope_analyzer::eval_declaration_instantiation_scope core/ast/src/scope_analyzer.rs:2305— FunctionTooLong — boa_ast::scope_analyzer::eval_declaration_instantiation_scope runs 116 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::temporal::plain_date_time::to_date_time_fields core/engine/src/builtins/temporal/plain_date_time/mod.rs:1733— FunctionTooLong — boa_engine::builtins::temporal::plain_date_time::to_date_time_fields runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_ast::scope_analyzer::function_declaration_instantiation core/ast/src/scope_analyzer.rs:1877— FunctionTooLong — boa_ast::scope_analyzer::function_declaration_instantiation runs 113 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::vm::opcode::call::load_dyn_import core/engine/src/vm/opcode/call/mod.rs:344— FunctionTooLong — boa_engine::vm::opcode::call::load_dyn_import runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::value::display::value::log_value_to core/engine/src/value/display/value.rs:28— FunctionTooLong — boa_engine::value::display::value::log_value_to runs 108 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_engine::builtins::temporal::duration::to_temporal_partial_duration core/engine/src/builtins/temporal/duration/mod.rs:1271— FunctionTooLong — boa_engine::builtins::temporal::duration::to_temporal_partial_duration runs 104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: boa_cli::main cli/src/main.rs:551— FunctionTooLong — boa_cli::main runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (5 lines × 2) core/engine/src/builtins/array/mod.rs:2724— core/engine/src/builtins/array/mod.rs:2724-2728 | core/engine/src/builtins/array/mod.rs:2790-2794 — 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 (5 lines × 2) core/engine/src/builtins/builder.rs:275— core/engine/src/builtins/builder.rs:275-279 | core/engine/src/builtins/builder.rs:355-359 — 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 (5 lines × 2) core/engine/src/builtins/date/mod.rs:1471— core/engine/src/builtins/date/mod.rs:1471-1475 | core/engine/src/builtins/date/utils.rs:504-512 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:1021— core/engine/src/builtins/temporal/plain_date/mod.rs:1021-1025 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1271-1275 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:1052— core/engine/src/builtins/temporal/plain_date/mod.rs:1052-1056 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1299-1303 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:101— core/engine/src/builtins/temporal/plain_month_day/mod.rs:101-105 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:181-185 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1219— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1219-1223 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1951-1955 — 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 (5 lines × 2) core/engine/src/vm/opcode/call/mod.rs:587— core/engine/src/vm/opcode/call/mod.rs:587-591 | core/engine/src/vm/opcode/call/mod.rs:597-601 — 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 (5 lines × 2) core/engine/src/vm/opcode/get/name.rs:24— core/engine/src/vm/opcode/get/name.rs:24-28 | core/engine/src/vm/opcode/get/name.rs:166-170 — 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 (5 lines × 2) core/parser/src/parser/statement/declaration/mod.rs:83— core/parser/src/parser/statement/declaration/mod.rs:83-87 | core/parser/src/parser/statement/mod.rs:440-444 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) core/parser/src/lexer/string.rs:300— core/parser/src/lexer/string.rs:300-304 | core/parser/src/lexer/string.rs:332-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) core/parser/src/parser/statement/declaration/export.rs:68— core/parser/src/parser/statement/declaration/export.rs:68-72 | core/parser/src/parser/statement/declaration/mod.rs:231-235 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) core/ast/src/operations/mod.rs:884— core/ast/src/operations/mod.rs:884-888 | core/ast/src/operations/mod.rs:2083-2087 — 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.
ByteCompiler::compile_expr_impl (cyclomatic 58) core/engine/src/bytecompiler/expression/mod.rs:90— ByteCompiler::compile_expr_impl has cyclomatic complexity 58 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ByteCompiler::compile_class (cyclomatic 46) core/engine/src/bytecompiler/class.rs:82— ByteCompiler::compile_class has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ByteCompiler::function_declaration_instantiation (cyclomatic 38) core/engine/src/bytecompiler/declarations.rs:876— ByteCompiler::function_declaration_instantiation has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ByteCompiler::compile_stmt (cyclomatic 32) core/engine/src/bytecompiler/statement/mod.rs:19— ByteCompiler::compile_stmt has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ByteCompiler::compile_assign (cyclomatic 30) core/engine/src/bytecompiler/expression/assign.rs:15— ByteCompiler::compile_assign has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ByteCompiler::compile_update (cyclomatic 30) core/engine/src/bytecompiler/expression/update.rs:13— ByteCompiler::compile_update has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ByteCompiler::eval_declaration_instantiation (cyclomatic 23) core/engine/src/bytecompiler/declarations.rs:615— ByteCompiler::eval_declaration_instantiation has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ByteCompiler::compile_declaration_pattern_impl (cyclomatic 22) core/engine/src/bytecompiler/declaration/declaration_pattern.rs:12— ByteCompiler::compile_declaration_pattern_impl has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ByteCompiler::compile_lexical_decl (cyclomatic 22) core/engine/src/bytecompiler/mod.rs:2218— ByteCompiler::compile_lexical_decl 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. This is NOT this file's highest cyclomatic complexity: ByteCompiler::emit_binding_access (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
ByteCompiler::call (cyclomatic 20) core/engine/src/bytecompiler/mod.rs:2635— ByteCompiler::call has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: ByteCompiler::emit_binding_access (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
ByteCompiler::global_declaration_instantiation (cyclomatic 18) core/engine/src/bytecompiler/declarations.rs:374— ByteCompiler::global_declaration_instantiation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ByteCompiler::compile_for_loop (cyclomatic 17) core/engine/src/bytecompiler/statement/loop.rs:18— ByteCompiler::compile_for_loop 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.
boa_engine::value::display::value::log_value_to (cyclomatic 34) core/engine/src/value/display/value.rs:28— boa_engine::value::display::value::log_value_to has cyclomatic complexity 34 (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.
boa_engine::object::internal_methods::validate_and_apply_property_descriptor (cyclomatic 31) core/engine/src/object/internal_methods/mod.rs:1026— boa_engine::object::internal_methods::validate_and_apply_property_descriptor 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.
boa_engine::builtins::typed_array::base64::decode_mut (cyclomatic 25) REDACTED:36— boa_engine::builtins::typed_array::base64::decode_mut has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
boa_engine::builtins::string::get_substitution (cyclomatic 22) core/engine/src/builtins/string/mod.rs:2643— boa_engine::builtins::string::get_substitution 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.
boa_engine::value::display::value::log_value_compact (cyclomatic 21) core/engine/src/value/display/value.rs:184— boa_engine::value::display::value::log_value_compact 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.
boa_engine::bytecompiler::declarations::prepare_eval_declaration_instantiation (cyclomatic 20) core/engine/src/bytecompiler/declarations.rs:194— boa_engine::bytecompiler::declarations::prepare_eval_declaration_instantiation 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.
boa_engine::builtins::intl::date_time_format::create_date_time_format (cyclomatic 19) core/engine/src/builtins/intl/date_time_format/mod.rs:599— boa_engine::builtins::intl::date_time_format::create_date_time_format 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.
boa_engine::builtins::array::from_async::from_async_iterator (cyclomatic 18) core/engine/src/builtins/array/from_async.rs:245— boa_engine::builtins::array::from_async::from_async_iterator 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.
boa_engine::builtins::number::globals::parse_int (cyclomatic 18) core/engine/src/builtins/number/globals.rs:156— boa_engine::builtins::number::globals::parse_int 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.
boa_engine::builtins::proxy::proxy_exotic_own_property_keys (cyclomatic 17) core/engine/src/builtins/proxy/mod.rs:1032— boa_engine::builtins::proxy::proxy_exotic_own_property_keys 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.
boa_engine::builtins::typed_array::builtin::compare_typed_array_elements (cyclomatic 17) core/engine/src/builtins/typed_array/builtin.rs:3184— boa_engine::builtins::typed_array::builtin::compare_typed_array_elements 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.
boa_engine::bytecompiler::declarations::global_declaration_instantiation_context (cyclomatic 17) core/engine/src/bytecompiler/declarations.rs:57— boa_engine::bytecompiler::declarations::global_declaration_instantiation_context 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.
Duplicated block (18 lines × 2) cli/src/executor.rs:130— cli/src/executor.rs:130-147 | cli/src/executor.rs:170-187 — 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 (18 lines × 2) core/ast/src/module_item_list/mod.rs:55— core/ast/src/module_item_list/mod.rs:55-72 | core/ast/src/module_item_list/mod.rs:135-152 — 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 (18 lines × 2) core/engine/src/builtins/date/utils.rs:909— core/engine/src/builtins/date/utils.rs:909-926 | core/engine/src/builtins/date/utils.rs:935-952 — 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 (18 lines × 2) core/engine/src/builtins/iterable/mod.rs:283— core/engine/src/builtins/iterable/mod.rs:283-300 | core/engine/src/builtins/iterable/mod.rs:351-368 — 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 (18 lines × 2) core/engine/src/builtins/map/mod.rs:753— core/engine/src/builtins/map/mod.rs:753-770 | core/engine/src/builtins/object/mod.rs:1381-1398 — 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 (18 lines × 2) core/engine/src/builtins/temporal/plain_year_month/mod.rs:633— core/engine/src/builtins/temporal/plain_year_month/mod.rs:633-650 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:668-685 — 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 (18 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1617— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1617-1634 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1646-1663 — 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 (18 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1085— core/engine/src/builtins/typed_array/builtin.rs:1085-1102 | core/engine/src/builtins/typed_array/builtin.rs:1149-1166 — 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 (18 lines × 2) core/engine/src/vm/opcode/environment/mod.rs:145— core/engine/src/vm/opcode/environment/mod.rs:145-162 | core/engine/src/vm/opcode/environment/mod.rs:211-228 — 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 (18 lines × 2) core/engine/src/vm/opcode/push/class/private.rs:95— core/engine/src/vm/opcode/push/class/private.rs:95-112 | core/engine/src/vm/opcode/push/class/private.rs:141-158 — 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 (18 lines × 2) core/parser/src/parser/statement/mod.rs:859— core/parser/src/parser/statement/mod.rs:859-876 | core/parser/src/parser/statement/mod.rs:883-900 — 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 (18 lines × 2) core/engine/src/builtins/iterable/iterator_prototype.rs:305— core/engine/src/builtins/iterable/iterator_prototype.rs:305-322 | core/engine/src/builtins/iterable/iterator_prototype.rs:380-397 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×11
Members sharing a duplicated core (4 members, 50+ identical tokens) core/ast/src/function/async_function.rs:260— core/ast/src/function/async_function.rs:260-279 | core/ast/src/function/async_generator.rs:261-276 | core/ast/src/function/generator.rs:258-273 | core/ast/src/function/ordinary_function.rs:293-308 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/ast/src/scope_analyzer.rs:392— core/ast/src/scope_analyzer.rs:392-407 | core/ast/src/scope_analyzer.rs:412-434 | core/ast/src/scope_analyzer.rs:782-799 | core/ast/src/scope_analyzer.rs:804-830 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/ast/src/scope_analyzer.rs:666— core/ast/src/scope_analyzer.rs:666-682 | core/ast/src/scope_analyzer.rs:687-703 | core/ast/src/scope_analyzer.rs:708-724 | core/ast/src/scope_analyzer.rs:729-745 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/builtins/array_buffer/utils.rs:428— core/engine/src/builtins/array_buffer/utils.rs:428-497 | core/engine/src/builtins/array_buffer/utils.rs:507-574 | core/engine/src/builtins/array_buffer/utils.rs:584-646 | core/engine/src/builtins/array_buffer/utils.rs:656-718 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/builtins/temporal/plain_date/mod.rs:75— core/engine/src/builtins/temporal/plain_date/mod.rs:75-260 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:78-324 | core/engine/src/builtins/temporal/plain_time/mod.rs:59-140 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:74-388 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/builtins/temporal/plain_date/mod.rs:75— core/engine/src/builtins/temporal/plain_date/mod.rs:75-260 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:78-324 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:64-185 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:74-388 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/builtins/typed_array/builtin.rs:871— core/engine/src/builtins/typed_array/builtin.rs:871-895 | core/engine/src/builtins/typed_array/builtin.rs:907-931 | core/engine/src/builtins/typed_array/builtin.rs:943-967 | core/engine/src/builtins/typed_array/builtin.rs:979-1003 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/bytecompiler/mod.rs:175— core/engine/src/bytecompiler/mod.rs:175-186 | core/engine/src/bytecompiler/mod.rs:190-201 | core/engine/src/bytecompiler/mod.rs:205-216 | core/engine/src/bytecompiler/mod.rs:220-231 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/module/namespace.rs:261— core/engine/src/module/namespace.rs:261-279 | core/engine/src/module/namespace.rs:296-375 | core/engine/src/module/namespace.rs:385-463 | core/engine/src/module/namespace.rs:487-506 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/value/display/arguments.rs:24— core/engine/src/value/display/arguments.rs:24-96 | core/engine/src/value/display/array.rs:11-71 | core/engine/src/value/display/array.rs:79-128 | core/engine/src/value/display/object.rs:172-229 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) core/engine/src/value/mod.rs:1141— core/engine/src/value/mod.rs:1141-1162 | core/engine/src/value/mod.rs:1170-1187 | core/engine/src/value/mod.rs:1242-1263 | core/engine/src/value/mod.rs:1271-1288 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (16 lines × 2) core/ast/src/operations/mod.rs:262— core/ast/src/operations/mod.rs:262-277 | core/ast/src/operations/mod.rs:282-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/array/mod.rs:1976— core/engine/src/builtins/array/mod.rs:1976-1991 | core/engine/src/builtins/array/mod.rs:2101-2116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/iterable/async_from_sync_iterator.rs:142— core/engine/src/builtins/iterable/async_from_sync_iterator.rs:142-157 | core/engine/src/builtins/iterable/async_from_sync_iterator.rs:224-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/iterable/iterator_prototype.rs:327— core/engine/src/builtins/iterable/iterator_prototype.rs:327-342 | core/engine/src/builtins/iterable/iterator_prototype.rs:402-417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/promise/mod.rs:716— core/engine/src/builtins/promise/mod.rs:716-731 | core/engine/src/builtins/promise/mod.rs:1617-1632 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/promise/mod.rs:881— core/engine/src/builtins/promise/mod.rs:881-896 | core/engine/src/builtins/promise/mod.rs:971-986 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:665— core/engine/src/builtins/temporal/instant/mod.rs:665-680 | core/engine/src/builtins/temporal/instant/mod.rs:692-707 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/bytecompiler/mod.rs:1871— core/engine/src/bytecompiler/mod.rs:1871-1886 | core/engine/src/bytecompiler/mod.rs:2110-2125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/engine/src/bytecompiler/mod.rs:2568— core/engine/src/bytecompiler/mod.rs:2568-2583 | core/engine/src/bytecompiler/mod.rs:2618-2633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) core/parser/src/parser/expression/left_hand_side/call.rs:180— core/parser/src/parser/expression/left_hand_side/call.rs:180-195 | core/parser/src/parser/expression/left_hand_side/member.rs:296-311 — before extracting anything, compare `core/parser/src/parser/expression/left_hand_side/call.rs` and `core/parser/src/parser/expression/left_hand_side/member.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) core/parser/src/parser/statement/declaration/export.rs:273— core/parser/src/parser/statement/declaration/export.rs:273-288 | core/parser/src/parser/statement/declaration/import.rs:238-253 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) core/ast/src/scope_analyzer.rs:1430— core/ast/src/scope_analyzer.rs:1430-1444 | core/ast/src/scope_analyzer.rs:1461-1475 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/engine/src/builtins/set/mod.rs:245— core/engine/src/builtins/set/mod.rs:245-259 | core/engine/src/builtins/weak_set/mod.rs:108-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1338— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1338-1352 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1369-1383 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:1471— core/engine/src/builtins/typed_array/builtin.rs:1471-1485 | core/engine/src/builtins/typed_array/builtin.rs:1544-1558 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/engine/src/value/display/array.rs:103— core/engine/src/value/display/array.rs:103-117 | core/engine/src/value/display/object.rs:203-217 — 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 (15 lines × 2) core/engine/src/vm/opcode/call/mod.rs:69— core/engine/src/vm/opcode/call/mod.rs:69-83 | core/engine/src/vm/opcode/call/mod.rs:144-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/engine/src/vm/opcode/push/class/field.rs:32— core/engine/src/vm/opcode/push/class/field.rs:32-46 | core/engine/src/vm/opcode/push/class/field.rs:87-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1166— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1166-1180 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1234-1248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/wintertc/src/timers/mod.rs:110— core/wintertc/src/timers/mod.rs:110-124 | core/wintertc/src/timers/mod.rs:157-171 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) core/engine/src/object/builtins/jsarraybuffer.rs:61— core/engine/src/object/builtins/jsarraybuffer.rs:61-75 | core/engine/src/object/builtins/jssharedarraybuffer.rs:36-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) core/engine/src/builtins/intl/locale/mod.rs:685— core/engine/src/builtins/intl/locale/mod.rs:685-699 | core/engine/src/builtins/intl/locale/mod.rs:716-730 — 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 (17 lines × 2) core/engine/src/builtins/array/mod.rs:2355— core/engine/src/builtins/array/mod.rs:2355-2371 | core/engine/src/builtins/array/mod.rs:2388-2405 — 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 (17 lines × 2) core/engine/src/builtins/array_buffer/mod.rs:435— core/engine/src/builtins/array_buffer/mod.rs:435-451 | core/engine/src/builtins/array_buffer/shared.rs:182-198 — before extracting anything, compare `core/engine/src/builtins/array_buffer/mod.rs` and `core/engine/src/builtins/array_buffer/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 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 (17 lines × 2) core/engine/src/builtins/date/mod.rs:861— core/engine/src/builtins/date/mod.rs:861-877 | core/engine/src/builtins/date/mod.rs:1062-1078 — 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 (17 lines × 2) core/engine/src/builtins/generator/mod.rs:317— core/engine/src/builtins/generator/mod.rs:317-333 | core/engine/src/builtins/generator/mod.rs:408-424 — 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 (17 lines × 2) core/engine/src/builtins/json/mod.rs:1098— core/engine/src/builtins/json/mod.rs:1098-1114 | core/engine/src/builtins/json/mod.rs:1225-1241 — 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 (17 lines × 2) core/engine/src/builtins/regexp/mod.rs:1439— core/engine/src/builtins/regexp/mod.rs:1439-1455 | core/engine/src/builtins/regexp/mod.rs:1672-1688 — 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 (17 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1824— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1824-1840 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2195-2211 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 2) core/engine/src/vm/opcode/set/property.rs:233— core/engine/src/vm/opcode/set/property.rs:233-249 | core/engine/src/vm/opcode/set/property.rs:277-293 — 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 (17 lines × 2) core/engine/src/vm/opcode/set/property.rs:326— core/engine/src/vm/opcode/set/property.rs:326-342 | core/engine/src/vm/opcode/set/property.rs:371-387 — 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 (17 lines × 2) core/parser/src/parser/statement/declaration/lexical.rs:471— core/parser/src/parser/statement/declaration/lexical.rs:471-487 | core/parser/src/parser/statement/variable/mod.rs:210-226 — before extracting anything, compare `core/parser/src/parser/statement/declaration/lexical.rs` and `core/parser/src/parser/statement/variable/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Change coupling: map_iterator.rs ↔ set_iterator.rs core/engine/src/builtins/map/map_iterator.rs:1— `core/engine/src/builtins/map/map_iterator.rs` and `core/engine/src/builtins/set/set_iterator.rs` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `c41b0310` Improve strictness around `Map` and `Set` objects (#4497); `47ab7e0a` Removed some unsafe_empty_trace!() calls to improve performance (#2233) (at that commit the files were still `boa_engine/src/builtins/map/map_iterator.rs` and `boa_engine/src/builtins/set/set_iterator.rs`); `518bad81` Integrate ICU4X into `Intl` module (#2083) (at that commit the files were still `boa_engine/src/builtins/map/map_iterator.rs` and `boa_engine/src/builtins/set/set_iterator.rs`) — run `git show` on any of them.
Change coupling: mod.rs ↔ name.rs core/engine/src/vm/opcode/define/mod.rs:1— `core/engine/src/vm/opcode/define/mod.rs` and `core/engine/src/vm/opcode/set/name.rs` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `8f5ef654` fix eval delete bindings (#5344); `ab0854f7` Refactor environment stack to remove some panics (#3893); `961d7b4d` Refactor call frame access to avoid panic checks (#3888) — run `git show` on any of them.
Change coupling: mod.rs ↔ yield_stm.rs core/engine/src/vm/opcode/await/mod.rs:1— `core/engine/src/vm/opcode/await/mod.rs` and `core/engine/src/vm/opcode/generator/yield_stm.rs` 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 — 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 `f90fd30c` fix(vm/opcode/push,environment,templates,generator,await,new): conver…; `d3df69cd` Separate VM registers from calling convention stack (#4867); `d69e7d34` Extract engine errors as their own `JsError` variant (#4534) — run `git show` on any of them.
Change coupling: mod.rs ↔ set_iterator.rs core/engine/src/builtins/map/mod.rs:1— `core/engine/src/builtins/map/mod.rs` and `core/engine/src/builtins/set/set_iterator.rs` 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 — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `c41b0310` Improve strictness around `Map` and `Set` objects (#4497); `518bad81` Integrate ICU4X into `Intl` module (#2083) (at that commit the files were still `boa_engine/src/builtins/map/mod.rs` and `boa_engine/src/builtins/set/set_iterator.rs`); `8ba500a2` Refactor builtin `Map` intrinsics to follow more closely the spec (#1… (at that commit the files were still `boa/src/builtins/map/mod.rs` and `boa/src/builtins/set/set_iterator.rs`) — run `git show` on any of them.
Change coupling: function.rs ↔ source.rs core/engine/src/bytecompiler/function.rs:1— `core/engine/src/bytecompiler/function.rs` and `core/engine/src/module/source.rs` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `ed40e6b8` Remove `CompletePromiseCapability` opcode (#4831); `c480a422` Implement register allocation (#3942); `4419e6df` Fix base objects in `with` statements (#3870) — run `git show` on any of them.
Change coupling: mod.rs ↔ yield_stm.rs core/engine/src/builtins/generator/mod.rs:1— `core/engine/src/builtins/generator/mod.rs` and `core/engine/src/vm/opcode/generator/yield_stm.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `d3df69cd` Separate VM registers from calling convention stack (#4867); `d69e7d34` Extract engine errors as their own `JsError` variant (#4534); `af9d3953` Refactor vm calling convention to allow locals (#3496) — run `git show` on any of them.
Change coupling: builtin.rs ↔ jsdataview.rs core/engine/src/builtins/typed_array/builtin.rs:1— `core/engine/src/builtins/typed_array/builtin.rs` and `core/engine/src/object/builtins/jsdataview.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `488ef539` Remove `Box` from `Object`'s data member (#4342); `a9aeaa5b` Implement resizable buffers (#3634); `20dba13a` Improve typing of `DataView` and related objects (#3626) — run `git show` on any of them.
Change coupling: utils.rs ↔ jsdataview.rs core/engine/src/builtins/array_buffer/utils.rs:1— `core/engine/src/builtins/array_buffer/utils.rs` and `core/engine/src/object/builtins/jsdataview.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `488ef539` Remove `Box` from `Object`'s data member (#4342); `a9aeaa5b` Implement resizable buffers (#3634); `20dba13a` Improve typing of `DataView` and related objects (#3626) — run `git show` on any of them.
Change coupling: declarations.rs ↔ environment.rs core/engine/src/bytecompiler/declarations.rs:1— `core/engine/src/bytecompiler/declarations.rs` and `core/engine/src/vm/opcode/push/environment.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `69eae8ce` Remove `environments` and `realm` fields from the Vm (#4507); `fee4048b` Merge `CodeBlock` constant pools (#3413) (at that commit the files were still `boa_engine/src/bytecompiler/declarations.rs` and `boa_engine/src/vm/opcode/push/environment.rs`); `ceaaec72` Fix super() construction with default parameters (#3339) (at that commit the files were still `boa_engine/src/bytecompiler/declarations.rs` and `boa_engine/src/vm/opcode/push/environment.rs`) — run `git show` on any of them.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/plain_year_month/mod.rs:450— core/engine/src/builtins/temporal/plain_year_month/mod.rs:450-457 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:473-480 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:496-503 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) core/parser/src/parser/expression/mod.rs:239— core/parser/src/parser/expression/mod.rs:239-246 | core/parser/src/parser/statement/declaration/lexical.rs:61-68 | core/parser/src/parser/statement/declaration/lexical.rs:357-364 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8 lines × 3) core/engine/src/builtins/typed_array/builtin.rs:209— core/engine/src/builtins/typed_array/builtin.rs:209-219 | core/engine/src/builtins/typed_array/builtin.rs:2270-2277 | core/engine/src/builtins/typed_array/builtin.rs:2322-2329 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/instant/mod.rs:743— core/engine/src/builtins/temporal/instant/mod.rs:743-752 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1532-1539 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1285-1292 — `core/engine/src/builtins/temporal/instant/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) cli/src/debug/limits.rs:70— cli/src/debug/limits.rs:70-78 | cli/src/debug/limits.rs:81-89 | cli/src/debug/limits.rs:92-99 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:982— core/engine/src/builtins/temporal/plain_date/mod.rs:982-990 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1167-1174 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1313-1320 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/plain_month_day/mod.rs:281— core/engine/src/builtins/temporal/plain_month_day/mod.rs:281-289 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:549-557 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1182-1189 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:541— core/engine/src/builtins/temporal/plain_date_time/mod.rs:541-549 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:384-391 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:559-567 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 172 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:336— core/engine/src/builtins/temporal/plain_date/mod.rs:336-343 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:492-499 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:483-490 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
boa_ast::scope_analyzer::eval_declaration_instantiation_scope (cognitive 83) core/ast/src/scope_analyzer.rs:2305— boa_ast::scope_analyzer::eval_declaration_instantiation_scope has cognitive complexity 83 (threshold 15). Drivers by points: if/else 19 (46 pts), loops 13 (30 pts), match/switch 3 (7 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.
boa_ast::scope_analyzer::function_declaration_instantiation (cognitive 72) core/ast/src/scope_analyzer.rs:1877— boa_ast::scope_analyzer::function_declaration_instantiation has cognitive complexity 72 (threshold 15). Drivers by points: if/else 23 (39 pts), loops 9 (21 pts), boolean chains 7, match/switch 2 (5 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_ast::operations::contains (cognitive 36) core/ast/src/operations/mod.rs:77— boa_ast::operations::contains has cognitive complexity 36 (threshold 15). Drivers by points: if/else 22 (26 pts), boolean chains 8, loops 1, match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
boa_ast::operations::check_labels (cognitive 28) core/ast/src/operations/mod.rs:1434— boa_ast::operations::check_labels has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20 (21 pts), match/switch 3, boolean chains 2, loops 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
boa_ast::scope_analyzer::module_instantiation (cognitive 28) core/ast/src/scope_analyzer.rs:2204— boa_ast::scope_analyzer::module_instantiation has cognitive complexity 28 (threshold 15). Drivers by points: loops 10 (23 pts), if/else 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
boa_ast::scope_analyzer::global_declaration_instantiation (cognitive 24) core/ast/src/scope_analyzer.rs:1740— boa_ast::scope_analyzer::global_declaration_instantiation has cognitive complexity 24 (threshold 15). Drivers by points: loops 6 (15 pts), if/else 3 (6 pts), match/switch 1 (3 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
boa_ast::operations::top_level_vars (cognitive 16) core/ast/src/operations/mod.rs:1125— boa_ast::operations::top_level_vars has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (9 pts), loops 2 (4 pts), if/else 1 (3 pts) (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
boa_ast::scope_analyzer::block_declaration_instantiation (cognitive 16) core/ast/src/scope_analyzer.rs:1817— boa_ast::scope_analyzer::block_declaration_instantiation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (7 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.
Duplicated block (6 lines × 2) core/engine/src/builtins/date/mod.rs:917— core/engine/src/builtins/date/mod.rs:917-922 | core/engine/src/builtins/date/mod.rs:1318-1323 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/engine/src/builtins/intl/number_format/mod.rs:1037— core/engine/src/builtins/intl/number_format/mod.rs:1037-1042 | core/string/src/str.rs:326-331 — 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) core/engine/src/builtins/temporal/calendar/mod.rs:24— core/engine/src/builtins/temporal/calendar/mod.rs:24-29 | core/engine/src/builtins/temporal/calendar/mod.rs:53-58 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/engine/src/object/builtins/jsregexp.rs:172— core/engine/src/object/builtins/jsregexp.rs:172-177 | core/engine/src/object/builtins/jsregexp.rs:197-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.
Duplicated block (6 lines × 2) core/engine/src/value/display/value.rs:107— core/engine/src/value/display/value.rs:107-112 | core/engine/src/value/display/value.rs:229-237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/gc/src/lib.rs:133— core/gc/src/lib.rs:133-138 | core/gc/src/lib.rs:152-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) core/ast/src/declaration/variable.rs:379— core/ast/src/declaration/variable.rs:379-384 | core/ast/src/expression/operator/update/mod.rs:137-142 — 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) core/engine/src/object/builtins/jsdataview.rs:177— core/engine/src/object/builtins/jsdataview.rs:177-182 | core/engine/src/object/builtins/jsdataview.rs:188-193 — 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.
Low cohesion: VarScopedDeclarationsVisitor (LCOM4 11) core/ast/src/operations/mod.rs:2065— VarScopedDeclarationsVisitor'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: ModuleItemList (LCOM4 6) core/ast/src/module_item_list/mod.rs:33— ModuleItemList's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Context (LCOM4 6) core/engine/src/context/mod.rs:96— Context's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: VarDeclaredNamesVisitor (LCOM4 5) core/ast/src/operations/mod.rs:837— VarDeclaredNamesVisitor'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: AnnexBFunctionDeclarationNamesVisitor (LCOM4 5) core/ast/src/operations/mod.rs:2324— AnnexBFunctionDeclarationNamesVisitor'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: JsValue (LCOM4 5) core/engine/src/value/mod.rs:118— JsValue'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: JumpControlInfo (LCOM4 4) core/engine/src/bytecompiler/jump_control.rs:251— JumpControlInfo'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: CallFrame (LCOM4 4) core/engine/src/vm/call_frame/mod.rs:52— CallFrame'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.
Array::flatten_into_array (cognitive 23) core/engine/src/builtins/array/mod.rs:1855— Array::flatten_into_array has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Array::splice_internal (cognitive 20) core/engine/src/builtins/array/mod.rs:2294— Array::splice_internal has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (8 pts), match/switch 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.
Array::from (cognitive 17) core/engine/src/builtins/array/mod.rs:533— Array::from has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (4 pts), loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Array::concat (cognitive 17) core/engine/src/builtins/array/mod.rs:780— Array::concat has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 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.
Array::from_async (cognitive 16) core/engine/src/builtins/array/from_async.rs:28— Array::from_async has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Array::reduce (cognitive 16) core/engine/src/builtins/array/mod.rs:2821— Array::reduce has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Array::reduce_right) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Array::reduce_right (cognitive 16) core/engine/src/builtins/array/mod.rs:2918— Array::reduce_right has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Array::reduce) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SourceTextModule::inner_evaluate (cognitive 61) core/engine/src/module/source.rs:1177— SourceTextModule::inner_evaluate has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (45 pts), match/switch 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceTextModule::initialize_environment (cognitive 29) core/engine/src/module/source.rs:1591— SourceTextModule::initialize_environment has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 5 (10 pts), loops 7 (8 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.
SourceTextModule::inner_link (cognitive 24) core/engine/src/module/source.rs:882— SourceTextModule::inner_link has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (5 pts), 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.
SourceTextModule::resolve_export (cognitive 23) core/engine/src/module/source.rs:694— SourceTextModule::resolve_export has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 3 (8 pts), loops 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceTextModule::inner_load (cognitive 16) core/engine/src/module/source.rs:493— SourceTextModule::inner_load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 6). Of this number, 11 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SourceTextModule::gather_available_ancestors (cognitive 16) core/engine/src/module/source.rs:1528— SourceTextModule::gather_available_ancestors has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 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.
Change-coupling hub: mod.rs → mod.rs, mod.rs, mod.rs core/engine/src/builtins/temporal/plain_month_day/mod.rs— `core/engine/src/builtins/temporal/plain_month_day/mod.rs` changes together with 3 other files — `core/engine/src/builtins/temporal/duration/mod.rs`, `core/engine/src/builtins/temporal/plain_date_time/mod.rs`, `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: mod.rs → now.rs, mod.rs, mod.rs core/engine/src/builtins/temporal/plain_year_month/mod.rs— `core/engine/src/builtins/temporal/plain_year_month/mod.rs` changes together with 3 other files — `core/engine/src/builtins/temporal/now.rs`, `core/engine/src/builtins/temporal/plain_date_time/mod.rs`, `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: code_block.rs → mod.rs, declaration_pattern.rs, mod.rs, update.rs, sym.rs core/engine/src/vm/code_block.rs— `core/engine/src/vm/code_block.rs` changes together with 5 other files — `core/ast/src/expression/mod.rs`, `core/engine/src/bytecompiler/declaration/declaration_pattern.rs`, `core/engine/src/bytecompiler/expression/mod.rs`, `core/engine/src/bytecompiler/expression/update.rs`, `core/interner/src/sym.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: mod.rs → declaration_pattern.rs, declarations.rs, update.rs core/engine/src/vm/flowgraph/mod.rs— `core/engine/src/vm/flowgraph/mod.rs` changes together with 3 other files — `core/engine/src/bytecompiler/declaration/declaration_pattern.rs`, `core/engine/src/bytecompiler/declarations.rs`, `core/engine/src/bytecompiler/expression/update.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: mod.rs → mod.rs, mod.rs, mod.rs, mod.rs, mod.rs core/engine/src/builtins/temporal/instant/mod.rs— `core/engine/src/builtins/temporal/instant/mod.rs` changes together with 5 other files — `core/engine/src/builtins/temporal/plain_date/mod.rs`, `core/engine/src/builtins/temporal/plain_date_time/mod.rs`, `core/engine/src/builtins/temporal/plain_month_day/mod.rs`, `core/engine/src/builtins/temporal/plain_time/mod.rs`, `core/engine/src/builtins/temporal/plain_year_month/mod.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: mod.rs → mod.rs, mod.rs, update.rs core/engine/src/vm/opcode/mod.rs— `core/engine/src/vm/opcode/mod.rs` changes together with 3 other files — `core/ast/src/expression/mod.rs`, `core/engine/src/bytecompiler/expression/mod.rs`, `core/engine/src/bytecompiler/expression/update.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Duplicated block (12–13 lines × 2) core/engine/src/builtins/array/mod.rs:1361— core/engine/src/builtins/array/mod.rs:1361-1373 | core/engine/src/builtins/array/mod.rs:1414-1425 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:458— core/engine/src/builtins/temporal/plain_month_day/mod.rs:458-470 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2238-2249 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 63 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12–13 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1464— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1464-1476 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1725-1736 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) core/engine/src/bytecompiler/declarations.rs:85— core/engine/src/bytecompiler/declarations.rs:85-97 | core/engine/src/bytecompiler/declarations.rs:250-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) core/engine/src/module/namespace.rs:301— core/engine/src/module/namespace.rs:301-313 | core/engine/src/module/namespace.rs:390-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) core/macros/src/lib.rs:467— core/macros/src/lib.rs:467-478 | core/macros/src/lib.rs:603-615 — 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 (5 lines × 4) core/ast/src/scope_analyzer.rs:2398— core/ast/src/scope_analyzer.rs:2398-2402 | core/ast/src/scope_analyzer.rs:2509-2513 | core/engine/src/bytecompiler/declarations.rs:248-252 | core/engine/src/bytecompiler/declarations.rs:656-660 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) core/engine/src/value/display/arguments.rs:73— core/engine/src/value/display/arguments.rs:73-79 | core/engine/src/value/display/array.rs:46-50 | core/engine/src/value/display/array.rs:111-117 | core/engine/src/value/display/object.rs:211-217 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) core/ast/src/function/async_function.rs:117— core/ast/src/function/async_function.rs:117-121 | core/ast/src/function/async_generator.rs:118-122 | core/ast/src/function/generator.rs:115-119 | core/ast/src/function/ordinary_function.rs:118-122 — before extracting anything, compare `core/ast/src/function/async_function.rs` and `core/ast/src/function/async_generator.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) core/ast/src/function/async_function.rs:126— core/ast/src/function/async_function.rs:126-130 | core/ast/src/function/async_generator.rs:127-131 | core/ast/src/function/generator.rs:124-128 | core/ast/src/function/ordinary_function.rs:127-131 — before extracting anything, compare `core/ast/src/function/async_function.rs` and `core/ast/src/function/async_generator.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:775— core/engine/src/builtins/temporal/plain_date/mod.rs:775-780 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1053-1065 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:288-292 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1156-1161 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 4) core/ast/src/function/async_function.rs:262— core/ast/src/function/async_function.rs:262-266 | core/ast/src/function/async_generator.rs:263-270 | core/ast/src/function/generator.rs:260-267 | core/ast/src/function/ordinary_function.rs:295-302 — before extracting anything, compare `core/ast/src/function/async_function.rs` and `core/ast/src/function/async_generator.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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.
boa_ast::scope_analyzer::function_declaration_instantiation (cyclomatic 43) core/ast/src/scope_analyzer.rs:1877— boa_ast::scope_analyzer::function_declaration_instantiation has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
boa_ast::scope_analyzer::eval_declaration_instantiation_scope (cyclomatic 42) core/ast/src/scope_analyzer.rs:2305— boa_ast::scope_analyzer::eval_declaration_instantiation_scope has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
boa_ast::operations::check_labels (cyclomatic 38) core/ast/src/operations/mod.rs:1434— boa_ast::operations::check_labels has cyclomatic complexity 38 (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.
boa_ast::operations::contains (cyclomatic 32) core/ast/src/operations/mod.rs:77— boa_ast::operations::contains has cyclomatic complexity 32 (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.
boa_ast::scope_analyzer::module_instantiation (cyclomatic 21) core/ast/src/scope_analyzer.rs:2204— boa_ast::scope_analyzer::module_instantiation has cyclomatic complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
RegExp::split (cognitive 29) core/engine/src/builtins/regexp/mod.rs:1886— RegExp::split has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 2 (5 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.
RegExp::abstract_builtin_exec (cognitive 28) core/engine/src/builtins/regexp/mod.rs:1100— RegExp::abstract_builtin_exec has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 6, loops 2 (3 pts), match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegExp::replace (cognitive 28) core/engine/src/builtins/regexp/mod.rs:1582— RegExp::replace has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 3 (4 pts), match/switch 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegExp::escape (cognitive 24) core/engine/src/builtins/regexp/mod.rs:860— RegExp::escape has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RegExp::constructor (cognitive 16) core/engine/src/builtins/regexp/mod.rs:202— RegExp::constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (5 members, 50+ identical tokens) core/engine/src/builtins/array/array_iterator.rs:40— core/engine/src/builtins/array/array_iterator.rs:40-50 | core/engine/src/builtins/map/map_iterator.rs:55-65 | core/engine/src/builtins/regexp/regexp_string_iterator.rs:43-53 | core/engine/src/builtins/set/set_iterator.rs:55-65 | core/engine/src/builtins/string/string_iterator.rs:34-44 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) core/engine/src/builtins/proxy/mod.rs:472— core/engine/src/builtins/proxy/mod.rs:472-588 | core/engine/src/builtins/proxy/mod.rs:601-704 | core/engine/src/builtins/proxy/mod.rs:716-770 | core/engine/src/builtins/proxy/mod.rs:807-871 | core/engine/src/builtins/proxy/mod.rs:885-958 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) core/engine/src/builtins/temporal/plain_date/mod.rs:279— core/engine/src/builtins/temporal/plain_date/mod.rs:279-314 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:343-472 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:124-167 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:204-254 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:407-463 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) core/engine/src/builtins/typed_array/builtin.rs:655— core/engine/src/builtins/typed_array/builtin.rs:655-700 | core/engine/src/builtins/typed_array/builtin.rs:1015-1052 | core/engine/src/builtins/typed_array/builtin.rs:1422-1485 | core/engine/src/builtins/typed_array/builtin.rs:1497-1558 | core/engine/src/builtins/typed_array/builtin.rs:2211-2255 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) core/engine/src/builtins/typed_array/object.rs:365— core/engine/src/builtins/typed_array/object.rs:365-393 | core/engine/src/builtins/typed_array/object.rs:405-423 | core/engine/src/builtins/typed_array/object.rs:436-485 | core/engine/src/builtins/typed_array/object.rs:502-521 | core/engine/src/builtins/typed_array/object.rs:534-553 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (12 lines × 4) core/engine/src/builtins/typed_array/builtin_uint8.rs:133— core/engine/src/builtins/typed_array/builtin_uint8.rs:133-144 | core/engine/src/builtins/typed_array/builtin_uint8.rs:256-267 | core/engine/src/builtins/typed_array/builtin_uint8.rs:392-403 | core/engine/src/builtins/typed_array/builtin_uint8.rs:520-531 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) core/engine/src/value/mod.rs:1143— core/engine/src/value/mod.rs:1143-1154 | core/engine/src/value/mod.rs:1172-1183 | core/engine/src/value/mod.rs:1244-1255 | core/engine/src/value/mod.rs:1273-1284 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) core/engine/src/vm/opcode/define/class/setter.rs:34— core/engine/src/vm/opcode/define/class/setter.rs:34-45 | core/engine/src/vm/opcode/define/class/setter.rs:92-103 | core/engine/src/vm/opcode/define/class/setter.rs:147-158 | core/engine/src/vm/opcode/define/class/setter.rs:202-213 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) core/ast/src/function/async_function.rs:46— core/ast/src/function/async_function.rs:46-57 | core/ast/src/function/async_generator.rs:47-58 | core/ast/src/function/generator.rs:44-55 | core/ast/src/function/ordinary_function.rs:47-58 — before extracting anything, compare `core/ast/src/function/async_function.rs` and `core/ast/src/function/async_generator.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 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 (12 lines × 4) core/engine/src/builtins/promise/mod.rs:564— core/engine/src/builtins/promise/mod.rs:564-578 | core/engine/src/builtins/promise/mod.rs:779-793 | core/engine/src/builtins/promise/mod.rs:1456-1470 | core/engine/src/builtins/promise/mod.rs:1688-1699 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) core/ast/src/scope_analyzer.rs:395— core/ast/src/scope_analyzer.rs:395-403 | core/ast/src/scope_analyzer.rs:420-428 | core/ast/src/scope_analyzer.rs:787-795 | core/ast/src/scope_analyzer.rs:817-825 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:1423— core/engine/src/builtins/temporal/plain_date/mod.rs:1423-1431 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1755-1763 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1023-1031 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2126-2134 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 4) core/engine/src/bytecompiler/mod.rs:178— core/engine/src/bytecompiler/mod.rs:178-186 | core/engine/src/bytecompiler/mod.rs:193-201 | core/engine/src/bytecompiler/mod.rs:208-216 | core/engine/src/bytecompiler/mod.rs:223-231 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) core/parser/src/parser/expression/update.rs:102— core/parser/src/parser/expression/update.rs:102-110 | core/parser/src/parser/expression/update.rs:130-138 | core/parser/src/parser/expression/update.rs:171-179 | core/parser/src/parser/expression/update.rs:194-202 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) core/parser/src/parser/statement/iteration/do_while_statement.rs:66— core/parser/src/parser/statement/iteration/do_while_statement.rs:66-74 | core/parser/src/parser/statement/iteration/for_statement.rs:211-219 | core/parser/src/parser/statement/iteration/for_statement.rs:298-306 | core/parser/src/parser/statement/iteration/while_statement.rs:63-71 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 6) core/engine/src/builtins/temporal/plain_date/mod.rs:1474— core/engine/src/builtins/temporal/plain_date/mod.rs:1474-1480 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1848-1854 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:464-470 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:578-584 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1076-1082 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2240-2246 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 6) core/engine/src/vm/opcode/define/class/getter.rs:140— core/engine/src/vm/opcode/define/class/getter.rs:140-146 | core/engine/src/vm/opcode/define/class/getter.rs:194-200 | core/engine/src/vm/opcode/define/class/method.rs:120-126 | core/engine/src/vm/opcode/define/class/method.rs:169-175 | core/engine/src/vm/opcode/define/class/setter.rs:143-149 | core/engine/src/vm/opcode/define/class/setter.rs:198-204 — before extracting anything, compare `core/engine/src/vm/opcode/define/class/getter.rs` and `core/engine/src/vm/opcode/define/class/setter.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 6) core/ast/src/function/arrow_function.rs:144— core/ast/src/function/arrow_function.rs:144-150 | core/ast/src/function/async_arrow_function.rs:145-151 | core/ast/src/function/async_function.rs:293-299 | core/ast/src/function/async_generator.rs:290-296 | core/ast/src/function/generator.rs:287-293 | core/ast/src/function/ordinary_function.rs:322-328 — before extracting anything, compare `core/ast/src/function/arrow_function.rs` and `core/ast/src/function/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 6) core/ast/src/function/arrow_function.rs:155— core/ast/src/function/arrow_function.rs:155-161 | core/ast/src/function/async_arrow_function.rs:156-162 | core/ast/src/function/async_function.rs:304-310 | core/ast/src/function/async_generator.rs:301-307 | core/ast/src/function/generator.rs:298-304 | core/ast/src/function/ordinary_function.rs:333-339 — before extracting anything, compare `core/ast/src/function/arrow_function.rs` and `core/ast/src/function/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 6) core/engine/src/builtins/set/mod.rs:598— core/engine/src/builtins/set/mod.rs:598-604 | core/engine/src/builtins/set/mod.rs:682-688 | core/engine/src/builtins/set/mod.rs:748-754 | core/engine/src/builtins/set/mod.rs:802-808 | core/engine/src/builtins/set/mod.rs:870-876 | core/engine/src/builtins/set/mod.rs:927-933 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) core/engine/src/builtins/intl/date_time_format/mod.rs:989— core/engine/src/builtins/intl/date_time_format/mod.rs:989-998 | core/engine/src/builtins/intl/list_format/mod.rs:332-338 | core/engine/src/builtins/intl/number_format/mod.rs:711-719 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/list_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 3) core/engine/src/builtins/string/mod.rs:1498— core/engine/src/builtins/string/mod.rs:1498-1505 | core/engine/src/builtins/string/mod.rs:2120-2126 | core/engine/src/builtins/string/mod.rs:2244-2251 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) core/engine/src/builtins/map/mod.rs:331— core/engine/src/builtins/map/mod.rs:331-337 | core/engine/src/builtins/map/mod.rs:363-369 | core/engine/src/builtins/map/mod.rs:423-431 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) core/engine/src/builtins/array_buffer/mod.rs:331— core/engine/src/builtins/array_buffer/mod.rs:331-337 | core/engine/src/builtins/array_buffer/shared.rs:100-106 | core/engine/src/builtins/dataview/mod.rs:98-104 — before extracting anything, compare `core/engine/src/builtins/array_buffer/mod.rs` and `core/engine/src/builtins/array_buffer/shared.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) core/engine/src/builtins/intl/date_time_format/options.rs:357— core/engine/src/builtins/intl/date_time_format/options.rs:357-363 | core/engine/src/builtins/intl/date_time_format/options.rs:395-401 | core/engine/src/builtins/intl/date_time_format/options.rs:489-495 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) cli/src/debug/limits.rs:24— cli/src/debug/limits.rs:24-29 | cli/src/debug/limits.rs:40-45 | cli/src/debug/limits.rs:56-61 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) core/engine/src/builtins/temporal/duration/mod.rs:1073— core/engine/src/builtins/temporal/duration/mod.rs:1073-1078 | core/engine/src/builtins/temporal/instant/mod.rs:625-631 | core/engine/src/builtins/temporal/plain_time/mod.rs:752-758 — `core/engine/src/builtins/temporal/duration/mod.rs` and `core/engine/src/builtins/temporal/instant/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 3) utils/small_btree/src/entry.rs:209— utils/small_btree/src/entry.rs:209-214 | utils/small_btree/src/lib.rs:158-163 | utils/small_btree/src/lib.rs:501-506 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:590— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:590-596 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:885-890 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:987-993 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) core/engine/src/object/builtins/jsregexp.rs:172— core/engine/src/object/builtins/jsregexp.rs:172-177 | core/engine/src/object/builtins/jsregexp.rs:197-202 | core/engine/src/object/builtins/jsregexp.rs:267-272 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Json::internalize_json_property (cognitive 39) core/engine/src/builtins/json/mod.rs:369— Json::internalize_json_property has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (25 pts), match/switch 3 (8 pts), loops 2 (6 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Json::stringify (cognitive 32) core/engine/src/builtins/json/mod.rs:625— Json::stringify has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 2 (7 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Json::serialize_json_property (cognitive 24) core/engine/src/builtins/json/mod.rs:771— Json::serialize_json_property has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (22 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, 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.
Json::serialize_json_object (cognitive 20) core/engine/src/builtins/json/mod.rs:963— Json::serialize_json_object has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (6 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.
Duplicated block (23 lines × 2) core/ast/src/function/class.rs:94— core/ast/src/function/class.rs:94-116 | core/ast/src/function/class.rs:262-284 — 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 (23 lines × 2) core/ast/src/scope_analyzer.rs:1943— core/ast/src/scope_analyzer.rs:1943-1965 | core/engine/src/bytecompiler/declarations.rs:944-966 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) core/engine/src/builtins/array/mod.rs:1471— core/engine/src/builtins/array/mod.rs:1471-1493 | core/engine/src/builtins/array/mod.rs:2045-2067 — 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 (23 lines × 2) core/engine/src/object/property_map.rs:211— core/engine/src/object/property_map.rs:211-233 | core/engine/src/object/property_map.rs:248-270 — 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 (20 lines × 2) core/ast/src/scope_analyzer.rs:2102— core/ast/src/scope_analyzer.rs:2102-2121 | core/engine/src/bytecompiler/declarations.rs:1148-1167 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) core/engine/src/builtins/json/mod.rs:399— core/engine/src/builtins/json/mod.rs:399-418 | core/engine/src/builtins/json/mod.rs:443-462 — 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 (20 lines × 2) core/engine/src/builtins/typed_array/builtin_uint8.rs:576— core/engine/src/builtins/typed_array/builtin_uint8.rs:576-595 | core/engine/src/builtins/typed_array/builtin_uint8.rs:630-649 — 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 (20 lines × 2) core/engine/src/bytecompiler/mod.rs:2463— core/engine/src/bytecompiler/mod.rs:2463-2482 | core/engine/src/bytecompiler/mod.rs:2593-2612 — 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 (17–18 lines × 2) core/engine/src/builtins/atomics/futex.rs:392— core/engine/src/builtins/atomics/futex.rs:392-409 | core/engine/src/builtins/atomics/futex.rs:503-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–18 lines × 2) core/engine/src/builtins/iterable/iterator_helper/mod.rs:183— core/engine/src/builtins/iterable/iterator_helper/mod.rs:183-199 | core/engine/src/builtins/iterable/iterator_helper/mod.rs:299-316 — 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 (17–18 lines × 2) core/engine/src/builtins/set/mod.rs:633— core/engine/src/builtins/set/mod.rs:633-649 | core/engine/src/builtins/set/mod.rs:969-986 — 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 (17–18 lines × 2) core/engine/src/vm/opcode/set/property.rs:224— core/engine/src/vm/opcode/set/property.rs:224-240 | core/engine/src/vm/opcode/set/property.rs:316-333 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 3) core/ast/src/function/async_function.rs:180— core/ast/src/function/async_function.rs:180-193 | core/ast/src/function/async_generator.rs:181-194 | core/ast/src/function/generator.rs:178-191 — before extracting anything, compare `core/ast/src/function/async_function.rs` and `core/ast/src/function/async_generator.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) core/ast/src/function/async_generator.rs:263— core/ast/src/function/async_generator.rs:263-276 | core/ast/src/function/generator.rs:260-273 | core/ast/src/function/ordinary_function.rs:295-308 — before extracting anything, compare `core/ast/src/function/async_generator.rs` and `core/ast/src/function/generator.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) core/engine/src/builtins/date/mod.rs:956— core/engine/src/builtins/date/mod.rs:956-969 | core/engine/src/builtins/date/mod.rs:1030-1043 | core/engine/src/builtins/date/mod.rs:1156-1169 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 3) core/engine/src/builtins/intl/list_format/mod.rs:124— core/engine/src/builtins/intl/list_format/mod.rs:124-138 | core/engine/src/builtins/intl/plural_rules/mod.rs:118-131 | core/engine/src/builtins/intl/segmenter/mod.rs:162-179 — `core/engine/src/builtins/intl/list_format/mod.rs` and `core/engine/src/builtins/intl/segmenter/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 57 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 3) core/ast/src/scope_analyzer.rs:950— core/ast/src/scope_analyzer.rs:950-961 | core/ast/src/scope_analyzer.rs:1033-1044 | core/ast/src/scope_analyzer.rs:1100-1111 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) core/engine/src/bytecompiler/mod.rs:1874— core/engine/src/bytecompiler/mod.rs:1874-1885 | core/engine/src/bytecompiler/mod.rs:1902-1913 | core/engine/src/bytecompiler/mod.rs:2113-2124 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) core/engine/src/builtins/builder.rs:663— core/engine/src/builtins/builder.rs:663-674 | core/engine/src/object/mod.rs:718-729 | core/engine/src/object/mod.rs:736-747 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 3) core/engine/src/vm/opcode/environment/mod.rs:145— core/engine/src/vm/opcode/environment/mod.rs:145-157 | core/engine/src/vm/opcode/environment/mod.rs:211-223 | core/engine/src/vm/opcode/environment/mod.rs:251-262 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 3) core/ast/src/scope_analyzer.rs:1924— core/ast/src/scope_analyzer.rs:1924-1932 | core/engine/src/bytecompiler/declarations.rs:78-87 | core/engine/src/bytecompiler/declarations.rs:404-413 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1010— core/engine/src/builtins/temporal/plain_date/mod.rs:1010-1018 | core/engine/src/builtins/temporal/plain_date/mod.rs:1041-1050 | core/engine/src/builtins/temporal/plain_date/mod.rs:1070-1078 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1261— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1261-1269 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1289-1297 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1386-1395 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 3) core/engine/src/builtins/temporal/plain_time/mod.rs:575— core/engine/src/builtins/temporal/plain_time/mod.rs:575-583 | core/engine/src/builtins/temporal/plain_time/mod.rs:605-613 | core/engine/src/builtins/temporal/plain_time/mod.rs:714-723 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1420— core/engine/src/builtins/temporal/plain_date/mod.rs:1420-1429 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1752-1761 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2123-2132 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 3) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:875— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:875-884 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:977-986 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1074-1083 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) core/engine/src/builtins/iterable/iterator_prototype.rs:228— core/engine/src/builtins/iterable/iterator_prototype.rs:228-237 | core/engine/src/builtins/iterable/iterator_prototype.rs:266-279 | core/engine/src/builtins/iterable/iterator_prototype.rs:455-468 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1101— core/engine/src/builtins/temporal/plain_date/mod.rs:1101-1111 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1138-1147 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1253-1262 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–10 lines × 2) core/engine/src/builtins/temporal/duration/mod.rs:827— core/engine/src/builtins/temporal/duration/mod.rs:827-836 | core/engine/src/builtins/temporal/duration/mod.rs:859-867 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) core/parser/src/parser/expression/primary/mod.rs:337— core/parser/src/parser/expression/primary/mod.rs:337-345 | core/parser/src/parser/expression/primary/mod.rs:389-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:942— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:942-951 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1045-1053 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) core/parser/src/parser/statement/declaration/mod.rs:158— core/parser/src/parser/statement/declaration/mod.rs:158-167 | core/parser/src/parser/statement/declaration/mod.rs:244-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Off the main sequence: boa_icu_provider — boa_icu_provider: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: small_btree — small_btree: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: tag_ptr — tag_ptr: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: boa_string — boa_string: abstractness 0.24, instability 0.00, distance 0.76 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
RegExp::abstract_builtin_exec (cyclomatic 22) core/engine/src/builtins/regexp/mod.rs:1100— RegExp::abstract_builtin_exec 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.
RegExp::regexp_has_flag (cyclomatic 20) core/engine/src/builtins/regexp/mod.rs:470— RegExp::regexp_has_flag has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RegExp::escape (cyclomatic 16) core/engine/src/builtins/regexp/mod.rs:860— RegExp::escape 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.
Json::serialize_json_property (cyclomatic 20) core/engine/src/builtins/json/mod.rs:771— Json::serialize_json_property 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.
Json::stringify (cyclomatic 19) core/engine/src/builtins/json/mod.rs:625— Json::stringify has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Json::internalize_json_property (cyclomatic 17) core/engine/src/builtins/json/mod.rs:369— Json::internalize_json_property 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.
Hotspot: core/engine/src/vm/code_block.rs core/engine/src/vm/code_block.rs:378— core/engine/src/vm/code_block.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in CodeBlock::instruction_operands at line 378. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:33:05 +00:00' --until='2026-10-25 15:33:05 +00:00' --full-history --no-merges -- core/engine/src/vm/code_block.rs`: 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: core/engine/src/bytecompiler/expression/mod.rs core/engine/src/bytecompiler/expression/mod.rs:90— core/engine/src/bytecompiler/expression/mod.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in ByteCompiler::compile_expr_impl at line 90. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:33:05 +00:00' --until='2026-10-25 15:33:05 +00:00' --full-history --no-merges -- core/engine/src/bytecompiler/expression/mod.rs`: 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: core/engine/src/vm/flowgraph/mod.rs core/engine/src/vm/flowgraph/mod.rs:24— core/engine/src/vm/flowgraph/mod.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in CodeBlock::to_graph at line 24. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 15:33:05 +00:00' --until='2026-10-25 15:33:05 +00:00' --full-history --no-merges -- core/engine/src/vm/flowgraph/mod.rs`: 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.
Number::to_js_string_radix (cognitive 41) core/engine/src/builtins/number/mod.rs:565— Number::to_js_string_radix has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 23). 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.
Number::round_to_precision (cognitive 26) core/engine/src/builtins/number/mod.rs:379— Number::round_to_precision has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (6 pts), match/switch 1 (4 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Number::to_precision (cognitive 23) core/engine/src/builtins/number/mod.rs:440— Number::to_precision has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsValue::to_json_inner (cognitive 31) core/engine/src/value/conversions/serde_json.rs:121— JsValue::to_json_inner has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (9 pts), match/switch 3 (9 pts) (nesting depth added 20). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsValue::abstract_relation (cognitive 21) core/engine/src/value/operations.rs:532— JsValue::abstract_relation has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsValue::pow (cognitive 16) core/engine/src/value/operations.rs:206— JsValue::pow has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (7 members, 50+ identical tokens) core/engine/src/builtins/error/aggregate.rs:30— core/engine/src/builtins/error/aggregate.rs:30-38 | core/engine/src/builtins/error/eval.rs:32-40 | core/engine/src/builtins/error/range.rs:30-38 | core/engine/src/builtins/error/reference.rs:29-37 | core/engine/src/builtins/error/syntax.rs:32-40 | core/engine/src/builtins/error/type.rs:38-46 | core/engine/src/builtins/error/uri.rs:31-39 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) core/engine/src/builtins/intl/locale/mod.rs:470— core/engine/src/builtins/intl/locale/mod.rs:470-491 | core/engine/src/builtins/intl/locale/mod.rs:500-521 | core/engine/src/builtins/intl/locale/mod.rs:530-551 | core/engine/src/builtins/intl/locale/mod.rs:560-581 | core/engine/src/builtins/intl/locale/mod.rs:625-646 | core/engine/src/builtins/intl/locale/mod.rs:681-703 | core/engine/src/builtins/intl/locale/mod.rs:712-734 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) core/parser/src/parser/expression/assignment/arrow_function.rs:69— core/parser/src/parser/expression/assignment/arrow_function.rs:69-165 | core/parser/src/parser/expression/assignment/async_arrow_function.rs:68-158 | core/parser/src/parser/expression/assignment/mod.rs:90-291 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:175-534 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:741-791 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:826-890 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:925-965 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) core/ast/src/scope_analyzer.rs:1884— core/ast/src/scope_analyzer.rs:1884-2199 | core/ast/src/scope_analyzer.rs:2312-2581 | core/engine/src/bytecompiler/declarations.rs:62-183 | core/engine/src/bytecompiler/declarations.rs:201-365 | core/engine/src/bytecompiler/declarations.rs:374-557 | core/engine/src/bytecompiler/declarations.rs:625-868 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) core/engine/src/builtins/date/mod.rs:855— core/engine/src/builtins/date/mod.rs:855-898 | core/engine/src/builtins/date/mod.rs:985-1043 | core/engine/src/builtins/date/mod.rs:1056-1104 | core/engine/src/builtins/date/mod.rs:1117-1169 | core/engine/src/builtins/date/mod.rs:1183-1232 | core/engine/src/builtins/date/mod.rs:1245-1294 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) core/engine/src/builtins/temporal/plain_date/mod.rs:1412— core/engine/src/builtins/temporal/plain_date/mod.rs:1412-1489 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1737-1877 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:441-479 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:526-629 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1021-1090 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2108-2272 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (27–28 lines × 2) core/engine/src/builtins/intl/list_format/mod.rs:110— core/engine/src/builtins/intl/list_format/mod.rs:110-137 | core/engine/src/builtins/intl/segmenter/mod.rs:149-175 — `core/engine/src/builtins/intl/list_format/mod.rs` and `core/engine/src/builtins/intl/segmenter/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 57 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (27–28 lines × 2) core/engine/src/builtins/iterable/iterator_helper/mod.rs:128— core/engine/src/builtins/iterable/iterator_helper/mod.rs:128-155 | core/engine/src/builtins/iterable/iterator_helper/mod.rs:230-256 — 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 (27–28 lines × 2) core/parser/src/parser/statement/mod.rs:598— core/parser/src/parser/statement/mod.rs:598-624 | core/parser/src/parser/statement/mod.rs:629-656 — 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 (26 lines × 2) core/engine/src/builtins/array/from_async.rs:472— core/engine/src/builtins/array/from_async.rs:472-497 | core/engine/src/builtins/array/from_async.rs:649-674 — 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 (26 lines × 2) core/engine/src/bytecompiler/mod.rs:2325— core/engine/src/bytecompiler/mod.rs:2325-2350 | core/engine/src/bytecompiler/mod.rs:2366-2391 — 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 (26 lines × 2) core/parser/src/parser/expression/left_hand_side/call.rs:134— core/parser/src/parser/expression/left_hand_side/call.rs:134-159 | core/parser/src/parser/expression/left_hand_side/member.rs:248-273 — before extracting anything, compare `core/parser/src/parser/expression/left_hand_side/call.rs` and `core/parser/src/parser/expression/left_hand_side/member.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 56 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 (23 lines × 3) core/engine/src/builtins/async_generator/mod.rs:122— core/engine/src/builtins/async_generator/mod.rs:122-144 | core/engine/src/builtins/async_generator/mod.rs:207-229 | core/engine/src/builtins/async_generator/mod.rs:287-309 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23 lines × 3) core/engine/src/builtins/temporal/plain_date_time/mod.rs:107— core/engine/src/builtins/temporal/plain_date_time/mod.rs:107-129 | core/engine/src/builtins/temporal/plain_time/mod.rs:60-82 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:107-129 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 3) core/engine/src/builtins/typed_array/builtin_uint8.rs:122— core/engine/src/builtins/typed_array/builtin_uint8.rs:122-144 | core/engine/src/builtins/typed_array/builtin_uint8.rs:381-403 | core/engine/src/builtins/typed_array/builtin_uint8.rs:509-531 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (21 lines × 2) core/engine/src/bytecompiler/declarations.rs:100— core/engine/src/bytecompiler/declarations.rs:100-120 | core/engine/src/bytecompiler/declarations.rs:705-731 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) core/engine/src/bytecompiler/declarations.rs:411— core/engine/src/bytecompiler/declarations.rs:411-431 | core/engine/src/bytecompiler/declarations.rs:658-678 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) core/parser/src/parser/statement/declaration/lexical.rs:398— core/parser/src/parser/statement/declaration/lexical.rs:398-418 | core/parser/src/parser/statement/declaration/lexical.rs:439-459 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 4) core/engine/src/builtins/promise/mod.rs:588— core/engine/src/builtins/promise/mod.rs:588-604 | core/engine/src/builtins/promise/mod.rs:803-819 | core/engine/src/builtins/promise/mod.rs:1480-1496 | core/engine/src/builtins/promise/mod.rs:1710-1726 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:122— core/engine/src/builtins/temporal/plain_date/mod.rs:122-138 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:149-165 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:87-103 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:161-177 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 4) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:146— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:146-162 | core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:178-194 | core/parser/src/parser/expression/primary/function_expression/mod.rs:141-157 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:157-173 — `core/parser/src/parser/expression/primary/async_function_expression/mod.rs` and `core/parser/src/parser/expression/primary/async_generator_expression/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (17 lines × 3) core/engine/src/vm/opcode/define/class/getter.rs:43— core/engine/src/vm/opcode/define/class/getter.rs:43-59 | core/engine/src/vm/opcode/define/class/getter.rs:100-116 | core/engine/src/vm/opcode/define/class/getter.rs:207-223 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 3) core/engine/src/vm/opcode/define/class/method.rs:32— core/engine/src/vm/opcode/define/class/method.rs:32-48 | core/engine/src/vm/opcode/define/class/method.rs:80-96 | core/engine/src/vm/opcode/define/class/method.rs:173-189 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 3) core/parser/src/parser/expression/primary/object_initializer/mod.rs:228— core/parser/src/parser/expression/primary/object_initializer/mod.rs:228-244 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:256-272 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:292-308 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 5) core/engine/src/builtins/temporal/plain_date/mod.rs:298— core/engine/src/builtins/temporal/plain_date/mod.rs:298-309 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:444-455 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:144-155 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:228-239 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:441-452 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 5) core/engine/src/builtins/typed_array/object.rs:366— core/engine/src/builtins/typed_array/object.rs:366-377 | core/engine/src/builtins/typed_array/object.rs:406-417 | core/engine/src/builtins/typed_array/object.rs:437-448 | core/engine/src/builtins/typed_array/object.rs:503-514 | core/engine/src/builtins/typed_array/object.rs:535-546 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 5) core/engine/src/builtins/temporal/plain_date_time/mod.rs:407— core/engine/src/builtins/temporal/plain_date_time/mod.rs:407-418 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:421-432 | core/engine/src/builtins/temporal/plain_time/mod.rs:207-218 | core/engine/src/builtins/temporal/plain_time/mod.rs:221-232 | core/engine/src/builtins/temporal/plain_time/mod.rs:233-244 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11–12 lines × 2) core/engine/src/builtins/iterable/wrap_for_valid_iterator.rs:67— core/engine/src/builtins/iterable/wrap_for_valid_iterator.rs:67-78 | core/engine/src/builtins/iterable/wrap_for_valid_iterator.rs:98-108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) core/engine/src/builtins/set/mod.rs:608— core/engine/src/builtins/set/mod.rs:608-619 | core/engine/src/builtins/set/mod.rs:940-950 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) core/engine/src/bytecompiler/class.rs:436— core/engine/src/bytecompiler/class.rs:436-447 | core/engine/src/bytecompiler/class.rs:482-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 3) cli/src/debug/string.rs:7— cli/src/debug/string.rs:7-17 | cli/src/debug/string.rs:24-34 | cli/src/debug/string.rs:45-55 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) core/engine/src/builtins/promise/mod.rs:881— core/engine/src/builtins/promise/mod.rs:881-896 | core/engine/src/builtins/promise/mod.rs:971-986 | core/engine/src/builtins/promise/mod.rs:1255-1265 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:937— core/engine/src/builtins/temporal/plain_date/mod.rs:937-947 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1090-1100 | core/engine/src/builtins/temporal/plain_time/mod.rs:534-545 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10–11 lines × 2) core/engine/src/builtins/date/utils.rs:721— core/engine/src/builtins/date/utils.rs:721-730 | core/engine/src/builtins/date/utils.rs:733-743 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) core/engine/src/value/display/arguments.rs:75— core/engine/src/value/display/arguments.rs:75-84 | core/engine/src/value/display/object.rs:213-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10–11 lines × 2) core/parser/src/parser/expression/primary/mod.rs:133— core/parser/src/parser/expression/primary/mod.rs:133-143 | core/parser/src/parser/statement/mod.rs:457-466 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 5) core/engine/src/bytecompiler/class.rs:412— core/engine/src/bytecompiler/class.rs:412-423 | core/engine/src/bytecompiler/class.rs:463-472 | core/engine/src/bytecompiler/class.rs:515-524 | core/engine/src/bytecompiler/class.rs:559-568 | core/engine/src/bytecompiler/class.rs:602-611 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 5) core/engine/src/vm/opcode/define/class/getter.rs:43— core/engine/src/vm/opcode/define/class/getter.rs:43-52 | core/engine/src/vm/opcode/define/class/getter.rs:100-109 | core/engine/src/vm/opcode/define/class/getter.rs:207-216 | core/engine/src/vm/opcode/set/property.rs:233-242 | core/engine/src/vm/opcode/set/property.rs:277-286 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 5) core/engine/src/builtins/proxy/mod.rs:473— core/engine/src/builtins/proxy/mod.rs:473-482 | core/engine/src/builtins/proxy/mod.rs:602-611 | core/engine/src/builtins/proxy/mod.rs:717-726 | core/engine/src/builtins/proxy/mod.rs:809-818 | core/engine/src/builtins/proxy/mod.rs:886-895 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) core/engine/src/builtins/array_buffer/utils.rs:466— core/engine/src/builtins/array_buffer/utils.rs:466-478 | core/engine/src/builtins/array_buffer/utils.rs:544-559 | core/engine/src/builtins/array_buffer/utils.rs:621-630 | core/engine/src/builtins/array_buffer/utils.rs:693-702 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) core/engine/src/builtins/date/mod.rs:991— core/engine/src/builtins/date/mod.rs:991-1000 | core/engine/src/builtins/date/mod.rs:1123-1132 | core/engine/src/builtins/date/mod.rs:1189-1198 | core/engine/src/builtins/date/mod.rs:1251-1260 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) core/engine/src/module/namespace.rs:265— core/engine/src/module/namespace.rs:265-274 | core/engine/src/module/namespace.rs:301-310 | core/engine/src/module/namespace.rs:390-399 | core/engine/src/module/namespace.rs:492-501 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
SourceTextModule::inner_evaluate (cyclomatic 28) core/engine/src/module/source.rs:1177— SourceTextModule::inner_evaluate 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.
SourceTextModule::initialize_environment (cyclomatic 20) core/engine/src/module/source.rs:1591— SourceTextModule::initialize_environment has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeBlock::to_graph (cyclomatic 27) core/engine/src/vm/flowgraph/mod.rs:24— CodeBlock::to_graph has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CodeBlock::fmt (cyclomatic 17) core/engine/src/vm/code_block.rs:938— CodeBlock::fmt has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: CodeBlock::instruction_operands (cyclomatic 67) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
JsValue::to_json_inner (cyclomatic 19) core/engine/src/value/conversions/serde_json.rs:121— JsValue::to_json_inner has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
JsValue::abstract_relation (cyclomatic 19) core/engine/src/value/operations.rs:532— JsValue::abstract_relation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
boa_parser::parser::statement::declaration::hoistable::parse_callable_declaration (cyclomatic 19) core/parser/src/parser/statement/declaration/hoistable/mod.rs:154— boa_parser::parser::statement::declaration::hoistable::parse_callable_declaration 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.
boa_parser::parser::statement::iteration::for_statement::initializer_to_iterable_loop_initializer (cyclomatic 18) core/parser/src/parser/statement/iteration/for_statement.rs:327— boa_parser::parser::statement::iteration::for_statement::initializer_to_iterable_loop_initializer has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FixmeComment core/macros/src/lib.rs:230— // FIXME: use phf when const expressions are allowed. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment core/engine/src/builtins/number/globals.rs:117— // FIXME: once then_some is const fn, use it here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
ObjectLiteral::to_pattern (cognitive 58) core/ast/src/expression/literal/object.rs:70— ObjectLiteral::to_pattern has cognitive complexity 58 (threshold 15). Drivers by points: if/else 9 (38 pts), match/switch 4 (12 pts), boolean chains 7, loops 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ObjectLiteral::parse (cognitive 17) core/parser/src/parser/expression/primary/object_initializer/mod.rs:80— ObjectLiteral::parse 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.
CodeBlock::fmt (cognitive 32) core/engine/src/vm/code_block.rs:938— CodeBlock::fmt has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (20 pts), loops 5 (9 pts), match/switch 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeBlock::to_graph (cognitive 18) core/engine/src/vm/flowgraph/mod.rs:24— CodeBlock::to_graph has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lexer::next_no_skip (cognitive 23) core/parser/src/lexer/mod.rs:218— Lexer::next_no_skip has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Lexer::lex_slash_token (cognitive 18) core/parser/src/lexer/mod.rs:123— Lexer::lex_slash_token has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_parser::parser::statement::iteration::for_statement::initializer_to_iterable_loop_initializer (cognitive 23) core/parser/src/parser/statement/iteration/for_statement.rs:327— boa_parser::parser::statement::iteration::for_statement::initializer_to_iterable_loop_initializer has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 4 (8 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_parser::parser::statement::declaration::hoistable::parse_callable_declaration (cognitive 21) core/parser/src/parser/statement/declaration/hoistable/mod.rs:154— boa_parser::parser::statement::declaration::hoistable::parse_callable_declaration has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 7, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AllPrivateIdentifiersValidVisitor::visit_class_expression (cognitive 20) core/ast/src/operations/mod.rs:1188— AllPrivateIdentifiersValidVisitor::visit_class_expression has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (AllPrivateIdentifiersValidVisitor::visit_class_declaration) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AllPrivateIdentifiersValidVisitor::visit_class_declaration (cognitive 20) core/ast/src/operations/mod.rs:1257— AllPrivateIdentifiersValidVisitor::visit_class_declaration has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 2 (4 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (AllPrivateIdentifiersValidVisitor::visit_class_expression) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BindingCollectorVisitor::visit_for_in_loop_mut (cognitive 18) core/ast/src/scope_analyzer.rs:1011— BindingCollectorVisitor::visit_for_in_loop_mut has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (8 pts), match/switch 4 (6 pts), if/else 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (BindingCollectorVisitor::visit_for_of_loop_mut) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BindingCollectorVisitor::visit_for_of_loop_mut (cognitive 18) core/ast/src/scope_analyzer.rs:1078— BindingCollectorVisitor::visit_for_of_loop_mut has cognitive complexity 18 (threshold 15). Drivers by points: loops 3 (8 pts), match/switch 4 (6 pts), if/else 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (BindingCollectorVisitor::visit_for_in_loop_mut) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
boa_macros::derive_trace (cognitive 17) core/macros/src/lib.rs:302— boa_macros::derive_trace has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 1 (3 pts), boolean chains 2, 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.
boa_macros::generate_obj_properties (cognitive 16) core/macros/src/lib.rs:641— boa_macros::generate_obj_properties has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (32–33 lines × 2) core/engine/src/builtins/array/mod.rs:2171— core/engine/src/builtins/array/mod.rs:2171-2203 | core/engine/src/builtins/typed_array/builtin.rs:2505-2536 — 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 (32–33 lines × 2) core/engine/src/native_function/mod.rs:339— core/engine/src/native_function/mod.rs:339-371 | core/engine/src/native_function/mod.rs:403-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2) core/engine/src/builtins/object/mod.rs:366— core/engine/src/builtins/object/mod.rs:366-395 | core/engine/src/builtins/object/mod.rs:412-441 — 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 (30 lines × 2) core/engine/src/module/source.rs:2044— core/engine/src/module/source.rs:2044-2073 | core/engine/src/module/source.rs:2199-2228 — 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 (22 lines × 3) core/engine/src/builtins/promise/mod.rs:590— core/engine/src/builtins/promise/mod.rs:590-611 | core/engine/src/builtins/promise/mod.rs:805-826 | core/engine/src/builtins/promise/mod.rs:1482-1503 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (22 lines × 3) core/parser/src/parser/expression/assignment/arrow_function.rs:100— core/parser/src/parser/expression/assignment/arrow_function.rs:100-121 | core/parser/src/parser/expression/assignment/async_arrow_function.rs:106-127 | core/parser/src/parser/expression/assignment/mod.rs:178-199 — before extracting anything, compare `core/parser/src/parser/expression/assignment/arrow_function.rs` and `core/parser/src/parser/expression/assignment/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 3) core/engine/src/builtins/iterable/iterator_prototype.rs:732— core/engine/src/builtins/iterable/iterator_prototype.rs:732-750 | core/engine/src/builtins/iterable/iterator_prototype.rs:788-805 | core/engine/src/builtins/iterable/iterator_prototype.rs:847-865 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18–19 lines × 3) core/engine/src/vm/opcode/define/class/setter.rs:43— core/engine/src/vm/opcode/define/class/setter.rs:43-60 | core/engine/src/vm/opcode/define/class/setter.rs:101-119 | core/engine/src/vm/opcode/define/class/setter.rs:211-229 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (19 lines × 2) core/parser/src/parser/statement/block/mod.rs:103— core/parser/src/parser/statement/block/mod.rs:103-121 | core/parser/src/parser/statement/switch/mod.rs:82-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19 lines × 2) core/parser/src/parser/statement/declaration/export.rs:244— core/parser/src/parser/statement/declaration/export.rs:244-262 | core/parser/src/parser/statement/declaration/import.rs:209-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 4) core/ast/src/scope_analyzer.rs:667— core/ast/src/scope_analyzer.rs:667-682 | core/ast/src/scope_analyzer.rs:688-703 | core/ast/src/scope_analyzer.rs:709-724 | core/ast/src/scope_analyzer.rs:730-745 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 4) core/engine/src/builtins/iterable/iterator_prototype.rs:731— core/engine/src/builtins/iterable/iterator_prototype.rs:731-747 | core/engine/src/builtins/iterable/iterator_prototype.rs:787-802 | core/engine/src/builtins/iterable/iterator_prototype.rs:846-862 | core/engine/src/builtins/iterable/iterator_prototype.rs:906-921 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 3) core/engine/src/builtins/date/mod.rs:883— core/engine/src/builtins/date/mod.rs:883-898 | core/engine/src/builtins/date/mod.rs:1217-1232 | core/engine/src/builtins/date/mod.rs:1279-1294 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:78— core/engine/src/builtins/temporal/plain_date/mod.rs:78-93 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:81-96 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:81-96 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14–16 lines × 2) core/engine/src/builtins/array/mod.rs:2223— core/engine/src/builtins/array/mod.rs:2223-2238 | core/engine/src/builtins/typed_array/builtin.rs:2550-2563 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14–16 lines × 2) core/engine/src/builtins/promise/mod.rs:717— core/engine/src/builtins/promise/mod.rs:717-732 | core/engine/src/builtins/promise/mod.rs:1045-1058 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) core/engine/src/builtins/array/mod.rs:3235— core/engine/src/builtins/array/mod.rs:3235-3249 | core/engine/src/builtins/array/mod.rs:3262-3277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–16 lines × 2) core/engine/src/builtins/set/mod.rs:610— core/engine/src/builtins/set/mod.rs:610-624 | core/engine/src/builtins/set/mod.rs:696-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–15 lines × 2) core/engine/src/bytecompiler/mod.rs:1508— core/engine/src/bytecompiler/mod.rs:1508-1520 | core/engine/src/bytecompiler/mod.rs:1549-1563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–15 lines × 2) core/engine/src/value/display/array.rs:27— core/engine/src/value/display/array.rs:27-41 | core/engine/src/value/display/array.rs:90-102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 4) core/engine/src/builtins/typed_array/builtin_uint8.rs:117— core/engine/src/builtins/typed_array/builtin_uint8.rs:117-130 | core/engine/src/builtins/typed_array/builtin_uint8.rs:229-242 | core/engine/src/builtins/typed_array/builtin_uint8.rs:376-389 | core/engine/src/builtins/typed_array/builtin_uint8.rs:504-517 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 4) core/parser/src/parser/statement/declaration/lexical.rs:393— core/parser/src/parser/statement/declaration/lexical.rs:393-406 | core/parser/src/parser/statement/declaration/lexical.rs:434-447 | core/parser/src/parser/statement/variable/mod.rs:170-183 | core/parser/src/parser/statement/variable/mod.rs:189-202 — before extracting anything, compare `core/parser/src/parser/statement/declaration/lexical.rs` and `core/parser/src/parser/statement/variable/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) core/engine/src/builtins/temporal/plain_month_day/mod.rs:555— core/engine/src/builtins/temporal/plain_month_day/mod.rs:555-568 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1054-1066 — `core/engine/src/builtins/temporal/plain_month_day/mod.rs` and `core/engine/src/builtins/temporal/plain_year_month/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 147 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 2) core/parser/src/parser/function/mod.rs:258— core/parser/src/parser/function/mod.rs:258-271 | core/parser/src/parser/function/mod.rs:284-296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 3) core/engine/src/builtins/string/mod.rs:492— core/engine/src/builtins/string/mod.rs:492-503 | core/engine/src/builtins/string/mod.rs:570-580 | core/engine/src/builtins/string/mod.rs:613-623 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11–12 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1467— core/engine/src/builtins/temporal/plain_date/mod.rs:1467-1477 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:570-581 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1068-1079 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_month_day/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 91 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 4) core/engine/src/builtins/date/mod.rs:1006— core/engine/src/builtins/date/mod.rs:1006-1016 | core/engine/src/builtins/date/mod.rs:1135-1145 | core/engine/src/builtins/date/mod.rs:1198-1208 | core/engine/src/builtins/date/mod.rs:1260-1270 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 4) core/engine/src/builtins/temporal/duration/mod.rs:946— core/engine/src/builtins/temporal/duration/mod.rs:946-956 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1353-1363 | core/engine/src/builtins/temporal/plain_time/mod.rs:674-684 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1505-1515 — `core/engine/src/builtins/temporal/duration/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 66 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–11 lines × 2) core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1930— core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1930-1940 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1988-1996 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–11 lines × 2) core/engine/src/bytecompiler/mod.rs:869— core/engine/src/bytecompiler/mod.rs:869-877 | core/engine/src/bytecompiler/mod.rs:1593-1603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–10 lines × 2) core/parser/src/parser/function/mod.rs:491— core/parser/src/parser/function/mod.rs:491-500 | core/parser/src/parser/statement/mod.rs:965-972 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8–10 lines × 2) core/runtime/src/fetch/fetchers.rs:46— core/runtime/src/fetch/fetchers.rs:46-53 | core/runtime/src/fetch/fetchers.rs:73-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 6) core/engine/src/builtins/date/mod.rs:859— core/engine/src/builtins/date/mod.rs:859-867 | core/engine/src/builtins/date/mod.rs:989-997 | core/engine/src/builtins/date/mod.rs:1060-1068 | core/engine/src/builtins/date/mod.rs:1121-1129 | core/engine/src/builtins/date/mod.rs:1187-1195 | core/engine/src/builtins/date/mod.rs:1249-1257 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 6) core/engine/src/builtins/temporal/plain_date_time/mod.rs:369— core/engine/src/builtins/temporal/plain_date_time/mod.rs:369-377 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:380-388 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:392-400 | core/engine/src/builtins/temporal/plain_time/mod.rs:170-178 | core/engine/src/builtins/temporal/plain_time/mod.rs:181-189 | core/engine/src/builtins/temporal/plain_time/mod.rs:192-200 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8–9 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:1472— core/engine/src/builtins/temporal/plain_date/mod.rs:1472-1479 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1845-1853 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:575-583 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1073-1081 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8–9 lines × 4) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:62— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:62-69 | core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:75-82 | core/parser/src/parser/expression/primary/function_expression/mod.rs:60-68 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:66-73 — `core/parser/src/parser/expression/primary/async_function_expression/mod.rs` and `core/parser/src/parser/expression/primary/async_generator_expression/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 5) core/engine/src/object/builtins/jsproxy.rs:405— core/engine/src/object/builtins/jsproxy.rs:405-412 | core/engine/src/object/builtins/jsproxy.rs:436-442 | core/engine/src/object/builtins/jsproxy.rs:466-472 | core/engine/src/object/builtins/jsproxy.rs:485-492 | core/engine/src/object/builtins/jsproxy.rs:505-511 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 5) core/parser/src/parser/statement/declaration/lexical.rs:393— core/parser/src/parser/statement/declaration/lexical.rs:393-399 | core/parser/src/parser/statement/declaration/lexical.rs:434-440 | core/parser/src/parser/statement/variable/mod.rs:170-176 | core/parser/src/parser/statement/variable/mod.rs:189-195 | core/parser/src/parser/statement/variable/mod.rs:208-214 — before extracting anything, compare `core/parser/src/parser/statement/declaration/lexical.rs` and `core/parser/src/parser/statement/variable/mod.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 5) core/engine/src/builtins/iterable/iterator_prototype.rs:623— core/engine/src/builtins/iterable/iterator_prototype.rs:623-638 | core/engine/src/builtins/iterable/iterator_prototype.rs:718-733 | core/engine/src/builtins/iterable/iterator_prototype.rs:777-789 | core/engine/src/builtins/iterable/iterator_prototype.rs:836-848 | core/engine/src/builtins/iterable/iterator_prototype.rs:896-908 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 5) core/engine/src/builtins/temporal/duration/mod.rs:1294— core/engine/src/builtins/temporal/duration/mod.rs:1294-1306 | core/engine/src/builtins/temporal/duration/mod.rs:1318-1330 | core/engine/src/builtins/temporal/duration/mod.rs:1342-1354 | core/engine/src/builtins/temporal/duration/mod.rs:1366-1378 | core/engine/src/builtins/temporal/duration/mod.rs:1390-1402 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 5) core/engine/src/builtins/temporal/plain_date/mod.rs:1200— core/engine/src/builtins/temporal/plain_date/mod.rs:1200-1208 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1421-1430 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:349-360 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:730-741 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1567-1576 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 5) core/engine/src/builtins/temporal/duration/mod.rs:991— core/engine/src/builtins/temporal/duration/mod.rs:991-999 | core/engine/src/builtins/temporal/instant/mod.rs:588-597 | core/engine/src/builtins/temporal/plain_date/mod.rs:1137-1145 | core/engine/src/builtins/temporal/plain_time/mod.rs:471-479 | core/engine/src/builtins/temporal/plain_time/mod.rs:500-508 — `core/engine/src/builtins/temporal/duration/mod.rs` and `core/engine/src/builtins/temporal/instant/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
ClassElement::parse (cyclomatic 92) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:535— ClassElement::parse has cyclomatic complexity 92 (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.
ConstantFolding::constant_fold_binary_expr (cyclomatic 36) core/engine/src/optimizer/pass/constant_folding.rs:114— ConstantFolding::constant_fold_binary_expr has cyclomatic complexity 36 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ClassBody::parse (cyclomatic 35) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:296— ClassBody::parse has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ForStatement::parse (cyclomatic 35) core/parser/src/parser/statement/iteration/for_statement.rs:79— ForStatement::parse has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ObjectLiteral::to_pattern (cyclomatic 34) core/ast/src/expression/literal/object.rs:70— ObjectLiteral::to_pattern has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PropertyDefinition::parse (cyclomatic 34) core/parser/src/parser/expression/primary/object_initializer/mod.rs:175— PropertyDefinition::parse has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Lexer::next_no_skip (cyclomatic 32) core/parser/src/lexer/mod.rs:218— Lexer::next_no_skip has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
MemberExpression::parse (cyclomatic 31) core/parser/src/parser/expression/left_hand_side/member.rs:63— MemberExpression::parse has cyclomatic complexity 31 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BuiltInFunctionObject::create_dynamic_function (cyclomatic 30) core/engine/src/builtins/function/mod.rs:394— BuiltInFunctionObject::create_dynamic_function has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NumberLiteral::lex (cyclomatic 29) core/parser/src/lexer/number.rs:182— NumberLiteral::lex 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.
LeftHandSideExpression::parse (cyclomatic 29) core/parser/src/parser/expression/left_hand_side/mod.rs:76— LeftHandSideExpression::parse has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 2 function items inside it that branch (is_import_phase_call, is_keyword_call). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
AssignmentExpression::parse (cyclomatic 28) core/parser/src/parser/expression/assignment/mod.rs:90— AssignmentExpression::parse 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.
PrimaryExpression::parse (cyclomatic 28) core/parser/src/parser/expression/primary/mod.rs:96— PrimaryExpression::parse has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TemplateString::as_cooked (cyclomatic 25) core/parser/src/lexer/template.rs:82— TemplateString::as_cooked has cyclomatic complexity 25 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CoverParenthesizedExpressionAndArrowParameterList::parse (cyclomatic 24) core/parser/src/parser/expression/primary/mod.rs:312— CoverParenthesizedExpressionAndArrowParameterList::parse has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DigitFormatOptions::from_options (cyclomatic 23) core/engine/src/builtins/intl/number_format/options.rs:539— DigitFormatOptions::from_options has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Eval::perform_eval (cyclomatic 22) core/engine/src/builtins/eval/mod.rs:73— Eval::perform_eval 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.
Context::find_runtime_binding (cyclomatic 22) core/engine/src/environments/runtime/mod.rs:463— Context::find_runtime_binding 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.
ArrayLiteral::to_pattern (cyclomatic 21) core/ast/src/expression/literal/array.rs:58— ArrayLiteral::to_pattern has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Zip::new (cyclomatic 20) core/engine/src/builtins/iterable/iterator_helper/zip.rs:59— Zip::new 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.
SimpleJobExecutor::run_jobs_async (cyclomatic 20) core/engine/src/job.rs:949— SimpleJobExecutor::run_jobs_async 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.
ExportDeclaration::parse (cyclomatic 19) core/parser/src/parser/statement/declaration/export.rs:48— ExportDeclaration::parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ObjectBindingPattern::parse (cyclomatic 19) core/parser/src/parser/statement/mod.rs:516— ObjectBindingPattern::parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: Statement::parse (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
IndexedProperties::insert (cyclomatic 18) core/engine/src/object/property_map.rs:172— IndexedProperties::insert 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.
BindingList::parse (cyclomatic 18) core/parser/src/parser/statement/declaration/lexical.rs:244— BindingList::parse has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ModuleItemList::export_entries (cyclomatic 17) core/ast/src/module_item_list/mod.rs:312— ModuleItemList::export_entries has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Number::to_js_string_radix (cyclomatic 17) core/engine/src/builtins/number/mod.rs:565— Number::to_js_string_radix 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.
StatementList::parse (cyclomatic 17) core/parser/src/parser/statement/mod.rs:290— StatementList::parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: Statement::parse (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
NumberFormat::new (cyclomatic 16) core/engine/src/builtins/intl/number_format/mod.rs:303— NumberFormat::new 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. This is NOT this file's highest cyclomatic complexity: NumberFormat::resolved_options (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
ArrayBindingPattern::parse (cyclomatic 16) core/parser/src/parser/statement/mod.rs:764— ArrayBindingPattern::parse has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: Statement::parse (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
JsStr::to_number (cyclomatic 16) core/string/src/str.rs:313— JsStr::to_number has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
boa_wintertc::console::formatter (cyclomatic 16) core/wintertc/src/console/mod.rs:194— boa_wintertc::console::formatter has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ClassElement::parse (cognitive 168) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:535— ClassElement::parse has cognitive complexity 168 (threshold 15). Drivers by points: if/else 46 (121 pts), match/switch 13 (26 pts), boolean chains 15, loops 2 (6 pts) (nesting depth added 92). 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.
ClassBody::parse (cognitive 80) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:296— ClassBody::parse has cognitive complexity 80 (threshold 15). Drivers by points: if/else 18 (56 pts), match/switch 5 (18 pts), boolean chains 5, loops 1 (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NumberLiteral::lex (cognitive 69) core/parser/src/lexer/number.rs:182— NumberLiteral::lex has cognitive complexity 69 (threshold 15). Drivers by points: if/else 22 (63 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 43). 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.
LeftHandSideExpression::parse (cognitive 57) core/parser/src/parser/expression/left_hand_side/mod.rs:76— LeftHandSideExpression::parse has cognitive complexity 57 (threshold 15). Drivers by points: if/else 25 (47 pts), boolean chains 7, match/switch 1 (3 pts) (nesting depth added 24). Of this number, 32 points are the body's own statements and 25 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatementList::parse (cognitive 56) core/parser/src/parser/statement/mod.rs:290— StatementList::parse has cognitive complexity 56 (threshold 15). Drivers by points: if/else 13 (45 pts), loops 2 (8 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 39). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BuiltInFunctionObject::create_dynamic_function (cognitive 54) core/engine/src/builtins/function/mod.rs:394— BuiltInFunctionObject::create_dynamic_function has cognitive complexity 54 (threshold 15). Drivers by points: if/else 27 (41 pts), loops 3 (7 pts), boolean chains 6 (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.
ObjectBindingPattern::parse (cognitive 53) core/parser/src/parser/statement/mod.rs:516— ObjectBindingPattern::parse has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (28 pts), match/switch 7 (23 pts), boolean chains 1, loops 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimpleJobExecutor::run_jobs_async (cognitive 51) core/engine/src/job.rs:949— SimpleJobExecutor::run_jobs_async has cognitive complexity 51 (threshold 15). Drivers by points: if/else 8 (28 pts), loops 7 (14 pts), match/switch 2 (8 pts), boolean chains 1 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyDefinition::parse (cognitive 49) core/parser/src/parser/expression/primary/object_initializer/mod.rs:175— PropertyDefinition::parse has cognitive complexity 49 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 6, match/switch 4 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForStatement::parse (cognitive 48) core/parser/src/parser/statement/iteration/for_statement.rs:79— ForStatement::parse has cognitive complexity 48 (threshold 15). Drivers by points: if/else 21 (35 pts), loops 3 (7 pts), boolean chains 3, match/switch 3 (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.
AssignmentExpression::parse (cognitive 47) core/parser/src/parser/expression/assignment/mod.rs:90— AssignmentExpression::parse has cognitive complexity 47 (threshold 15). Drivers by points: if/else 19 (36 pts), boolean chains 7, match/switch 3 (4 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Zip::new (cognitive 41) core/engine/src/builtins/iterable/iterator_helper/zip.rs:59— Zip::new has cognitive complexity 41 (threshold 15). Drivers by points: if/else 9 (24 pts), match/switch 6 (11 pts), loops 3 (6 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Context::find_runtime_binding (cognitive 38) core/engine/src/environments/runtime/mod.rs:463— Context::find_runtime_binding has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 6, loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DigitFormatOptions::from_options (cognitive 32) core/engine/src/builtins/intl/number_format/options.rs:539— DigitFormatOptions::from_options has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (22 pts), match/switch 3 (6 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConstantFolding::constant_fold_binary_expr (cognitive 32) core/engine/src/optimizer/pass/constant_folding.rs:114— ConstantFolding::constant_fold_binary_expr has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (22 pts), match/switch 5 (9 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.
ExportDeclaration::parse (cognitive 31) core/parser/src/parser/statement/declaration/export.rs:48— ExportDeclaration::parse has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 4 (8 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 17). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
boa_wintertc::console::formatter (cognitive 30) core/wintertc/src/console/mod.rs:194— boa_wintertc::console::formatter has cognitive complexity 30 (threshold 15). Drivers by points: if/else 4 (14 pts), match/switch 4 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 19). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MemberExpression::parse (cognitive 29) core/parser/src/parser/expression/left_hand_side/member.rs:63— MemberExpression::parse has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 8 (19 pts), if/else 5 (9 pts), loops 1 (nesting depth added 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Promise::perform_promise_all_keyed (cognitive 27) core/engine/src/builtins/promise/mod.rs:1190— Promise::perform_promise_all_keyed has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 1, 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.
TemplateString::as_cooked (cognitive 27) core/parser/src/lexer/template.rs:82— TemplateString::as_cooked has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 2 (6 pts), match/switch 2 (5 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
boa_cli::main (cognitive 26) cli/src/main.rs:551— boa_cli::main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayLiteral::to_pattern (cognitive 26) core/ast/src/expression/literal/array.rs:58— ArrayLiteral::to_pattern has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 4 (12 pts), boolean chains 1, 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.
Eval::perform_eval (cognitive 26) core/engine/src/builtins/eval/mod.rs:73— Eval::perform_eval has cognitive complexity 26 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 4, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Stack::display_trace (cognitive 25) core/engine/src/vm/mod.rs:306— Stack::display_trace has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 2, 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.
IndexedProperties::insert (cognitive 23) core/engine/src/object/property_map.rs:172— IndexedProperties::insert has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (22 pts), match/switch 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.
CoverParenthesizedExpressionAndArrowParameterList::parse (cognitive 23) core/parser/src/parser/expression/primary/mod.rs:312— CoverParenthesizedExpressionAndArrowParameterList::parse has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 9 (10 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
JsHeaders::constructor (cognitive 23) core/runtime/src/fetch/headers.rs:89— JsHeaders::constructor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 3 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForInIterator::next (cognitive 22) core/engine/src/builtins/object/for_in_iterator.rs:84— ForInIterator::next has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), match/switch 2 (6 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.
BuiltinUint8Array::get_base64_options (cognitive 22) core/engine/src/builtins/typed_array/builtin_uint8.rs:569— BuiltinUint8Array::get_base64_options has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (22 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.
RegexLiteral::lex (cognitive 22) core/parser/src/lexer/regex.rs:41— RegexLiteral::lex has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3 (10 pts), loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArrayBindingPattern::parse (cognitive 22) core/parser/src/parser/statement/mod.rs:764— ArrayBindingPattern::parse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 5 (10 pts), boolean chains 1, 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.
StringLiteral::take_unicode_escape_sequence (cognitive 20) core/parser/src/lexer/string.rs:242— StringLiteral::take_unicode_escape_sequence has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 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.
PrimaryExpression::parse (cognitive 20) core/parser/src/parser/expression/primary/mod.rs:96— PrimaryExpression::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
LexicalBinding::parse (cognitive 20) core/parser/src/parser/statement/declaration/lexical.rs:373— LexicalBinding::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (19 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
IfStatement::parse (cognitive 20) core/parser/src/parser/statement/if_stm/mod.rs:59— IfStatement::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 3 (6 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.
Catch::parse (cognitive 20) core/parser/src/parser/statement/try_stm/catch.rs:56— Catch::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RequestInit::into_request_builder (cognitive 20) core/runtime/src/fetch/request.rs:40— RequestInit::into_request_builder has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 2 (4 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.
Atomics::wait (cognitive 19) core/engine/src/builtins/atomics/mod.rs:405— Atomics::wait has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), match/switch 3 (4 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.
DisplayShadowEntry::fmt (cognitive 19) core/engine/src/vm/shadow_stack.rs:81— DisplayShadowEntry::fmt has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BindingList::parse (cognitive 18) core/parser/src/parser/statement/declaration/lexical.rs:244— BindingList::parse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 3 (7 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormalParameterList::from_parameters (cognitive 17) core/ast/src/function/parameters.rs:36— FormalParameterList::from_parameters has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Drop::new (cognitive 17) core/engine/src/builtins/iterable/iterator_helper/drop.rs:34— Drop::new has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (7 pts), match/switch 3 (6 pts), if/else 1 (4 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.
SharedShape::rollback_before (cognitive 17) core/engine/src/object/shape/shared_shape/mod.rs:359— SharedShape::rollback_before 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.
BufferedLexer::peek (cognitive 17) core/parser/src/parser/cursor/buffered_lexer/mod.rs:230— BufferedLexer::peek has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsStr::to_number (cognitive 17) core/string/src/str.rs:313— JsStr::to_number has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 3, 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.
ScopeIndexVisitor::visit_function_like (cognitive 16) core/ast/src/scope_analyzer.rs:1674— ScopeIndexVisitor::visit_function_like has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrdinaryObject::assign (cognitive 16) core/engine/src/builtins/object/mod.rs:963— OrdinaryObject::assign has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 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.
Set::is_disjoint_from (cognitive 16) core/engine/src/builtins/set/mod.rs:590— Set::is_disjoint_from has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 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.
FunctionCompiler::compile (cognitive 16) core/engine/src/bytecompiler/function.rs:116— FunctionCompiler::compile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6 (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.
JsObject::to_property_descriptor (cognitive 16) core/engine/src/object/jsobject.rs:680— JsObject::to_property_descriptor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (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.
FormalParameter::parse (cognitive 16) core/parser/src/parser/function/mod.rs:348— FormalParameter::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 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.
WithClause::parse (cognitive 16) core/parser/src/parser/statement/declaration/mod.rs:198— WithClause::parse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFields: ByteCompiler core/engine/src/bytecompiler/mod.rs:496— TooManyFields — 34 stored fields beside 152 methods. The bar is 30 stored fields; this is 4 over it, 1.13× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFunctions: boa_engine::builtins::date::utils core/engine/src/builtins/date/utils.rs:43— TooManyFunctions — 33 free functions. The bar is 30 free functions; this is 3 over it, 1.10× the bar. This type is on a published API surface — a cargo-semver-checks gate in CI (.github/workflows/rust.yml) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×1
Change coupling clique: mod.rs, mod.rs, mod.rs core/engine/src/builtins/intl/collator/mod.rs— 3 files — `core/engine/src/builtins/intl/collator/mod.rs`, `core/engine/src/builtins/intl/list_format/mod.rs`, `core/engine/src/builtins/intl/plural_rules/mod.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Near-duplicate member family (5 members, 40 shared lines) · ×1
Near-duplicate member family (5 members, 40 shared lines) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:46— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:46-162 | core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:54-194 | core/parser/src/parser/expression/primary/function_expression/mod.rs:55-157 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:55-173 | core/parser/src/parser/statement/declaration/hoistable/mod.rs:158-270 — These 5 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 40 shared lines) · ×1
Near-duplicate member family (4 members, 40 shared lines) core/engine/src/builtins/temporal/duration/mod.rs:888— core/engine/src/builtins/temporal/duration/mod.rs:888-971 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1316-1370 | core/engine/src/builtins/temporal/plain_time/mod.rs:634-698 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1461-1525 — These 4 members are variants of one another: a block of 40 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 29 shared lines) · ×1
Near-duplicate member family (4 members, 29 shared lines) core/engine/src/builtins/promise/mod.rs:561— core/engine/src/builtins/promise/mod.rs:561-611 | core/engine/src/builtins/promise/mod.rs:776-826 | core/engine/src/builtins/promise/mod.rs:1453-1503 | core/engine/src/builtins/promise/mod.rs:1683-1733 — These 4 members are variants of one another: a block of 29 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 26 shared lines) · ×1
Near-duplicate member family (4 members, 26 shared lines) core/engine/src/builtins/typed_array/builtin_uint8.rs:114— core/engine/src/builtins/typed_array/builtin_uint8.rs:114-214 | core/engine/src/builtins/typed_array/builtin_uint8.rs:226-283 | core/engine/src/builtins/typed_array/builtin_uint8.rs:373-489 | core/engine/src/builtins/typed_array/builtin_uint8.rs:501-548 — These 4 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 25 shared lines) · ×1
Near-duplicate member family (4 members, 25 shared lines) core/engine/src/vm/opcode/define/class/getter.rs:23— core/engine/src/vm/opcode/define/class/getter.rs:23-59 | core/engine/src/vm/opcode/define/class/getter.rs:80-116 | core/engine/src/vm/opcode/define/class/setter.rs:23-60 | core/engine/src/vm/opcode/define/class/setter.rs:81-119 — These 4 members are variants of one another: a block of 25 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (4 members, 17 shared lines) · ×1
Near-duplicate member family (4 members, 17 shared lines) core/engine/src/vm/opcode/define/class/getter.rs:137— core/engine/src/vm/opcode/define/class/getter.rs:137-170 | core/engine/src/vm/opcode/define/class/getter.rs:191-223 | core/engine/src/vm/opcode/define/class/setter.rs:140-174 | core/engine/src/vm/opcode/define/class/setter.rs:195-229 — These 4 members are variants of one another: a block of 17 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Near-duplicate member pair (56 shared lines) core/parser/src/parser/expression/left_hand_side/call.rs:119— core/parser/src/parser/expression/left_hand_side/call.rs:119-198 | core/parser/src/parser/expression/left_hand_side/member.rs:63-314 — These two members are variants of one another: 56 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (55 shared lines) core/engine/src/builtins/json/mod.rs:967— core/engine/src/builtins/json/mod.rs:967-1114 | core/engine/src/builtins/json/mod.rs:1126-1241 — These two members are variants of one another: 55 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (45 shared lines) core/parser/src/parser/statement/declaration/lexical.rs:373— core/parser/src/parser/statement/declaration/lexical.rs:373-487 | core/parser/src/parser/statement/variable/mod.rs:164-226 — These two members are variants of one another: 45 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (36 shared lines) core/engine/src/builtins/set/mod.rs:594— core/engine/src/builtins/set/mod.rs:594-660 | core/engine/src/builtins/set/mod.rs:924-1004 — These two members are variants of one another: 36 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 (76 corresponding lines) · ×1
Edited copy of a member (76 corresponding lines) core/engine/src/builtins/temporal/plain_date_time/mod.rs:343— core/engine/src/builtins/temporal/plain_date_time/mod.rs:343-472 | core/engine/src/builtins/temporal/plain_time/mod.rs:159-249 — These two members are one piece of code written twice and then edited apart: 76 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) core/ast/src/scope_analyzer.rs:1744— core/ast/src/scope_analyzer.rs:1744-1809 | core/ast/src/scope_analyzer.rs:1884-2199 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) core/engine/src/vm/opcode/define/class/method.rs:117— core/engine/src/vm/opcode/define/class/method.rs:117-145 | core/engine/src/vm/opcode/define/class/method.rs:166-189 — 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· Members sharing a duplicated core (15 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (15 members, 50+ identical tokens) core/engine/src/builtins/temporal/plain_date/mod.rs:358— core/engine/src/builtins/temporal/plain_date/mod.rs:358-374 | core/engine/src/builtins/temporal/plain_date/mod.rs:389-401 | core/engine/src/builtins/temporal/plain_date/mod.rs:416-428 | core/engine/src/builtins/temporal/plain_date/mod.rs:443-455 | core/engine/src/builtins/temporal/plain_date/mod.rs:470-482 | core/engine/src/builtins/temporal/plain_date/mod.rs:497-509 | core/engine/src/builtins/temporal/plain_date/mod.rs:522-534 | core/engine/src/builtins/temporal/plain_date/mod.rs:547-559 | core/engine/src/builtins/temporal/plain_date/mod.rs:572-584 | core/engine/src/builtins/temporal/plain_date/mod.rs:597-609 | core/engine/src/builtins/temporal/plain_date/mod.rs:622-634 | core/engine/src/builtins/temporal/plain_date/mod.rs:647-659 | core/engine/src/builtins/temporal/plain_date/mod.rs:672-684 | core/engine/src/builtins/temporal/plain_date/mod.rs:697-709 | core/engine/src/builtins/temporal/plain_date/mod.rs:722-734 — These 15 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 15 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 15 times.
D4 · Code Duplication· Members sharing a duplicated core (14 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (14 members, 50+ identical tokens) core/engine/src/builtins/date/mod.rs:450— core/engine/src/builtins/date/mod.rs:450-475 | core/engine/src/builtins/date/mod.rs:489-514 | core/engine/src/builtins/date/mod.rs:531-550 | core/engine/src/builtins/date/mod.rs:563-588 | core/engine/src/builtins/date/mod.rs:601-626 | core/engine/src/builtins/date/mod.rs:639-664 | core/engine/src/builtins/date/mod.rs:677-702 | core/engine/src/builtins/date/mod.rs:716-741 | core/engine/src/builtins/date/mod.rs:754-779 | core/engine/src/builtins/date/mod.rs:822-841 | core/engine/src/builtins/date/mod.rs:1402-1422 | core/engine/src/builtins/date/mod.rs:1539-1560 | core/engine/src/builtins/date/mod.rs:1680-1703 | core/engine/src/builtins/date/mod.rs:1718-1807 — These 14 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 14 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 14 times.
Duplicated block (75 lines × 2) core/engine/src/bytecompiler/declarations.rs:434— core/engine/src/bytecompiler/declarations.rs:434-508 | core/engine/src/bytecompiler/declarations.rs:705-779 — 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 (64 lines × 2) core/ast/src/operations/mod.rs:1192— core/ast/src/operations/mod.rs:1192-1255 | core/ast/src/operations/mod.rs:1261-1324 — 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 (42–50 lines × 2) core/engine/src/builtins/intl/date_time_format/mod.rs:210— core/engine/src/builtins/intl/date_time_format/mod.rs:210-251 | core/engine/src/builtins/intl/number_format/mod.rs:249-298 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/number_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 137 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (47 lines × 2) core/engine/src/builtins/date/mod.rs:1734— core/engine/src/builtins/date/mod.rs:1734-1780 | core/engine/src/builtins/date/utils.rs:541-587 — 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 (46 lines × 2) core/engine/src/module/namespace.rs:315— core/engine/src/module/namespace.rs:315-360 | core/engine/src/module/namespace.rs:403-448 — 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 (43–46 lines × 2) core/parser/src/parser/expression/left_hand_side/mod.rs:162— core/parser/src/parser/expression/left_hand_side/mod.rs:162-207 | core/parser/src/parser/expression/left_hand_side/mod.rs:222-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (44–45 lines × 2) core/engine/src/builtins/typed_array/builtin_uint8.rs:58— core/engine/src/builtins/typed_array/builtin_uint8.rs:58-102 | core/engine/src/builtins/typed_array/builtin_uint8.rs:318-361 — 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 (41 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1779— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1779-1819 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2150-2190 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (36 lines × 2) core/ast/src/scope_analyzer.rs:1030— core/ast/src/scope_analyzer.rs:1030-1065 | core/ast/src/scope_analyzer.rs:1097-1132 — 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 (33–34 lines × 2) core/engine/src/builtins/iterable/async_from_sync_iterator.rs:176— core/engine/src/builtins/iterable/async_from_sync_iterator.rs:176-208 | core/engine/src/builtins/iterable/async_from_sync_iterator.rs:269-302 — 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 (29–33 lines × 5) core/engine/src/builtins/temporal/duration/mod.rs:897— core/engine/src/builtins/temporal/duration/mod.rs:897-928 | core/engine/src/builtins/temporal/instant/mod.rs:495-525 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1323-1351 | core/engine/src/builtins/temporal/plain_time/mod.rs:643-671 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1470-1502 — `core/engine/src/builtins/temporal/duration/mod.rs` and `core/engine/src/builtins/temporal/instant/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (30–32 lines × 3) core/parser/src/parser/expression/primary/object_initializer/mod.rs:760— core/parser/src/parser/expression/primary/object_initializer/mod.rs:760-791 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:859-890 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:936-965 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (31 lines × 2) core/engine/src/builtins/intl/date_time_format/mod.rs:979— core/engine/src/builtins/intl/date_time_format/mod.rs:979-1009 | core/engine/src/builtins/intl/number_format/mod.rs:700-730 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/number_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 137 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (28–29 lines × 2) core/engine/src/builtins/promise/mod.rs:649— core/engine/src/builtins/promise/mod.rs:649-676 | core/engine/src/builtins/promise/mod.rs:1542-1570 — 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 (24–29 lines × 2) core/engine/src/builtins/typed_array/builtin_uint8.rs:178— core/engine/src/builtins/typed_array/builtin_uint8.rs:178-206 | core/engine/src/builtins/typed_array/builtin_uint8.rs:458-481 — 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 (23–28 lines × 2) core/engine/src/builtins/intl/collator/mod.rs:423— core/engine/src/builtins/intl/collator/mod.rs:423-450 | core/engine/src/builtins/intl/list_format/mod.rs:380-402 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (26–28 lines × 2) core/parser/src/parser/expression/assignment/async_arrow_function.rs:115— core/parser/src/parser/expression/assignment/async_arrow_function.rs:115-140 | core/parser/src/parser/expression/assignment/mod.rs:187-214 — before extracting anything, compare `core/parser/src/parser/expression/assignment/async_arrow_function.rs` and `core/parser/src/parser/expression/assignment/mod.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23–26 lines × 5) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:115— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:115-140 | core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:148-172 | core/parser/src/parser/expression/primary/function_expression/mod.rs:110-135 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:117-142 | core/parser/src/parser/statement/declaration/hoistable/mod.rs:214-236 — `core/parser/src/parser/expression/primary/async_function_expression/mod.rs` and `core/parser/src/parser/expression/primary/async_generator_expression/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (24–26 lines × 3) core/engine/src/bytecompiler/class.rs:416— core/engine/src/bytecompiler/class.rs:416-441 | core/engine/src/bytecompiler/class.rs:519-542 | core/engine/src/bytecompiler/class.rs:563-586 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–26 lines × 2) core/engine/src/builtins/promise/mod.rs:871— core/engine/src/builtins/promise/mod.rs:871-896 | core/engine/src/builtins/promise/mod.rs:1252-1265 — 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 (24–25 lines × 2) core/engine/src/builtins/function/mod.rs:1065— core/engine/src/builtins/function/mod.rs:1065-1088 | core/engine/src/builtins/function/mod.rs:1173-1197 — 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 (22–24 lines × 5) core/parser/src/parser/expression/primary/object_initializer/mod.rs:433— core/parser/src/parser/expression/primary/object_initializer/mod.rs:433-456 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:499-521 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:767-788 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:866-887 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:941-962 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (24 lines × 3) core/ast/src/scope_analyzer.rs:1783— core/ast/src/scope_analyzer.rs:1783-1806 | core/ast/src/scope_analyzer.rs:2163-2186 | core/ast/src/scope_analyzer.rs:2481-2504 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (24 lines × 2) core/engine/src/builtins/builder.rs:437— core/engine/src/builtins/builder.rs:437-460 | core/engine/src/builtins/builder.rs:469-492 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23–24 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:2288— core/engine/src/builtins/typed_array/builtin.rs:2288-2310 | core/engine/src/builtins/typed_array/builtin.rs:2343-2366 — 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 (20–23 lines × 2) core/parser/src/parser/expression/primary/object_initializer/mod.rs:222— core/parser/src/parser/expression/primary/object_initializer/mod.rs:222-244 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:253-272 — 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 (22 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1738— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1738-1759 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2109-2130 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20–21 lines × 3) core/engine/src/builtins/intl/date_time_format/mod.rs:945— core/engine/src/builtins/intl/date_time_format/mod.rs:945-965 | core/engine/src/builtins/intl/list_format/mod.rs:269-288 | core/engine/src/builtins/intl/number_format/mod.rs:647-667 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/list_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19–21 lines × 3) core/parser/src/parser/expression/assignment/arrow_function.rs:138— core/parser/src/parser/expression/assignment/arrow_function.rs:138-157 | core/parser/src/parser/expression/assignment/async_arrow_function.rs:132-150 | core/parser/src/parser/expression/assignment/mod.rs:204-224 — before extracting anything, compare `core/parser/src/parser/expression/assignment/arrow_function.rs` and `core/parser/src/parser/expression/assignment/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 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 (20–21 lines × 2) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:871— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:871-890 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:973-993 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–20 lines × 5) core/parser/src/parser/expression/primary/async_function_expression/mod.rs:95— core/parser/src/parser/expression/primary/async_function_expression/mod.rs:95-109 | core/parser/src/parser/expression/primary/async_generator_expression/mod.rs:128-142 | core/parser/src/parser/expression/primary/function_expression/mod.rs:90-104 | core/parser/src/parser/expression/primary/generator_expression/mod.rs:96-111 | core/parser/src/parser/statement/declaration/hoistable/mod.rs:190-209 — `core/parser/src/parser/expression/primary/async_function_expression/mod.rs` and `core/parser/src/parser/expression/primary/async_generator_expression/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 82 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16–20 lines × 4) core/engine/src/bytecompiler/mod.rs:2254— core/engine/src/bytecompiler/mod.rs:2254-2269 | core/engine/src/bytecompiler/mod.rs:2304-2319 | core/engine/src/bytecompiler/mod.rs:2345-2364 | core/engine/src/bytecompiler/mod.rs:2386-2404 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (20 lines × 3) core/engine/src/builtins/promise/mod.rs:565— core/engine/src/builtins/promise/mod.rs:565-584 | core/engine/src/builtins/promise/mod.rs:780-799 | core/engine/src/builtins/promise/mod.rs:1457-1476 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–20 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:283— core/engine/src/builtins/temporal/plain_date/mod.rs:283-295 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:349-364 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:210-229 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16–20 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:2269— core/engine/src/builtins/typed_array/builtin.rs:2269-2288 | core/engine/src/builtins/typed_array/builtin.rs:2321-2336 — 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 (18–20 lines × 2) core/engine/src/builtins/uri/mod.rs:401— core/engine/src/builtins/uri/mod.rs:401-420 | core/engine/src/builtins/uri/mod.rs:468-485 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–19 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:1436— core/engine/src/builtins/temporal/plain_date/mod.rs:1436-1453 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1768-1785 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1036-1054 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2139-2156 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18–19 lines × 2) core/engine/src/builtins/dataview/mod.rs:221— core/engine/src/builtins/dataview/mod.rs:221-239 | core/engine/src/object/builtins/jsdataview.rs:68-85 — 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 (17–19 lines × 2) core/engine/src/object/builtins/jspromise.rs:1235— core/engine/src/object/builtins/jspromise.rs:1235-1251 | core/engine/src/object/builtins/jspromise.rs:1299-1317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–18 lines × 5) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:885— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:885-901 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:987-1004 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1029-1045 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1116-1131 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:1206-1223 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15–18 lines × 2) core/engine/src/builtins/array/mod.rs:2707— core/engine/src/builtins/array/mod.rs:2707-2724 | core/engine/src/builtins/array/mod.rs:2770-2784 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–18 lines × 2) core/engine/src/builtins/json/mod.rs:1073— core/engine/src/builtins/json/mod.rs:1073-1090 | core/engine/src/builtins/json/mod.rs:1202-1217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–18 lines × 2) core/engine/src/vm/opcode/call/mod.rs:35— core/engine/src/vm/opcode/call/mod.rs:35-52 | core/engine/src/vm/opcode/call/mod.rs:119-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.
Duplicated block (15–17 lines × 8) core/parser/src/parser/expression/assignment/arrow_function.rs:137— core/parser/src/parser/expression/assignment/arrow_function.rs:137-152 | core/parser/src/parser/expression/assignment/async_arrow_function.rs:131-145 | core/parser/src/parser/expression/assignment/mod.rs:203-219 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:432-448 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:498-513 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:766-780 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:865-879 | core/parser/src/parser/expression/primary/object_initializer/mod.rs:940-954 — before extracting anything, compare `core/parser/src/parser/expression/assignment/arrow_function.rs` and `core/parser/src/parser/expression/assignment/async_arrow_function.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–17 lines × 3) core/engine/src/builtins/promise/mod.rs:638— core/engine/src/builtins/promise/mod.rs:638-653 | core/engine/src/builtins/promise/mod.rs:853-868 | core/engine/src/builtins/promise/mod.rs:1530-1546 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–17 lines × 2) core/engine/src/builtins/set/mod.rs:808— core/engine/src/builtins/set/mod.rs:808-819 | core/engine/src/builtins/set/mod.rs:876-892 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15–17 lines × 2) core/engine/src/builtins/string/mod.rs:1134— core/engine/src/builtins/string/mod.rs:1134-1150 | core/engine/src/builtins/string/mod.rs:2097-2111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16–17 lines × 2) core/parser/src/parser/statement/if_stm/mod.rs:87— core/parser/src/parser/statement/if_stm/mod.rs:87-102 | core/parser/src/parser/statement/if_stm/mod.rs:138-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–16 lines × 4) core/engine/src/bytecompiler/class.rs:410— core/engine/src/bytecompiler/class.rs:410-425 | core/engine/src/bytecompiler/class.rs:461-474 | core/engine/src/bytecompiler/class.rs:513-526 | core/engine/src/bytecompiler/class.rs:557-570 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–16 lines × 3) core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:720— core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:720-733 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:785-800 | core/parser/src/parser/statement/declaration/hoistable/class_decl/mod.rs:826-841 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (15 lines × 4) core/engine/src/builtins/temporal/plain_date/mod.rs:86— core/engine/src/builtins/temporal/plain_date/mod.rs:86-100 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:89-103 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:75-89 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:89-103 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:102— core/engine/src/builtins/temporal/plain_date/mod.rs:102-116 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:129-143 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:137-151 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–15 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:294— core/engine/src/builtins/temporal/plain_date/mod.rs:294-306 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:139-152 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:222-236 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_month_day/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 91 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10–15 lines × 2) core/engine/src/builtins/error/aggregate.rs:92— core/engine/src/builtins/error/aggregate.rs:92-106 | core/engine/src/builtins/error/mod.rs:474-483 — 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–15 lines × 2) core/engine/src/builtins/set/mod.rs:227— core/engine/src/builtins/set/mod.rs:227-237 | core/engine/src/builtins/weak_set/mod.rs:90-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14–15 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:860— core/engine/src/builtins/temporal/plain_date/mod.rs:860-874 | core/engine/src/builtins/temporal/plain_date/mod.rs:896-909 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 5) core/ast/src/operations/mod.rs:1517— core/ast/src/operations/mod.rs:1517-1530 | core/ast/src/operations/mod.rs:1535-1548 | core/ast/src/operations/mod.rs:1553-1566 | core/ast/src/operations/mod.rs:1571-1584 | core/ast/src/operations/mod.rs:1589-1602 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 2) core/engine/src/builtins/temporal/instant/mod.rs:419— core/engine/src/builtins/temporal/instant/mod.rs:419-432 | core/engine/src/builtins/temporal/instant/mod.rs:455-466 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–14 lines × 2) core/engine/src/builtins/temporal/plain_date/mod.rs:946— core/engine/src/builtins/temporal/plain_date/mod.rs:946-959 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:292-302 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_month_day/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 8 separate duplicated blocks between them, totalling at least 91 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10–14 lines × 2) core/engine/src/vm/opcode/call/mod.rs:54— core/engine/src/vm/opcode/call/mod.rs:54-67 | core/engine/src/vm/opcode/call/mod.rs:133-142 — 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–13 lines × 5) core/engine/src/bytecompiler/mod.rs:2203— core/engine/src/bytecompiler/mod.rs:2203-2209 | core/engine/src/bytecompiler/mod.rs:2253-2261 | core/engine/src/bytecompiler/mod.rs:2303-2311 | core/engine/src/bytecompiler/mod.rs:2344-2356 | core/engine/src/bytecompiler/mod.rs:2385-2396 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 4) core/engine/src/vm/opcode/define/class/getter.rs:34— core/engine/src/vm/opcode/define/class/getter.rs:34-45 | core/engine/src/vm/opcode/define/class/getter.rs:91-102 | core/engine/src/vm/opcode/define/class/getter.rs:144-156 | core/engine/src/vm/opcode/define/class/getter.rs:198-209 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–13 lines × 3) core/engine/src/builtins/temporal/plain_date/mod.rs:1453— core/engine/src/builtins/temporal/plain_date/mod.rs:1453-1464 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1809-1821 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2180-2192 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–13 lines × 2) core/engine/src/object/operations.rs:815— core/engine/src/object/operations.rs:815-827 | core/engine/src/object/operations.rs:1376-1384 — 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 (3–13 lines × 4) core/engine/src/vm/opcode/define/own_property.rs:63— core/engine/src/vm/opcode/define/own_property.rs:63-65 | core/engine/src/vm/opcode/set/property.rs:160-162 | core/engine/src/vm/opcode/set/property.rs:273-284 | core/engine/src/vm/opcode/set/property.rs:366-378 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (12 lines × 6) core/engine/src/vm/opcode/define/class/getter.rs:25— core/engine/src/vm/opcode/define/class/getter.rs:25-36 | core/engine/src/vm/opcode/define/class/getter.rs:82-93 | core/engine/src/vm/opcode/define/class/method.rs:23-34 | core/engine/src/vm/opcode/define/class/method.rs:71-82 | core/engine/src/vm/opcode/define/class/setter.rs:25-36 | core/engine/src/vm/opcode/define/class/setter.rs:83-94 — before extracting anything, compare `core/engine/src/vm/opcode/define/class/getter.rs` and `core/engine/src/vm/opcode/define/class/setter.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 6) core/engine/src/vm/opcode/define/class/getter.rs:40— core/engine/src/vm/opcode/define/class/getter.rs:40-50 | core/engine/src/vm/opcode/define/class/getter.rs:97-107 | core/engine/src/vm/opcode/define/class/getter.rs:204-214 | core/engine/src/vm/opcode/define/class/setter.rs:40-51 | core/engine/src/vm/opcode/define/class/setter.rs:98-109 | core/engine/src/vm/opcode/define/class/setter.rs:208-219 — before extracting anything, compare `core/engine/src/vm/opcode/define/class/getter.rs` and `core/engine/src/vm/opcode/define/class/setter.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–12 lines × 3) core/engine/src/builtins/array_buffer/utils.rs:468— core/engine/src/builtins/array_buffer/utils.rs:468-479 | core/engine/src/builtins/array_buffer/utils.rs:551-560 | core/engine/src/builtins/array_buffer/utils.rs:695-703 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–12 lines × 2) core/engine/src/builtins/typed_array/builtin.rs:435— core/engine/src/builtins/typed_array/builtin.rs:435-446 | core/engine/src/builtins/typed_array/builtin.rs:1330-1336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–12 lines × 2) core/engine/src/bytecompiler/mod.rs:793— core/engine/src/bytecompiler/mod.rs:793-801 | core/engine/src/bytecompiler/mod.rs:822-833 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 8) core/engine/src/vm/opcode/define/class/getter.rs:38— core/engine/src/vm/opcode/define/class/getter.rs:38-47 | core/engine/src/vm/opcode/define/class/getter.rs:95-104 | core/engine/src/vm/opcode/define/class/getter.rs:148-158 | core/engine/src/vm/opcode/define/class/getter.rs:202-211 | core/engine/src/vm/opcode/define/class/setter.rs:38-47 | core/engine/src/vm/opcode/define/class/setter.rs:96-105 | core/engine/src/vm/opcode/define/class/setter.rs:151-160 | core/engine/src/vm/opcode/define/class/setter.rs:206-215 — before extracting anything, compare `core/engine/src/vm/opcode/define/class/getter.rs` and `core/engine/src/vm/opcode/define/class/setter.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 5) core/engine/src/vm/opcode/define/class/setter.rs:43— core/engine/src/vm/opcode/define/class/setter.rs:43-53 | core/engine/src/vm/opcode/define/class/setter.rs:101-111 | core/engine/src/vm/opcode/define/class/setter.rs:211-221 | core/engine/src/vm/opcode/set/property.rs:326-335 | core/engine/src/vm/opcode/set/property.rs:371-380 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (8–11 lines × 2) core/engine/src/vm/opcode/push/class/private.rs:45— core/engine/src/vm/opcode/push/class/private.rs:45-55 | core/engine/src/vm/opcode/set/private.rs:110-117 — before extracting anything, compare `core/engine/src/vm/opcode/push/class/private.rs` and `core/engine/src/vm/opcode/set/private.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7–10 lines × 14) core/engine/src/builtins/temporal/plain_date/mod.rs:361— core/engine/src/builtins/temporal/plain_date/mod.rs:361-370 | core/engine/src/builtins/temporal/plain_date/mod.rs:392-398 | core/engine/src/builtins/temporal/plain_date/mod.rs:419-425 | core/engine/src/builtins/temporal/plain_date/mod.rs:446-452 | core/engine/src/builtins/temporal/plain_date/mod.rs:500-506 | core/engine/src/builtins/temporal/plain_date/mod.rs:525-531 | core/engine/src/builtins/temporal/plain_date/mod.rs:550-556 | core/engine/src/builtins/temporal/plain_date/mod.rs:575-581 | core/engine/src/builtins/temporal/plain_date/mod.rs:600-606 | core/engine/src/builtins/temporal/plain_date/mod.rs:625-631 | core/engine/src/builtins/temporal/plain_date/mod.rs:650-656 | core/engine/src/builtins/temporal/plain_date/mod.rs:675-681 | core/engine/src/builtins/temporal/plain_date/mod.rs:700-706 | core/engine/src/builtins/temporal/plain_date/mod.rs:725-731 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 7) core/engine/src/object/builtins/jsproxy.rs:414— core/engine/src/object/builtins/jsproxy.rs:414-423 | core/engine/src/object/builtins/jsproxy.rs:425-434 | core/engine/src/object/builtins/jsproxy.rs:444-453 | core/engine/src/object/builtins/jsproxy.rs:455-464 | core/engine/src/object/builtins/jsproxy.rs:474-483 | core/engine/src/object/builtins/jsproxy.rs:494-503 | core/engine/src/object/builtins/jsproxy.rs:513-522 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 5) core/engine/src/builtins/temporal/plain_date/mod.rs:1466— core/engine/src/builtins/temporal/plain_date/mod.rs:1466-1474 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:1823-1832 | core/engine/src/builtins/temporal/plain_month_day/mod.rs:569-578 | core/engine/src/builtins/temporal/plain_year_month/mod.rs:1067-1076 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:2194-2203 — `core/engine/src/builtins/temporal/plain_date/mod.rs` and `core/engine/src/builtins/temporal/plain_date_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 22 separate duplicated blocks between them, totalling at least 257 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–10 lines × 4) core/engine/src/builtins/temporal/plain_date_time/mod.rs:371— core/engine/src/builtins/temporal/plain_date_time/mod.rs:371-379 | core/engine/src/builtins/temporal/plain_date_time/mod.rs:382-391 | core/engine/src/builtins/temporal/plain_time/mod.rs:172-180 | core/engine/src/builtins/temporal/plain_time/mod.rs:183-191 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 184 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 15) core/engine/src/builtins/temporal/plain_date/mod.rs:359— core/engine/src/builtins/temporal/plain_date/mod.rs:359-367 | core/engine/src/builtins/temporal/plain_date/mod.rs:390-398 | core/engine/src/builtins/temporal/plain_date/mod.rs:417-425 | core/engine/src/builtins/temporal/plain_date/mod.rs:444-452 | core/engine/src/builtins/temporal/plain_date/mod.rs:471-479 | core/engine/src/builtins/temporal/plain_date/mod.rs:498-506 | core/engine/src/builtins/temporal/plain_date/mod.rs:523-531 | core/engine/src/builtins/temporal/plain_date/mod.rs:548-556 | core/engine/src/builtins/temporal/plain_date/mod.rs:573-581 | core/engine/src/builtins/temporal/plain_date/mod.rs:598-606 | core/engine/src/builtins/temporal/plain_date/mod.rs:623-631 | core/engine/src/builtins/temporal/plain_date/mod.rs:648-656 | core/engine/src/builtins/temporal/plain_date/mod.rs:673-681 | core/engine/src/builtins/temporal/plain_date/mod.rs:698-706 | core/engine/src/builtins/temporal/plain_date/mod.rs:723-731 — all 15 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 7) core/engine/src/builtins/date/mod.rs:496— core/engine/src/builtins/date/mod.rs:496-504 | core/engine/src/builtins/date/mod.rs:570-578 | core/engine/src/builtins/date/mod.rs:608-616 | core/engine/src/builtins/date/mod.rs:646-654 | core/engine/src/builtins/date/mod.rs:684-692 | core/engine/src/builtins/date/mod.rs:723-731 | core/engine/src/builtins/date/mod.rs:761-769 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–9 lines × 5) core/engine/src/builtins/typed_array/builtin.rs:658— core/engine/src/builtins/typed_array/builtin.rs:658-665 | core/engine/src/builtins/typed_array/builtin.rs:1018-1026 | core/engine/src/builtins/typed_array/builtin.rs:1425-1433 | core/engine/src/builtins/typed_array/builtin.rs:1500-1507 | core/engine/src/builtins/typed_array/builtin.rs:2214-2221 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–9 lines × 5) core/engine/src/vm/opcode/push/class/field.rs:79— core/engine/src/vm/opcode/push/class/field.rs:79-87 | core/engine/src/vm/opcode/push/class/private.rs:94-100 | core/engine/src/vm/opcode/push/class/private.rs:140-146 | core/engine/src/vm/opcode/set/private.rs:147-153 | core/engine/src/vm/opcode/set/private.rs:189-195 — before extracting anything, compare `core/engine/src/vm/opcode/push/class/private.rs` and `core/engine/src/vm/opcode/set/private.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7–9 lines × 2) core/engine/src/builtins/atomics/mod.rs:220— core/engine/src/builtins/atomics/mod.rs:220-226 | core/engine/src/builtins/atomics/mod.rs:272-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8–9 lines × 2) core/engine/src/builtins/temporal/plain_date_time/mod.rs:1426— core/engine/src/builtins/temporal/plain_date_time/mod.rs:1426-1434 | core/engine/src/builtins/temporal/zoneddatetime/mod.rs:1572-1579 — `core/engine/src/builtins/temporal/plain_date_time/mod.rs` and `core/engine/src/builtins/temporal/zoneddatetime/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 47 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 14) core/engine/src/builtins/date/mod.rs:454— core/engine/src/builtins/date/mod.rs:454-461 | core/engine/src/builtins/date/mod.rs:493-500 | core/engine/src/builtins/date/mod.rs:535-542 | core/engine/src/builtins/date/mod.rs:567-574 | core/engine/src/builtins/date/mod.rs:605-612 | core/engine/src/builtins/date/mod.rs:643-650 | core/engine/src/builtins/date/mod.rs:681-688 | core/engine/src/builtins/date/mod.rs:720-727 | core/engine/src/builtins/date/mod.rs:758-765 | core/engine/src/builtins/date/mod.rs:826-833 | core/engine/src/builtins/date/mod.rs:1406-1413 | core/engine/src/builtins/date/mod.rs:1543-1550 | core/engine/src/builtins/date/mod.rs:1684-1691 | core/engine/src/builtins/date/mod.rs:1722-1729 — all 14 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–8 lines × 4) core/engine/src/vm/opcode/define/own_property.rs:22— core/engine/src/vm/opcode/define/own_property.rs:22-27 | core/engine/src/vm/opcode/push/class/private.rs:30-35 | core/engine/src/vm/opcode/set/private.rs:61-68 | core/engine/src/vm/opcode/set/private.rs:98-103 — before extracting anything, compare `core/engine/src/vm/opcode/push/class/private.rs` and `core/engine/src/vm/opcode/set/private.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6–7 lines × 6) core/engine/src/vm/opcode/define/own_property.rs:21— core/engine/src/vm/opcode/define/own_property.rs:21-26 | core/engine/src/vm/opcode/push/class/private.rs:29-34 | core/engine/src/vm/opcode/set/private.rs:60-65 | core/engine/src/vm/opcode/set/private.rs:97-102 | core/engine/src/vm/opcode/set/property.rs:223-229 | core/engine/src/vm/opcode/set/property.rs:315-321 — before extracting anything, compare `core/engine/src/vm/opcode/push/class/private.rs` and `core/engine/src/vm/opcode/set/private.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) core/engine/src/builtins/typed_array/builtin.rs:874— core/engine/src/builtins/typed_array/builtin.rs:874-880 | core/engine/src/builtins/typed_array/builtin.rs:910-916 | core/engine/src/builtins/typed_array/builtin.rs:946-952 | core/engine/src/builtins/typed_array/builtin.rs:982-988 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 6) core/ast/src/scope_analyzer.rs:1930— core/ast/src/scope_analyzer.rs:1930-1934 | core/ast/src/scope_analyzer.rs:2400-2404 | core/engine/src/bytecompiler/declarations.rs:85-89 | core/engine/src/bytecompiler/declarations.rs:250-254 | core/engine/src/bytecompiler/declarations.rs:411-415 | core/engine/src/bytecompiler/declarations.rs:658-662 — before extracting anything, compare `core/ast/src/scope_analyzer.rs` and `core/engine/src/bytecompiler/declarations.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) core/engine/src/builtins/temporal/duration/mod.rs:199— core/engine/src/builtins/temporal/duration/mod.rs:199-203 | core/engine/src/builtins/temporal/plain_date/mod.rs:256-260 | core/engine/src/builtins/temporal/plain_time/mod.rs:136-140 — `core/engine/src/builtins/temporal/duration/mod.rs` and `core/engine/src/builtins/temporal/plain_time/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 66 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 6) core/engine/src/builtins/intl/collator/mod.rs:314— core/engine/src/builtins/intl/collator/mod.rs:314-324 | core/engine/src/builtins/intl/date_time_format/mod.rs:398-408 | core/engine/src/builtins/intl/list_format/mod.rs:207-217 | core/engine/src/builtins/intl/number_format/mod.rs:576-586 | core/engine/src/builtins/intl/plural_rules/mod.rs:277-287 | core/engine/src/builtins/intl/segmenter/mod.rs:240-250 — `core/engine/src/builtins/intl/date_time_format/mod.rs` and `core/engine/src/builtins/intl/list_format/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 42 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (12 lines × 7) core/engine/src/builtins/intl/locale/mod.rs:473— core/engine/src/builtins/intl/locale/mod.rs:473-484 | core/engine/src/builtins/intl/locale/mod.rs:503-514 | core/engine/src/builtins/intl/locale/mod.rs:533-544 | core/engine/src/builtins/intl/locale/mod.rs:563-574 | core/engine/src/builtins/intl/locale/mod.rs:628-639 | core/engine/src/builtins/intl/locale/mod.rs:684-698 | core/engine/src/builtins/intl/locale/mod.rs:715-729 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) core/engine/src/builtins/temporal/duration/mod.rs:1291— core/engine/src/builtins/temporal/duration/mod.rs:1291-1303 | core/engine/src/builtins/temporal/duration/mod.rs:1327-1339 | core/engine/src/builtins/temporal/duration/mod.rs:1351-1363 | core/engine/src/builtins/temporal/duration/mod.rs:1375-1387 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 5) core/engine/src/builtins/array/array_iterator.rs:43— core/engine/src/builtins/array/array_iterator.rs:43-50 | core/engine/src/builtins/map/map_iterator.rs:58-65 | core/engine/src/builtins/regexp/regexp_string_iterator.rs:46-53 | core/engine/src/builtins/set/set_iterator.rs:58-65 | core/engine/src/builtins/string/string_iterator.rs:37-44 — 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.
Duplicated block (6 lines × 6) core/engine/src/object/builtins/jsproxy.rs:399— core/engine/src/object/builtins/jsproxy.rs:399-404 | core/engine/src/object/builtins/jsproxy.rs:407-413 | core/engine/src/object/builtins/jsproxy.rs:438-443 | core/engine/src/object/builtins/jsproxy.rs:468-473 | core/engine/src/object/builtins/jsproxy.rs:487-493 | core/engine/src/object/builtins/jsproxy.rs:507-512 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) cli/src/debug/limits.rs:68— cli/src/debug/limits.rs:68-73 | cli/src/debug/limits.rs:79-84 | cli/src/debug/limits.rs:90-95 | cli/src/debug/limits.rs:100-105 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 7) core/engine/src/builtins/error/aggregate.rs:31— core/engine/src/builtins/error/aggregate.rs:31-38 | core/engine/src/builtins/error/eval.rs:33-40 | core/engine/src/builtins/error/range.rs:31-38 | core/engine/src/builtins/error/reference.rs:30-37 | core/engine/src/builtins/error/syntax.rs:33-40 | core/engine/src/builtins/error/type.rs:39-46 | core/engine/src/builtins/error/uri.rs:32-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 151 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
P12 · CI test-gate honesty· Coverage collected but not gated · ×1
Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
Swallowed exception (caught, then discarded) core/runtime/assets/harness.js:54— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Orphaned file core/parser/src/parser/function/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/gc/src/trace.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/statement/declaration/export.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/statement/declaration/import.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/expression/assignment/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/punctuator/tests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/keyword/tests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/interop/into_js_arguments.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/value/conversions/nullable/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/function/ordinary_function.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/interop/into_js_function_impls.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/cursor/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/lexer/template.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/value/conversions/try_into_js.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/function/async_function.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/function/async_generator.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/cursor/buffered_lexer/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/statement/declaration/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/function/generator.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/punctuator/mod.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/builtins/weak_map/tests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/expression/assignment/arrow_function.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/ast/src/declaration/import.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/parser/src/parser/expression/update.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/engine/src/bytecompiler/expression/object_literal.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate core/parser/src/parser/expression/primary/async_function_expression/mod.rs:95— `(cursor.strict() || body.strict()) && params.has_duplicates()` appears character-identically in 5 files — core/parser/src/parser/expression/primary/async_function_expression/mod.rs, core/parser/src/parser/expression/primary/async_generator_expression/mod.rs, core/parser/src/parser/expression/primary/function_expression/mod.rs, core/parser/src/parser/expression/primary/generator_expression/mod.rs. 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 core/engine/src/builtins/function/mod.rs:594— `body.strict() && !parameters.is_simple()` appears character-identically in 2 files — core/engine/src/builtins/function/mod.rs, core/parser/src/parser/expression/assignment/mod.rs. 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 core/engine/src/builtins/temporal/plain_date/mod.rs:1423— `calendar.kind() == AnyCalendarKind::Iso || calendar.kind() == AnyCalendarKind::Chinese || calendar.kind() == AnyCalendarKind::Dangi` appears character-identically in 4 files — core/engine/src/builtins/temporal/plain_date/mod.rs, core/engine/src/builtins/temporal/plain_date_time/mod.rs, core/engine/src/builtins/temporal/plain_year_month/mod.rs, core/engine/src/builtins/temporal/zoneddatetime/mod.rs. 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 core/parser/src/parser/statement/if_stm/mod.rs:77— `cfg!(not(feature = "annex-b")) || strict` appears character-identically in 2 files — core/parser/src/parser/statement/if_stm/mod.rs, core/parser/src/parser/statement/labelled_stm/mod.rs. 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 core/engine/src/vm/opcode/get/name.rs:73— `slot.attributes.has_get() && result.is_object()` appears character-identically in 2 files — core/engine/src/vm/opcode/get/name.rs, core/engine/src/vm/opcode/get/property.rs. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: core/wintertc/src/lib.rs, core/engine/src/object/builtins/jsregexp.rs, core/wintertc/src/timers/mod.rs, core/wintertc/src/base64/mod.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: core/macros/src/utils.rs, core/string/src/vtable/sequence.rs, core/string/src/display.rs, core/string/src/vtable/slice.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 13 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (24 single-owned of 520 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 520 of the 662 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (1 file(s)), anonymized user #7 (1 file(s)), anonymized user #8 (1 file(s)) (+7 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: core/engine/src/builtins/typed_array/builtin_uint8.rs, REDACTED, core/runtime/src/process/tests.rs, core/runtime/src/process/mod.rs, core/engine/src/builtins/proxy/tests.rs, core/engine/src/builtins/weak_set/tests.rs, core/runtime/src/url/tests.rs, core/engine/src/builtins/bigint/tests.rs (+8 more).
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 16 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. The most over is `core/engine` (136146 LoC, 338 module-visible types across 76 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 85 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: core/parser/src/parser/function/mod.rs, core/gc/src/trace.rs, core/parser/src/parser/statement/declaration/export.rs, core/parser/src/parser/statement/declaration/import.rs, core/parser/src/parser/expression/assignment/mod.rs, core/ast/src/punctuator/tests.rs, core/ast/src/keyword/tests.rs, core/engine/src/interop/into_js_arguments.rs (and 77 more) (90 orphaned of 521 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 521 of the 662 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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.
README/code drift tests/fuzz/README.md:5— tests/fuzz/README.md links to `fuzz/fuzz_targets/common.rs`, but `tests/fuzz/fuzz/fuzz_targets/common.rs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cli`.
Subsumed condition operand core/engine/src/module/loader/mod.rs:71— `short_path.starts_with("..")` can never decide this `||` — every value satisfying `short_path.starts_with("..")` also satisfies `short_path.starts_with(".")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Outdated: fixed_decimal — `fixed_decimal` is locked at 0.7.2 but 0.7.3 is the current stable release on crates.io, and it already satisfies the `"0.7.2"` requirement declared in core/engine/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fixed_decimal` and commit the updated REDACTED.
Outdated: icu_locale_core — `icu_locale_core` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3.0"` requirement declared in core/gc/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_locale_core` and commit the updated REDACTED.
Outdated: icu_provider — `icu_provider` is locked at 2.3.1 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3.1"` requirement declared in core/engine/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icu_provider` and commit the updated REDACTED.
Outdated: mimalloc-safe — `mimalloc-safe` is locked at 0.1.67 but 0.1.68 is the current stable release on crates.io, and it already satisfies the `"0.1.65"` requirement declared in cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mimalloc-safe` and commit the updated REDACTED.
Outdated: tinystr — `tinystr` is locked at 0.8.4 but 0.8.5 is the current stable release on crates.io, and it already satisfies the `"0.8.4"` requirement declared in core/engine/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tinystr` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.3 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.53.1"` requirement declared in examples/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: toml — `toml` is locked at 1.1.6+spec-1.1.0 but 1.1.8+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.1.4"` requirement declared in tests/tester/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml` and commit the updated REDACTED.
Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.127 but 0.2.129 is the current stable release on crates.io, and it already satisfies the `"0.2.127"` requirement declared in ffi/wasm/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated REDACTED.
Outdated: yoke — `yoke` is locked at 0.8.3 but 0.8.4 is the current stable release on crates.io, and it already satisfies the `"0.8.3"` requirement declared in core/engine/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p yoke` and commit the updated REDACTED.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17d7a-c23b-76be-8bc5-26d5f5b7a539 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 7 · Warnings: 1157 · Recommendations: 104 · Info: 9 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 27-10-2026 @ 13:09 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.