Public report of fabulous-dev/Fabulous, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 18:46 UTC · Survey ID cd_f43e2e61410b432c92b33d8cd552c11d
fabulous-dev/Fabulous
Measured 26 October 2026, 18:40 UTC, at code version def6f63
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.
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 55,914 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Security and Compliance, 45
Findings by how serious they are
74 critical309 serious15 minor
5 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
26 October 2026, 18:40 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 ▸
65of 65 dimensions measured by tools.
382of 398 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
65dimensions across 6 lenses, read from 55,914 lines of product code in 2 projects.
fabulous-dev/Fabulous falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 56 out of 100 and is rated Adequate, and 73 of its 74 critical findings are security problems.
Security and Compliance, at 45, is the weakest lens and counts most in the score. The best first step is fixing the six unsafe steps in the pipeline, worth about 4 points. Replacing the three passwords or keys found in the code's history comes next, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 65.
Fifty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six pipeline steps let untrusted code run, and three passwords or keys are open to anyone who can read the repository. Pinning each tool to an exact version, fixing the unsafe pipeline steps and replacing each exposed password or key would close these risks. Correcting the flagged pipeline settings would fix the three weaknesses in the build pipeline's configuration, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The set of compiler warnings switched off in a project needs turning back on in the build file.
The product code is 55,914 lines, about €71,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.
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: 9 findings
These 9 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one.
Code Coverage · No test project references NewApp templates/maui/content/blank/NewApp.fsproj
Code Coverage · No test project references NewApp templates/avalonia/content/blank/NewApp.fsproj
Code Coverage · No test project references NewApp templates/avalonia/content/desktop/NewApp.fsproj
Code Coverage · No test project references NewApp.Android templates/avalonia/content/multi/NewApp.Android/NewApp.Android.fsproj
Code Coverage · No test project references NewApp templates/avalonia/content/multi/NewApp/NewApp.fsproj
Code Coverage · No test project references NewApp.Browser templates/avalonia/content/multi/NewApp.Browser/NewApp.Browser.fsproj
Code Coverage · No test project references NewApp.Desktop templates/avalonia/content/multi/NewApp.Desktop/NewApp.Desktop.fsproj
Code Coverage · No test project references NewApp.iOS templates/avalonia/content/multi/NewApp.iOS/NewApp.iOS.fsproj
Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €71,000 · Estimate
Cost to rebuild
€24,000 to €120,000, for 393 to 1,247 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 56. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 55,914 lines of product code
Comment lines
The estimate prices 55,905 lines. Comment lines count towards the size of 55,914 lines but aren't priced as work.
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.
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 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3).
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €71,000 to build again, about 0.5 person-years of work. Its weakest lens is Security and Compliance, at 45 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST). Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 6 Static Analysis (SAST) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
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.
895 modules, with 1292 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 855 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.
ScalarAttributeDefinitions uses Fabulous, so a change to Fabulous can break ScalarAttributeDefinitions, while a change to ScalarAttributeDefinitions can't break Fabulous.
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→3 WidgetCollectionAttributeDefinitions uses Fabulouspart of a loop✕
Connections
1 pair of types, where a type in WidgetCollectionAttributeDefinitions uses a type in Fabulous.
WidgetCollectionAttributeDefinitions uses Fabulous, so a change to Fabulous can break WidgetCollectionAttributeDefinitions, while a change to WidgetCollectionAttributeDefinitions can't break Fabulous.
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.
Fabulous uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Fabulous, while a change to Fabulous can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Fabulous uses a module listed above it, which is the healthy direction.
Fabulous uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Fabulous, while a change to Fabulous can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Fabulous uses a module listed above it, which is the healthy direction.
Avalonia.ViewHelpers uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.ViewHelpers, while a change to Avalonia.ViewHelpers can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.ViewHelpers uses a module listed above it, which is the healthy direction.
Avalonia.ViewHelpers uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.ViewHelpers, while a change to Avalonia.ViewHelpers can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.ViewHelpers uses a module listed above it, which is the healthy direction.
Avalonia.ViewHelpers uses Fabulous, so a change to Fabulous can break Avalonia.ViewHelpers, while a change to Avalonia.ViewHelpers can't break Fabulous.
Position
Below the diagonal: Avalonia.ViewHelpers uses a module listed above it, which is the healthy direction.
Maui.Cell uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.Cell, while a change to Maui.Cell can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.Cell uses a module listed above it, which is the healthy direction.
Maui.Cell uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.Cell, while a change to Maui.Cell can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.Cell uses a module listed above it, which is the healthy direction.
Memo uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Memo, while a change to Memo can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Memo uses a module listed above it, which is the healthy direction.
WidgetAttributeDefinitions uses Fabulous, so a change to Fabulous can break WidgetAttributeDefinitions, while a change to WidgetAttributeDefinitions can't break Fabulous.
Position
Below the diagonal: WidgetAttributeDefinitions uses a module listed above it, which is the healthy direction.
AttributeDefinitionStore uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break AttributeDefinitionStore, while a change to AttributeDefinitionStore can't break ScalarAttributeDefinitions.
Position
Below the diagonal: AttributeDefinitionStore uses a module listed above it, which is the healthy direction.
AttributeDefinitionStore uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break AttributeDefinitionStore, while a change to AttributeDefinitionStore can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: AttributeDefinitionStore uses a module listed above it, which is the healthy direction.
AttributeDefinitionStore uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break AttributeDefinitionStore, while a change to AttributeDefinitionStore can't break WidgetAttributeDefinitions.
Position
Below the diagonal: AttributeDefinitionStore uses a module listed above it, which is the healthy direction.
Attributes uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Attributes, while a change to Attributes can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
Attributes uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Attributes, while a change to Attributes can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
Attributes uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Attributes, while a change to Attributes can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Attributes uses a module listed above it, which is the healthy direction.
548 pairs of types, where a type in Avalonia uses a type in Fabulous. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Avalonia.Application uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.Application, while a change to Avalonia.Application can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.Application uses a module listed above it, which is the healthy direction.
Avalonia.Application uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.Application, while a change to Avalonia.Application can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.Application uses a module listed above it, which is the healthy direction.
Avalonia.Application uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.Application, while a change to Avalonia.Application can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.Application uses a module listed above it, which is the healthy direction.
Avalonia.DataGrid uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.DataGrid, while a change to Avalonia.DataGrid can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.DataGrid uses a module listed above it, which is the healthy direction.
Avalonia.DataGrid uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.DataGrid, while a change to Avalonia.DataGrid can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.DataGrid uses a module listed above it, which is the healthy direction.
Avalonia.DataGrid uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.DataGrid, while a change to Avalonia.DataGrid can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.DataGrid uses a module listed above it, which is the healthy direction.
Avalonia.DrawingGroup uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.DrawingGroup, while a change to Avalonia.DrawingGroup can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.DrawingGroup uses a module listed above it, which is the healthy direction.
Avalonia.DrawingGroup uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.DrawingGroup, while a change to Avalonia.DrawingGroup can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.DrawingGroup uses a module listed above it, which is the healthy direction.
Avalonia.DrawingGroup uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.DrawingGroup, while a change to Avalonia.DrawingGroup can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.DrawingGroup uses a module listed above it, which is the healthy direction.
Avalonia.Panel uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.Panel, while a change to Avalonia.Panel can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.Panel uses a module listed above it, which is the healthy direction.
Avalonia.Panel uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.Panel, while a change to Avalonia.Panel can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.Panel uses a module listed above it, which is the healthy direction.
Avalonia.Panel uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.Panel, while a change to Avalonia.Panel can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.Panel uses a module listed above it, which is the healthy direction.
Avalonia.TemplatedControl uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.TemplatedControl, while a change to Avalonia.TemplatedControl can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.TemplatedControl uses a module listed above it, which is the healthy direction.
Avalonia.TemplatedControl uses Fabulous, so a change to Fabulous can break Avalonia.TemplatedControl, while a change to Avalonia.TemplatedControl can't break Fabulous.
Position
Below the diagonal: Avalonia.TemplatedControl uses a module listed above it, which is the healthy direction.
Avalonia.TemplatedControl uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.TemplatedControl, while a change to Avalonia.TemplatedControl can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.TemplatedControl uses a module listed above it, which is the healthy direction.
Avalonia.TextBlock uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.TextBlock, while a change to Avalonia.TextBlock can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.TextBlock uses a module listed above it, which is the healthy direction.
Avalonia.TextBlock uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.TextBlock, while a change to Avalonia.TextBlock can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.TextBlock uses a module listed above it, which is the healthy direction.
Avalonia.TextBlock uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.TextBlock, while a change to Avalonia.TextBlock can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.TextBlock uses a module listed above it, which is the healthy direction.
Avalonia.ToggleSwitch uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.ToggleSwitch, while a change to Avalonia.ToggleSwitch can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.ToggleSwitch uses a module listed above it, which is the healthy direction.
Avalonia.ToggleSwitch uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.ToggleSwitch, while a change to Avalonia.ToggleSwitch can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.ToggleSwitch uses a module listed above it, which is the healthy direction.
Avalonia.ToggleSwitch uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.ToggleSwitch, while a change to Avalonia.ToggleSwitch can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.ToggleSwitch uses a module listed above it, which is the healthy direction.
Maui.Application uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.Application, while a change to Maui.Application can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.Application uses a module listed above it, which is the healthy direction.
Maui.Application uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.Application, while a change to Maui.Application can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.Application uses a module listed above it, which is the healthy direction.
Maui.Application uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.Application, while a change to Maui.Application can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.Application uses a module listed above it, which is the healthy direction.
Maui.NavigationPage uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.NavigationPage, while a change to Maui.NavigationPage can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.NavigationPage uses a module listed above it, which is the healthy direction.
Maui.NavigationPage uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.NavigationPage, while a change to Maui.NavigationPage can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.NavigationPage uses a module listed above it, which is the healthy direction.
Maui.NavigationPage uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.NavigationPage, while a change to Maui.NavigationPage can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.NavigationPage uses a module listed above it, which is the healthy direction.
Avalonia.Attributes uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.Attributes, while a change to Avalonia.Attributes can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.Attributes uses a module listed above it, which is the healthy direction.
Avalonia.Attributes uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.Attributes, while a change to Avalonia.Attributes can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.Attributes uses a module listed above it, which is the healthy direction.
Avalonia.Attributes uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.Attributes, while a change to Avalonia.Attributes can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.Attributes uses a module listed above it, which is the healthy direction.
Avalonia.Image uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.Image, while a change to Avalonia.Image can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.Image uses a module listed above it, which is the healthy direction.
Avalonia.Image uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.Image, while a change to Avalonia.Image can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.Image uses a module listed above it, which is the healthy direction.
Avalonia.ImageDrawing uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.ImageDrawing, while a change to Avalonia.ImageDrawing can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.ImageDrawing uses a module listed above it, which is the healthy direction.
Avalonia.ImageDrawing uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.ImageDrawing, while a change to Avalonia.ImageDrawing can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.ImageDrawing uses a module listed above it, which is the healthy direction.
Avalonia.ImageDrawing uses Avalonia, so a change to Avalonia can break Avalonia.ImageDrawing, while a change to Avalonia.ImageDrawing can't break Avalonia.
Position
Below the diagonal: Avalonia.ImageDrawing uses a module listed above it, which is the healthy direction.
Avalonia.ItemsControl uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.ItemsControl, while a change to Avalonia.ItemsControl can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.ItemsControl uses a module listed above it, which is the healthy direction.
Avalonia.ItemsControl uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Avalonia.ItemsControl, while a change to Avalonia.ItemsControl can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Avalonia.ItemsControl uses a module listed above it, which is the healthy direction.
Avalonia.ItemsControl uses Fabulous, so a change to Fabulous can break Avalonia.ItemsControl, while a change to Avalonia.ItemsControl can't break Fabulous.
Position
Below the diagonal: Avalonia.ItemsControl uses a module listed above it, which is the healthy direction.
Avalonia.ItemsControl uses Avalonia, so a change to Avalonia can break Avalonia.ItemsControl, while a change to Avalonia.ItemsControl can't break Avalonia.
Position
Below the diagonal: Avalonia.ItemsControl uses a module listed above it, which is the healthy direction.
Avalonia.MvuCalendarDatePicker uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.MvuCalendarDatePicker, while a change to Avalonia.MvuCalendarDatePicker can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.MvuCalendarDatePicker uses a module listed above it, which is the healthy direction.
Avalonia.MvuCalendarDatePicker uses Fabulous, so a change to Fabulous can break Avalonia.MvuCalendarDatePicker, while a change to Avalonia.MvuCalendarDatePicker can't break Fabulous.
Position
Below the diagonal: Avalonia.MvuCalendarDatePicker uses a module listed above it, which is the healthy direction.
Avalonia.MvuCalendarDatePicker uses Avalonia, so a change to Avalonia can break Avalonia.MvuCalendarDatePicker, while a change to Avalonia.MvuCalendarDatePicker can't break Avalonia.
Position
Below the diagonal: Avalonia.MvuCalendarDatePicker uses a module listed above it, which is the healthy direction.
Avalonia.NativeMenuItem uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.NativeMenuItem, while a change to Avalonia.NativeMenuItem can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.NativeMenuItem uses a module listed above it, which is the healthy direction.
Avalonia.NativeMenuItem uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.NativeMenuItem, while a change to Avalonia.NativeMenuItem can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.NativeMenuItem uses a module listed above it, which is the healthy direction.
Avalonia.NativeMenuItem uses Avalonia, so a change to Avalonia can break Avalonia.NativeMenuItem, while a change to Avalonia.NativeMenuItem can't break Avalonia.
Position
Below the diagonal: Avalonia.NativeMenuItem uses a module listed above it, which is the healthy direction.
Avalonia.TrayIcon uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.TrayIcon, while a change to Avalonia.TrayIcon can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.TrayIcon uses a module listed above it, which is the healthy direction.
Avalonia.TrayIcon uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Avalonia.TrayIcon, while a change to Avalonia.TrayIcon can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Avalonia.TrayIcon uses a module listed above it, which is the healthy direction.
Avalonia.WidgetHelpers uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Avalonia.WidgetHelpers, while a change to Avalonia.WidgetHelpers can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Avalonia.WidgetHelpers uses a module listed above it, which is the healthy direction.
Avalonia.WidgetHelpers uses Fabulous, so a change to Fabulous can break Avalonia.WidgetHelpers, while a change to Avalonia.WidgetHelpers can't break Fabulous.
Position
Below the diagonal: Avalonia.WidgetHelpers uses a module listed above it, which is the healthy direction.
Avalonia.WidgetHelpers uses Avalonia, so a change to Avalonia can break Avalonia.WidgetHelpers, while a change to Avalonia.WidgetHelpers can't break Avalonia.
Position
Below the diagonal: Avalonia.WidgetHelpers uses a module listed above it, which is the healthy direction.
Maui.Attributes uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.Attributes, while a change to Maui.Attributes can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.Attributes uses a module listed above it, which is the healthy direction.
Maui.Attributes uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.Attributes, while a change to Maui.Attributes can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.Attributes uses a module listed above it, which is the healthy direction.
Maui.Button uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.Button, while a change to Maui.Button can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.Button uses a module listed above it, which is the healthy direction.
Maui.CheckBox uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.CheckBox, while a change to Maui.CheckBox can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.CheckBox uses a module listed above it, which is the healthy direction.
Maui.CollectionView uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.CollectionView, while a change to Maui.CollectionView can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.CollectionView uses a module listed above it, which is the healthy direction.
Maui.CollectionView uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.CollectionView, while a change to Maui.CollectionView can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.CollectionView uses a module listed above it, which is the healthy direction.
Maui.EntryCell uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.EntryCell, while a change to Maui.EntryCell can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.EntryCell uses a module listed above it, which is the healthy direction.
Maui.ItemsView uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.ItemsView, while a change to Maui.ItemsView can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.ItemsView uses a module listed above it, which is the healthy direction.
Maui.ItemsView uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.ItemsView, while a change to Maui.ItemsView can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.ItemsView uses a module listed above it, which is the healthy direction.
Maui.ListView uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.ListView, while a change to Maui.ListView can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.ListView uses a module listed above it, which is the healthy direction.
Maui.ListView uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.ListView, while a change to Maui.ListView can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.ListView uses a module listed above it, which is the healthy direction.
Maui.MultiPageOfPage uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.MultiPageOfPage, while a change to Maui.MultiPageOfPage can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.MultiPageOfPage uses a module listed above it, which is the healthy direction.
Maui.MultiPageOfPage uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.MultiPageOfPage, while a change to Maui.MultiPageOfPage can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.MultiPageOfPage uses a module listed above it, which is the healthy direction.
Maui.MultiPageOfPage uses Fabulous, so a change to Fabulous can break Maui.MultiPageOfPage, while a change to Maui.MultiPageOfPage can't break Fabulous.
Position
Below the diagonal: Maui.MultiPageOfPage uses a module listed above it, which is the healthy direction.
Maui.Page uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.Page, while a change to Maui.Page can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.Page uses a module listed above it, which is the healthy direction.
Maui.Page uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.Page, while a change to Maui.Page can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.Page uses a module listed above it, which is the healthy direction.
Maui.RadioButton uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.RadioButton, while a change to Maui.RadioButton can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.RadioButton uses a module listed above it, which is the healthy direction.
Maui.RadioButton uses WidgetAttributeDefinitions, so a change to WidgetAttributeDefinitions can break Maui.RadioButton, while a change to Maui.RadioButton can't break WidgetAttributeDefinitions.
Position
Below the diagonal: Maui.RadioButton uses a module listed above it, which is the healthy direction.
Maui.WidgetHelpers uses ScalarAttributeDefinitions, so a change to ScalarAttributeDefinitions can break Maui.WidgetHelpers, while a change to Maui.WidgetHelpers can't break ScalarAttributeDefinitions.
Position
Below the diagonal: Maui.WidgetHelpers uses a module listed above it, which is the healthy direction.
Maui.WidgetHelpers uses WidgetCollectionAttributeDefinitions, so a change to WidgetCollectionAttributeDefinitions can break Maui.WidgetHelpers, while a change to Maui.WidgetHelpers can't break WidgetCollectionAttributeDefinitions.
Position
Below the diagonal: Maui.WidgetHelpers uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
77
High / Critical
A03:2025 — Software Supply Chain Failures
9
Medium
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Begin by resolving the six static analysis findings related to watchdog-network-fetched values in the Avalonia and MAUI template verification workflows, followed by addressing the three secret history issues in REDACTED and REDACTED. Next, fix the two supply-chain provenance warnings regarding missing permissions blocks in the same template workflows and clear the three environment secret findings in REDACTED. Finally, ensure that every release requires explicit human approval or is published as a draft to prevent bad builds from being downloaded.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3).
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Code Duplication: Members sharing a duplicated core (7 members, 50+ identical tokens)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 74
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 — 309
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 — 15
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
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. 65 of 65 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 — 65 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, 382 of 398 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.
D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: maui-tizen [src/maui/Fabulous.MauiControls.Maps/Fabu….
D15 Churn × Complexity Hotspots — 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For src/neutral/Fabulous.Core/Array.fs, samples/avalonia/Gallery/App.fs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
D17 Explicit Debt — 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. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'src/neutral/Fabulous.Core/Fabulous.Core.fsproj' because the file extension '.fsproj' is not associated with a language.
D17 Explicit Debt — 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. The 1 deducted marker(s) and the 0.4/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (55,074 lines, 99% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 552 commits in the last 90 days, yet 207 of 232 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
M3 Folder & project structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
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.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/maui/Fabulous.MauiControls/Fabulous.MauiControls.fsproj, src/maui/Fabulous.MauiControls.Tests/Fabulous.MauiControls.Tests.fsproj, src/maui/Fabulous.MauiControls.Maps/Fabulous.MauiControls.Maps.fsproj, src/maui/Fabulous.MauiControls.MediaElement/Fabulous.MauiControls.MediaElement.fsproj, templates/maui/content/blank/NewApp.fsproj and 7 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations: 1 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was validate-packages.validate_package at 24. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being StackArray3.combine at 22 — they are counted neither in the figure above nor in this dimension's score.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with validate-packages.validate_package (cyclomatic 24), ScalarChangesEnumerator.MoveNext (cyclomatic 21), StackList`1.replace (cyclomatic 19). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with ScalarChangesEnumerator.MoveNext (cognitive 47), validate-doc-links.validate (cognitive 45), WidgetChangesEnumerator.MoveNext (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 9 together lifts Cognitive Complexity from 8.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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 Classes10.0 / 10Exemplary✓ 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.
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.
249 duplicated block group(s) detected. A further 12 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 196 of the 261 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 109 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 24 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with Program.fs (15), App.fs (2), ReversibleStackPanel.fs. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 10 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with DrawingPage.fs (2), UniformGridPage.fs (2), RadioButton.Components.fs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with AppDelegate.fs (2), UniformGridPage.fs (2), _Visual.Components.fs. — One of this dimension's main actionable groups (10 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 · Coupling10.0 / 10Exemplary✓ 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.
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 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ImplicitCanvasAnimationsPage.fs, OpenGLPage.fs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No test project references Fabulous.Avalonia.ColorPickersrc/avalonia/Fabulous.Avalonia.ColorPicker/Fabulous.Avalonia.ColorPicker.fsproj
No test project references Fabulous.Avalonia.DataGridsrc/avalonia/Fabulous.Avalonia.DataGrid/Fabulous.Avalonia.DataGrid.fsproj
No test project references Fabulous.MauiControls.Mapssrc/maui/Fabulous.MauiControls.Maps/Fabulous.MauiControls.Maps.fsproj
No test project references Fabulous.Avalonia.Labssrc/avalonia/Fabulous.Avalonia.Labs/Fabulous.Avalonia.Labs.fsproj
No test project references Fabulous.Avalonia.TreeDataGridsrc/avalonia/Fabulous.Avalonia.TreeDataGrid/Fabulous.Avalonia.TreeDataGrid.fsproj
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 No test project references Fabulous.Avalonia.ColorPicker finding(s) in Code Coverage — start with Fabulous.Avalonia.ColorPicker.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references Fabulous.Avalonia.DataGrid finding(s) in Code Coverage — start with Fabulous.Avalonia.DataGrid.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references Fabulous.MauiControls.Maps finding(s) in Code Coverage — start with Fabulous.MauiControls.Maps.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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 130 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 44 direct `PackageReference`(s), and 125 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.fs, Array.fs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.3 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/maui/Fabulous.MauiControls/Views/Collections/ListView.fs. Counted over 219 of the 535 production source files in this repository: 303 are under the ~2,400-byte size floor this dimension measures over, and the remaining 13 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ 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.
1 deducted debt markers + unmeasured dead symbols across 424 LoC in the .NET projects (0.4/KLoC) → score 9.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (99% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with FSharp.Maui.WinUICompat.csproj. — One of this dimension's main actionable groups (1 issue-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. 169 document(s) read across 2 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.
1 of 2 projects 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: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
95 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
78 finding(s): 0 critical, 71 high, 7 medium, 0 low. 59 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 7 file(s) — `eng/ci/capture-avalonia-samples.sh` (line 43, line 72), `eng/ci/capture-maui-android-samples.sh` (line 120), `REDACTED`, `website/themes/fabulous-theme/layouts/404.html` (lines 1–3, line 15), `website/themes/fabulous-theme/layouts/partials/footer.html` (line 1), … (+2 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 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 59 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (59 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with SelectableTextBlock.fs, Attributes.fs, Primitives.fs. — One of this dimension's main actionable groups (4 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 66 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.
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.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. 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 · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/maui/FSharp.Maui.WinUICompat/Platforms/Windows/App.xaml.cs:22
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`CreateMauiApp` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/maui/FSharp.Maui.WinUICompat/Platforms/Windows/App.xaml.cs:22
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 1 of 2 project(s) that lack one — worth up to 1 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
src/maui/Fabulous.MauiControls.MediaElement/README.md links to `Fabulous_MauiControls_MediaElement_Demo.gif`, but `src/maui/Fabulous.MauiControls.MediaElement/Fabulous_MauiControls_MediaElement_Demo.gif` 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. — src/maui/Fabulous.MauiControls.MediaElement/README.md:5
What to do
Reconcile the README with reality: src/maui/Fabulous.MauiControls.MediaElement/README.md links to `Fabulous_MauiControls_MediaElement_Demo.gif`, but `src/maui/Fabulous.MauiControls.MediaElement/Fabulous_MauiControls_MediaElement_Demo.gif` 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 & versioning6.0 / 10Adequate✓ Tool-verified
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.
What to do
Make types internal by default and expose only the deliberate public API — even for a small library, every public type is a stability contract.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 282581 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
What to do
On hot paths, prefer Span<T>/ReadOnlySpan<T>, ArrayPool<T>, stackalloc and ValueTask to cut the allocations those paths would otherwise make.
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 an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). 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.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. 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 `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items 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.
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?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~1.2 `!` suppressions per 1k syntax nodes — 4 suppression(s) across the 3314 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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.
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 — 55 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 user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — ~2674 lines of test source are present (.fs) 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.
D12 Dependency Hygiene — Dependency hygiene not measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, .py, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D21 Naming Consistency — Naming consistency is measured on C# only; F#, Python not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed F# surface was not measured.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D24 Comment Value — D24 reads C# and Visual Basic comments only; comments in this repository's .fs, .py source were not judged.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
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.
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 247 value object(s); 48 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no async method does work a token could cancel
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
NoWarnInCsproj src/maui/FSharp.Maui.WinUICompat/FSharp.Maui.WinUICompat.csproj:17— CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
Duplicated block (9 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Panels/ReversibleStackPanel.fs:30— src/avalonia/Fabulous.Avalonia/Views/Panels/ReversibleStackPanel.fs:30-38 | src/avalonia/Fabulous.Avalonia/Views/Panels/ReversibleStackPanel.fs:48-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 (9 lines × 2) src/avalonia/Fabulous.Avalonia/Widgets.fs:19— src/avalonia/Fabulous.Avalonia/Widgets.fs:19-27 | src/maui/Fabulous.MauiControls/Widgets.fs:19-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Widgets.fs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/avalonia/Fabulous.Avalonia/_Element.fs:16— src/avalonia/Fabulous.Avalonia/_Element.fs:16-24 | src/maui/Fabulous.MauiControls/Views/_Element.fs:28-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/_Element.fs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) samples/avalonia/Component/TicTacToe/App.fs:134— samples/avalonia/Component/TicTacToe/App.fs:134-142 | samples/avalonia/Mvu/TicTacToe/App.fs:221-229 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) samples/avalonia/Component/TicTacToe/App.fs:203— samples/avalonia/Component/TicTacToe/App.fs:203-211 | samples/avalonia/Mvu/TicTacToe/App.fs:137-145 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) samples/avalonia/Gallery/Pages/CanvasPage.fs:142— samples/avalonia/Gallery/Pages/CanvasPage.fs:142-150 | samples/maui/Gallery/Samples/Shapes.fs:79-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/CanvasPage.fs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/CanvasPage.fs:138` calls `fill`, `SolidColorBrush`, `canvasLeft` and `samples/maui/Gallery/Samples/Shapes.fs:77` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) samples/avalonia/Gallery/Pages/RenderTransformPage.fs:13— samples/avalonia/Gallery/Pages/RenderTransformPage.fs:13-21 | samples/avalonia/Gallery/Pages/SpringAnimationsPage.fs:13-21 — 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) samples/maui/Calculator/Platforms/MacCatalyst/Program.fs:1— samples/maui/Calculator/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Calculator/Platforms/iOS/Program.fs:1-9 — `samples/maui/Calculator/Platforms/MacCatalyst/Program.fs` and `samples/maui/Calculator/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Components/HelloComponent/Platforms/MacCatalyst/Program.fs:1— samples/maui/Components/HelloComponent/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Components/HelloComponent/Platforms/iOS/Program.fs:1-9 — `samples/maui/Components/HelloComponent/Platforms/MacCatalyst/Program.fs` and `samples/maui/Components/HelloComponent/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Components/HelloComponent/Platforms/Windows/Main.fs:1— samples/maui/Components/HelloComponent/Platforms/Windows/Main.fs:1-9 | samples/maui/HelloWorld/Platforms/Windows/Main.fs:1-9 — before extracting anything, compare `samples/maui/Components/HelloComponent/Platforms/Windows/Main.fs` and `samples/maui/HelloWorld/Platforms/Windows/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) samples/maui/Components/MultipleMvus/Platforms/MacCatalyst/Program.fs:1— samples/maui/Components/MultipleMvus/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Components/MultipleMvus/Platforms/iOS/Program.fs:1-9 — `samples/maui/Components/MultipleMvus/Platforms/MacCatalyst/Program.fs` and `samples/maui/Components/MultipleMvus/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Components/MvuCounter/Platforms/MacCatalyst/Program.fs:1— samples/maui/Components/MvuCounter/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Components/MvuCounter/Platforms/iOS/Program.fs:1-9 — `samples/maui/Components/MvuCounter/Platforms/MacCatalyst/Program.fs` and `samples/maui/Components/MvuCounter/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Components/SimpleCounter/Platforms/MacCatalyst/Program.fs:1— samples/maui/Components/SimpleCounter/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Components/SimpleCounter/Platforms/iOS/Program.fs:1-9 — `samples/maui/Components/SimpleCounter/Platforms/MacCatalyst/Program.fs` and `samples/maui/Components/SimpleCounter/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Components/TicTacComponent/Platforms/MacCatalyst/Program.fs:1— samples/maui/Components/TicTacComponent/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Components/TicTacComponent/Platforms/iOS/Program.fs:1-9 — `samples/maui/Components/TicTacComponent/Platforms/MacCatalyst/Program.fs` and `samples/maui/Components/TicTacComponent/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/CounterApp/Platforms/MacCatalyst/Program.fs:1— samples/maui/CounterApp/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/CounterApp/Platforms/iOS/Program.fs:1-9 — `samples/maui/CounterApp/Platforms/MacCatalyst/Program.fs` and `samples/maui/CounterApp/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Gallery/Platforms/MacCatalyst/Program.fs:1— samples/maui/Gallery/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Gallery/Platforms/iOS/Program.fs:1-9 — `samples/maui/Gallery/Platforms/MacCatalyst/Program.fs` and `samples/maui/Gallery/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/HelloWorld/Platforms/MacCatalyst/Program.fs:1— samples/maui/HelloWorld/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/HelloWorld/Platforms/iOS/Program.fs:1-9 — `samples/maui/HelloWorld/Platforms/MacCatalyst/Program.fs` and `samples/maui/HelloWorld/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Maps/HelloMap/Platforms/MacCatalyst/Program.fs:1— samples/maui/Maps/HelloMap/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Maps/HelloMap/Platforms/iOS/Program.fs:1-9 — `samples/maui/Maps/HelloMap/Platforms/MacCatalyst/Program.fs` and `samples/maui/Maps/HelloMap/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/MediaElement/HelloMediaElement/Platforms/MacCatalyst/Program.fs:1— samples/maui/MediaElement/HelloMediaElement/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/MediaElement/HelloMediaElement/Platforms/iOS/Program.fs:1-9 — `samples/maui/MediaElement/HelloMediaElement/Platforms/MacCatalyst/Program.fs` and `samples/maui/MediaElement/HelloMediaElement/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Navigation/ComponentNavigation/Platforms/MacCatalyst/Program.fs:1— samples/maui/Navigation/ComponentNavigation/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Navigation/ComponentNavigation/Platforms/iOS/Program.fs:1-9 — `samples/maui/Navigation/ComponentNavigation/Platforms/MacCatalyst/Program.fs` and `samples/maui/Navigation/ComponentNavigation/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/Playground/Platforms/MacCatalyst/Program.fs:1— samples/maui/Playground/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Playground/Platforms/iOS/Program.fs:1-9 — `samples/maui/Playground/Platforms/MacCatalyst/Program.fs` and `samples/maui/Playground/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/maui/TicTacToe/Platforms/MacCatalyst/Program.fs:1— samples/maui/TicTacToe/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/TicTacToe/Platforms/iOS/Program.fs:1-9 — `samples/maui/TicTacToe/Platforms/MacCatalyst/Program.fs` and `samples/maui/TicTacToe/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) templates/maui/content/blank/Platforms/MacCatalyst/Program.fs:1— templates/maui/content/blank/Platforms/MacCatalyst/Program.fs:1-9 | templates/maui/content/blank/Platforms/iOS/Program.fs:1-9 — `templates/maui/content/blank/Platforms/MacCatalyst/Program.fs` and `templates/maui/content/blank/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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) samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:284— samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:284-292 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:296-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Components.fs:58— src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Components.fs:58-67 | src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/ToggleButton.Components.fs:68-77 | src/avalonia/Fabulous.Avalonia/Views/Controls/CheckBox.Components.fs:76-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Components.fs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Mvu.fs:56— src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Mvu.fs:56-65 | src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/ToggleButton.Mvu.fs:66-75 | src/avalonia/Fabulous.Avalonia/Views/Controls/CheckBox.Mvu.fs:72-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Controls/Buttons/RadioButton.Mvu.fs:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) src/neutral/Fabulous.Core/Builders.fs:115— src/neutral/Fabulous.Core/Builders.fs:115-124 | src/neutral/Fabulous.Core/Builders.fs:133-142 | src/neutral/Fabulous.Core/Builders.fs:158-167 — 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) samples/avalonia/Gallery/Pages/DrawingPage.fs:67— samples/avalonia/Gallery/Pages/DrawingPage.fs:67-76 | samples/avalonia/Gallery/Pages/DrawingPage.fs:82-91 | samples/avalonia/Gallery/Pages/DrawingPage.fs:97-106 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/DrawingPage.fs:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) samples/avalonia/Gallery/Pages/GridPage.fs:121— samples/avalonia/Gallery/Pages/GridPage.fs:121-130 | samples/avalonia/Gallery/Pages/GridPage.fs:145-154 | samples/avalonia/Gallery/Pages/GridPage.fs:179-188 — 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) samples/avalonia/Gallery/Pages/UniformGridPage.fs:98— samples/avalonia/Gallery/Pages/UniformGridPage.fs:98-107 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:126-135 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:188-197 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/UniformGridPage.fs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) samples/maui/Navigation/BasicNavigation/Platforms/Windows/App.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/Windows/App.fs:1-10 | samples/maui/Navigation/ComponentNavigation/Platforms/Windows/App.fs:1-10 | samples/maui/Navigation/NavigationPath/Platforms/Windows/App.fs:1-10 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/Windows/App.fs` and `samples/maui/Navigation/ComponentNavigation/Platforms/Windows/App.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) samples/avalonia/Gallery/Pages/DrawingPage.fs:56— samples/avalonia/Gallery/Pages/DrawingPage.fs:56-65 | samples/avalonia/Gallery/Pages/DrawingPage.fs:71-80 | samples/avalonia/Gallery/Pages/DrawingPage.fs:86-95 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/DrawingPage.fs:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:42— samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:42-51 | samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:177-186 | samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:233-242 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) samples/avalonia/Gallery/Pages/UniformGridPage.fs:121— samples/avalonia/Gallery/Pages/UniformGridPage.fs:121-130 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:149-158 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:183-192 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/UniformGridPage.fs:121` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/UniformGridPage.fs:180` calls `rowSpacing` and `samples/avalonia/Gallery/Pages/UniformGridPage.fs:118` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) src/avalonia/Fabulous.Avalonia/Views/_Visual.Components.fs:35— src/avalonia/Fabulous.Avalonia/Views/_Visual.Components.fs:35-44 | src/avalonia/Fabulous.Avalonia/Views/_Visual.Mvu.fs:35-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/_Visual.Components.fs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/neutral/Fabulous.Core/WidgetDiff.fs:355— src/neutral/Fabulous.Core/WidgetDiff.fs:355-365 | src/neutral/Fabulous.Core/WidgetDiff.fs:469-478 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) samples/maui/Maps/HelloMap/App.fs:56— samples/maui/Maps/HelloMap/App.fs:56-65 | samples/maui/Maps/HelloMap/App.fs:111-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) samples/maui/Navigation/BasicNavigation/Platforms/Android/MainApplication.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/Android/MainApplication.fs:1-10 | samples/maui/Navigation/NavigationPath/Platforms/Android/MainApplication.fs:1-10 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/Android/MainApplication.fs` and `samples/maui/Navigation/NavigationPath/Platforms/Android/MainApplication.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/AppDelegate.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/AppDelegate.fs:1-10 | samples/maui/Navigation/NavigationPath/Platforms/MacCatalyst/AppDelegate.fs:1-10 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/AppDelegate.fs` and `samples/maui/Navigation/NavigationPath/Platforms/MacCatalyst/AppDelegate.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) samples/maui/Navigation/BasicNavigation/Platforms/iOS/AppDelegate.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/iOS/AppDelegate.fs:1-10 | samples/maui/Navigation/NavigationPath/Platforms/iOS/AppDelegate.fs:1-10 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/iOS/AppDelegate.fs` and `samples/maui/Navigation/NavigationPath/Platforms/iOS/AppDelegate.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) samples/maui/WinUICompat/HelloWorld.Fabulous/Platforms/Windows/Main.fs:1— samples/maui/WinUICompat/HelloWorld.Fabulous/Platforms/Windows/Main.fs:1-10 | samples/maui/WinUICompat/HelloWorld.Maui/Platforms/Windows/Main.fs:1-10 — before extracting anything, compare `samples/maui/WinUICompat/HelloWorld.Fabulous/Platforms/Windows/Main.fs` and `samples/maui/WinUICompat/HelloWorld.Maui/Platforms/Windows/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:136— samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:136-145 | samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:286-295 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:136` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) samples/avalonia/Gallery/Pages/UniformGridPage.fs:195— samples/avalonia/Gallery/Pages/UniformGridPage.fs:195-204 | samples/avalonia/Gallery/Pages/WrapPanelsPage.fs:74-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/UniformGridPage.fs:195` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) samples/avalonia/Gallery/Pages/UniformGridPage.fs:138— samples/avalonia/Gallery/Pages/UniformGridPage.fs:138-147 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:207-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/UniformGridPage.fs:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) samples/avalonia/Component/CounterApp/Platform/Desktop/Program.fs:1— samples/avalonia/Component/CounterApp/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/CounterApp/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/CounterApp/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/CounterApp/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/DrawingApp/Platform/Desktop/Program.fs:1— samples/avalonia/Component/DrawingApp/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/DrawingApp/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/DrawingApp/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/DrawingApp/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/MultiWindow/Platform/Desktop/Program.fs:1— samples/avalonia/Component/MultiWindow/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/MultiWindow/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/MultiWindow/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/MultiWindow/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/Navigation/BasicNavigation/Platform/Desktop/Program.fs:1— samples/avalonia/Component/Navigation/BasicNavigation/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/Navigation/BasicNavigation/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/Navigation/BasicNavigation/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/Navigation/BasicNavigation/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/Navigation/ComponentNavigation/Platform/Desktop/Program.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/Platform/Desktop/Program.fs:1— samples/avalonia/Component/Navigation/NavigationPath/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/Navigation/NavigationPath/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/Tetris/Platform/Desktop/Program.fs:1— samples/avalonia/Component/Tetris/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/Tetris/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/Tetris/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/Tetris/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Component/TicTacToe/Platform/Desktop/Program.fs:1— samples/avalonia/Component/TicTacToe/Platform/Desktop/Program.fs:1-19 | samples/avalonia/Mvu/TicTacToe/Platform/Desktop/Program.fs:1-19 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/Platform/Desktop/Program.fs` and `samples/avalonia/Mvu/TicTacToe/Platform/Desktop/Program.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) samples/avalonia/Gallery/Pages/UniformGridPage.fs:99— samples/avalonia/Gallery/Pages/UniformGridPage.fs:99-117 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:127-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/UniformGridPage.fs:99` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/avalonia/Fabulous.Avalonia.TreeDataGrid/TreeDataGrid.Components.fs:9— src/avalonia/Fabulous.Avalonia.TreeDataGrid/TreeDataGrid.Components.fs:9-16 | src/avalonia/Fabulous.Avalonia.TreeDataGrid/TreeDataGrid.Mvu.fs:9-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:120— src/avalonia/Fabulous.Avalonia/Attributes.fs:120-127 | src/avalonia/Fabulous.Avalonia/Attributes.fs:138-145 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:120` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Controls/Primitives/Thumb.Components.fs:12— src/avalonia/Fabulous.Avalonia/Views/Controls/Primitives/Thumb.Components.fs:12-19 | src/avalonia/Fabulous.Avalonia/Views/Controls/Primitives/Thumb.Mvu.fs:11-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/neutral/Fabulous.Core/Attributes.fs:361— src/neutral/Fabulous.Core/Attributes.fs:361-368 | src/neutral/Fabulous.Core/Attributes.fs:384-391 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/_GradientBrush.Components.fs:1— src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/_GradientBrush.Components.fs:1-8 | src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/_GradientBrush.Mvu.fs:1-8 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/avalonia/Fabulous.Avalonia/Views/_Spinner.Components.fs:1— src/avalonia/Fabulous.Avalonia/Views/_Spinner.Components.fs:1-8 | src/avalonia/Fabulous.Avalonia/Views/_Spinner.Mvu.fs:1-8 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) samples/maui/Components/TicTacComponent/App.fs:211— samples/maui/Components/TicTacComponent/App.fs:211-218 | samples/maui/TicTacToe/App.fs:195-202 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/Components/TicTacComponent/App.fs:211` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:49— src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:49-53 | src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:83-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:53` calls `Compile` and `src/avalonia/Fabulous.Avalonia/AppBuilderExtensions.fs:89` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Application.fs:310— src/avalonia/Fabulous.Avalonia/Views/Application.fs:310-314 | src/avalonia/Fabulous.Avalonia/Views/Application.fs:316-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Application.fs:310` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Menu/ContextMenu.fs:137— src/avalonia/Fabulous.Avalonia/Views/Menu/ContextMenu.fs:137-141 | src/avalonia/Fabulous.Avalonia/Views/Panels/Panel.fs:85-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 (5 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:123— src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:123-127 | src/avalonia/Fabulous.Avalonia/Views/Styling/Style.fs:37-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:124— src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:124-128 | src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:130-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/neutral/Fabulous.Core/Cmd.fs:102— src/neutral/Fabulous.Core/Cmd.fs:102-106 | src/neutral/Fabulous.Core/Cmd.fs:115-119 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/neutral/Fabulous.Core/Cmd.fs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) samples/avalonia/Gallery/Pages/CanvasPage.fs:110— samples/avalonia/Gallery/Pages/CanvasPage.fs:110-114 | samples/avalonia/Gallery/Pages/ImagePage.fs:22-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/CanvasPage.fs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) samples/avalonia/Component/Tetris/Core.fs:197— samples/avalonia/Component/Tetris/Core.fs:197-216 | samples/avalonia/Mvu/Tetris/Core.fs:191-210 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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) samples/avalonia/Component/Tetris/Core.fs:271— samples/avalonia/Component/Tetris/Core.fs:271-290 | samples/avalonia/Mvu/Tetris/Core.fs:265-284 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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) samples/avalonia/Gallery/Pages/DropDownButtonPage.fs:53— samples/avalonia/Gallery/Pages/DropDownButtonPage.fs:53-72 | samples/avalonia/Gallery/Pages/MenuFlyoutPage.fs:47-66 — before extracting anything, compare `samples/avalonia/Gallery/Pages/DropDownButtonPage.fs` and `samples/avalonia/Gallery/Pages/MenuFlyoutPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/DropDownButtonPage.fs:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:14— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:14-33 | samples/maui/Navigation/ComponentNavigation/PageA.fs:11-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:37— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:37-56 | samples/maui/Navigation/ComponentNavigation/PageA.fs:34-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) samples/maui/Navigation/ComponentNavigation/PageB.fs:57— samples/maui/Navigation/ComponentNavigation/PageB.fs:57-76 | samples/maui/Navigation/NavigationPath/PageB.fs:32-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) templates/avalonia/content/blank/App.fs:1— templates/avalonia/content/blank/App.fs:1-20 | templates/avalonia/content/desktop/App.fs:1-20 — `templates/avalonia/content/blank/App.fs` and `templates/avalonia/content/desktop/App.fs` 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 4 separate duplicated blocks between them, totalling at least 95 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 × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:468— src/avalonia/Fabulous.Avalonia/Attributes.fs:468-482 | src/neutral/Fabulous.Core/Attributes.fs:341-355 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:468` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:50— samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:50-64 | samples/avalonia/Gallery/Pages/ThemeAwarePage.fs:47-61 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AdornerLayerPage.fs` and `samples/avalonia/Gallery/Pages/ThemeAwarePage.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) samples/avalonia/Gallery/Pages/AnimationsPage.fs:13— samples/avalonia/Gallery/Pages/AnimationsPage.fs:13-27 | samples/avalonia/Gallery/Pages/TransitionsPage.fs:13-27 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AnimationsPage.fs` and `samples/avalonia/Gallery/Pages/TransitionsPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/AnimationsPage.fs:28` calls `ScrollViewer`, `VStack` and `samples/avalonia/Gallery/Pages/TransitionsPage.fs:28` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) samples/avalonia/Gallery/Pages/GridPage.fs:145— samples/avalonia/Gallery/Pages/GridPage.fs:145-159 | samples/avalonia/Gallery/Pages/GridPage.fs:179-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.
Duplicated block (15 lines × 2) samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs:1— samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs:1-15 | samples/maui/HelloWorld/Platforms/Tizen/Main.fs:1-15 — before extracting anything, compare `samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs` and `samples/maui/HelloWorld/Platforms/Tizen/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) samples/avalonia/Gallery/MainView.fs:144— samples/avalonia/Gallery/MainView.fs:144-159 | samples/avalonia/Gallery/Pages/LabelPage.fs:66-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/MainView.fs:144` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/avalonia/Fabulous.Avalonia/Program.fs:58— src/avalonia/Fabulous.Avalonia/Program.fs:58-71 | src/neutral/Fabulous.Core/Program.fs:34-47 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/avalonia/Fabulous.Avalonia/Program.fs:73` calls `defaultSyncAction` and `src/neutral/Fabulous.Core/Program.fs:49` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) src/maui/Fabulous.MauiControls/Widgets.fs:30— src/maui/Fabulous.MauiControls/Widgets.fs:30-43 | src/maui/Fabulous.MauiControls/Widgets.fs:50-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/neutral/Fabulous.Core/Components/Widget.fs:18— src/neutral/Fabulous.Core/Components/Widget.fs:18-31 | src/neutral/Fabulous.Core/Components/Widget.fs:39-52 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) src/avalonia/Fabulous.Avalonia/Views/_HeaderedItemsControl.fs:1— src/avalonia/Fabulous.Avalonia/Views/_HeaderedItemsControl.fs:1-14 | src/avalonia/Fabulous.Avalonia/Views/_HeaderedSelectingItemsControl.fs:1-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) samples/avalonia/Gallery/Pages/GridPage.fs:161— samples/avalonia/Gallery/Pages/GridPage.fs:161-174 | samples/avalonia/Gallery/Pages/GridPage.fs:205-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/GridPage.fs:178` calls `Grid`, `Stars` and `samples/avalonia/Gallery/Pages/GridPage.fs:220` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) samples/avalonia/Gallery/Pages/ButtonsPage.fs:33— samples/avalonia/Gallery/Pages/ButtonsPage.fs:33-46 | samples/avalonia/Gallery/Pages/SplitButtonPage.fs:78-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ButtonsPage.fs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:202— src/avalonia/Fabulous.Avalonia/Attributes.fs:202-212 | src/avalonia/Fabulous.Avalonia/Attributes.fs:268-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Panels/Grid.fs:42— src/avalonia/Fabulous.Avalonia/Views/Panels/Grid.fs:42-52 | src/maui/Fabulous.MauiControls/Views/Layouts/Grid.fs:41-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) samples/avalonia/Gallery/Pages/CanvasPage.fs:142— samples/avalonia/Gallery/Pages/CanvasPage.fs:142-152 | samples/avalonia/Gallery/Pages/ShapesPage.fs:63-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/CanvasPage.fs:139` calls `canvasLeft`, `canvasTop` and `samples/avalonia/Gallery/Pages/ShapesPage.fs:61` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:284— samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:284-294 | samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:317-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) samples/avalonia/Gallery/Pages/PathMeasurementPage.fs:36— samples/avalonia/Gallery/Pages/PathMeasurementPage.fs:36-46 | samples/avalonia/Gallery/Pages/RenderTargetBitmapPage.fs:22-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) samples/maui/Maps/HelloMap/App.fs:82— samples/maui/Maps/HelloMap/App.fs:82-92 | samples/maui/Maps/HelloMap/App.fs:96-106 — both copies are in the same file, so extract the block into 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) src/neutral/Fabulous.Core/WidgetDiff.fs:222— src/neutral/Fabulous.Core/WidgetDiff.fs:222-230 | src/neutral/Fabulous.Core/WidgetDiff.fs:337-345 | src/neutral/Fabulous.Core/WidgetDiff.fs:604-612 — 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) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:31— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:31-39 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:31-39 | samples/maui/Navigation/ComponentNavigation/Navigation.fs:31-39 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:31— samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:31-39 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs:31-39 | samples/maui/Navigation/NavigationPath/NavigationTypes.fs:31-39 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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) samples/maui/Calculator/Platforms/Windows/App.fs:1— samples/maui/Calculator/Platforms/Windows/App.fs:1-9 | samples/maui/Components/TicTacComponent/Platforms/Windows/App.fs:1-9 | samples/maui/TicTacToe/Platforms/Windows/App.fs:1-9 — before extracting anything, compare `samples/maui/Calculator/Platforms/Windows/App.fs` and `samples/maui/Components/TicTacComponent/Platforms/Windows/App.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) samples/maui/Calculator/Platforms/Windows/Main.fs:1— samples/maui/Calculator/Platforms/Windows/Main.fs:1-9 | samples/maui/Components/TicTacComponent/Platforms/Windows/Main.fs:1-9 | samples/maui/TicTacToe/Platforms/Windows/Main.fs:1-9 — before extracting anything, compare `samples/maui/Calculator/Platforms/Windows/Main.fs` and `samples/maui/Components/TicTacComponent/Platforms/Windows/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) samples/maui/Navigation/BasicNavigation/Platforms/Windows/Main.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/Windows/Main.fs:1-9 | samples/maui/Navigation/ComponentNavigation/Platforms/Windows/Main.fs:1-9 | samples/maui/Navigation/NavigationPath/Platforms/Windows/Main.fs:1-9 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/Windows/Main.fs` and `samples/maui/Navigation/ComponentNavigation/Platforms/Windows/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/avalonia/Fabulous.Avalonia/Style.fs:6— src/avalonia/Fabulous.Avalonia/Style.fs:6-11 | src/maui/Fabulous.MauiControls/Style.fs:7-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/maui/Fabulous.MauiControls/Style.fs:7` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:81— src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:81-86 | src/avalonia/Fabulous.Avalonia/Views/Controls/TextBlock.fs:319-324 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:44— src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:44-49 | src/avalonia/Fabulous.Avalonia/Views/MenuItems/MenuItem.fs:111-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:117— src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:117-122 | src/avalonia/Fabulous.Avalonia/Views/Styling/Style.fs:31-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) samples/avalonia/Component/Navigation/ComponentNavigation/App.fs:49— samples/avalonia/Component/Navigation/ComponentNavigation/App.fs:49-54 | samples/avalonia/Mvu/Navigation/ComponentNavigation/App.fs:49-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Navigation/ComponentNavigation/App.fs:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) samples/avalonia/Component/Tetris/App.fs:166— samples/avalonia/Component/Tetris/App.fs:166-171 | samples/avalonia/Mvu/Tetris/App.fs:244-249 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Tetris/App.fs:166` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:543— src/avalonia/Fabulous.Avalonia/Attributes.fs:543-554 | src/avalonia/Fabulous.Avalonia/Attributes.fs:564-575 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:543` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Panels/Grid.fs:22— src/avalonia/Fabulous.Avalonia/Views/Panels/Grid.fs:22-33 | src/maui/Fabulous.MauiControls/Views/Layouts/Grid.fs:22-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/neutral/Fabulous.Core/Components/Component.fs:74— src/neutral/Fabulous.Core/Components/Component.fs:74-85 | src/neutral/Fabulous.Core/Components/Component.fs:116-127 — both copies are in the same file, so extract the block into 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) samples/avalonia/Gallery/Pages/Pointers/PointersPage.fs:148— samples/avalonia/Gallery/Pages/Pointers/PointersPage.fs:148-159 | samples/avalonia/Gallery/Pages/Pointers/PointersPage.fs:162-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/Pointers/PointersPage.fs:148` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:196— samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:196-207 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:218-229 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:196` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/avalonia/Fabulous.Avalonia/Attributes.fs:248— src/avalonia/Fabulous.Avalonia/Attributes.fs:248-253 | src/avalonia/Fabulous.Avalonia/Attributes.fs:327-331 | src/neutral/Fabulous.Core/Attributes.fs:243-248 — 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 (5 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Controls/Documents/Span.fs:38— src/avalonia/Fabulous.Avalonia/Views/Controls/Documents/Span.fs:38-42 | src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:82-86 | src/avalonia/Fabulous.Avalonia/Views/Controls/TextBlock.fs:320-324 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Controls/Documents/Span.fs:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:82— src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:82-86 | src/avalonia/Fabulous.Avalonia/Views/Controls/TextBlock.fs:314-318 | src/avalonia/Fabulous.Avalonia/Views/Controls/TextBlock.fs:320-324 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:82` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Menu/Menu.fs:34— src/avalonia/Fabulous.Avalonia/Views/Menu/Menu.fs:34-38 | src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:44-48 | src/avalonia/Fabulous.Avalonia/Views/MenuItems/MenuItem.fs:111-115 — 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 (5 lines × 3) src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:112— src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:112-116 | src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:118-122 | src/avalonia/Fabulous.Avalonia/Views/Styling/Style.fs:32-36 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.fs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Change coupling: SelectableTextBlock.fs ↔ TextBox.fs src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs:1— `src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs` and `src/avalonia/Fabulous.Avalonia/Views/Controls/TextBox.fs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e30773d6` SolidColorBrush(value: string) (at that commit the files were still `src/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs` and `src/Fabulous.Avalonia/Views/Controls/TextBox.fs`); `2b989978` Update modifiers (at that commit the files were still `src/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs` and `src/Fabulous.Avalonia/Views/Controls/TextBox.fs`); `f907b6bf` Brush Extensions: Add support for Colors parameter e.g., background(C… (at that commit the files were still `src/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs` and `src/Fabulous.Avalonia/Views/Controls/TextBox.fs`) — run `git show` on any of them.
Change coupling: Attributes.fs ↔ ViewNode.fs src/neutral/Fabulous.Core/Attributes.fs:1— `src/neutral/Fabulous.Core/Attributes.fs` and `src/neutral/Fabulous.Core/ViewNode.fs` change together 61% of the time (11 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `f7a294d7` Ensure old widgets are disposed when replaced by new ones (at that commit the files were still `src/Fabulous/Attributes.fs` and `src/Fabulous/ViewNode.fs`); `7f541a01` Reworked components (at that commit the files were still `src/Fabulous/Attributes.fs` and `src/Fabulous/ViewNode.fs`); `860e2eff` Make ViewNode disposable (at that commit the files were still `src/Fabulous/Attributes.fs` and `src/Fabulous/ViewNode.fs`) — run `git show` on any of them.
Change coupling: Primitives.fs ↔ Reconciler.fs src/neutral/Fabulous.Core/Primitives.fs:1— `src/neutral/Fabulous.Core/Primitives.fs` and `src/neutral/Fabulous.Core/Reconciler.fs` change together 61% of the time (11 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `1bd0aedf` Optimize (at that commit the files were still `src/Fabulous/Primitives.fs` and `src/Fabulous/Reconciler.fs`); `89a4b8b9` First iteration of streaming diffing e2e (at that commit the files were still `src/Fabulous/Core.fs` and `src/Fabulous/Reconciler.fs`); `6ce5a110` PoC for diffing enumerator for scalars (at that commit the files were still `src/Fabulous/Core.fs` and `src/Fabulous/Reconciler.fs`) — run `git show` on any of them.
Change coupling: _TextElement.fs ↔ _TopLevel.fs src/avalonia/Fabulous.Avalonia/Views/_TextElement.fs:1— `src/avalonia/Fabulous.Avalonia/Views/_TextElement.fs` and `src/avalonia/Fabulous.Avalonia/Views/_TopLevel.fs` 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e30773d6` SolidColorBrush(value: string) (at that commit the files were still `src/Fabulous.Avalonia/Views/_TextElement.fs` and `src/Fabulous.Avalonia/Views/_TopLevel.fs`); `be5c4757` Update file ordering (at that commit the files were still `src/Fabulous.Avalonia/Views/_TextElement.fs` and `src/Fabulous.Avalonia/Views/_TopLevel.fs`); `f907b6bf` Brush Extensions: Add support for Colors parameter e.g., background(C… (at that commit the files were still `src/Fabulous.Avalonia/Views/_TextElement.fs` and `src/Fabulous.Avalonia/Views/_TopLevel.fs`) — run `git show` on any of them.
Duplicated block (17 lines × 2) src/neutral/Fabulous.Core/Components/Environment.fs:22— src/neutral/Fabulous.Core/Components/Environment.fs:22-38 | src/neutral/Fabulous.Core/Components/EnvironmentObject.fs:31-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/neutral/Fabulous.Core/Components/Environment.fs:22` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) samples/avalonia/Component/Tetris/App.fs:527— samples/avalonia/Component/Tetris/App.fs:527-543 | samples/avalonia/Component/Tetris/App.fs:583-599 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Tetris/App.fs:527` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) samples/avalonia/Component/TicTacToe/App.fs:113— samples/avalonia/Component/TicTacToe/App.fs:113-129 | samples/avalonia/Mvu/TicTacToe/App.fs:200-216 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/TicTacToe/App.fs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) samples/avalonia/Gallery/Pages/CalendarDatePicker.fs:21— samples/avalonia/Gallery/Pages/CalendarDatePicker.fs:21-37 | samples/avalonia/Gallery/Pages/CalendarPage.fs:30-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 3) samples/avalonia/Component/Navigation/BasicNavigation/PageA.fs:17— samples/avalonia/Component/Navigation/BasicNavigation/PageA.fs:17-30 | samples/avalonia/Component/Navigation/BasicNavigation/PageB.fs:17-30 | samples/avalonia/Component/Navigation/BasicNavigation/PageC.fs:17-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Navigation/BasicNavigation/PageA.fs:17` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) samples/avalonia/Gallery/Pages/CanvasPage.fs:125— samples/avalonia/Gallery/Pages/CanvasPage.fs:125-138 | samples/avalonia/Gallery/Pages/ShapesPage.fs:48-61 | samples/maui/Gallery/Samples/Shapes.fs:59-72 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/CanvasPage.fs:121` calls `canvasLeft`, `canvasTop` and `samples/maui/Gallery/Samples/Shapes.fs:57` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 3) samples/avalonia/Gallery/Pages/UniformGridPage.fs:104— samples/avalonia/Gallery/Pages/UniformGridPage.fs:104-117 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:132-145 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:160-173 — 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) samples/maui/Components/MultipleMvus/MauiProgram.fs:3— samples/maui/Components/MultipleMvus/MauiProgram.fs:3-16 | samples/maui/Components/MvuCounter/MauiProgram.fs:3-16 | samples/maui/Components/TicTacComponent/MauiProgram.fs:3-16 — `samples/maui/Components/MultipleMvus/MauiProgram.fs` and `samples/maui/Components/MvuCounter/MauiProgram.fs` 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 1 separate duplicated blocks between them, totalling at least 14 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) samples/maui/Components/HelloComponent/Platforms/Windows/App.fs:1— samples/maui/Components/HelloComponent/Platforms/Windows/App.fs:1-9 | samples/maui/HelloWorld/Platforms/Windows/App.fs:1-9 | samples/maui/WinUICompat/HelloWorld.Fabulous/Platforms/Windows/App.fs:1-10 | samples/maui/WinUICompat/HelloWorld.Maui/Platforms/Windows/App.fs:1-10 — before extracting anything, compare `samples/maui/Components/HelloComponent/Platforms/Windows/App.fs` and `samples/maui/HelloWorld/Platforms/Windows/App.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) samples/maui/Components/MultipleMvus/Platforms/Windows/App.fs:1— samples/maui/Components/MultipleMvus/Platforms/Windows/App.fs:1-9 | samples/maui/Components/MvuCounter/Platforms/Windows/App.fs:1-9 | samples/maui/Components/SimpleCounter/Platforms/Windows/App.fs:1-9 | samples/maui/CounterApp/Platforms/Windows/App.fs:1-9 — before extracting anything, compare `samples/maui/Components/MultipleMvus/Platforms/Windows/App.fs` and `samples/maui/Components/MvuCounter/Platforms/Windows/App.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) samples/maui/Components/MultipleMvus/Platforms/Windows/Main.fs:1— samples/maui/Components/MultipleMvus/Platforms/Windows/Main.fs:1-9 | samples/maui/Components/MvuCounter/Platforms/Windows/Main.fs:1-9 | samples/maui/Components/SimpleCounter/Platforms/Windows/Main.fs:1-9 | samples/maui/CounterApp/Platforms/Windows/Main.fs:1-9 — before extracting anything, compare `samples/maui/Components/MultipleMvus/Platforms/Windows/Main.fs` and `samples/maui/Components/MvuCounter/Platforms/Windows/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/Program.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Navigation/BasicNavigation/Platforms/iOS/Program.fs:1-9 | samples/maui/Navigation/NavigationPath/Platforms/MacCatalyst/Program.fs:1-9 | samples/maui/Navigation/NavigationPath/Platforms/iOS/Program.fs:1-9 — `samples/maui/Navigation/BasicNavigation/Platforms/MacCatalyst/Program.fs` and `samples/maui/Navigation/BasicNavigation/Platforms/iOS/Program.fs` 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 1 separate duplicated blocks between them, totalling at least 9 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 (29 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:240— src/avalonia/Fabulous.Avalonia/Attributes.fs:240-268 | src/neutral/Fabulous.Core/Attributes.fs:235-263 — 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 (29 lines × 2) src/avalonia/Fabulous.Avalonia/Component.fs:133— src/avalonia/Fabulous.Avalonia/Component.fs:133-161 | src/neutral/Fabulous.Core/Components/Modifiers.fs:112-140 — before extracting anything, compare `src/avalonia/Fabulous.Avalonia/Component.fs` and `src/neutral/Fabulous.Core/Components/Modifiers.fs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/App.fs:37— samples/avalonia/Component/Navigation/NavigationPath/App.fs:37-65 | samples/avalonia/Mvu/Navigation/NavigationPath/App.fs:36-64 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/App.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/App.fs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/NavigationPath/App.fs:36` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/neutral/Fabulous.Core/WidgetDiff.fs:46— src/neutral/Fabulous.Core/WidgetDiff.fs:46-58 | src/neutral/Fabulous.Core/WidgetDiff.fs:61-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) samples/avalonia/Component/Tetris/App.fs:503— samples/avalonia/Component/Tetris/App.fs:503-515 | samples/avalonia/Component/Tetris/App.fs:565-577 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Tetris/App.fs:503` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:57— samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:57-69 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:74-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) src/maui/Fabulous.MauiControls/Widgets.fs:102— src/maui/Fabulous.MauiControls/Widgets.fs:102-111 | src/maui/Fabulous.MauiControls/Widgets.fs:118-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/maui/Fabulous.MauiControls/Widgets.fs:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) src/neutral/Fabulous.Core/Components/Widget.fs:63— src/neutral/Fabulous.Core/Components/Widget.fs:63-72 | src/neutral/Fabulous.Core/Components/Widget.fs:75-83 — both copies are in the same file, so extract the block into 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) samples/avalonia/Component/Tetris/App.fs:493— samples/avalonia/Component/Tetris/App.fs:493-501 | samples/avalonia/Component/Tetris/App.fs:554-563 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Tetris/App.fs:493` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/maui/Fabulous.MauiControls/Views/Layouts/Grid.fs:31— src/maui/Fabulous.MauiControls/Views/Layouts/Grid.fs:31-37 | src/maui/Fabulous.MauiControls/Views/Layouts/Grid.fs:49-55 — both copies are in the same file, so extract the block into 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) samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245— samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245-251 | samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:255-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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:254` calls `numberFormat` and `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:264` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) samples/avalonia/Gallery/Pages/GridPage.fs:313— samples/avalonia/Gallery/Pages/GridPage.fs:313-319 | samples/avalonia/Gallery/Pages/GridPage.fs:348-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/GridPage.fs:313` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/GridPage.fs:346` calls `width`, `height` and `samples/avalonia/Gallery/Pages/GridPage.fs:312` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:1-66 | samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:1-39 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:1-66 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs:1-39 | samples/maui/Navigation/ComponentNavigation/Navigation.fs:1-39 | samples/maui/Navigation/NavigationPath/NavigationTypes.fs:1-39 — 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) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:1— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:1-82 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:1-83 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:1-91 | samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:1-61 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:1-59 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:1-68 — 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) samples/maui/Calculator/MauiProgram.fs:1— samples/maui/Calculator/MauiProgram.fs:1-16 | samples/maui/CounterApp/MauiProgram.fs:1-16 | samples/maui/Playground/MauiProgram.fs:1-16 | samples/maui/TicTacToe/MauiProgram.fs:1-16 | samples/maui/WinUICompat/HelloWorld.Fabulous/MauiProgram.fs:1-16 | templates/maui/content/blank/MauiProgram.fs:1-16 — 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 (23–25 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:60— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:60-82 | samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:37-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23–25 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:61— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:61-83 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:35-59 — `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs` 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 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23–25 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:69— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:69-91 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:44-68 — `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs` 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 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) samples/avalonia/Component/MultiWindow/App.fs:118— samples/avalonia/Component/MultiWindow/App.fs:118-141 | samples/avalonia/Mvu/MultiWindow/App.fs:206-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/MultiWindow/App.fs:118` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) samples/avalonia/Component/Tetris/Core.fs:219— samples/avalonia/Component/Tetris/Core.fs:219-242 | samples/avalonia/Mvu/Tetris/Core.fs:213-236 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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 (24 lines × 2) samples/maui/Components/MvuCounter/App.fs:58— samples/maui/Components/MvuCounter/App.fs:58-81 | samples/maui/CounterApp/App.fs:53-76 — before extracting anything, compare `samples/maui/Components/MvuCounter/App.fs` and `samples/maui/CounterApp/App.fs` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/Components/MvuCounter/App.fs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) samples/avalonia/Component/Navigation/ComponentNavigation/AppMsg.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/AppMsg.fs:1-17 | samples/avalonia/Mvu/Navigation/ComponentNavigation/AppMsg.fs:1-17 | samples/maui/Navigation/ComponentNavigation/AppMsg.fs:1-17 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/AppMsg.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/AppMsg.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs:52— samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs:52-68 | samples/avalonia/Gallery/Pages/ContextMenuPage.fs:53-69 | samples/avalonia/Gallery/Pages/FlyoutPage.fs:59-75 — before extracting anything, compare `samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs` and `samples/avalonia/Gallery/Pages/ContextMenuPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) samples/avalonia/Gallery/Pages/GridPage.fs:291— samples/avalonia/Gallery/Pages/GridPage.fs:291-307 | samples/avalonia/Gallery/Pages/GridPage.fs:322-338 | samples/avalonia/Gallery/Pages/GridPage.fs:357-373 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/GridPage.fs:339` calls `width`, `height` and `samples/avalonia/Gallery/Pages/GridPage.fs:308` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) samples/avalonia/Gallery/Pages/GridPage.fs:68— samples/avalonia/Gallery/Pages/GridPage.fs:68-83 | samples/avalonia/Gallery/Pages/GridPage.fs:125-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/GridPage.fs:68` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/GridPage.fs:124` calls `size` and `samples/avalonia/Gallery/Pages/GridPage.fs:67` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) samples/maui/Navigation/BasicNavigation/MauiProgram.fs:1— samples/maui/Navigation/BasicNavigation/MauiProgram.fs:1-16 | samples/maui/Navigation/NavigationPath/MauiProgram.fs:1-16 — `samples/maui/Navigation/BasicNavigation/MauiProgram.fs` and `samples/maui/Navigation/NavigationPath/MauiProgram.fs` 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 1 separate duplicated blocks between them, totalling at least 16 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 lines × 2) samples/maui/Navigation/BasicNavigation/Platforms/Android/MainActivity.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/Android/MainActivity.fs:1-16 | samples/maui/Navigation/NavigationPath/Platforms/Android/MainActivity.fs:1-16 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/Android/MainActivity.fs` and `samples/maui/Navigation/NavigationPath/Platforms/Android/MainActivity.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) samples/avalonia/Gallery/Pages/ExpressionAnimation.fs:43— samples/avalonia/Gallery/Pages/ExpressionAnimation.fs:43-57 | samples/avalonia/Gallery/Pages/GalaxyAnimation.fs:97-111 | samples/avalonia/Gallery/Pages/Vector3KeyFrameAnimation.fs:47-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (15 lines × 3) samples/maui/Calculator/Platforms/Tizen/Main.fs:1— samples/maui/Calculator/Platforms/Tizen/Main.fs:1-15 | samples/maui/Components/TicTacComponent/Platforms/Tizen/Main.fs:1-15 | samples/maui/TicTacToe/Platforms/Tizen/Main.fs:1-15 — before extracting anything, compare `samples/maui/Calculator/Platforms/Tizen/Main.fs` and `samples/maui/Components/TicTacComponent/Platforms/Tizen/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) samples/maui/Navigation/BasicNavigation/Platforms/Tizen/Main.fs:1— samples/maui/Navigation/BasicNavigation/Platforms/Tizen/Main.fs:1-15 | samples/maui/Navigation/ComponentNavigation/Platforms/Tizen/Main.fs:1-15 | samples/maui/Navigation/NavigationPath/Platforms/Tizen/Main.fs:1-15 — before extracting anything, compare `samples/maui/Navigation/BasicNavigation/Platforms/Tizen/Main.fs` and `samples/maui/Navigation/ComponentNavigation/Platforms/Tizen/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:54— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:54-64 | samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:71-81 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:54-64 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs:71-81 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) samples/avalonia/Gallery/Pages/ThumbPage.fs:229— samples/avalonia/Gallery/Pages/ThumbPage.fs:229-239 | samples/avalonia/Gallery/Pages/ThumbPage.fs:252-262 | samples/avalonia/Gallery/Pages/ThumbPage.fs:275-285 | samples/avalonia/Gallery/Pages/ThumbPage.fs:298-308 — 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) samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:197— samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:197-207 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:208-218 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:219-229 | samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:230-240 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:197` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Hotspot: samples/avalonia/Gallery/App.fs samples/avalonia/Gallery/App.fs:112— samples/avalonia/Gallery/App.fs changed 2 times in last 90 days, max cyclomatic complexity 98 in App.|CurrentPage|_| at line 112. 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-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:18:25 +00:00' --until='2026-10-26 12:18:25 +00:00' --full-history --no-merges -- samples/avalonia/Gallery/App.fs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/neutral/Fabulous.Core/Array.fs src/neutral/Fabulous.Core/Array.fs:376— src/neutral/Fabulous.Core/Array.fs changed 3 times in last 90 days, max cyclomatic complexity 22 in StackArray3.combine at line 376. 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-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:18:25 +00:00' --until='2026-10-26 12:18:25 +00:00' --full-history --no-merges -- src/neutral/Fabulous.Core/Array.fs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Duplicated block (23 lines × 3) src/avalonia/Fabulous.Avalonia/Attributes.fs:160— src/avalonia/Fabulous.Avalonia/Attributes.fs:160-182 | src/avalonia/Fabulous.Avalonia/Attributes.fs:226-248 | src/neutral/Fabulous.Core/Attributes.fs:221-243 — 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 (23 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/PageA.fs:11— samples/avalonia/Component/Navigation/NavigationPath/PageA.fs:11-33 | samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:13-35 | samples/maui/Navigation/NavigationPath/PageA.fs:11-33 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/maui/Navigation/NavigationPath/PageA.fs:34` calls `ContentPage` and `samples/avalonia/Component/Navigation/NavigationPath/PageA.fs:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) src/avalonia/Fabulous.Avalonia/Program.fs:87— src/avalonia/Fabulous.Avalonia/Program.fs:87-107 | src/maui/Fabulous.MauiControls/Program.fs:80-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 (21 lines × 2) samples/maui/Navigation/ComponentNavigation/PageC.fs:64— samples/maui/Navigation/ComponentNavigation/PageC.fs:64-84 | samples/maui/Navigation/NavigationPath/PageC.fs:41-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 (12–14 lines × 2) src/avalonia/Fabulous.Avalonia/Widgets.fs:32— src/avalonia/Fabulous.Avalonia/Widgets.fs:32-43 | src/avalonia/Fabulous.Avalonia/Widgets.fs:49-62 — both copies are in the same file, so extract the block into 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–14 lines × 2) samples/maui/Components/TicTacComponent/App.fs:190— samples/maui/Components/TicTacComponent/App.fs:190-201 | samples/maui/TicTacToe/App.fs:252-265 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) src/maui/Fabulous.MauiControls.Maps/Map.fs:129— src/maui/Fabulous.MauiControls.Maps/Map.fs:129-136 | src/maui/Fabulous.MauiControls.Maps/Map.fs:138-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/maui/Fabulous.MauiControls.Maps/Map.fs:129` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) samples/avalonia/Gallery/Pages/ThumbPage.fs:131— samples/avalonia/Gallery/Pages/ThumbPage.fs:131-138 | samples/avalonia/Gallery/Pages/ThumbPage.fs:178-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (35 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Controls/Shapes/Arc.fs:1— src/avalonia/Fabulous.Avalonia/Views/Controls/Shapes/Arc.fs:1-35 | src/avalonia/Fabulous.Avalonia/Views/Controls/Shapes/Sector.fs:1-35 — 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 (35 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.Components.fs:1— src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.Components.fs:1-35 | src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.Mvu.fs:1-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Styling/Animation.Components.fs:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/DrawingBrush.fs:1— src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/DrawingBrush.fs:1-31 | src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/VisualBrush.fs:1-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Media/Brushes/DrawingBrush.fs:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) samples/maui/WinUICompat/HelloWorld.Fabulous/App.fs:3— samples/maui/WinUICompat/HelloWorld.Fabulous/App.fs:3-33 | templates/maui/content/blank/App.fs:3-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/WinUICompat/HelloWorld.Fabulous/App.fs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Members sharing a duplicated core (16 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (16 members, 50+ identical tokens) samples/maui/Calculator/Platforms/Android/MainActivity.fs:1— samples/maui/Calculator/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Components/HelloComponent/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Components/MultipleMvus/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Components/MvuCounter/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Components/SimpleCounter/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Components/TicTacComponent/Platforms/Android/MainActivity.fs:1-17 | samples/maui/CounterApp/Platforms/Android/MainActivity.fs:1-17 | samples/maui/HelloWorld/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Maps/HelloMap/Platforms/Android/MainActivity.fs:1-17 | samples/maui/MediaElement/HelloMediaElement/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Navigation/BasicNavigation/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Navigation/ComponentNavigation/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Navigation/NavigationPath/Platforms/Android/MainActivity.fs:1-17 | samples/maui/Playground/Platforms/Android/MainActivity.fs:1-17 | samples/maui/TicTacToe/Platforms/Android/MainActivity.fs:1-17 | templates/maui/content/blank/Platforms/Android/MainActivity.fs:1-17 — These 16 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 16 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 16 times.
Members sharing a duplicated core (16 members, 50+ identical tokens) samples/maui/Calculator/Platforms/Tizen/Main.fs:1— samples/maui/Calculator/Platforms/Tizen/Main.fs:1-16 | samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs:1-16 | samples/maui/Components/MultipleMvus/Platforms/Tizen/Main.fs:1-16 | samples/maui/Components/MvuCounter/Platforms/Tizen/Main.fs:1-16 | samples/maui/Components/SimpleCounter/Platforms/Tizen/Main.fs:1-16 | samples/maui/Components/TicTacComponent/Platforms/Tizen/Main.fs:1-16 | samples/maui/CounterApp/Platforms/Tizen/Main.fs:1-16 | samples/maui/HelloWorld/Platforms/Tizen/Main.fs:1-16 | samples/maui/Maps/HelloMap/Platforms/Tizen/Main.fs:1-16 | samples/maui/MediaElement/HelloMediaElement/Platforms/Tizen/Main.fs:1-16 | samples/maui/Navigation/BasicNavigation/Platforms/Tizen/Main.fs:1-16 | samples/maui/Navigation/ComponentNavigation/Platforms/Tizen/Main.fs:1-16 | samples/maui/Navigation/NavigationPath/Platforms/Tizen/Main.fs:1-16 | samples/maui/Playground/Platforms/Tizen/Main.fs:1-16 | samples/maui/TicTacToe/Platforms/Tizen/Main.fs:1-16 | templates/maui/content/blank/Platforms/Tizen/Main.fs:1-16 — These 16 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 16 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 16 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) samples/avalonia/Mvu/CounterApp/App.fs:1— samples/avalonia/Mvu/CounterApp/App.fs:1-103 | samples/avalonia/Mvu/MultiWindow/App.fs:1-229 | samples/maui/Components/MvuCounter/App.fs:1-81 | samples/maui/CounterApp/App.fs:1-80 | templates/avalonia/content/blank/App.fs:1-91 | templates/avalonia/content/desktop/App.fs:1-85 | templates/avalonia/content/multi/NewApp/App.fs:1-91 — 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) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:1— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:1-35 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:1-35 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageC.fs:1-35 | samples/maui/Components/MultipleMvus/App.fs:1-68 | samples/maui/Navigation/BasicNavigation/PageA.fs:1-28 | samples/maui/Navigation/BasicNavigation/PageB.fs:1-28 | samples/maui/Navigation/BasicNavigation/PageC.fs:1-28 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Duplicated block (43 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:41— samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:41-83 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs:41-83 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs` as WHOLE FILES: this scan already matched 3 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. 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 (43 lines × 2) samples/avalonia/Component/Tetris/Core.fs:293— samples/avalonia/Component/Tetris/Core.fs:293-335 | samples/avalonia/Mvu/Tetris/Core.fs:287-329 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 3) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:1-29 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:1-29 | samples/maui/Navigation/ComponentNavigation/Navigation.fs:1-29 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:1— samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:1-29 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs:1-29 | samples/maui/Navigation/NavigationPath/NavigationTypes.fs:1-29 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) samples/avalonia/Gallery/Pages/AnimationsPage.fs:39— samples/avalonia/Gallery/Pages/AnimationsPage.fs:39-64 | samples/avalonia/Gallery/Pages/TransitionsPage.fs:37-62 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AnimationsPage.fs` and `samples/avalonia/Gallery/Pages/TransitionsPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/AnimationsPage.fs:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:10— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:10-35 | samples/maui/Navigation/ComponentNavigation/PageB.fs:8-33 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs` and `samples/maui/Navigation/ComponentNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) samples/avalonia/Component/Tetris/Core.fs:1— samples/avalonia/Component/Tetris/Core.fs:1-23 | samples/avalonia/Mvu/Tetris/Core.fs:1-23 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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) samples/avalonia/Component/TicTacToe/App.fs:67— samples/avalonia/Component/TicTacToe/App.fs:67-89 | samples/avalonia/Mvu/TicTacToe/App.fs:89-111 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/TicTacToe/App.fs:67` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 2) samples/avalonia/Gallery/Pages/ItemsRepeaterPage.fs:44— samples/avalonia/Gallery/Pages/ItemsRepeaterPage.fs:44-62 | samples/avalonia/Gallery/Pages/ItemsRepeaterPage.fs:68-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 (18–19 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/App.fs:31— samples/avalonia/Mvu/Navigation/ComponentNavigation/App.fs:31-48 | samples/maui/Navigation/ComponentNavigation/Sample.fs:43-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 (16–17 lines × 2) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:8— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:8-24 | samples/maui/Navigation/BasicNavigation/PageA.fs:7-22 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs` and `samples/maui/Navigation/BasicNavigation/PageA.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–17 lines × 2) samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:8— samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:8-24 | samples/maui/Navigation/BasicNavigation/PageB.fs:7-22 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs` and `samples/maui/Navigation/BasicNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 4) samples/avalonia/Component/Tetris/Core.fs:193— samples/avalonia/Component/Tetris/Core.fs:193-204 | samples/avalonia/Component/Tetris/Core.fs:267-278 | samples/avalonia/Mvu/Tetris/Core.fs:187-198 | samples/avalonia/Mvu/Tetris/Core.fs:261-272 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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 (12 lines × 4) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:42— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:42-53 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:50-61 | samples/maui/Navigation/ComponentNavigation/PageB.fs:40-51 | samples/maui/Navigation/ComponentNavigation/PageC.fs:47-58 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs` and `samples/maui/Navigation/ComponentNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) samples/avalonia/Gallery/Pages/RenderTransformPage.fs:47— samples/avalonia/Gallery/Pages/RenderTransformPage.fs:47-53 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:67-73 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:87-93 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/RenderTransformPage.fs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245— samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245-251 | samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:255-261 | samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:264-270 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:245` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:254` calls `numberFormat` and `samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:264` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Low cohesion: CanvasItem (LCOM4 5) samples/avalonia/Gallery/Pages/ImplicitCanvasAnimationsPage.fs:17— CanvasItem'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: OpenGlPageControl (LCOM4 4) samples/avalonia/Gallery/Pages/OpenGLPage.fs:33— OpenGlPageControl'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.
validate-packages.validate_package (cyclomatic 24) REDACTED:30— validate-packages.validate_package has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScalarChangesEnumerator.MoveNext (cyclomatic 21) src/neutral/Fabulous.Core/WidgetDiff.fs:197— ScalarChangesEnumerator.MoveNext has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StackList`1.replace (cyclomatic 19) src/neutral/Fabulous.Core/Array.fs:208— StackList`1.replace has cyclomatic complexity 19 (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: StackArray3.combine (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
WidgetChangesEnumerator.MoveNext (cyclomatic 18) src/neutral/Fabulous.Core/WidgetDiff.fs:313— WidgetChangesEnumerator.MoveNext 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.
EnvironmentChangesEnumerator.MoveNext (cyclomatic 17) src/neutral/Fabulous.Core/WidgetDiff.fs:579— EnvironmentChangesEnumerator.MoveNext 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.
StackArray3.sortInPlace (cyclomatic 17) src/neutral/Fabulous.Core/Array.fs:328— StackArray3.sortInPlace 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. This is NOT this file's highest cyclomatic complexity: StackArray3.combine (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
validate-doc-links.validate (cyclomatic 17) eng/monorepo/validate-doc-links.py:67— validate-doc-links.validate 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.
Component.MergeAttributes (cyclomatic 16) src/neutral/Fabulous.Core/Components/Component.fs:28— Component.MergeAttributes 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.
VisualElementUpdaters.updateVisualElementFocus (cyclomatic 16) src/maui/Fabulous.MauiControls/Views/_VisualElement.fs:37— VisualElementUpdaters.updateVisualElementFocus 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.
ScalarChangesEnumerator.MoveNext (cognitive 47) src/neutral/Fabulous.Core/WidgetDiff.fs:197— ScalarChangesEnumerator.MoveNext has cognitive complexity 47 (threshold 15). Drivers by points: match/switch 6 (24 pts), if/else 8 (20 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 31). 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. This file is where this pass's cognitive complexity CONCENTRATES: src/neutral/Fabulous.Core/WidgetDiff.fs holds 4 of the 9 methods over the threshold — including the worst — and 82 of the 140 points over it (59%), 2.7× the next-largest file (eng/monorepo/validate-doc-links.py at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
validate-doc-links.validate (cognitive 45) eng/monorepo/validate-doc-links.py:67— validate-doc-links.validate has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (31 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WidgetChangesEnumerator.MoveNext (cognitive 41) src/neutral/Fabulous.Core/WidgetDiff.fs:313— WidgetChangesEnumerator.MoveNext has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (27 pts), match/switch 4 (11 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 25). 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. This file is where this pass's cognitive complexity CONCENTRATES: src/neutral/Fabulous.Core/WidgetDiff.fs holds 4 of the 9 methods over the threshold — including the worst — and 82 of the 140 points over it (59%), 2.7× the next-largest file (eng/monorepo/validate-doc-links.py at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EnvironmentChangesEnumerator.MoveNext (cognitive 34) src/neutral/Fabulous.Core/WidgetDiff.fs:579— EnvironmentChangesEnumerator.MoveNext has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 4 (11 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 19). 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. This file is where this pass's cognitive complexity CONCENTRATES: src/neutral/Fabulous.Core/WidgetDiff.fs holds 4 of the 9 methods over the threshold — including the worst — and 82 of the 140 points over it (59%), 2.7× the next-largest file (eng/monorepo/validate-doc-links.py at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
validate-packages.validate_package (cognitive 29) REDACTED:30— validate-packages.validate_package has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 8, loops 3 (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.
NavigationPageUpdaters.applyDiffNavigationPagePages (cognitive 23) src/maui/Fabulous.MauiControls/Views/Pages/NavigationPage.fs:110— NavigationPageUpdaters.applyDiffNavigationPagePages has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 1 (2 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.
WidgetCollectionChangesEnumerator.MoveNext (cognitive 20) src/neutral/Fabulous.Core/WidgetDiff.fs:430— WidgetCollectionChangesEnumerator.MoveNext has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (8 pts), boolean chains 1 (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. This file is where this pass's cognitive complexity CONCENTRATES: src/neutral/Fabulous.Core/WidgetDiff.fs holds 4 of the 9 methods over the threshold — including the worst — and 82 of the 140 points over it (59%), 2.7× the next-largest file (eng/monorepo/validate-doc-links.py at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
VisualElementUpdaters.updateVisualElementFocus (cognitive 20) src/maui/Fabulous.MauiControls/Views/_VisualElement.fs:37— VisualElementUpdaters.updateVisualElementFocus has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 6 (11 pts), if/else 4 (9 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.
StackList`1.replace (cognitive 16) src/neutral/Fabulous.Core/Array.fs:208— StackList`1.replace has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 6 (7 pts) (nesting depth added 5). 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· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:1— src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:1-52 | src/avalonia/Fabulous.Avalonia/Views/MenuItems/MenuItem.fs:1-119 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (104–105 lines × 2) src/avalonia/Fabulous.Avalonia/Component.fs:29— src/avalonia/Fabulous.Avalonia/Component.fs:29-132 | src/neutral/Fabulous.Core/Components/Modifiers.fs:7-111 — before extracting anything, compare `src/avalonia/Fabulous.Avalonia/Component.fs` and `src/neutral/Fabulous.Core/Components/Modifiers.fs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (52 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Controls/Expander.Components.fs:22— src/avalonia/Fabulous.Avalonia/Views/Controls/Expander.Components.fs:22-73 | src/avalonia/Fabulous.Avalonia/Views/Controls/Expander.fs:26-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Views/Controls/Expander.Components.fs:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (33 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:386— src/avalonia/Fabulous.Avalonia/Attributes.fs:386-418 | src/avalonia/Fabulous.Avalonia/Attributes.fs:495-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 4) src/neutral/Fabulous.Core/WidgetDiff.fs:189— src/neutral/Fabulous.Core/WidgetDiff.fs:189-204 | src/neutral/Fabulous.Core/WidgetDiff.fs:305-320 | src/neutral/Fabulous.Core/WidgetDiff.fs:422-437 | src/neutral/Fabulous.Core/WidgetDiff.fs:571-586 — 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–15 lines × 2) src/neutral/Fabulous.Core/WidgetDiff.fs:328— src/neutral/Fabulous.Core/WidgetDiff.fs:328-338 | src/neutral/Fabulous.Core/WidgetDiff.fs:445-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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:434— src/avalonia/Fabulous.Avalonia/Attributes.fs:434-445 | src/avalonia/Fabulous.Avalonia/Attributes.fs:458-468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:434` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–12 lines × 2) src/avalonia/Fabulous.Avalonia/Attributes.fs:461— src/avalonia/Fabulous.Avalonia/Attributes.fs:461-472 | src/avalonia/Fabulous.Avalonia/Attributes.fs:568-576 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:461` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 3) src/avalonia/Fabulous.Avalonia/Attributes.fs:433— src/avalonia/Fabulous.Avalonia/Attributes.fs:433-441 | src/avalonia/Fabulous.Avalonia/Attributes.fs:457-465 | src/neutral/Fabulous.Core/Attributes.fs:330-339 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/avalonia/Fabulous.Avalonia/Attributes.fs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) src/avalonia/Fabulous.Avalonia/Views/Media/Geometries/LineGeometry.fs:1— src/avalonia/Fabulous.Avalonia/Views/Media/Geometries/LineGeometry.fs:1-41 | src/avalonia/Fabulous.Avalonia/Views/Media/PathSegments/QuadraticBezierSegment.fs:1-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (32 lines × 2) src/maui/Fabulous.MauiControls/Views/Shapes/Geometries/RectangleGeometry.fs:1— src/maui/Fabulous.MauiControls/Views/Shapes/Geometries/RectangleGeometry.fs:1-33 | src/maui/Fabulous.MauiControls/Views/Shapes/Segments/LineSegment.fs:1-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Near-duplicate member pair (309 shared lines) samples/avalonia/Component/Tetris/Core.fs:1— samples/avalonia/Component/Tetris/Core.fs:1-346 | samples/avalonia/Mvu/Tetris/Core.fs:1-329 — These two members are variants of one another: 309 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 (248 shared lines) samples/maui/Components/TicTacComponent/App.fs:1— samples/maui/Components/TicTacComponent/App.fs:1-263 | samples/maui/TicTacToe/App.fs:1-266 — These two members are variants of one another: 248 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 (101 shared lines) samples/avalonia/Component/TicTacToe/App.fs:1— samples/avalonia/Component/TicTacToe/App.fs:1-226 | samples/avalonia/Mvu/TicTacToe/App.fs:1-266 — These two members are variants of one another: 101 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:1— samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:1-47 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:1-83 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:1-59 | samples/maui/Navigation/ComponentNavigation/PageB.fs:1-78 | samples/maui/Navigation/NavigationPath/PageB.fs:1-51 — 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 (136–138 lines × 2) samples/avalonia/Component/Tetris/Core.fs:33— samples/avalonia/Component/Tetris/Core.fs:33-168 | samples/avalonia/Mvu/Tetris/Core.fs:25-162 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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 (106 lines × 2) samples/maui/Components/TicTacComponent/App.fs:3— samples/maui/Components/TicTacComponent/App.fs:3-108 | samples/maui/TicTacToe/App.fs:3-108 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/Components/TicTacComponent/App.fs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (77–80 lines × 2) samples/maui/Components/TicTacComponent/App.fs:112— samples/maui/Components/TicTacComponent/App.fs:112-188 | samples/maui/TicTacToe/App.fs:112-191 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/Components/TicTacComponent/App.fs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (55 lines × 2) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:11— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:11-65 | samples/maui/Navigation/ComponentNavigation/PageC.fs:8-62 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs` and `samples/maui/Navigation/ComponentNavigation/PageC.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (44 lines × 2) samples/avalonia/Gallery/Pages/GlyphRunPage.fs:16— samples/avalonia/Gallery/Pages/GlyphRunPage.fs:16-59 | samples/avalonia/Gallery/Pages/GlyphRunPage.fs:64-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (42 lines × 2) samples/maui/Components/TicTacComponent/App.fs:222— samples/maui/Components/TicTacComponent/App.fs:222-263 | samples/maui/TicTacToe/App.fs:206-247 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/maui/Components/TicTacComponent/App.fs:222` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (41 lines × 3) samples/avalonia/Component/CounterApp/App.fs:13— samples/avalonia/Component/CounterApp/App.fs:13-53 | samples/avalonia/Component/MultiWindow/App.fs:13-53 | samples/avalonia/Component/MultiWindow/App.fs:69-109 — `samples/avalonia/Component/CounterApp/App.fs` and `samples/avalonia/Component/MultiWindow/App.fs` 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 1 separate duplicated blocks between them, totalling at least 41 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/CounterApp/App.fs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (40 lines × 2) samples/avalonia/Mvu/Navigation/BasicNavigation/App.fs:20— samples/avalonia/Mvu/Navigation/BasicNavigation/App.fs:20-59 | samples/maui/Navigation/BasicNavigation/Sample.fs:17-56 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (34 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:15— samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:15-48 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs:15-48 | samples/maui/Navigation/NavigationPath/NavigationState.fs:15-48 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs` as WHOLE FILES: this scan already matched 3 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (34 lines × 2) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:33— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:33-66 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:33-66 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33–34 lines × 2) samples/avalonia/Component/TicTacToe/App.fs:14— samples/avalonia/Component/TicTacToe/App.fs:14-47 | samples/avalonia/Mvu/TicTacToe/App.fs:15-47 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 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 (33 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:8— samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:8-40 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:10-42 | samples/maui/Navigation/NavigationPath/PageC.fs:8-40 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/PageC.fs` and `samples/maui/Navigation/NavigationPath/PageC.fs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/maui/Navigation/NavigationPath/PageC.fs:41` calls `ContentPage` and `samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:41` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (31 lines × 8) samples/avalonia/Mvu/CounterApp/App.fs:22— samples/avalonia/Mvu/CounterApp/App.fs:22-52 | samples/avalonia/Mvu/MultiWindow/App.fs:25-55 | samples/avalonia/Mvu/MultiWindow/App.fs:126-156 | samples/maui/Components/MvuCounter/App.fs:20-50 | samples/maui/CounterApp/App.fs:20-50 | templates/avalonia/content/blank/App.fs:22-52 | templates/avalonia/content/desktop/App.fs:22-52 | templates/avalonia/content/multi/NewApp/App.fs:23-53 — `samples/avalonia/Mvu/CounterApp/App.fs` and `samples/avalonia/Mvu/MultiWindow/App.fs` 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 4 separate duplicated blocks between them, totalling at least 93 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Mvu/MultiWindow/App.fs:57` calls `ofEffect`, `ShowWindow`, `HideWindow` and `samples/avalonia/Mvu/CounterApp/App.fs:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (29–30 lines × 2) samples/avalonia/Gallery/Pages/CarouselPage.fs:79— samples/avalonia/Gallery/Pages/CarouselPage.fs:79-107 | samples/avalonia/Gallery/Pages/PageTransitions.fs:98-127 — before extracting anything, compare `samples/avalonia/Gallery/Pages/CarouselPage.fs` and `samples/avalonia/Gallery/Pages/PageTransitions.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/CarouselPage.fs:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) samples/avalonia/Gallery/Pages/PopupPage.fs:33— samples/avalonia/Gallery/Pages/PopupPage.fs:33-62 | samples/avalonia/Gallery/Pages/ToolTipPage.fs:33-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (28 lines × 2) samples/avalonia/Gallery/Pages/GridPage.fs:322— samples/avalonia/Gallery/Pages/GridPage.fs:322-349 | samples/avalonia/Gallery/Pages/GridPage.fs:357-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/GridPage.fs:322` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (27 lines × 3) samples/avalonia/Mvu/CounterApp/App.fs:54— samples/avalonia/Mvu/CounterApp/App.fs:54-80 | samples/avalonia/Mvu/MultiWindow/App.fs:61-87 | samples/avalonia/Mvu/MultiWindow/App.fs:162-188 — `samples/avalonia/Mvu/CounterApp/App.fs` and `samples/avalonia/Mvu/MultiWindow/App.fs` 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 4 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/CounterApp/App.fs:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Mvu/MultiWindow/App.fs:57` calls `ofEffect`, `ShowWindow`, `HideWindow` and `samples/avalonia/Mvu/CounterApp/App.fs:52` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24–26 lines × 2) samples/avalonia/Gallery/Pages/ShapesPage.fs:38— samples/avalonia/Gallery/Pages/ShapesPage.fs:38-63 | samples/maui/Gallery/Samples/Shapes.fs:49-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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/ShapesPage.fs:38` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (4–24 lines × 5) samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:8— samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:8-31 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:37-40 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:10-33 | samples/maui/Navigation/ComponentNavigation/PageB.fs:35-38 | samples/maui/Navigation/NavigationPath/PageB.fs:8-31 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/PageB.fs` and `samples/maui/Navigation/NavigationPath/PageB.fs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/maui/Navigation/NavigationPath/PageB.fs:32` calls `ContentPage` and `samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:32` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17–24 lines × 2) samples/avalonia/Component/Tetris/App.fs:681— samples/avalonia/Component/Tetris/App.fs:681-704 | samples/avalonia/Component/Tetris/App.fs:720-736 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/Tetris/App.fs:681` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16–24 lines × 2) templates/avalonia/content/blank/App.fs:65— templates/avalonia/content/blank/App.fs:65-88 | templates/avalonia/content/desktop/App.fs:65-80 — `templates/avalonia/content/blank/App.fs` and `templates/avalonia/content/desktop/App.fs` 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 4 separate duplicated blocks between them, totalling at least 95 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. Read the line range as the matched WINDOW rather than a finished unit: at `templates/avalonia/content/blank/App.fs:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `templates/avalonia/content/desktop/App.fs:80` calls `DesktopApplication`, `Window` and `templates/avalonia/content/blank/App.fs:88` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14–23 lines × 2) samples/maui/WinUICompat/HelloWorld.Fabulous/App.fs:39— samples/maui/WinUICompat/HelloWorld.Fabulous/App.fs:39-52 | templates/maui/content/blank/App.fs:38-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `templates/maui/content/blank/App.fs:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17–21 lines × 2) samples/avalonia/Mvu/Navigation/NavigationPath/App.fs:20— samples/avalonia/Mvu/Navigation/NavigationPath/App.fs:20-40 | samples/maui/Navigation/NavigationPath/Sample.fs:17-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 6) samples/avalonia/Mvu/CounterApp/App.fs:70— samples/avalonia/Mvu/CounterApp/App.fs:70-89 | samples/avalonia/Mvu/MultiWindow/App.fs:77-96 | samples/avalonia/Mvu/MultiWindow/App.fs:178-197 | templates/avalonia/content/blank/App.fs:55-74 | templates/avalonia/content/desktop/App.fs:55-74 | templates/avalonia/content/multi/NewApp/App.fs:56-75 — `samples/avalonia/Mvu/CounterApp/App.fs` and `samples/avalonia/Mvu/MultiWindow/App.fs` 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 4 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/CounterApp/App.fs:70` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 3) samples/avalonia/Gallery/Pages/TreeView/SimpleTreeView.fs:21— samples/avalonia/Gallery/Pages/TreeView/SimpleTreeView.fs:21-40 | samples/avalonia/Gallery/Pages/TreeView/SimpleTreeViewItem.fs:32-51 | samples/avalonia/Gallery/Pages/TreeView/TreeViewWithNodeInteraction.fs:66-85 — before extracting anything, compare `samples/avalonia/Gallery/Pages/TreeView/SimpleTreeView.fs` and `samples/avalonia/Gallery/Pages/TreeView/SimpleTreeViewItem.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 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–20 lines × 3) samples/avalonia/Mvu/TicTacToe/App.fs:153— samples/avalonia/Mvu/TicTacToe/App.fs:153-168 | samples/maui/Components/TicTacComponent/App.fs:152-171 | samples/maui/TicTacToe/App.fs:152-171 — before extracting anything, compare `samples/maui/Components/TicTacComponent/App.fs` and `samples/maui/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 280 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–20 lines × 2) samples/avalonia/Gallery/Pages/AcrylicPage.fs:142— samples/avalonia/Gallery/Pages/AcrylicPage.fs:142-160 | samples/avalonia/Gallery/Pages/AcrylicPage.fs:162-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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/AcrylicPage.fs:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) samples/maui/Navigation/ComponentNavigation/PageA.fs:55— samples/maui/Navigation/ComponentNavigation/PageA.fs:55-72 | samples/maui/Navigation/NavigationPath/PageA.fs:34-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 6) samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:61— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:61-77 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:62-78 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:70-86 | samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:40-56 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:38-54 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:47-63 — `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs` 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 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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/ComponentNavigation/PageA.fs:61` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–16 lines × 2) samples/avalonia/Gallery/Pages/SelectableTextBlockPage.fs:53— samples/avalonia/Gallery/Pages/SelectableTextBlockPage.fs:53-68 | samples/avalonia/Gallery/Pages/TextBlockPage.fs:132-144 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/SelectableTextBlockPage.fs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 16) samples/maui/Calculator/Platforms/Android/MainActivity.fs:3— samples/maui/Calculator/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Components/HelloComponent/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Components/MultipleMvus/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Components/MvuCounter/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Components/SimpleCounter/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Components/TicTacComponent/Platforms/Android/MainActivity.fs:3-17 | samples/maui/CounterApp/Platforms/Android/MainActivity.fs:3-17 | samples/maui/HelloWorld/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Maps/HelloMap/Platforms/Android/MainActivity.fs:3-17 | samples/maui/MediaElement/HelloMediaElement/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Navigation/BasicNavigation/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Navigation/ComponentNavigation/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Navigation/NavigationPath/Platforms/Android/MainActivity.fs:3-17 | samples/maui/Playground/Platforms/Android/MainActivity.fs:3-17 | samples/maui/TicTacToe/Platforms/Android/MainActivity.fs:3-17 | templates/maui/content/blank/Platforms/Android/MainActivity.fs:3-17 — before extracting anything, compare `samples/maui/Calculator/Platforms/Android/MainActivity.fs` and `samples/maui/Components/HelloComponent/Platforms/Android/MainActivity.fs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 5) samples/maui/Components/MultipleMvus/Platforms/Tizen/Main.fs:1— samples/maui/Components/MultipleMvus/Platforms/Tizen/Main.fs:1-15 | samples/maui/Components/MvuCounter/Platforms/Tizen/Main.fs:1-15 | samples/maui/Components/SimpleCounter/Platforms/Tizen/Main.fs:1-15 | samples/maui/CounterApp/Platforms/Tizen/Main.fs:1-15 | samples/maui/Playground/Platforms/Tizen/Main.fs:1-15 — before extracting anything, compare `samples/maui/Components/MultipleMvus/Platforms/Tizen/Main.fs` and `samples/maui/Components/MvuCounter/Platforms/Tizen/Main.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 16) samples/maui/Calculator/Platforms/Tizen/Main.fs:3— samples/maui/Calculator/Platforms/Tizen/Main.fs:3-16 | samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs:3-16 | samples/maui/Components/MultipleMvus/Platforms/Tizen/Main.fs:3-16 | samples/maui/Components/MvuCounter/Platforms/Tizen/Main.fs:3-16 | samples/maui/Components/SimpleCounter/Platforms/Tizen/Main.fs:3-16 | samples/maui/Components/TicTacComponent/Platforms/Tizen/Main.fs:3-16 | samples/maui/CounterApp/Platforms/Tizen/Main.fs:3-16 | samples/maui/HelloWorld/Platforms/Tizen/Main.fs:3-16 | samples/maui/Maps/HelloMap/Platforms/Tizen/Main.fs:3-16 | samples/maui/MediaElement/HelloMediaElement/Platforms/Tizen/Main.fs:3-16 | samples/maui/Navigation/BasicNavigation/Platforms/Tizen/Main.fs:3-16 | samples/maui/Navigation/ComponentNavigation/Platforms/Tizen/Main.fs:3-16 | samples/maui/Navigation/NavigationPath/Platforms/Tizen/Main.fs:3-16 | samples/maui/Playground/Platforms/Tizen/Main.fs:3-16 | samples/maui/TicTacToe/Platforms/Tizen/Main.fs:3-16 | templates/maui/content/blank/Platforms/Tizen/Main.fs:3-16 — before extracting anything, compare `samples/maui/Calculator/Platforms/Tizen/Main.fs` and `samples/maui/Components/HelloComponent/Platforms/Tizen/Main.fs` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 6) samples/maui/Calculator/MauiProgram.fs:3— samples/maui/Calculator/MauiProgram.fs:3-16 | samples/maui/CounterApp/MauiProgram.fs:3-16 | samples/maui/Playground/MauiProgram.fs:3-16 | samples/maui/TicTacToe/MauiProgram.fs:3-16 | samples/maui/WinUICompat/HelloWorld.Fabulous/MauiProgram.fs:3-16 | templates/maui/content/blank/MauiProgram.fs:3-16 — `samples/maui/Calculator/MauiProgram.fs` and `samples/maui/CounterApp/MauiProgram.fs` 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 1 separate duplicated blocks between them, totalling at least 14 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–14 lines × 2) samples/avalonia/Gallery/Pages/AnimationsPage.fs:65— samples/avalonia/Gallery/Pages/AnimationsPage.fs:65-75 | samples/avalonia/Gallery/Pages/TransitionsPage.fs:82-95 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AnimationsPage.fs` and `samples/avalonia/Gallery/Pages/TransitionsPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/AnimationsPage.fs:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/TransitionsPage.fs:95` calls `style`, `classes` and `samples/avalonia/Gallery/Pages/AnimationsPage.fs:75` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 48) samples/avalonia/Gallery/Pages/AcrylicPage.fs:73— samples/avalonia/Gallery/Pages/AcrylicPage.fs:73-85 | samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:52-64 | samples/avalonia/Gallery/Pages/AsyncImagePage.fs:41-55 | samples/avalonia/Gallery/Pages/AutoCompleteBoxPage.fs:389-401 | samples/avalonia/Gallery/Pages/ButtonSpinnerPage.fs:40-52 | samples/avalonia/Gallery/Pages/CanvasPage.fs:57-69 | samples/avalonia/Gallery/Pages/CarouselPage.fs:60-74 | samples/avalonia/Gallery/Pages/CheckBoxPage.fs:33-45 | samples/avalonia/Gallery/Pages/ClipboardPage.fs:167-179 | samples/avalonia/Gallery/Pages/ColorPickerPage.fs:44-58 | samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs:32-44 | samples/avalonia/Gallery/Pages/ContextMenuPage.fs:33-45 | samples/avalonia/Gallery/Pages/CursorPage.fs:54-66 | samples/avalonia/Gallery/Pages/DragAndDropPage.fs:228-240 | samples/avalonia/Gallery/Pages/DropDownButtonPage.fs:33-45 | samples/avalonia/Gallery/Pages/ExpanderPage.fs:29-41 | samples/avalonia/Gallery/Pages/ExpressionAnimation.fs:45-57 | samples/avalonia/Gallery/Pages/GalaxyAnimation.fs:99-111 | samples/avalonia/Gallery/Pages/ImplicitCanvasAnimationsPage.fs:188-200 | samples/avalonia/Gallery/Pages/LayoutTransformControlPage.fs:23-35 | samples/avalonia/Gallery/Pages/ListBoxPage.fs:109-121 | samples/avalonia/Gallery/Pages/MaskedTextBoxPage.fs:20-32 | samples/avalonia/Gallery/Pages/MenuFlyoutPage.fs:26-38 | samples/avalonia/Gallery/Pages/MenuPage.fs:22-34 | samples/avalonia/Gallery/Pages/NotificationsPage.fs:169-183 | samples/avalonia/Gallery/Pages/OpenGLPage.fs:445-459 | samples/avalonia/Gallery/Pages/PageTransitions.fs:81-93 | samples/avalonia/Gallery/Pages/ProgressBarPage.fs:25-37 | samples/avalonia/Gallery/Pages/RadioButtonPage.fs:125-137 | samples/avalonia/Gallery/Pages/RepeatButtonPage.fs:21-33 | samples/avalonia/Gallery/Pages/ScrollBarPage.fs:26-38 | samples/avalonia/Gallery/Pages/SelectableTextBlockPage.fs:26-38 | samples/avalonia/Gallery/Pages/SplitViewPage.fs:23-35 | samples/avalonia/Gallery/Pages/StackPanelPage.fs:28-40 | samples/avalonia/Gallery/Pages/TabControlPage.fs:40-54 | samples/avalonia/Gallery/Pages/TextBoxPage.fs:30-42 | samples/avalonia/Gallery/Pages/ThemeAwarePage.fs:49-61 | samples/avalonia/Gallery/Pages/ToggleButtonPage.fs:74-86 | samples/avalonia/Gallery/Pages/ToggleSwitchPage.fs:42-54 | samples/avalonia/Gallery/Pages/TransitioningContentControlPage.fs:100-112 | samples/avalonia/Gallery/Pages/TreeView/SimpleTreeView.fs:48-60 | samples/avalonia/Gallery/Pages/TreeView/SimpleTreeViewItem.fs:64-76 | samples/avalonia/Gallery/Pages/TreeView/TreeViewWithNodeInteraction.fs:105-117 | samples/avalonia/Gallery/Pages/Vector3KeyFrameAnimation.fs:49-61 | samples/avalonia/Gallery/Pages/ViewBoxPage.fs:25-37 | samples/avalonia/Mvu/CounterApp/App.fs:54-66 | samples/avalonia/Mvu/DrawingApp/App.fs:197-211 | samples/avalonia/Mvu/GitHubClient/App.fs:106-118 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AdornerLayerPage.fs` and `samples/avalonia/Gallery/Pages/ThemeAwarePage.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/PageTransitions.fs:97` calls `VStack` and `samples/avalonia/Gallery/Pages/CarouselPage.fs:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 6) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:11— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:11-23 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:11-23 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageC.fs:11-23 | samples/maui/Navigation/BasicNavigation/PageA.fs:10-22 | samples/maui/Navigation/BasicNavigation/PageB.fs:10-22 | samples/maui/Navigation/BasicNavigation/PageC.fs:10-22 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs` and `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:52— samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:52-64 | samples/avalonia/Gallery/Pages/ThemeAwarePage.fs:49-61 | samples/avalonia/Gallery/Pages/UniformGridPage.fs:20-34 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AdornerLayerPage.fs` and `samples/avalonia/Gallery/Pages/ThemeAwarePage.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 7) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:9— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:9-20 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:9-20 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageC.fs:9-20 | samples/maui/Components/MultipleMvus/App.fs:9-20 | samples/maui/Navigation/BasicNavigation/PageA.fs:8-19 | samples/maui/Navigation/BasicNavigation/PageB.fs:8-19 | samples/maui/Navigation/BasicNavigation/PageC.fs:8-19 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs` and `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 × 3) samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34— samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34-45 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:55-65 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:75-85 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (2–12 lines × 7) samples/avalonia/Gallery/Pages/ThumbPage.fs:146— samples/avalonia/Gallery/Pages/ThumbPage.fs:146-148 | samples/avalonia/Gallery/Pages/ThumbPage.fs:193-204 | samples/avalonia/Gallery/Pages/ThumbPage.fs:209-220 | samples/avalonia/Gallery/Pages/ThumbPage.fs:224-225 | samples/avalonia/Gallery/Pages/ThumbPage.fs:247-248 | samples/avalonia/Gallery/Pages/ThumbPage.fs:270-271 | samples/avalonia/Gallery/Pages/ThumbPage.fs:293-294 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/ThumbPage.fs:191` calls `SetLeft`, `GetLeft` and `samples/avalonia/Gallery/Pages/ThumbPage.fs:222` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 5) samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:28— samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:28-38 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:39-48 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:30-40 | samples/maui/Navigation/ComponentNavigation/PageC.fs:36-45 | samples/maui/Navigation/NavigationPath/PageC.fs:28-38 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/PageC.fs` and `samples/maui/Navigation/NavigationPath/PageC.fs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/maui/Navigation/NavigationPath/PageC.fs:41` calls `ContentPage` and `samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:41` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (3–10 lines × 6) samples/avalonia/Component/Tetris/Core.fs:172— samples/avalonia/Component/Tetris/Core.fs:172-181 | samples/avalonia/Component/Tetris/Core.fs:246-255 | samples/avalonia/Component/Tetris/Core.fs:259-261 | samples/avalonia/Mvu/Tetris/Core.fs:166-175 | samples/avalonia/Mvu/Tetris/Core.fs:240-249 | samples/avalonia/Mvu/Tetris/Core.fs:253-255 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 4) samples/avalonia/Component/TicTacToe/App.fs:57— samples/avalonia/Component/TicTacToe/App.fs:57-66 | samples/avalonia/Mvu/TicTacToe/App.fs:79-88 | samples/maui/Components/TicTacComponent/App.fs:102-111 | samples/maui/TicTacToe/App.fs:102-111 — before extracting anything, compare `samples/avalonia/Component/TicTacToe/App.fs` and `samples/avalonia/Mvu/TicTacToe/App.fs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 102 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Component/TicTacToe/App.fs:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 6) samples/avalonia/Gallery/Pages/ThumbPage.fs:136— samples/avalonia/Gallery/Pages/ThumbPage.fs:136-142 | samples/avalonia/Gallery/Pages/ThumbPage.fs:182-188 | samples/avalonia/Gallery/Pages/ThumbPage.fs:237-243 | samples/avalonia/Gallery/Pages/ThumbPage.fs:260-266 | samples/avalonia/Gallery/Pages/ThumbPage.fs:283-289 | samples/avalonia/Gallery/Pages/ThumbPage.fs:306-312 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/ThumbPage.fs:233` calls `SetLeft` and `samples/avalonia/Gallery/Pages/ThumbPage.fs:133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (2–7 lines × 6) samples/avalonia/Component/Tetris/Core.fs:185— samples/avalonia/Component/Tetris/Core.fs:185-191 | samples/avalonia/Component/Tetris/Core.fs:262-263 | samples/avalonia/Component/Tetris/Core.fs:264-266 | samples/avalonia/Mvu/Tetris/Core.fs:179-185 | samples/avalonia/Mvu/Tetris/Core.fs:256-257 | samples/avalonia/Mvu/Tetris/Core.fs:258-260 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 6) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:24— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:24-29 | samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:24-29 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:24-29 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationTypes.fs:24-29 | samples/maui/Navigation/ComponentNavigation/Navigation.fs:24-29 | samples/maui/Navigation/NavigationPath/NavigationTypes.fs:24-29 — before extracting anything, compare `samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs` and `samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34— samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34-39 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:55-60 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:75-80 | samples/avalonia/Gallery/Pages/RenderTransformPage.fs:95-100 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/RenderTransformPage.fs:34` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 4) samples/avalonia/Component/Tetris/Core.fs:164— samples/avalonia/Component/Tetris/Core.fs:164-168 | samples/avalonia/Component/Tetris/Core.fs:238-242 | samples/avalonia/Mvu/Tetris/Core.fs:158-162 | samples/avalonia/Mvu/Tetris/Core.fs:232-236 — before extracting anything, compare `samples/avalonia/Component/Tetris/Core.fs` and `samples/avalonia/Mvu/Tetris/Core.fs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 302 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 3) samples/avalonia/Gallery/Pages/SlidingAnimation.fs:117— samples/avalonia/Gallery/Pages/SlidingAnimation.fs:117-133 | samples/avalonia/Gallery/Pages/SlidingAnimation.fs:137-152 | samples/avalonia/Gallery/Pages/SlidingAnimation.fs:155-170 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/SlidingAnimation.fs:117` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 62) samples/avalonia/Gallery/MainView.fs:143— samples/avalonia/Gallery/MainView.fs:143-157 | samples/avalonia/Gallery/Pages/AcrylicPage.fs:74-87 | samples/avalonia/Gallery/Pages/AdornerLayerPage.fs:53-66 | samples/avalonia/Gallery/Pages/AsyncImagePage.fs:44-57 | samples/avalonia/Gallery/Pages/AutoCompleteBoxPage.fs:390-403 | samples/avalonia/Gallery/Pages/CalendarDatePicker.fs:26-39 | samples/avalonia/Gallery/Pages/CalendarPage.fs:35-48 | samples/avalonia/Gallery/Pages/CanvasPage.fs:58-71 | samples/avalonia/Gallery/Pages/CarouselPage.fs:63-76 | samples/avalonia/Gallery/Pages/CheckBoxPage.fs:34-47 | samples/avalonia/Gallery/Pages/ClipboardPage.fs:168-181 | samples/avalonia/Gallery/Pages/ClippingPage.fs:63-76 | samples/avalonia/Gallery/Pages/ColorPickerPage.fs:47-60 | samples/avalonia/Gallery/Pages/ContextFlyoutPage.fs:33-46 | samples/avalonia/Gallery/Pages/ContextMenuPage.fs:34-47 | samples/avalonia/Gallery/Pages/CursorPage.fs:55-68 | samples/avalonia/Gallery/Pages/DialogsPage.fs:329-342 | samples/avalonia/Gallery/Pages/DragAndDropPage.fs:229-242 | samples/avalonia/Gallery/Pages/DrawLineAnimationPage.fs:89-102 | samples/avalonia/Gallery/Pages/DropDownButtonPage.fs:34-47 | samples/avalonia/Gallery/Pages/ExpanderPage.fs:30-43 | samples/avalonia/Gallery/Pages/ImplicitCanvasAnimationsPage.fs:189-202 | samples/avalonia/Gallery/Pages/LabelPage.fs:65-78 | samples/avalonia/Gallery/Pages/LayoutTransformControlPage.fs:24-37 | samples/avalonia/Gallery/Pages/ListBoxPage.fs:110-123 | samples/avalonia/Gallery/Pages/LottiePage.fs:108-121 | samples/avalonia/Gallery/Pages/MaskedTextBoxPage.fs:21-34 | samples/avalonia/Gallery/Pages/MenuFlyoutPage.fs:27-40 | samples/avalonia/Gallery/Pages/MenuPage.fs:23-36 | samples/avalonia/Gallery/Pages/NotificationsPage.fs:172-185 | samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:152-165 | samples/avalonia/Gallery/Pages/OpenGLPage.fs:448-461 | samples/avalonia/Gallery/Pages/PageTransitions.fs:82-95 | samples/avalonia/Gallery/Pages/Pointers/PointersPage.fs:89-102 | samples/avalonia/Gallery/Pages/ProgressBarPage.fs:26-39 | samples/avalonia/Gallery/Pages/RadioButtonPage.fs:126-139 | samples/avalonia/Gallery/Pages/RefreshContainerPage.fs:41-54 | samples/avalonia/Gallery/Pages/RepeatButtonPage.fs:22-35 | samples/avalonia/Gallery/Pages/ScrollBarPage.fs:27-40 | samples/avalonia/Gallery/Pages/SelectableTextBlockPage.fs:27-40 | samples/avalonia/Gallery/Pages/SliderPage.fs:60-73 | samples/avalonia/Gallery/Pages/SplitButtonPage.fs:76-89 | samples/avalonia/Gallery/Pages/SplitViewPage.fs:24-37 | samples/avalonia/Gallery/Pages/StackPanelPage.fs:29-42 | samples/avalonia/Gallery/Pages/TabControlPage.fs:43-56 | samples/avalonia/Gallery/Pages/TextBoxPage.fs:31-44 | samples/avalonia/Gallery/Pages/ThemeAwarePage.fs:50-63 | samples/avalonia/Gallery/Pages/ToggleButtonPage.fs:75-88 | samples/avalonia/Gallery/Pages/ToggleSplitButtonPage.fs:52-65 | samples/avalonia/Gallery/Pages/ToggleSwitchPage.fs:43-56 | samples/avalonia/Gallery/Pages/Transform3DPage.fs:59-72 | samples/avalonia/Gallery/Pages/TransitioningContentControlPage.fs:101-114 | samples/avalonia/Gallery/Pages/TreeView/SimpleTreeView.fs:49-62 | samples/avalonia/Gallery/Pages/TreeView/SimpleTreeViewItem.fs:65-78 | samples/avalonia/Gallery/Pages/TreeView/TreeViewWithNodeInteraction.fs:106-119 | samples/avalonia/Gallery/Pages/ViewBoxPage.fs:26-39 | samples/avalonia/Mvu/CounterApp/App.fs:55-68 | samples/avalonia/Mvu/DrawingApp/App.fs:200-213 | samples/avalonia/Mvu/GitHubClient/App.fs:107-120 | samples/avalonia/Mvu/MultiWindow/App.fs:62-75 | samples/avalonia/Mvu/MultiWindow/App.fs:163-176 | samples/avalonia/Mvu/TicTacToe/App.fs:184-197 — before extracting anything, compare `samples/avalonia/Gallery/Pages/AdornerLayerPage.fs` and `samples/avalonia/Gallery/Pages/ThemeAwarePage.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/MainView.fs:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `samples/avalonia/Gallery/Pages/AcrylicPage.fs:89` calls `VStack`, `ExperimentalAcrylicBorder` and `samples/avalonia/Gallery/Pages/PageTransitions.fs:97` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 6) samples/avalonia/Gallery/Pages/DragAndDropPage.fs:230— samples/avalonia/Gallery/Pages/DragAndDropPage.fs:230-244 | samples/avalonia/Gallery/Pages/LayoutTransformControlPage.fs:25-39 | samples/avalonia/Gallery/Pages/MenuPage.fs:24-38 | samples/avalonia/Gallery/Pages/PageTransitions.fs:83-97 | samples/avalonia/Gallery/Pages/StackPanelPage.fs:30-44 | samples/avalonia/Gallery/Pages/TimePickerPage.fs:23-37 — before extracting anything, compare `samples/avalonia/Gallery/Pages/DragAndDropPage.fs` and `samples/avalonia/Gallery/Pages/LayoutTransformControlPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/DragAndDropPage.fs:230` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 4) samples/avalonia/Gallery/Pages/AcrylicPage.fs:135— samples/avalonia/Gallery/Pages/AcrylicPage.fs:135-147 | samples/avalonia/Gallery/Pages/AcrylicPage.fs:155-168 | samples/avalonia/Gallery/Pages/AcrylicPage.fs:176-188 | samples/avalonia/Gallery/Pages/AcrylicPage.fs:196-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. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/Pages/AcrylicPage.fs:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 5) samples/avalonia/Gallery/MainWindow.fs:292— samples/avalonia/Gallery/MainWindow.fs:292-305 | samples/avalonia/Gallery/Pages/ButtonsPage.fs:31-43 | samples/avalonia/Gallery/Pages/ComboBoxPage.fs:37-49 | samples/avalonia/Gallery/Pages/TimePickerPage.fs:22-34 | samples/avalonia/Mvu/Navigation/BasicNavigation/App.fs:62-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Gallery/MainWindow.fs:292` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:25— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:25-35 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:25-35 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageC.fs:25-35 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs` and `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:25` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D8 · Code Coverage· No test project references Fabulous.Avalonia.ColorPicker · ×1
No test project references Fabulous.Avalonia.ColorPicker src/avalonia/Fabulous.Avalonia.ColorPicker/Fabulous.Avalonia.ColorPicker.fsproj— No test project in this repository references Fabulous.Avalonia.ColorPicker (15 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.Avalonia.DataGrid · ×1
No test project references Fabulous.Avalonia.DataGrid src/avalonia/Fabulous.Avalonia.DataGrid/Fabulous.Avalonia.DataGrid.fsproj— No test project in this repository references Fabulous.Avalonia.DataGrid (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.MauiControls.Maps · ×1
No test project references Fabulous.MauiControls.Maps src/maui/Fabulous.MauiControls.Maps/Fabulous.MauiControls.Maps.fsproj— No test project in this repository references Fabulous.MauiControls.Maps (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.Avalonia.Labs · ×1
No test project references Fabulous.Avalonia.Labs src/avalonia/Fabulous.Avalonia.Labs/Fabulous.Avalonia.Labs.fsproj— No test project in this repository references Fabulous.Avalonia.Labs (4 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.Avalonia.TreeDataGrid · ×1
No test project references Fabulous.Avalonia.TreeDataGrid src/avalonia/Fabulous.Avalonia.TreeDataGrid/Fabulous.Avalonia.TreeDataGrid.fsproj— No test project in this repository references Fabulous.Avalonia.TreeDataGrid (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.MauiControls.MediaElement · ×1
No test project references Fabulous.MauiControls.MediaElement src/maui/Fabulous.MauiControls.MediaElement/Fabulous.MauiControls.MediaElement.fsproj— No test project in this repository references Fabulous.MauiControls.MediaElement (3 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references FSharp.Maui.WinUICompat · ×1
No test project references FSharp.Maui.WinUICompat src/maui/FSharp.Maui.WinUICompat/FSharp.Maui.WinUICompat.csproj— No test project in this repository references FSharp.Maui.WinUICompat (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.Avalonia.Diagnostics · ×1
No test project references Fabulous.Avalonia.Diagnostics src/avalonia/Fabulous.Avalonia.Diagnostics/Fabulous.Avalonia.Diagnostics.fsproj— No test project in this repository references Fabulous.Avalonia.Diagnostics (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Fabulous.Avalonia.ItemsRepeater · ×1
No test project references Fabulous.Avalonia.ItemsRepeater src/avalonia/Fabulous.Avalonia.ItemsRepeater/Fabulous.Avalonia.ItemsRepeater.fsproj— No test project in this repository references Fabulous.Avalonia.ItemsRepeater (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 58.6% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
Unfinished stub — throws NotImplementedException src/maui/FSharp.Maui.WinUICompat/Platforms/Windows/App.xaml.cs:22— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/maui/FSharp.Maui.WinUICompat/Platforms/Windows/App.xaml.cs:22— `CreateMauiApp` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: src/maui/Fabulous.MauiControls/Views/Collections/ListView.fs, src/maui/Fabulous.MauiControls/Views/Controls/DatePicker.fs, src/maui/Fabulous.MauiControls/Views/Collections/CollectionView.fs, src/maui/Fabulous.MauiControls/Views/Controls/TimePicker.fs, src/neutral/Fabulous.Core/Components/Modifiers.fs, src/maui/Fabulous.MauiControls/Views/Collections/_ItemsView.fs, src/maui/Fabulous.MauiControls/Views/MenuItems/MenuItem.fs, src/maui/FSharp.Maui.WinUICompat/Platforms/Windows/App.xaml.cs (+2 more). Pair on, review, or document these before any departure.
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 — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `ControlSamples` (352 LoC, 2535 public types across 1155 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
README/code drift src/maui/Fabulous.MauiControls.MediaElement/README.md:5— src/maui/Fabulous.MauiControls.MediaElement/README.md links to `Fabulous_MauiControls_MediaElement_Demo.gif`, but `src/maui/Fabulous.MauiControls.MediaElement/Fabulous_MauiControls_MediaElement_Demo.gif` 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.
No SAST — No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 282581 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
PF2 · Allocation hygiene· No allocation-aware APIs detected · ×1
No allocation-aware APIs detected — No Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc, ValueTask or buffer-writer usage was found. If this code sits on a hot path, these reduce the GC pressure it creates — a bonus, not a requirement.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.2 `!` suppressions per 1k syntax nodes — 4 suppression(s) across the 3314 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a17983-8835-71b4-90d7-9ccd7e3ec309 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 74 · Warnings: 309 · Recommendations: 15 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 18:40 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.