Public report — Fabulous, published 10 Sep 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.8 (frozen) · verify this surveyFiledcd_39e671c44a5d4d8dbdfe27c151f7a823
Filed 10 September 2026, 21:04 UTC
Public
Medium · 55,865 LoC · 2 projects · rebuild ~0.4 person-years · weakest lens: Security (27%)
Findings by grade
73 critical236 serious19 minor5 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
10 September 2026, 20:59 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
310findings with an exact file:lineof 328 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
63/120dimensions across the health lenses55865 LoC · 2 projects — wide & deep
This system presents a fragile security posture that threatens the business’s operational stability and reputation. With an overall health score of 47%, the asset is functional but carries significant risk, particularly in how it handles external threats and internal controls. While the underlying code is maintainable and the architecture is sound, the low security maturity means the organization is exposed to potential breaches and compliance failures that could halt delivery or incur heavy remediation costs.
The value at stake is moderate, with approximately 55,000 lines of production code representing a rebuild effort of roughly 0.4 person-years, or €63,000. This is not a massive legacy monolith, but it is substantial enough that technical debt accumulates quickly if left unaddressed. The code is entirely straight-line logic with no boilerplate, suggesting a straightforward structure that is easy to understand but currently lacks the defensive layers needed for safe operation. Rebuilding is feasible, but the cost of inaction in terms of security exposure outweighs the modest cost of modernization.
The primary risk is security vulnerability. The security lens scored only 27%, indicating critical gaps in how the system validates inputs, manages dependencies, and protects data. This is not a minor oversight; it is a fundamental weakness that could lead to data breaches or unauthorized access. The second theme is operational readiness. With a readiness score of 55%, the system lacks robust testing and observability, making it difficult to detect issues before they impact users. This increases the likelihood of outages and slows down the team’s ability to respond to incidents, directly affecting customer trust and delivery speed.
On the positive side, the code health and architecture scores are strong, at 73% and 84% respectively. This means the code is clean, well-structured, and easy for new team members to pick up. The domain modeling and event-driven aspects were not measured, so their status remains unknown, but the existing foundation is solid. The immediate focus must be on resolving the 10 high-severity static analysis findings. These are the most critical vulnerabilities and offer the highest return on effort. Addressing these first will significantly reduce security exposure and lay the groundwork for improving overall operational readiness.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
307 finding(s) are new versus the previous scan (2026-08-05) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 47% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified for 55,450 line(s) outside the .NET model (the tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.4 person-years of build effort (about ~€63,000 to rebuild). Its weakest lens is Security at 27% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — desktop/game, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 7 Medium finding(s) in Static Analysis (SAST) — start with index.html (5), validate-packages.py, header.html.
Resolve the 10 High finding(s) charged to Static Analysis (SAST) — the other 59 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.4 person-years to rebuild), and its weakest lens is Security at 27%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Resolve the 10 High finding(s) charged to Static Analysis (SAST) — the other 59 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 10 High finding(s) charged to Static Analysis (SAST) — the other 59 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
1163 modules, 1666 dependencies. 2 dependency cycles across 8 modules, marked above the diagonal.
Showing the 40 most-connected modules; 1123 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
Fabulous.WidgetCollectionAttributeDefinitions uses Fabulous. Changing Fabulous can break Fabulous.WidgetCollectionAttributeDefinitions, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
6→4 Fabulous depends on Fabulous.ScalarAttributeDefinitions✕
Type pairs
2 distinct (type in Fabulous → type in Fabulous.ScalarAttributeDefinitions) references.
Fabulous uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
7→4 Fabulous.Memo depends on Fabulous.ScalarAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Memo → type in Fabulous.ScalarAttributeDefinitions) reference.
548 distinct (type in Fabulous.Avalonia → type in Fabulous) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Fabulous.Maui.Application uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.Application, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
11→5 Fabulous.Maui.Application depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Maui.Application → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Maui.Application uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Maui.Application, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
11→6 Fabulous.Maui.Application depends on Fabulous✕
Type pairs
1 distinct (type in Fabulous.Maui.Application → type in Fabulous) reference.
Fabulous.Maui.Application uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Maui.Application, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
12→4 Fabulous.Maui.NavigationPage depends on Fabulous.ScalarAttributeDefinitions✕
Type pairs
2 distinct (type in Fabulous.Maui.NavigationPage → type in Fabulous.ScalarAttributeDefinitions) references.
Fabulous.Maui.NavigationPage uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.NavigationPage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
12→5 Fabulous.Maui.NavigationPage depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Maui.NavigationPage → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Maui.NavigationPage uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Maui.NavigationPage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
12→6 Fabulous.Maui.NavigationPage depends on Fabulous✕
Type pairs
1 distinct (type in Fabulous.Maui.NavigationPage → type in Fabulous) reference.
Fabulous.Maui.NavigationPage uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Maui.NavigationPage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
13→6 Fabulous.Tests.APISketchTests.TestUI_Widgets depends on Fabulous✕
Type pairs
7 distinct (type in Fabulous.Tests.APISketchTests.TestUI_Widgets → type in Fabulous) references.
Fabulous.Tests.APISketchTests.TestUI_Widgets uses Fabulous.Memo. Changing Fabulous.Memo can break Fabulous.Tests.APISketchTests.TestUI_Widgets, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
Fabulous.Avalonia.Attributes uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Avalonia.Attributes, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
20→5 Fabulous.Avalonia.Attributes depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Avalonia.Attributes → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Avalonia.Attributes uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Avalonia.Attributes, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
20→8 Fabulous.Avalonia.Attributes depends on Fabulous.WidgetAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Avalonia.Attributes → type in Fabulous.WidgetAttributeDefinitions) reference.
Fabulous.Avalonia.Attributes uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Avalonia.Attributes, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
20→9 Fabulous.Avalonia.Attributes depends on Fabulous.Avalonia✕
Type pairs
1 distinct (type in Fabulous.Avalonia.Attributes → type in Fabulous.Avalonia) reference.
Fabulous.Avalonia.ItemsControl uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Avalonia.ItemsControl, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→5 Fabulous.Avalonia.ItemsControl depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Avalonia.ItemsControl → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Avalonia.ItemsControl uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Avalonia.ItemsControl, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→6 Fabulous.Avalonia.ItemsControl depends on Fabulous✕
Type pairs
1 distinct (type in Fabulous.Avalonia.ItemsControl → type in Fabulous) reference.
Fabulous.Avalonia.WidgetHelpers uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Avalonia.WidgetHelpers, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→6 Fabulous.Avalonia.WidgetHelpers depends on Fabulous✕
Type pairs
4 distinct (type in Fabulous.Avalonia.WidgetHelpers → type in Fabulous) references.
Fabulous.Maui.ItemsView uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.ItemsView, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
Fabulous.Maui.ItemsView uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Maui.ItemsView, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→10 Fabulous.Maui.ItemsView depends on Fabulous.Maui✕
Type pairs
1 distinct (type in Fabulous.Maui.ItemsView → type in Fabulous.Maui) reference.
Fabulous.Maui.ListView uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.ListView, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
Fabulous.Maui.ListView uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Maui.ListView, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
24→10 Fabulous.Maui.ListView depends on Fabulous.Maui✕
Type pairs
1 distinct (type in Fabulous.Maui.ListView → type in Fabulous.Maui) reference.
Fabulous.Maui.MultiPageOfPage uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.MultiPageOfPage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
25→5 Fabulous.Maui.MultiPageOfPage depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Maui.MultiPageOfPage → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Maui.MultiPageOfPage uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Maui.MultiPageOfPage, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
25→6 Fabulous.Maui.MultiPageOfPage depends on Fabulous✕
Type pairs
1 distinct (type in Fabulous.Maui.MultiPageOfPage → type in Fabulous) reference.
Fabulous.Maui.Page uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.Page, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
26→5 Fabulous.Maui.Page depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Maui.Page → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Maui.Page uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Maui.Page, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
Fabulous.Maui.RadioButton uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.RadioButton, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→6 Fabulous.Maui.RadioButton depends on Fabulous✕
Type pairs
1 distinct (type in Fabulous.Maui.RadioButton → type in Fabulous) reference.
Fabulous.Maui.RadioButton uses Fabulous.WidgetAttributeDefinitions. Changing Fabulous.WidgetAttributeDefinitions can break Fabulous.Maui.RadioButton, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
27→10 Fabulous.Maui.RadioButton depends on Fabulous.Maui✕
Type pairs
1 distinct (type in Fabulous.Maui.RadioButton → type in Fabulous.Maui) reference.
Fabulous.Maui.WidgetHelpers uses Fabulous.ScalarAttributeDefinitions. Changing Fabulous.ScalarAttributeDefinitions can break Fabulous.Maui.WidgetHelpers, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→5 Fabulous.Maui.WidgetHelpers depends on Fabulous.WidgetCollectionAttributeDefinitions✕
Type pairs
1 distinct (type in Fabulous.Maui.WidgetHelpers → type in Fabulous.WidgetCollectionAttributeDefinitions) reference.
Fabulous.Maui.WidgetHelpers uses Fabulous.WidgetCollectionAttributeDefinitions. Changing Fabulous.WidgetCollectionAttributeDefinitions can break Fabulous.Maui.WidgetHelpers, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
28→6 Fabulous.Maui.WidgetHelpers depends on Fabulous✕
Type pairs
4 distinct (type in Fabulous.Maui.WidgetHelpers → type in Fabulous) references.
NavigationSample.NavigationState uses NavigationSample.PageA. Changing NavigationSample.PageA can break NavigationSample.NavigationState, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→32 NavigationSample.NavigationState depends on NavigationSample.PageB✕
Type pairs
2 distinct (type in NavigationSample.NavigationState → type in NavigationSample.PageB) references.
NavigationSample.NavigationState uses NavigationSample.PageB. Changing NavigationSample.PageB can break NavigationSample.NavigationState, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→33 NavigationSample.NavigationState depends on NavigationSample.PageC✕
Type pairs
2 distinct (type in NavigationSample.NavigationState → type in NavigationSample.PageC) references.
NavigationSample.NavigationState uses NavigationSample.PageC. Changing NavigationSample.PageC can break NavigationSample.NavigationState, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
37→39 NavigationSample.NavigationState depends on NavigationSamplecycle✕
Type pairs
2 distinct (type in NavigationSample.NavigationState → type in NavigationSample) references.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
76
High / Critical
A02:2021 — Cryptographic Failures
4
High / Critical
Roadmap
Immediately resolve the ten high-severity static analysis findings and the seven medium-severity issues, prioritizing fixes in index.html, validate-packages.py, and header.html. Secure the deployment pipeline by verifying that required reviewers are attached to protection rules or publishing as a draft release to prevent bad builds from reaching users. Finally, restrict library types to internal by default to protect the public API contract and remove three historical secrets from WeatherApi.fs and AndroidManifest.xml.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 7 Medium finding(s) in Static Analysis (SAST) — start with index.html (5), validate-packages.py, header.html.
Resolve the 10 High finding(s) charged to Static Analysis (SAST) — the other 59 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download it.
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 — 73
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 — 236
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 — 19
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. 58 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — 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 — 63 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, 310 of 328 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.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.fs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository has NuGet-managed production source (.cs, .fs), whose `<PackageReference>` dependencies are exactly what this dimension assesses — but `dotnet list package` returned no packages, so there was nothing to assess. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED. This is a gap in the analysis run (restore or project-load failed), not a verdict about this repository. Dependencies declared for the other ecosystems present here (.fs, .py) are not read yet either.
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,034 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.
D27 Navigability — evaluation did not complete — Navigability not included (check did not complete) — excluded from the score.
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: 367 commits in the last 90 days, yet 198 of 233 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.
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.
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, 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.
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.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
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.
The LLM boundary
LLM-set scores this run (5): D19, D21, D22, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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 16 — 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
Resolve the 1 validate-packages.validate_package (cyclomatic 24) finding(s) in Cyclomatic Complexity — start with validate-packages.py. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ScalarChangesEnumerator.MoveNext (cyclomatic 21) finding(s) in Cyclomatic Complexity — start with WidgetDiff.fs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 StackList`1.replace (cyclomatic 19) finding(s) in Cyclomatic Complexity — start with Array.fs. — One of this dimension's main actionable groups (1 warning-level).
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
Resolve the 1 ScalarChangesEnumerator.MoveNext (cognitive 47) finding(s) in Cognitive Complexity — start with WidgetDiff.fs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 validate-doc-links.validate (cognitive 45) finding(s) in Cognitive Complexity — start with validate-doc-links.py. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 WidgetChangesEnumerator.MoveNext (cognitive 41) finding(s) in Cognitive Complexity — start with WidgetDiff.fs. — One of this dimension's main actionable groups (1 warning-level).
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.
181 duplicated block group(s) detected. A further 7 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 118 of the 188 are in trees this repository does not ship — vendored, example/demo, 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.
+ 89 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (10 lines × 3) finding(s) in Code Duplication — start with UniformGridPage.fs (2), DrawingPage.fs (2), Builders.fs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (19 lines × 2) finding(s) in Code Duplication — start with Program.fs (8), UniformGridPage.fs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with App.fs (2), _Element.fs, Widgets.fs. — One of this dimension's main actionable groups (8 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 · Coupling6.9 / 10Adequate✓ 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.
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage8.6 / 10Strong✓ Tool-verified
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.
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
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.
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 14 Hotspot finding(s) in Churn × Complexity Hotspots — start with App.fs (3), Core.fs (2), DialogsPage.fs. — One of this dimension's main actionable groups (14 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
12 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 233 of the 559 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
1 deducted debt markers + 0 dead symbols across 424 LoC in the .NET projects (0.4/KLoC) → score 9.2. 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: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Fabulous is an expressive declarative UI framework combining F# with the Model-View-Update architecture to build mobile and desktop apps. The documentation is comprehensive: a top-level 'Documentation' section links to the home page, get-started tutorial, authored docs, API reference, samples, and contributing; there are dedicated MAUI/Avalonia templates for getting started, usage, and media element/bindable-property examples; an architecture doc explains the declarative engine vs native backends, reconciliation, widget attributes, and a MediaElement example covering initial set-up, binding, and configuration. Fabulous.Avalonia's READMEs are clear and complete documentation of a cross-platform UI framework tailored to Avalonia with Fabulous, covering installation, usage examples, licensing guidance, and links to the main Fabulous docs. The architecture/design docs (136) provide deeper structure for controls like TreeDataGrid, ItemsRepeater, ColorPicker, and diagnostics, while XML-doc coverage is low (<25% of 173 documents).
Documentation: written for insiders · ×2avalonia/Fabulous.Avalonia.Labs/README.md
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 59 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyExemplary◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
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: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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.
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 3 Secret finding(s) in Secrets (history) — start with WeatherApi.fs (2), AndroidManifest.xml. — 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).
76 finding(s): 0 critical, 69 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), `website/layouts/index.html`, `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.
High: github-actions-mutable-action-tag · ×69.github/workflows/pages.yml:33detected by semgrep finding
Medium: use-defused-xml · ×7eng/monorepo/validate-packages.py:8detected by semgrep finding
What to do
Resolve the 10 High finding(s) charged to Static Analysis (SAST) — the other 59 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (69 issue-level, 10 of them charged here).
Resolve the 7 Medium finding(s) in Static Analysis (SAST) — start with index.html (5), validate-packages.py, header.html. — One of this dimension's main actionable groups (7 warning-level).
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 Primitives.fs, SelectableTextBlock.fs, Attributes.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 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret exported as workflow-level env 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.
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 — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
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.
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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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.
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. 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 214666 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
The release job declares an environment, but its protection rules are not visible from the repository — confirm required reviewers are attached, or publish as a draft release so a bad build can be stopped before users can download 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 — 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.
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 (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock, and, where the code is a reusable library, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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 — 54 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No 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
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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 — ~2045 lines of test source are present (.fs) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
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.
D23 Boundary Type-Coupling — At only 55k LoC across 2 projects this is a small single-purpose codebase that does not require explicit bounded contexts. No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D27 Navigability — Navigability not included (check did not complete)
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); 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.
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is mostly .fs, .py, which this pass does not read, so cohesion was not assessed for this repository. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D9 Test Distribution — Test source is present (.fs) but the test-pyramid classifier reads C# only, 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): 216 value object(s); 42 domain event(s)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check 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) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, 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 methods found
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.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:33— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:35— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: peaceiris/actions-hugo@<40-character SHA>`. This step references `peaceiris/actions-hugo@v3`; resolve the SHA it points at today with `gh api repos/peaceiris/actions-hugo/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:40— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-python@<40-character SHA>`. This step references `actions/setup-python@v5`; resolve the SHA it points at today with `gh api repos/actions/setup-python/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:45— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/configure-pages@<40-character SHA>`. This step references `actions/configure-pages@v5`; resolve the SHA it points at today with `gh api repos/actions/configure-pages/commits/v5 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:59— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-pages-artifact@<40-character SHA>`. This step references `actions/upload-pages-artifact@v3`; resolve the SHA it points at today with `gh api repos/actions/upload-pages-artifact/commits/v3 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pages.yml:74— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/deploy-pages@<40-character SHA>`. This step references `actions/deploy-pages@v4`; resolve the SHA it points at today with `gh api repos/actions/deploy-pages/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:26— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:28— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:32— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:53— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:55— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:59— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: watchdog-unpinned-package-install-in-run .github/workflows/pull_request.yml:79— This CI step installs a third-party package by name with no version, so what lands on the runner is whatever the registry serves at the moment the job happens to run. A global or tool install resolves outside every lockfile in this repository, so nothing in version control records or constrains what was installed, and two runs of an UNCHANGED workflow file can install different code. That matters more than reproducibility here: package managers execute the downloaded package's install-time scripts with the job's environment in scope, tokens included, so a compromised release or a taken-over maintainer account upstream becomes code execution inside this job — the same supply-chain exposure as a floating action reference, reached through the `run:` key instead. Name an exact version on this command, in your manager's own syntax (`pkg@1.2.3` for npm/pnpm/yarn, `pkg==1.2.3` for pip, `-v 1.2.3` for gem, `--version 1.2.3` for cargo and `dotnet tool`, a real `@v1.2.3` module version for `go install` and `go run`), or move the tool into a manifest the repository already pins and installs from — a devDependency plus `npm ci`, a `requirements.txt` fed to `pip install -r`, or a `dotnet-tools.json` restored with `dotnet tool restore`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:92— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:102— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:104— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:108— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:123— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:138— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:140— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v4`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:144— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/cache@<40-character SHA>`. This step references `actions/cache@v4`; resolve the SHA it points at today with `gh api repos/actions/cache/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:159— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:171— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/download-artifact@<40-character SHA>`. This step references `actions/download-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/download-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:177— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/upload-artifact@<40-character SHA>`. This step references `actions/upload-artifact@v4`; resolve the SHA it points at today with `gh api repos/actions/upload-artifact/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/pull_request.yml:193— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
Secret: gcp-api-key Fabulous.XamarinForms/samples/AllControls/Droid/Properties/AndroidManifest.xml @ 85fcf04:6 (committed 2019-11-26)— gitleaks matched rule 'gcp-api-key' here, in git history. Deleting the file does not remove it — the commit persists on every clone, fork and backup — so the act is to ROTATE this credential and treat it as compromised. The "Rotate the exposed credentials" row carries the full procedure, including when a `.gitattributes` provenance declaration is the correct answer instead.
Secret: generic-api-key Fabulous.XamarinForms/samples/FabulousWeather/FabulousWeather/WeatherApi.fs @ d80e1fc:8 (committed 2020-04-12)— gitleaks matched rule 'generic-api-key' here, in git history. Deleting the file does not remove it — the commit persists on every clone, fork and backup — so the act is to ROTATE this credential and treat it as compromised. The "Rotate the exposed credentials" row carries the full procedure, including when a `.gitattributes` provenance declaration is the correct answer instead.
Secret: generic-api-key samples/Xamarin.Forms/FabulousWeather/FabulousWeather/WeatherApi.fs @ cdeea7b:8 (committed 2021-11-12)— gitleaks matched rule 'generic-api-key' here, in git history. Deleting the file does not remove it — the commit persists on every clone, fork and backup — so the act is to ROTATE this credential and treat it as compromised. The "Rotate the exposed credentials" row carries the full procedure, including when a `.gitattributes` provenance declaration is the correct answer instead.
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.
Hotspot: samples/avalonia/Gallery/App.fs samples/avalonia/Gallery/App.fs:112— samples/avalonia/Gallery/App.fs changed 4 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02: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: samples/avalonia/Gallery/Pages/DialogsPage.fs samples/avalonia/Gallery/Pages/DialogsPage.fs:261— samples/avalonia/Gallery/Pages/DialogsPage.fs changed 3 times in last 90 days, max cyclomatic complexity 21 in DialogsPage.update at line 261. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/DialogsPage.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: samples/avalonia/Component/Tetris/Core.fs samples/avalonia/Component/Tetris/Core.fs:156— samples/avalonia/Component/Tetris/Core.fs changed 2 times in last 90 days, max cyclomatic complexity 30 in TetriminoModule.rotateRight at line 156. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Component/Tetris/Core.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: samples/avalonia/Mvu/Tetris/Core.fs samples/avalonia/Mvu/Tetris/Core.fs:150— samples/avalonia/Mvu/Tetris/Core.fs changed 2 times in last 90 days, max cyclomatic complexity 30 in TetriminoModule.rotateRight at line 150. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Mvu/Tetris/Core.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: samples/avalonia/Mvu/Tetris/App.fs samples/avalonia/Mvu/Tetris/App.fs:82— samples/avalonia/Mvu/Tetris/App.fs changed 2 times in last 90 days, max cyclomatic complexity 28 in App.update at line 82. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Mvu/Tetris/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: samples/avalonia/Gallery/Pages/RadioButtonPage.fs samples/avalonia/Gallery/Pages/RadioButtonPage.fs:96— samples/avalonia/Gallery/Pages/RadioButtonPage.fs changed 2 times in last 90 days, max cyclomatic complexity 26 in RadioButtonPage.update at line 96. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/RadioButtonPage.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/maui/Fabulous.MauiControls/Views/_VisualElement.fs src/maui/Fabulous.MauiControls/Views/_VisualElement.fs:37— src/maui/Fabulous.MauiControls/Views/_VisualElement.fs changed 3 times in last 90 days, max cyclomatic complexity 16 in VisualElementUpdaters.updateVisualElementFocus at line 37. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- src/maui/Fabulous.MauiControls/Views/_VisualElement.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: samples/avalonia/Component/Tetris/App.fs samples/avalonia/Component/Tetris/App.fs:195— samples/avalonia/Component/Tetris/App.fs changed 2 times in last 90 days, max cyclomatic complexity 23 in App.applyControlActions at line 195. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Component/Tetris/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: samples/avalonia/Gallery/Pages/NumericUpDownPage.fs samples/avalonia/Gallery/Pages/NumericUpDownPage.fs:85— samples/avalonia/Gallery/Pages/NumericUpDownPage.fs changed 3 times in last 90 days, max cyclomatic complexity 15 in NumericUpDownPage.update at line 85. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/NumericUpDownPage.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: samples/avalonia/Gallery/Pages/ScrollViewerPage.fs samples/avalonia/Gallery/Pages/ScrollViewerPage.fs:52— samples/avalonia/Gallery/Pages/ScrollViewerPage.fs changed 2 times in last 90 days, max cyclomatic complexity 22 in ScrollViewerPage.update at line 52. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/ScrollViewerPage.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:208— src/neutral/Fabulous.Core/Array.fs changed 2 times in last 90 days, max cyclomatic complexity 19 in StackList`1.replace at line 208. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02: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.
Hotspot: samples/avalonia/Gallery/Pages/ListBoxPage.fs samples/avalonia/Gallery/Pages/ListBoxPage.fs:52— samples/avalonia/Gallery/Pages/ListBoxPage.fs changed 2 times in last 90 days, max cyclomatic complexity 19 in ListBoxPage.update at line 52. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/ListBoxPage.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: samples/avalonia/Gallery/Pages/LottiePage.fs samples/avalonia/Gallery/Pages/LottiePage.fs:51— samples/avalonia/Gallery/Pages/LottiePage.fs changed 2 times in last 90 days, max cyclomatic complexity 15 in LottiePage.update at line 51. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/LottiePage.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: samples/avalonia/Gallery/Pages/ToggleButtonPage.fs samples/avalonia/Gallery/Pages/ToggleButtonPage.fs:38— samples/avalonia/Gallery/Pages/ToggleButtonPage.fs changed 2 times in last 90 days, max cyclomatic complexity 15 in ToggleButtonPage.update at line 38. 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-06-12..2026-09-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-12 15:27:57 +02:00' --until='2026-09-10 15:27:57 +02:00' --full-history --no-merges -- samples/avalonia/Gallery/Pages/ToggleButtonPage.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 (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) 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/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) 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/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/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 — the window is that declaration's tail, not a fragment that begins part-way through something, 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/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 (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 (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/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/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 (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) 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/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) 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/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/Component/Navigation/NavigationPath/NavigationTypes.fs:31— samples/avalonia/Component/Navigation/NavigationPath/NavigationTypes.fs:31-39 | samples/avalonia/Mvu/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 × 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.
Medium: use-defused-xml eng/monorepo/validate-packages.py:8— The Python documentation recommends using `defusedxml` instead of `xml` because the native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/layouts/index.html:36— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/layouts/index.html:163— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/layouts/index.html:169— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/layouts/index.html:182— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/layouts/index.html:183— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href website/themes/fabulous-theme/layouts/partials/header.html:21— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
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/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/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/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/CanvasPage.fs:125— samples/avalonia/Gallery/Pages/CanvasPage.fs:125-138 | samples/avalonia/Gallery/Pages/ShapesPage.fs:48-61 — before extracting anything, compare `samples/avalonia/Gallery/Pages/CanvasPage.fs` and `samples/avalonia/Gallery/Pages/ShapesPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) 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 (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) 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) 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/Mvu/Navigation/ComponentNavigation/PageB.fs:42— samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:42-53 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageC.fs:50-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 both call sites, so a change lands once.
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 (10 lines × 2) src/neutral/Fabulous.Core/WidgetDiff.fs:356— src/neutral/Fabulous.Core/WidgetDiff.fs:356-366 | src/neutral/Fabulous.Core/WidgetDiff.fs:470-479 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/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) samples/avalonia/Component/TicTacToe/App.fs:57— samples/avalonia/Component/TicTacToe/App.fs:57-66 | samples/avalonia/Mvu/TicTacToe/App.fs:79-88 — 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 (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 — the window is that declaration's tail, not a fragment that begins part-way through something, 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: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 (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/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/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/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) 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 (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) 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/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) 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 (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 (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) 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/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/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/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 (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/ComponentNavigation/Navigation.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:1-29 | samples/avalonia/Mvu/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 4 separate duplicated blocks between them, totalling at least 82 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 × 2) 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 — 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 (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 (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/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 (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/Component/Navigation/ComponentNavigation/AppMsg.fs:1— samples/avalonia/Component/Navigation/ComponentNavigation/AppMsg.fs:1-17 | samples/avalonia/Mvu/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 (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 — before extracting anything, compare `samples/avalonia/Gallery/Pages/CanvasPage.fs` and `samples/avalonia/Gallery/Pages/ShapesPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 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.
Change coupling: Primitives.fs ↔ Reconciler.fs src/neutral/Fabulous.Core/Primitives.fs— `src/neutral/Fabulous.Core/Primitives.fs` and `src/neutral/Fabulous.Core/Reconciler.fs` change together 65% of the time (11 of the 17 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 or a formatter/rename sweep 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: SelectableTextBlock.fs ↔ TextBox.fs src/avalonia/Fabulous.Avalonia/Views/Controls/SelectableTextBlock.fs— `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 or a formatter/rename sweep 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— `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 or a formatter/rename sweep 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: _TextElement.fs ↔ _TopLevel.fs src/avalonia/Fabulous.Avalonia/Views/_TextElement.fs— `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 or a formatter/rename sweep 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 (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 (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/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 (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/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/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/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 (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.
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 (13 lines × 2) src/neutral/Fabulous.Core/WidgetDiff.fs:47— src/neutral/Fabulous.Core/WidgetDiff.fs:47-59 | src/neutral/Fabulous.Core/WidgetDiff.fs:62-74 — both copies are in the same file, so extract the block into 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/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 (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 (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) 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) 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.
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 71 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 (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/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 4 separate duplicated blocks between them, totalling at least 82 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/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.
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/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 (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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 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/NavigationState.fs:1-83 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:1-66 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs:1-83 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) 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 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (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 (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 (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 (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/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 (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.
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 — the window is that declaration's tail, not a fragment that begins part-way through something, 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 × 4) 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 — 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 4 separate duplicated blocks between them, totalling at least 82 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.
validate-packages.validate_package (cyclomatic 24) eng/monorepo/validate-packages.py: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:198— 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.
WidgetChangesEnumerator.MoveNext (cyclomatic 18) src/neutral/Fabulous.Core/WidgetDiff.fs:314— 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:580— 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.
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:198— 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:314— 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:580— 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) eng/monorepo/validate-packages.py: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:431— 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.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 59 floating ref(s) across 5 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 2 workflow(s) triggered by pull_request run at least one job at the repository's default GITHUB_TOKEN scope (verify-avalonia-template.yml, verify-maui-template.yml) — no top-level `permissions:` block, and at least one job declaring none of its own — while 5 sibling workflows in the same repository are already scoped. A job that declares nothing inherits the workflow-level block, and with no workflow-level block it inherits the repository default, so scoping some of a workflow's jobs leaves the rest exactly as wide as scoping none. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
Secret exported as workflow-level env — 2 workflow-level `env:` entries interpolate a secret (repo-assist.lock.yml:133 (OTEL_EXPORTER_OTLP_HEADERS); repo-assist.lock.yml:134 (GH_AW_OTLP_ENDPOINTS)), which places the credential in the process environment of EVERY step of every job in the workflow — the dependency-installing and compiling steps included, which execute third-party installers and every build script in the transitive dependency tree. Any one of those processes can read and exfiltrate it, and no `permissions:` block narrows who receives it: scoping bounds what the token may do, not which steps hold it. Move each mapping onto the step that actually uses the credential (an `env:` block on that step), so the build and install steps never see it.
D4 · Code Duplication· Near-duplicate member family (5 members, 51 shared lines) · ×1
Near-duplicate member family (5 members, 51 shared lines) samples/avalonia/Mvu/CounterApp/App.fs:1— samples/avalonia/Mvu/CounterApp/App.fs:1-103 | samples/avalonia/Mvu/MultiWindow/App.fs:1-229 | 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 5 members are variants of one another: a block of 51 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) src/avalonia/Fabulous.Avalonia/Views/MenuItems/MenuItem.fs:1— src/avalonia/Fabulous.Avalonia/Views/MenuItems/MenuItem.fs:1-119 | src/avalonia/Fabulous.Avalonia/Views/Menu/MenuFlyout.fs:1-52 — 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 (31 lines × 6) 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 | 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 (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 — the window is that declaration's tail, not a fragment that begins part-way through something, 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, `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 (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 (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 (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 (16 lines × 4) src/neutral/Fabulous.Core/WidgetDiff.fs:190— src/neutral/Fabulous.Core/WidgetDiff.fs:190-205 | src/neutral/Fabulous.Core/WidgetDiff.fs:306-321 | src/neutral/Fabulous.Core/WidgetDiff.fs:423-438 | src/neutral/Fabulous.Core/WidgetDiff.fs:572-587 — 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:329— src/neutral/Fabulous.Core/WidgetDiff.fs:329-339 | src/neutral/Fabulous.Core/WidgetDiff.fs:446-460 — both copies are in the same file, so extract the 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 (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 (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 (9 lines × 3) src/neutral/Fabulous.Core/WidgetDiff.fs:223— src/neutral/Fabulous.Core/WidgetDiff.fs:223-231 | src/neutral/Fabulous.Core/WidgetDiff.fs:338-346 | src/neutral/Fabulous.Core/WidgetDiff.fs:605-613 — 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 (5–6 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 (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 (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 (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 (6 members, 50+ identical tokens) · ×1
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.
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 (83 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:1— samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs:1-83 | samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.fs:1-83 — before extracting anything, compare `samples/avalonia/Component/Navigation/NavigationPath/NavigationState.fs` and `samples/avalonia/Mvu/Navigation/NavigationPath/NavigationState.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 (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 (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 (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 (37–38 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:4— samples/avalonia/Component/Navigation/NavigationPath/PageC.fs:4-40 | samples/avalonia/Mvu/Navigation/NavigationPath/PageC.fs:5-42 — 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 (36 lines × 2) samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:31— samples/avalonia/Component/Navigation/ComponentNavigation/Navigation.fs:31-66 | samples/avalonia/Mvu/Navigation/ComponentNavigation/Navigation.fs:31-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 4 separate duplicated blocks between them, totalling at least 82 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 (30–31 lines × 2) samples/avalonia/Component/Navigation/NavigationPath/PageA.fs:4— samples/avalonia/Component/Navigation/NavigationPath/PageA.fs:4-33 | samples/avalonia/Mvu/Navigation/NavigationPath/PageA.fs:5-35 — 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–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 (4–29 lines × 3) samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:4— samples/avalonia/Component/Navigation/NavigationPath/PageB.fs:4-31 | samples/avalonia/Mvu/Navigation/ComponentNavigation/PageB.fs:37-40 | samples/avalonia/Mvu/Navigation/NavigationPath/PageB.fs:5-33 — `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 71 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (28 lines × 2) 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 — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (27 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 (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 (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 (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 (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–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 (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 71 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 (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 (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 (13–15 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 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. ★ 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 (15 lines × 3) samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:9— samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:9-23 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs:9-23 | samples/avalonia/Mvu/Navigation/BasicNavigation/PageC.fs:9-23 — before extracting anything, compare `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs` and `samples/avalonia/Mvu/Navigation/BasicNavigation/PageB.fs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `samples/avalonia/Mvu/Navigation/BasicNavigation/PageA.fs:9` 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–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 × 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 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.
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 (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 — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (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 × 3) 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/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.
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 (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 (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 (4–5 lines × 3) samples/avalonia/Gallery/Pages/CanvasPage.fs:110— samples/avalonia/Gallery/Pages/CanvasPage.fs:110-114 | samples/avalonia/Gallery/Pages/ImagePage.fs:22-26 | samples/avalonia/Gallery/Pages/ShapesPage.fs:38-41 — before extracting anything, compare `samples/avalonia/Gallery/Pages/CanvasPage.fs` and `samples/avalonia/Gallery/Pages/ShapesPage.fs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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/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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `samples/avalonia/Gallery/Pages/ShapesPage.fs:37` calls `PathFigure`, `Point`, `QuadraticBezierSegment` and `samples/avalonia/Gallery/Pages/CanvasPage.fs:110` 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 (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 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/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: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `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.
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.
Documentation: written for insiders avalonia/Fabulous.Avalonia.Labs/README.md— The Labs README describes experimental controls but omits any context (e.g. the Avalonia Labs repo, what is stable) and does not link to the main Fabulous documentation. Add a brief note stating this repository serves as staging ground for new Avalonia.Labs controls and that the main Fabulous docs guide the decision process.
Documentation: written for insiders avalonia/Fabulous.Avalonia.ItemsRepeater/README.md— The ItemsRepeater README is a usage example but does not explain what ItemsRepeater does beyond its name. Add a short description of the control's purpose (container for multiple items with layout management) so readers understand it before the code.
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/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, src/maui/Fabulous.MauiControls/VirtualizedCollection.fs (+2 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (12 single-owned of 233 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 233 of the 559 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above.
No ADRs found — No ADRs found. None of the conventional ADR directories exists in this tree. What was searched, so you can tell an empty log from a search that missed one: the conventional ADR directories (`docs/adr/`, `docs/decisions/`, `adr/`, `Docs/ADL/` and their siblings), TOP LEVEL ONLY — a file in a subdirectory such as `docs/adr/2024/` is not read — and within those, only files whose name carries TWO OR MORE DIGITS (`0001-use-postgres.md`, `adr-012-caching.md`). A decision log kept under unnumbered names such as `use-postgres.md`, or nested a level deeper, 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 one of those directories.
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, 2537 public types across 1156 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Rotate the exposed credentials — git history can't be un-committed — Some of these secrets are in git HISTORY: deleting the file does not remove them (the commit persists on every clone, fork and backup). The remediation is to ROTATE each historically-exposed credential and treat it as compromised — not to delete the file. Rewriting history is disruptive and unreliable across existing forks. (Working-tree-only secrets — no commit — can instead be removed from the file and moved to a secret store.) If flagged rows sit in content that is not this repository's own authored code — tool-emitted artifacts, recorded scanner output, wholesale-vendored third-party files — declare that provenance in .gitattributes (`path/** linguist-generated` or `linguist-vendored`): this scanner honors the repository's own declarations and stops counting such content, history-anchored rows included, on the next scan. The declaration is a reviewable statement about provenance, not a suppression — never use it on files that carry your own credentials. Every location above sits inside a test/fixture/sample tree, so there may be no live credential to revoke — in that case the performable actions are different ones: confirm each value was never reused outside the tests (a fixture key shared with a staging or demo environment IS a live credential and must be rotated), generate this material at test time instead of committing it so the next one cannot be mistaken for a real leak, and record the deliberate exposure where a reader of the file will see it. Rotate anything that fails the first check.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it. What was searched, so you can tell an absence from a miss: the 7 CI config file(s) in this repository, the scripts they invoke, and this repository's own composite actions — matched against the provenance acts by name (`attest-build-provenance`, `actions/attest`, `slsa-github-generator`, `cosign attest`, `in-toto`, `--provenance`) plus npm/PyPI trusted publishing. An attestation produced by a tool none of those names, or by a pipeline whose configuration is not in this repository, is not seen by this check.
No artifact signing — No artifact signing found in CI — sign your released artifacts with whatever your ecosystem ships (a GPG/minisign detached signature — or `cosign sign-blob` — over the release archives, or over a checksum file published alongside them, `dotnet nuget sign` with a code-signing certificate for the NuGet packages (`dotnet nuget verify` checks it), or Authenticode via signtool for any executable you ship) so consumers can verify what you built. What was searched, so you can tell an absence from a miss: this repository's CI files, the scripts they invoke and its own composite actions, its root build manifest and its release manifest, its release task runner if it has one, and its own release automation script — plus the trusted-publishing declarations that sign on the registry's side. A signature produced by a pipeline whose configuration is not in this repository, or by a signer whose name is none of the ones this check carries, is not seen here.
D36 · Supply-chain Provenance & Signing· No checksums published for release artifacts · ×1
No checksums published for release artifacts — The release uploads downloadable files but publishes no digest for them (release.yml), so someone who downloads a release asset has nothing to compare it against — a truncated download, a corrupted mirror and a substituted file are indistinguishable. This pipeline signs and attests nothing either, so the digest is the cheapest control available to it: hash every asset in the release job and upload the result alongside them (`sha256sum <files> > SHA256SUMS` on Linux/macOS, `Get-FileHash` on Windows). Publishing the digest is also what makes the next rung cheap: an artifact signature is conventionally a detached signature over exactly this file rather than over each asset.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing. What was searched, so you can tell an absence from a miss: this repository's CI files, the scripts they invoke and its own composite actions, any SBOM committed to the repository, the SBOM configuration declared in its build and release manifests, and the container-build SBOM inputs. An SBOM produced by a pipeline whose configuration is not in this repository, or by a generator whose name is none of the ones this check carries, is not seen here.
No dependency advisory monitoring — Nothing in this repository re-checks its pinned dependencies when an advisory is published: no Dependabot or Renovate configuration (`.github/dependabot.yml`, `renovate.json`), no advisory scanner invoked from CI and no committed scanner configuration (`deny.toml`, `.cargo/audit.toml`, `osv-scanner.toml`, `.snyk`). The manifests present — `nuget` (*.csproj) — pin versions that advisories are published against on the advisory database's clock, not this repository's, so every advisory that lands against a pinned version stays unseen until someone points a scanner at the tree (any already published are reported under D30, one row per package — this row names the control whose absence lets them accumulate). GitHub's Dependabot alerts, if switched on in the repository settings, notify but leave nothing in the tree; a committed configuration is what makes the control reviewable and carries it to a fork or mirror. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per manifest listed (or a `renovate.json`) so each advisory arrives as a pull request against the affected lockfile; or wire the ecosystem's own advisory scanner into CI on a `schedule:` trigger — nuget: `dotnet list package --vulnerable` failing on output, or promote the SDK's audit warnings to errors (`<WarningsAsErrors>NU1901;NU1902;NU1903;NU1904</WarningsAsErrors>`).
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.
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 214666 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.
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); 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.
0
—
Run 01a08d1e-250c-794f-b308-dcacb546cd25 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 73 · Warnings: 236 · Recommendations: 17 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 10-09-2026 @ 20:59 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.