Public report of WPFDevelopersOrg/WPFDevelopers, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 16:42 UTC · Survey ID cd_4075b537bb2c4c34816823606f8d4089
WPFDevelopersOrg/WPFDevelopers
Measured 17 November 2026, 16:40 UTC, at code version b3d0dd7
Boundary Type-Coupling is not measured: Bounded contexts not declared.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 72,321 lines of product code in 48 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Production Readiness, 34.0
Findings by how serious they are
56 critical551 serious85 minor
8 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 16:40 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
55of 55 dimensions measured by tools.
686of 692 findings point to an exact file and line, so you can open each one in the code. The other 6 concern the repository as a whole, such as missing documentation.
55dimensions across 5 lenses, read from 72,321 lines of product code in 48 projects.
WPFDevelopersOrg/WPFDevelopers falls short of our standard for production because the project has no automated tests and we found no automated security scanning of the code, its secrets or its dependencies. It scores 40.7 out of 100 and is rated Weak, and 11 of its 56 critical findings are security problems in the build pipeline and in its code.
Production Readiness, at 34.0, is the weakest lens and counts most in the score. The best first step for the work it takes is adding automated security scanning, worth about 5.4 points. Adding automated tests comes next, worth about 8.4 points. Raising Production Readiness to 70 would lift the score to about 47.8.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One weakness in the code could be used by an attacker, and fifteen errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and handling or logging the ignored errors would close these risks. The 13 data fields that are written but never read need removing.
The product code is 72,321 lines, about €190,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 34.0 to 70, the lowest score rated Strong, the score would rise from 40.7 to about 47.8.
Code composition: what the lines of code are
Business logic 45%Supporting code 54%Generated by tools 1%
Rebuild cost: about €190,000 · Estimate
Cost to rebuild
€61,000 to €310,000, for 1,016 to 3,309 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 72,321 lines of product code, of which 32% is declarations and boilerplate, 22% straight logic and 45% logic with branches
Comment lines
The estimate prices 71,018 lines. Comment lines count towards the size of 72,321 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 8.4 points · High effort · Code Coverage
3
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 4.2 points · Medium effort · Data Protection
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €190,000 to build again, about 1.3 person-years of work. Its weakest lens is Production Readiness, at 34.0 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. Of all the actions in this report, it raises the score most for the work it takes: about 5.4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
42 modules, with 42 dependencies between them. 3 loops run through 7 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 2 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Microsoft.Expression.Drawing.Media uses Microsoft.Expression.Drawing.Core, so a change to Microsoft.Expression.Drawing.Core can break Microsoft.Expression.Drawing.Media, while a change to Microsoft.Expression.Drawing.Media can't break Microsoft.Expression.Drawing.Core.
Position
Below the diagonal: Microsoft.Expression.Drawing.Media uses a module listed above it, which is the healthy direction.
Microsoft.Windows.Shell uses Standard, so a change to Standard can break Microsoft.Windows.Shell, while a change to Microsoft.Windows.Shell can't break Standard.
Position
Below the diagonal: Microsoft.Windows.Shell uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls.Runtimes uses WPFDevelopers.Controls.Runtimes.Interop, so a change to WPFDevelopers.Controls.Runtimes.Interop can break WPFDevelopers.Controls.Runtimes, while a change to WPFDevelopers.Controls.Runtimes can't break WPFDevelopers.Controls.Runtimes.Interop.
Position
Below the diagonal: WPFDevelopers.Controls.Runtimes uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls.Runtimes uses WPFDevelopers.Controls.Runtimes.Shell32, so a change to WPFDevelopers.Controls.Runtimes.Shell32 can break WPFDevelopers.Controls.Runtimes, while a change to WPFDevelopers.Controls.Runtimes can't break WPFDevelopers.Controls.Runtimes.Shell32.
Position
Below the diagonal: WPFDevelopers.Controls.Runtimes uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls.Runtimes uses WPFDevelopers.Controls.Runtimes.User32, so a change to WPFDevelopers.Controls.Runtimes.User32 can break WPFDevelopers.Controls.Runtimes, while a change to WPFDevelopers.Controls.Runtimes can't break WPFDevelopers.Controls.Runtimes.User32.
Position
Below the diagonal: WPFDevelopers.Controls.Runtimes uses a module listed above it, which is the healthy direction.
25→33 WPFDevelopers.Core uses WPFDeveloperspart of a loop✕
Connections
1 pair of types, where a type in WPFDevelopers.Core uses a type in WPFDevelopers.
WPFDevelopers.Core uses WPFDevelopers, so a change to WPFDevelopers can break WPFDevelopers.Core, while a change to WPFDevelopers.Core can't break WPFDevelopers.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
WPFDevelopers.Sample.Models uses WPFDevelopers.Samples, so a change to WPFDevelopers.Samples can break WPFDevelopers.Sample.Models, while a change to WPFDevelopers.Sample.Models can't break WPFDevelopers.Samples.
Position
Below the diagonal: WPFDevelopers.Sample.Models uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.Controls uses WPFDevelopers.Samples, so a change to WPFDevelopers.Samples can break WPFDevelopers.Samples.Controls, while a change to WPFDevelopers.Samples.Controls can't break WPFDevelopers.Samples.
Position
Below the diagonal: WPFDevelopers.Samples.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.Models uses WPFDevelopers.Samples, so a change to WPFDevelopers.Samples can break WPFDevelopers.Samples.Models, while a change to WPFDevelopers.Samples.Models can't break WPFDevelopers.Samples.
Position
Below the diagonal: WPFDevelopers.Samples.Models uses a module listed above it, which is the healthy direction.
29→38 WPFDevelopers.Utilities uses WPFDevelopers.Controlspart of a loop✕
Connections
1 pair of types, where a type in WPFDevelopers.Utilities uses a type in WPFDevelopers.Controls.
WPFDevelopers.Utilities uses WPFDevelopers.Controls, so a change to WPFDevelopers.Controls can break WPFDevelopers.Utilities, while a change to WPFDevelopers.Utilities can't break WPFDevelopers.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Microsoft.Expression.Controls uses Microsoft.Expression.Drawing.Core, so a change to Microsoft.Expression.Drawing.Core can break Microsoft.Expression.Controls, while a change to Microsoft.Expression.Controls can't break Microsoft.Expression.Drawing.Core.
Position
Below the diagonal: Microsoft.Expression.Controls uses a module listed above it, which is the healthy direction.
Microsoft.Expression.Controls uses Microsoft.Expression.Drawing.Media, so a change to Microsoft.Expression.Drawing.Media can break Microsoft.Expression.Controls, while a change to Microsoft.Expression.Controls can't break Microsoft.Expression.Drawing.Media.
Position
Below the diagonal: Microsoft.Expression.Controls uses a module listed above it, which is the healthy direction.
Microsoft.Expression.Drawing.Controls uses Microsoft.Expression.Drawing.Media, so a change to Microsoft.Expression.Drawing.Media can break Microsoft.Expression.Drawing.Controls, while a change to Microsoft.Expression.Drawing.Controls can't break Microsoft.Expression.Drawing.Media.
Position
Below the diagonal: Microsoft.Expression.Drawing.Controls uses a module listed above it, which is the healthy direction.
Microsoft.Expression.Drawing.Shapes uses Microsoft.Expression.Drawing.Media, so a change to Microsoft.Expression.Drawing.Media can break Microsoft.Expression.Drawing.Shapes, while a change to Microsoft.Expression.Drawing.Shapes can't break Microsoft.Expression.Drawing.Media.
Position
Below the diagonal: Microsoft.Expression.Drawing.Shapes uses a module listed above it, which is the healthy direction.
WPFDevelopers uses WPFDevelopers.Core, so a change to WPFDevelopers.Core can break WPFDevelopers, while a change to WPFDevelopers can't break WPFDevelopers.Core.
Position
Below the diagonal: WPFDevelopers uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ExampleViews.Basics uses WPFDevelopers.Sample.Models, so a change to WPFDevelopers.Sample.Models can break WPFDevelopers.Samples.ExampleViews.Basics, while a change to WPFDevelopers.Samples.ExampleViews.Basics can't break WPFDevelopers.Sample.Models.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews.Basics uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ViewModels uses WPFDevelopers.Samples, so a change to WPFDevelopers.Samples can break WPFDevelopers.Samples.ViewModels, while a change to WPFDevelopers.Samples.ViewModels can't break WPFDevelopers.Samples.
Position
Below the diagonal: WPFDevelopers.Samples.ViewModels uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ViewModels uses WPFDevelopers.Samples.Helpers, so a change to WPFDevelopers.Samples.Helpers can break WPFDevelopers.Samples.ViewModels, while a change to WPFDevelopers.Samples.ViewModels can't break WPFDevelopers.Samples.Helpers.
Position
Below the diagonal: WPFDevelopers.Samples.ViewModels uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ViewModels uses WPFDevelopers.Samples.Models, so a change to WPFDevelopers.Samples.Models can break WPFDevelopers.Samples.ViewModels, while a change to WPFDevelopers.Samples.ViewModels can't break WPFDevelopers.Samples.Models.
Position
Below the diagonal: WPFDevelopers.Samples.ViewModels uses a module listed above it, which is the healthy direction.
35→37 WPFDevelopers.Samples.ViewModels uses WPFDevelopers.Samples.ExampleViewspart of a loop✕
Connections
1 pair of types, where a type in WPFDevelopers.Samples.ViewModels uses a type in WPFDevelopers.Samples.ExampleViews.
WPFDevelopers.Samples.ViewModels uses WPFDevelopers.Samples.ExampleViews, so a change to WPFDevelopers.Samples.ExampleViews can break WPFDevelopers.Samples.ViewModels, while a change to WPFDevelopers.Samples.ViewModels can't break WPFDevelopers.Samples.ExampleViews.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
WPFDevelopers.Helpers uses WPFDevelopers.Utilities, so a change to WPFDevelopers.Utilities can break WPFDevelopers.Helpers, while a change to WPFDevelopers.Helpers can't break WPFDevelopers.Utilities.
Position
Below the diagonal: WPFDevelopers.Helpers uses a module listed above it, which is the healthy direction.
WPFDevelopers.Helpers uses WPFDevelopers, so a change to WPFDevelopers can break WPFDevelopers.Helpers, while a change to WPFDevelopers.Helpers can't break WPFDevelopers.
Position
Below the diagonal: WPFDevelopers.Helpers uses a module listed above it, which is the healthy direction.
36→38 WPFDevelopers.Helpers uses WPFDevelopers.Controlspart of a loop✕
Connections
2 pairs of types, where a type in WPFDevelopers.Helpers uses a type in WPFDevelopers.Controls.
WPFDevelopers.Helpers uses WPFDevelopers.Controls, so a change to WPFDevelopers.Controls can break WPFDevelopers.Helpers, while a change to WPFDevelopers.Helpers can't break WPFDevelopers.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
WPFDevelopers.Samples.ExampleViews uses WPFDevelopers.Samples, so a change to WPFDevelopers.Samples can break WPFDevelopers.Samples.ExampleViews, while a change to WPFDevelopers.Samples.ExampleViews can't break WPFDevelopers.Samples.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ExampleViews uses WPFDevelopers.Sample.Models, so a change to WPFDevelopers.Sample.Models can break WPFDevelopers.Samples.ExampleViews, while a change to WPFDevelopers.Samples.ExampleViews can't break WPFDevelopers.Sample.Models.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ExampleViews uses WPFDevelopers.Samples.Controls, so a change to WPFDevelopers.Samples.Controls can break WPFDevelopers.Samples.ExampleViews, while a change to WPFDevelopers.Samples.ExampleViews can't break WPFDevelopers.Samples.Controls.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ExampleViews uses WPFDevelopers.Samples.Models, so a change to WPFDevelopers.Samples.Models can break WPFDevelopers.Samples.ExampleViews, while a change to WPFDevelopers.Samples.ExampleViews can't break WPFDevelopers.Samples.Models.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews uses a module listed above it, which is the healthy direction.
WPFDevelopers.Samples.ExampleViews uses WPFDevelopers.Samples.ViewModels, so a change to WPFDevelopers.Samples.ViewModels can break WPFDevelopers.Samples.ExampleViews, while a change to WPFDevelopers.Samples.ExampleViews can't break WPFDevelopers.Samples.ViewModels.
Position
Below the diagonal: WPFDevelopers.Samples.ExampleViews uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Controls.Runtimes.Interop, so a change to WPFDevelopers.Controls.Runtimes.Interop can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Controls.Runtimes.Interop.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Controls.Runtimes.Shell32, so a change to WPFDevelopers.Controls.Runtimes.Shell32 can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Controls.Runtimes.Shell32.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Controls.Runtimes.User32, so a change to WPFDevelopers.Controls.Runtimes.User32 can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Controls.Runtimes.User32.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses Microsoft.Windows.Shell, so a change to Microsoft.Windows.Shell can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break Microsoft.Windows.Shell.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Core, so a change to WPFDevelopers.Core can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Core.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Utilities, so a change to WPFDevelopers.Utilities can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Utilities.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses Microsoft.Expression.Drawing.Shapes, so a change to Microsoft.Expression.Drawing.Shapes can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break Microsoft.Expression.Drawing.Shapes.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers, so a change to WPFDevelopers can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Controls uses WPFDevelopers.Helpers, so a change to WPFDevelopers.Helpers can break WPFDevelopers.Controls, while a change to WPFDevelopers.Controls can't break WPFDevelopers.Helpers.
Position
Below the diagonal: WPFDevelopers.Controls uses a module listed above it, which is the healthy direction.
WPFDevelopers.Net40 uses Microsoft.Windows.Shell, so a change to Microsoft.Windows.Shell can break WPFDevelopers.Net40, while a change to WPFDevelopers.Net40 can't break Microsoft.Windows.Shell.
Position
Below the diagonal: WPFDevelopers.Net40 uses a module listed above it, which is the healthy direction.
WPFDevelopers.Net40 uses WPFDevelopers, so a change to WPFDevelopers can break WPFDevelopers.Net40, while a change to WPFDevelopers.Net40 can't break WPFDevelopers.
Position
Below the diagonal: WPFDevelopers.Net40 uses a module listed above it, which is the healthy direction.
WPFDevelopers.Net40 uses WPFDevelopers.Controls, so a change to WPFDevelopers.Controls can break WPFDevelopers.Net40, while a change to WPFDevelopers.Net40 can't break WPFDevelopers.Controls.
Position
Below the diagonal: WPFDevelopers.Net40 uses a module listed above it, which is the healthy direction.
WPFDevelopers.Net45x uses WPFDevelopers, so a change to WPFDevelopers can break WPFDevelopers.Net45x, while a change to WPFDevelopers.Net45x can't break WPFDevelopers.
Position
Below the diagonal: WPFDevelopers.Net45x uses a module listed above it, which is the healthy direction.
WPFDevelopers.Net45x uses WPFDevelopers.Controls, so a change to WPFDevelopers.Controls can break WPFDevelopers.Net45x, while a change to WPFDevelopers.Net45x can't break WPFDevelopers.Controls.
Position
Below the diagonal: WPFDevelopers.Net45x uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 44.5 · Weak · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
26
High / Critical
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
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 — 56
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 — 551
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 — 85
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 55 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, 686 of 692 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj' with message: File 'src/WPFDevelopers.Samples.Shared/ExampleViews/TimelineExample.xaml' cannot be found.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 35 error(s), and the diagnostics it printed were: MSB3073: The command "src/WPFDevelopers.Shared/Themes/XamlCombine.exe src/WPFDevelopers.Shared/Themes/Theme45x.txt src/WPFDevelopers.Net45x/Themes/Theme.xaml" exited with code 126.; BG1002: File '../WPFDevelopers.Samples.Shared/ExampleViews/TimelineExample.xaml.cs' cannot be found.; BG1002: File '../WPFDevelopers.Samples.Shared/ExampleViews/TimelineExample.xaml' cannot be found.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scored solution `src/WPFDevelopers.sln` is not representative of this repository — it references only 4 of 755 discovered C# files (1 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. You can widen what we reach: point the scan at the product solution, or scan its directory directly, so the whole codebase is analyzed rather than a build-tooling sub-solution.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (72,321 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/WPFDevelopers.Samples.Shared/ExampleViews/ChartRadarExample.xaml.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (src/WPFDevelopers.Shared/Themes/AnimationAudio.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 37 further occurrence(s) are not listed individually; the score already reflects all 77.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our 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.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
56 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AbbreviatedGeometryParser.Parse at 41. A further 3 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 MainVM.MenuItemSelection at 129 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/WPFDevelopers.Samples.Shared/ViewModels/MainVM.cs (MainVM.MenuItemSelection at 129). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 51 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with AbbreviatedGeometryParser.Parse (cyclomatic 41), FocusCarousel.FocusCarousel_MouseLeftButtonDown (cyclomatic 32). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 121 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with AbbreviatedGeometryParser.Parse (cognitive 90), MultiSelectComboBox.OnSelectionChanged (cognitive 77). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 17 TooManyMethods finding(s) in God Classes — start with Window.cs (2), REDACTED, NativeMethods.cs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 14 MethodTooLong finding(s) in God Classes — start with CardCarousel.cs (3), MainVM.cs (2), FocusCarousel.cs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 10 FileTooLong finding(s) in God Classes — start with REDACTED, ScreenCut.cs, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
109 duplicated block group(s) detected. 4.6 % of the production lines (3,311 of 72,321) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with Window.cs (3), AudioWindow.cs (3), PathFigureHelper.cs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with MultiSelectSearchComboBox.cs (2), MultiSelectComboBox.cs (2), BallLoading.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with DrawingPanel.cs (2), ElementAdorner.cs (2), MultiSelectSearchComboBox.cs. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with MapViewFeaturesWindow.xaml.cs, NotifyIconExample.xaml.cs, CarouselBase.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, 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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 5 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 2 direct `PackageReference`(s), and 2 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with Window.cs (2), ScrollViewerBehavior.cs, REDACTED. — One of this dimension's main actionable groups (5 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 Factor0.0 / 10Critical✓ 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.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/WPFDevelopers.Net45x/Window.cs. Counted over 2 of the 4 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
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
410 deducted debt markers + unmeasured dead symbols across 72321 LoC in the .NET projects (1.6/KLoC) → score 6.8. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (3), Resources.cs (3), Utility.cs (2). — One of this dimension's main actionable groups (15 issue-level).
Resolve the 13 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PKEY.cs (2), RoundPicker.cs, ThumbAdorner.cs. — One of this dimension's main actionable groups (13 issue-level).
Resolve the 12 NoWarnInCsproj finding(s) in Explicit Debt — start with WPFDevelopers.Samples40.csproj (12). — One of this dimension's main actionable groups (12 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape8.5 / 10Strong✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
48 projects, 12076 source files, 72321 hand-written lines of code (72321 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 779 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 20 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
Resolve the 1 Shell project finding(s) in Solution Shape — start with WPFDevelopers.SamplesCode.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F4 map. 6 document(s) read across 6 unit(s).
Documentation: no map of the repository's partsREADME.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundsrc/WPFDevelopers.Net45x/WPFDevelopers.Net45x.csproj:5
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with WPFDevelopers.Net45x.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
4 of 54 judged comments only repeat the code they sit on (7.4 %). 100 comment(s) in another language or script were not judged.
redundant comment · ×4REDACTED:5
doc comments repeat the namessrc/WPFDevelopers.Shared/Controls/Filter/FilterEngine.cs:264
What to do
Resolve the 4 redundant comment finding(s) in Comment Value — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 5 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with WPFDevelopers.Net40.csproj, WPFDevelopers.Net45x.csproj, WPFDevelopers.Samples40.csproj. — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
82 % of calls cross a namespace and 0 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
26 finding(s): 0 critical, 11 high, 15 medium, 0 low. 10 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 1 file(s) — `src/WPFDevelopers.Samples.Shared/ExampleViews/ChartRadarExample.xaml.cs` (lines 10–126) — 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. In 1 of those file(s) — `src/WPFDevelopers.Samples.Shared/ExampleViews/ChartRadarExample.xaml.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED, REDACTED. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 10 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (10 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 2 of the 4 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ScreenCutExample.xaml.cs. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with WPFDevelopers.Net40.csproj, WPFDevelopers.Samples40.csproj. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_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.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`SampleLanguageManager` keeps one instance of itself in the static `LazyInstance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_exampleViews, _initialized; e.g. `_exampleViews` at line 89). — src/WPFDevelopers.Samples.Shared/SampleLanguageManager.cs:22
`ThemeManager` keeps one instance of itself in the static `_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_themeAnimating; e.g. `_themeAnimating` at line 90). — src/WPFDevelopers.Shared/ThemeManager.cs:11
`LanguageManager` keeps one instance of itself in the static `_lazy`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_currentCulture; e.g. `_currentCulture` at line 22). — src/WPFDevelopers.Shared/LanguageManager.cs:9
`ToastExt` is not registered, but `Toast` creates it and keeps it in the static `_toastExt`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (IsPosition; e.g. `IsPosition` at line 48). — src/WPFDevelopers.Shared/Controls/Toast/ToastExt.cs:9
`DefaultLoading` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_indicator; e.g. `_indicator` at line 28). — src/WPFDevelopers.Shared/Controls/Loading/DefaultLoading.cs:7
`Magnifier` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_factor, _adornerContainer, _border, _visualBrush; e.g. `_factor` at line 70). — src/WPFDevelopers.Shared/Controls/Magnifier/Magnifier.cs:10
`HandleType` is not registered, but `HandleCollector` creates it and keeps it in the static `handleTypes`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (threshHold; e.g. `threshHold` at line 165). — src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/Interop/HandleCollector.cs:95
`AdornerContainer` is not registered, but the singleton `Magnifier` creates it and keeps it in `_adornerContainer`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_child; e.g. `_child` at line 21). — src/WPFDevelopers.Shared/Core/Utilities/AdornerContainer.cs:7
`Dialog` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (OpenDialogs; e.g. `OpenDialogs` at line 272). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/Dialog/Dialog.cs:18
`PropertyAccessor` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_cache; e.g. `_cache` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/Filter/PropertyAccessor.cs:7
`Toast` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_toastExt, _position; e.g. `_toastExt` at line 117). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/Toast/Toast.cs:9
`Loading` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_loadingMap, _adornerMap, _wrapperMap; e.g. `_loadingMap` at line 131). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:13
`NotifyIcon` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_NotifyIcon; e.g. `s_NotifyIcon` at line 290). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs:26
`ScreenCut` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CaptureScreenID; e.g. `CaptureScreenID` at line 340). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:91
`DatePickerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_timeStorage, _textBoxStorage, _timePickerStorage; e.g. `_timeStorage` at line 321). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Core/Helpers/DatePickerHelper.cs:13
`DesignerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isInDesignMode; e.g. `_isInDesignMode` at line 240). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Core/Helpers/ControlsHelper.cs:230
`ElementHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isMetadataOverridden; e.g. `_isMetadataOverridden` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Core/Helpers/ElementHelper.cs:7
`OSVersionHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isSnapLayoutSupported; e.g. `_isSnapLayoutSupported` at line 60). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Core/Helpers/OSVersionHelper.cs:12
`GeometryEffect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultGeometryEffect; e.g. `defaultGeometryEffect` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/GeometryEffect.cs:9
`Global` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (assemblyShortName; e.g. `assemblyShortName` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/WPFDevelopers.Shared/Microsoft.Expression.Media.Effects/Global.cs:6
`ThumbButtonInfoCollection` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_empty; e.g. `s_empty` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Microsoft.Windows.Shell/ThumbButtonInfoCollection.cs:5
`MessageWindow` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_windowLookup; e.g. `s_windowLookup` at line 79). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Microsoft.Windows.Shell/Standard/MessageWindow.cs:10
`Utility` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_bitDepth; e.g. `s_bitDepth` at line 349). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Microsoft.Windows.Shell/Standard/Utility.cs:17
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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.
The namespaces WPFDevelopers ↔ WPFDevelopers.Core depend on each other. The lightest dependency in the cycle is WPFDevelopers.Core → WPFDevelopers (WPFDevelopers.Core.ThemeChangedEvent → WPFDevelopers.ThemeType, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/WPFDevelopers.Shared/Core/ThemeChangedEvent.cs:5
The namespaces WPFDevelopers.Controls ↔ WPFDevelopers.Helpers ↔ WPFDevelopers.Utilities depend on each other. The lightest dependency in the cycle is WPFDevelopers.Helpers → WPFDevelopers.Utilities (WPFDevelopers.Helpers.MaskAdorner → WPFDevelopers.Utilities.AdornerContainer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/WPFDevelopers.Shared/Core/Helpers/WindowHelpers.cs:12
The namespaces WPFDevelopers.Samples.ExampleViews ↔ WPFDevelopers.Samples.ViewModels depend on each other. The lightest dependency in the cycle is WPFDevelopers.Samples.ExampleViews → WPFDevelopers.Samples.ViewModels (WPFDevelopers.Samples.ExampleViews.PaginationExample → WPFDevelopers.Samples.ViewModels.PaginationExampleVM, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/WPFDevelopers.Samples.Shared/ExampleViews/PaginationExample.xaml.cs:6
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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 · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
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. (×30) — src/WPFDevelopers.Samples.Shared/Converts/DrawPrizeIndexToColor.cs:20, src/WPFDevelopers.Samples.Shared/Converts/StateConvert.cs:31, src/WPFDevelopers.Shared/Core/Converts/FirstLastMarginConverter.cs:23, …
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.
The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. (×2) — src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:194, src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:224
`AddChild` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:87
`AddText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:92
`vHeight == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead. — src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:214
`vWidth == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead. — src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:214
`_displayWidth == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead. — src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:269
1 guard above `return _textBox4;` also returns `_textBox4`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:287
Control only reaches here when `isLoading` is true, because the guard on line 129 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test. (×2) — src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:140, src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:169
The `if` and its `else` contain the same 2 statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body. — src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:202
`CreateInstanceCore` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:212
`Convert` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/WPFDevelopers.Shared/Core/Converts/ElementConvert.cs:9
The branch `if ((result = BezierSegmentImplementation.Create(segment as BezierSegment)) == null && (result = LineSegmentImplementation.Create(segment as LineSegment)) == null && (result = ArcSegmentImplementation.Create(segment as ArcSegment)) == null && (result = PolyLineSegmentImplementation.Create(segment as PolyLineSegment)) == null && (result = PolyBezierSegmentImplementation.Create(segment as PolyBezierSegment)) == null && (result = QuadraticBezierSegmentImplementation.Create(segment as QuadraticBezierSegment)) == null && (result = PolyQuadraticBezierSegmentImplementation.Create(segment as PolyQuadraticBezierSegment)) == null)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported. — src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:492
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×25) — src/Microsoft.Windows.Shell/Standard/IObjectCollection.cs:14, src/WPFDevelopers.Samples.Shared/Controls/ChatEmoji/ChatEmoji.cs:125, src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:95, …
`GetDC` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/Microsoft.Windows.Shell/Standard/NativeMethods.cs:361
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P2 · Observability7.8 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 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. — REDACTED:7
`src/TargetFrameworks.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — src/TargetFrameworks.props:6
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — 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 traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. (×2) — src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:81, src/Microsoft.Windows.Shell/Standard/Utility.cs:520
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `src/Microsoft.Windows.Shell/Standard/Utility.cs:520` (MD5), `src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:81` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`streamReader` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 195). Every use of it in `GetCodeText` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var streamReader = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:195
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 107). Every use of it in `Loading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:107
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 138). Every use of it in `LoadingTask_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:138
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 159). Every use of it in `BtnLoading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:159
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `Btn_LoadingExtClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/LoadingExample.xaml.cs:41
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 16). Every use of it in `Loading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:16
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `LoadingTask_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:34
`task` is a `Task`, which implements `IDisposable`, and it is created here (line 53). Every use of it in `BtnLoading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:53
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 119). Every use of it in `ShowScreenShot` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs:119
`CropAvatar` declares a finalizer (line 352), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/WPFDevelopers.Shared/Controls/CropAvatar/CropAvatar.cs:352
`client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 4308). Every use of it in `DownloadTileImageAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:4308
`regKey` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 65). Every use of it in `GetWindowOSVersion` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var regKey = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:65
`player1` is a `SoundPlayer`, which implements `IDisposable`, and it is created here (line 48). Every use of it in `WindowShake` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var player1 = …;`), which releases it at the end of the scope on every path including a throw. — src/WPFDevelopers.Shared/Core/Helpers/ControlsHelper.cs:48
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
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 (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — 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)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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 element7.2 / 10Strong✓ Tool-verified
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[num3]`. The test deciding whether that statement runs does not: `flag` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 317, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — src/Microsoft.Windows.Shell/Standard/Utility.cs:321
What to do
Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×15) — src/WPFDevelopers.Samples.Shared/Helpers/BrowserHelper.cs:21, src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:78, src/WPFDevelopers.Shared/Core/Helpers/OSVersionHelper.cs:83, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:152, REDACTED:134, src/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:69
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Microsoft.Windows.Shell/JumpList.cs:582
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
This method contradicts itself about `ctrl`: line 75 assigns it with `as BubbleSelection`, which hands back null rather than throwing when the value is not a `BubbleSelection`, but line 77 then dereferences it directly as `ctrl.SetValue` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctrl` once before the first use and handle the null case, or cast with `(BubbleSelection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleSelection.cs:77
This method contradicts itself about `ctrl`: line 128 assigns it with `as BubbleSelection`, which hands back null rather than throwing when the value is not a `BubbleSelection`, but line 133 then dereferences it directly as `ctrl._items` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctrl` once before the first use and handle the null case, or cast with `(BubbleSelection)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleSelection.cs:133
This method contradicts itself about `item`: line 31 assigns it with `as FrameworkElement`, which hands back null rather than throwing when the value is not a `FrameworkElement`, but line 33 then dereferences it directly as `item.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `item` once before the first use and handle the null case, or cast with `(FrameworkElement)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleCanvas.cs:33
This method contradicts itself about `rect1`: line 78 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 85 then dereferences it directly as `rect1.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rect1` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:85
This method contradicts itself about `scaleTransform`: line 85 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 86 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:86
This method contradicts itself about `rect1`: line 91 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 93 then dereferences it directly as `rect1.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rect1` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:93
This method contradicts itself about `scaleTransform`: line 93 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 99 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:99
This method contradicts itself about `cutCustoms`: line 88 assigns it with `as CutImage`, which hands back null rather than throwing when the value is not a `CutImage`, but line 89 then dereferences it directly as `cutCustoms.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cutCustoms` once before the first use and handle the null case, or cast with `(CutImage)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/CutImage/CutImage.cs:89
This method contradicts itself about `bar`: line 47 assigns it with `as Dashboard`, which hands back null rather than throwing when the value is not a `Dashboard`, but line 48 then dereferences it directly as `bar.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `bar` once before the first use and handle the null case, or cast with `(Dashboard)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/Dashboard/Dashboard.cs:48
This method contradicts itself about `mltiSelectionSearchComboBox`: line 598 assigns it with `as MultiSelectionSearchComboBox`, which hands back null rather than throwing when the value is not a `MultiSelectionSearchComboBox`, but line 604 then dereferences it directly as `mltiSelectionSearchComboBox._listBox` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mltiSelectionSearchComboBox` once before the first use and handle the null case, or cast with `(MultiSelectionSearchComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:604
This method contradicts itself about `collection`: line 602 assigns it with `as IList`, which hands back null rather than throwing when the value is not a `IList`, but line 603 then dereferences it directly as `collection.Count` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `collection` once before the first use and handle the null case, or cast with `(IList)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:603
This method contradicts itself about `parent`: line 253 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 265 then dereferences it directly as `parent.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `parent` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:265
This method contradicts itself about `rotateTransform`: line 321 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 322 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:322
This method contradicts itself about `rotateTransform`: line 65 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 66 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. (×2) — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:66, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:66
This method contradicts itself about `thumb`: line 73 assigns it with `as Thumb`, which hands back null rather than throwing when the value is not a `Thumb`, but line 74 then dereferences it directly as `thumb.DataContext` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `thumb` once before the first use and handle the null case, or cast with `(Thumb)` so the failure is reported where it happens — rather than leaving the two readings side by side. (×2) — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:74, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:74
This method contradicts itself about `pieSegment`: line 47 assigns it with `as PieSegment`, which hands back null rather than throwing when the value is not a `PieSegment`, but line 55 then dereferences it directly as `pieSegment.ColorArray` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `pieSegment` once before the first use and handle the null case, or cast with `(PieSegment)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/PieSegment/PieSegment.cs:55
This method contradicts itself about `array`: line 50 assigns it with `as ObservableCollection<PieSegmentModel>`, which hands back null rather than throwing when the value is not a `ObservableCollection<PieSegmentModel>`, but line 55 then dereferences it directly as `array.IndexOf` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `array` once before the first use and handle the null case, or cast with `(ObservableCollection<PieSegmentModel>)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/PieSegment/PieSegment.cs:55
This method contradicts itself about `btn`: line 118 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 125 then dereferences it directly as `btn.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:125
This method contradicts itself about `scaleTransform`: line 125 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 126 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:126
This method contradicts itself about `btn`: line 131 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 132 then dereferences it directly as `btn.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:132
This method contradicts itself about `scaleTransform`: line 132 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 138 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:138
This method contradicts itself about `btn`: line 144 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 145 then dereferences it directly as `btn.Content` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:145
This method contradicts itself about `animationAudio`: line 23 assigns it with `as AnimationAudio`, which hands back null rather than throwing when the value is not a `AnimationAudio`, but line 26 then dereferences it directly as `animationAudio.IsPlay` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `animationAudio` once before the first use and handle the null case, or cast with `(AnimationAudio)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/AnimationAudioExample.xaml.cs:26
This method contradicts itself about `item`: line 34 assigns it with `as NavMenu3DItem`, which hands back null rather than throwing when the value is not a `NavMenu3DItem`, but line 35 then dereferences it directly as `item.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `item` once before the first use and handle the null case, or cast with `(NavMenu3DItem)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/NavMenu3DExample.xaml.cs:35
This method contradicts itself about `view`: line 192 assigns it with `as BasicControlsExample`, which hands back null rather than throwing when the value is not a `BasicControlsExample`, but line 195 then dereferences it directly as `view.UserCollection` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `view` once before the first use and handle the null case, or cast with `(BasicControlsExample)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:195
This method contradicts itself about `send`: line 58 assigns it with `as Border`, which hands back null rather than throwing when the value is not a `Border`, but line 59 then dereferences it directly as `send.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `send` once before the first use and handle the null case, or cast with `(Border)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/ChatEmojiExample.xaml.cs:59
This method contradicts itself about `send`: line 127 assigns it with `as Border`, which hands back null rather than throwing when the value is not a `Border`, but line 128 then dereferences it directly as `send.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `send` once before the first use and handle the null case, or cast with `(Border)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/ChatEmojiExample.xaml.cs:128
This method contradicts itself about `parent`: line 200 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 212 then dereferences it directly as `parent.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `parent` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:212
This method contradicts itself about `rotateTransform`: line 268 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 269 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:269
This method contradicts itself about `parent`: line 133 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 145 then dereferences it directly as `parent.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `parent` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:145
This method contradicts itself about `rotateTransform`: line 214 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 215 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:215
This method contradicts itself about `rotateTransform`: line 90 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 91 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:91
This method contradicts itself about `parent`: line 188 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 200 then dereferences it directly as `parent.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `parent` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:200
This method contradicts itself about `ep`: line 210 assigns it with `as Ellipse`, which hands back null rather than throwing when the value is not a `Ellipse`, but line 211 then dereferences it directly as `ep.StrokeThickness` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ep` once before the first use and handle the null case, or cast with `(Ellipse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:211
This method contradicts itself about `ep`: line 216 assigns it with `as Ellipse`, which hands back null rather than throwing when the value is not a `Ellipse`, but line 217 then dereferences it directly as `ep.StrokeThickness` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ep` once before the first use and handle the null case, or cast with `(Ellipse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:217
This method contradicts itself about `ep`: line 221 assigns it with `as Ellipse`, which hands back null rather than throwing when the value is not a `Ellipse`, but line 222 then dereferences it directly as `ep.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ep` once before the first use and handle the null case, or cast with `(Ellipse)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:222
This method contradicts itself about `control`: line 36 assigns it with `as InputBoxBase`, which hands back null rather than throwing when the value is not a `InputBoxBase`, but line 37 then dereferences it directly as `control.ApplyText` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(InputBoxBase)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/LoginWindow/CustomControl/InputBoxBase.cs:37
This method contradicts itself about `control`: line 53 assigns it with `as InputBoxBase`, which hands back null rather than throwing when the value is not a `InputBoxBase`, but line 54 then dereferences it directly as `control.ApplyPlaceHolder` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `control` once before the first use and handle the null case, or cast with `(InputBoxBase)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/WPFDevelopers.Samples.Shared/ExampleViews/LoginWindow/CustomControl/InputBoxBase.cs:54
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — No access-control surface detected in the analyzed source — 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.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D21 Naming Consistency — Naming Consistency not included (check did not complete)
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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'.
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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no async method does work a token could cancel
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock src/Microsoft.Windows.Shell/JumpList.cs:618— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Microsoft.Windows.Shell/Standard/Utility.cs:149— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Microsoft.Windows.Shell/Standard/Utility.cs:152— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Microsoft.Windows.Shell/WindowChromeWorker.cs:218— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Samples.Shared/Helpers/BrowserHelper.cs:21— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:142— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:605— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:747— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:774— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:78— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:64— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Core/Helpers/OSVersionHelper.cs:83— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Resources.cs:213— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Resources.cs:266— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/WPFDevelopers.Shared/Resources.cs:280— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
WriteOnlyPrivateField src/Microsoft.Windows.Shell/Standard/PKEY.cs:15— private Guid _fmtid — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Microsoft.Windows.Shell/Standard/PKEY.cs:17— private uint _pid — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:69— private int zIndex — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:39— private TransformThumb parentElemt — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:419— private bool _isLoaded — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/CircleProgressBar/CircleProgressBar.cs:24— private TextBlock _textBlock — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:87— private PopupWindowHook _popupWindowHook — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:91— private PopupWindowHook _popupWindowHook — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/TimePicker/TimePicker.cs:50— private PopupWindowHook _popupWindowHook — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/DrawerMenu/DrawerMenuItem.cs:12— private bool _isExpanded — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/Mask/MaskControl.cs:13— private Visual visual — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs:62— private bool s_Loaded — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/DrawingPropertyMetadata.cs:71— private DrawingPropertyMetadataOptions options — assigned 2 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:21— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:24— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:27— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:30— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:21— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:24— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:27— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:30— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:21— CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:24— CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:27— CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:30— CS0067 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
Namespace dependency cycle src/WPFDevelopers.Shared/Core/ThemeChangedEvent.cs:5— The namespaces WPFDevelopers ↔ WPFDevelopers.Core depend on each other. The lightest dependency in the cycle is WPFDevelopers.Core → WPFDevelopers (WPFDevelopers.Core.ThemeChangedEvent → WPFDevelopers.ThemeType, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/WPFDevelopers.Shared/Core/Helpers/WindowHelpers.cs:12— The namespaces WPFDevelopers.Controls ↔ WPFDevelopers.Helpers ↔ WPFDevelopers.Utilities depend on each other. The lightest dependency in the cycle is WPFDevelopers.Helpers → WPFDevelopers.Utilities (WPFDevelopers.Helpers.MaskAdorner → WPFDevelopers.Utilities.AdornerContainer, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/WPFDevelopers.Samples.Shared/ExampleViews/PaginationExample.xaml.cs:6— The namespaces WPFDevelopers.Samples.ExampleViews ↔ WPFDevelopers.Samples.ViewModels depend on each other. The lightest dependency in the cycle is WPFDevelopers.Samples.ExampleViews → WPFDevelopers.Samples.ViewModels (WPFDevelopers.Samples.ExampleViews.PaginationExample → WPFDevelopers.Samples.ViewModels.PaginationExampleVM, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Boundary-crossing change coupling: ScreenCutExample.xaml.cs ↔ ScreenCut.cs src/WPFDevelopers.Samples.Shared/ExampleViews/ScreenCutExample.xaml.cs:1— `src/WPFDevelopers.Samples.Shared/ExampleViews/ScreenCutExample.xaml.cs` (context WPFDevelopers.Samples.Shared) and `src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs` (context WPFDevelopers.Shared) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e3f5fa7a` Fix issue: First Screenshot is a black Screen (#208 ) 👍; `f29d4a81` Fix issue #123; `95941666` #77 Fix issue — run `git show` on any of them.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 551 finding(s)
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×40
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleSelection.cs:77— This method contradicts itself about `ctrl`: line 75 assigns it with `as BubbleSelection`, which hands back null rather than throwing when the value is not a `BubbleSelection`, but line 77 then dereferences it directly as `ctrl.SetValue` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctrl` once before the first use and handle the null case, or cast with `(BubbleSelection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleSelection.cs:133— This method contradicts itself about `ctrl`: line 128 assigns it with `as BubbleSelection`, which hands back null rather than throwing when the value is not a `BubbleSelection`, but line 133 then dereferences it directly as `ctrl._items` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `ctrl` once before the first use and handle the null case, or cast with `(BubbleSelection)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleCanvas.cs:33— This method contradicts itself about `item`: line 31 assigns it with `as FrameworkElement`, which hands back null rather than throwing when the value is not a `FrameworkElement`, but line 33 then dereferences it directly as `item.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `item` once before the first use and handle the null case, or cast with `(FrameworkElement)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:85— This method contradicts itself about `rect1`: line 78 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 85 then dereferences it directly as `rect1.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rect1` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:86— This method contradicts itself about `scaleTransform`: line 85 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 86 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:93— This method contradicts itself about `rect1`: line 91 assigns it with `as Rectangle`, which hands back null rather than throwing when the value is not a `Rectangle`, but line 93 then dereferences it directly as `rect1.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rect1` once before the first use and handle the null case, or cast with `(Rectangle)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:99— This method contradicts itself about `scaleTransform`: line 93 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 99 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/CutImage/CutImage.cs:89— This method contradicts itself about `cutCustoms`: line 88 assigns it with `as CutImage`, which hands back null rather than throwing when the value is not a `CutImage`, but line 89 then dereferences it directly as `cutCustoms.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `cutCustoms` once before the first use and handle the null case, or cast with `(CutImage)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/Dashboard/Dashboard.cs:48— This method contradicts itself about `bar`: line 47 assigns it with `as Dashboard`, which hands back null rather than throwing when the value is not a `Dashboard`, but line 48 then dereferences it directly as `bar.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `bar` once before the first use and handle the null case, or cast with `(Dashboard)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:604— This method contradicts itself about `mltiSelectionSearchComboBox`: line 598 assigns it with `as MultiSelectionSearchComboBox`, which hands back null rather than throwing when the value is not a `MultiSelectionSearchComboBox`, but line 604 then dereferences it directly as `mltiSelectionSearchComboBox._listBox` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `mltiSelectionSearchComboBox` once before the first use and handle the null case, or cast with `(MultiSelectionSearchComboBox)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:603— This method contradicts itself about `collection`: line 602 assigns it with `as IList`, which hands back null rather than throwing when the value is not a `IList`, but line 603 then dereferences it directly as `collection.Count` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `collection` once before the first use and handle the null case, or cast with `(IList)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:265— This method contradicts itself about `parent`: line 253 assigns it with `as Canvas`, which hands back null rather than throwing when the value is not a `Canvas`, but line 265 then dereferences it directly as `parent.ActualWidth` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `parent` once before the first use and handle the null case, or cast with `(Canvas)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:322— This method contradicts itself about `rotateTransform`: line 321 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 322 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:66— This method contradicts itself about `rotateTransform`: line 65 assigns it with `as RotateTransform`, which hands back null rather than throwing when the value is not a `RotateTransform`, but line 66 then dereferences it directly as `rotateTransform.Angle` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `rotateTransform` once before the first use and handle the null case, or cast with `(RotateTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:74— This method contradicts itself about `thumb`: line 73 assigns it with `as Thumb`, which hands back null rather than throwing when the value is not a `Thumb`, but line 74 then dereferences it directly as `thumb.DataContext` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `thumb` once before the first use and handle the null case, or cast with `(Thumb)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/PieSegment/PieSegment.cs:55— This method contradicts itself about `pieSegment`: line 47 assigns it with `as PieSegment`, which hands back null rather than throwing when the value is not a `PieSegment`, but line 55 then dereferences it directly as `pieSegment.ColorArray` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `pieSegment` once before the first use and handle the null case, or cast with `(PieSegment)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/PieSegment/PieSegment.cs:55— This method contradicts itself about `array`: line 50 assigns it with `as ObservableCollection<PieSegmentModel>`, which hands back null rather than throwing when the value is not a `ObservableCollection<PieSegmentModel>`, but line 55 then dereferences it directly as `array.IndexOf` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `array` once before the first use and handle the null case, or cast with `(ObservableCollection<PieSegmentModel>)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:125— This method contradicts itself about `btn`: line 118 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 125 then dereferences it directly as `btn.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:126— This method contradicts itself about `scaleTransform`: line 125 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 126 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:132— This method contradicts itself about `btn`: line 131 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 132 then dereferences it directly as `btn.RenderTransform` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:138— This method contradicts itself about `scaleTransform`: line 132 assigns it with `as ScaleTransform`, which hands back null rather than throwing when the value is not a `ScaleTransform`, but line 138 then dereferences it directly as `scaleTransform.BeginAnimation` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `scaleTransform` once before the first use and handle the null case, or cast with `(ScaleTransform)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:145— This method contradicts itself about `btn`: line 144 assigns it with `as Button`, which hands back null rather than throwing when the value is not a `Button`, but line 145 then dereferences it directly as `btn.Content` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `btn` once before the first use and handle the null case, or cast with `(Button)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/ExampleViews/AnimationAudioExample.xaml.cs:26— This method contradicts itself about `animationAudio`: line 23 assigns it with `as AnimationAudio`, which hands back null rather than throwing when the value is not a `AnimationAudio`, but line 26 then dereferences it directly as `animationAudio.IsPlay` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `animationAudio` once before the first use and handle the null case, or cast with `(AnimationAudio)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/ExampleViews/NavMenu3DExample.xaml.cs:35— This method contradicts itself about `item`: line 34 assigns it with `as NavMenu3DItem`, which hands back null rather than throwing when the value is not a `NavMenu3DItem`, but line 35 then dereferences it directly as `item.Tag` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `item` once before the first use and handle the null case, or cast with `(NavMenu3DItem)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:195— This method contradicts itself about `view`: line 192 assigns it with `as BasicControlsExample`, which hands back null rather than throwing when the value is not a `BasicControlsExample`, but line 195 then dereferences it directly as `view.UserCollection` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `view` once before the first use and handle the null case, or cast with `(BasicControlsExample)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Samples.Shared/Converts/DrawPrizeIndexToColor.cs:20— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Samples.Shared/Converts/StateConvert.cs:31— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/FirstLastMarginConverter.cs:23— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/FilterVisibilityMultiConverter.cs:52— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/SelectedIndexToBoolConverter.cs:16— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/BreadCrumbBarConverter.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/WPFDevelopers.Shared/Core/Converts/ButtonPositionToColumnConverter.cs:18— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/ButtonPositionToColumnConverter.cs:35— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/ColorConverter.cs:71— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/ColorTypeToVisibilityConverter.cs:18— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/CornerRadiusToSurroundConverter.cs:57— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/GridLinesBorderBrushConverter.cs:25— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/LastColumnGridLineVisibilityConverter.cs:32— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/MultiBoolToVisibilityConverter.cs:19— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/NullToVisibilityConverter.cs:40— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/DirectionalThicknessConverter.cs:25— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/DatePickerToCurrentConverter.cs:40— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/HalfValueConverter.cs:20— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/OrientationConverter.cs:17— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/WidthHeightEqualValueConverter.cs:19— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/WidthHeightToRectConverter.cs:16— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:87— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:92— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:212— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Core/Converts/AngleToIsLargeConverter.cs:15— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
TooManyMethods: MapView REDACTED— TooManyMethods — 2437 significant lines (blank, comment-only and punctuation-only lines excluded), 146 methods. The bar is 30 methods; this is 116 over it, 4.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NativeMethods src/Microsoft.Windows.Shell/Standard/NativeMethods.cs— TooManyMethods — 562 significant lines (blank, comment-only and punctuation-only lines excluded), 136 methods. The bar is 30 methods; this is 106 over it, 4.53× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: GeometryHelper src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/GeometryHelper.cs— TooManyMethods — 264 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 30 methods; this is 31 over it, 2.03× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MarkdownViewer REDACTED— TooManyMethods — 953 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ScreenCut src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs— TooManyMethods — 1006 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DateRangePicker src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs— TooManyMethods — 622 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WaterfallPanel src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs— TooManyMethods — 572 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods, declared across 2 files: WaterfallPanel/WaterfallPanel.Virtualization.cs (39), WaterfallPanel/WaterfallPanel.cs (8). The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowChromeWorker src/Microsoft.Windows.Shell/WindowChromeWorker.cs— TooManyMethods — 468 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Utility src/Microsoft.Windows.Shell/Standard/Utility.cs— TooManyMethods — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: MultiSelectComboBox src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs— TooManyMethods — 599 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NumericBox src/WPFDevelopers.Shared/Controls/NumericBox/NumericBox.cs— TooManyMethods — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NotifyIcon src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs— TooManyMethods — 481 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BackToTopState src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs— TooManyMethods — 304 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DatePickerHelper src/WPFDevelopers.Shared/Core/Helpers/DatePickerHelper.cs— TooManyMethods — 256 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Window src/WPFDevelopers.Net45x/Window.cs— TooManyMethods — 295 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VirtualizingWrapPanel src/WPFDevelopers.Shared/Controls/VirtualizingWrapPanel/VirtualizingWrapPanel.cs— TooManyMethods — 224 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Window src/WPFDevelopers.Net40/Window.cs— TooManyMethods — 286 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
AX2 · Stateful singletons· Process-global static state · ×15
Process-global static state: Dialog src/WPFDevelopers.Shared/Controls/Dialog/Dialog.cs:18— `Dialog` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (OpenDialogs; e.g. `OpenDialogs` at line 272). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: PropertyAccessor src/WPFDevelopers.Shared/Controls/Filter/PropertyAccessor.cs:7— `PropertyAccessor` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_cache; e.g. `_cache` at line 27). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Toast src/WPFDevelopers.Shared/Controls/Toast/Toast.cs:9— `Toast` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_toastExt, _position; e.g. `_toastExt` at line 117). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Loading src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:13— `Loading` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_loadingMap, _adornerMap, _wrapperMap; e.g. `_loadingMap` at line 131). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: NotifyIcon src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs:26— `NotifyIcon` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_NotifyIcon; e.g. `s_NotifyIcon` at line 290). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ScreenCut src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:91— `ScreenCut` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CaptureScreenID; e.g. `CaptureScreenID` at line 340). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: DatePickerHelper src/WPFDevelopers.Shared/Core/Helpers/DatePickerHelper.cs:13— `DatePickerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_timeStorage, _textBoxStorage, _timePickerStorage; e.g. `_timeStorage` at line 321). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: DesignerHelper src/WPFDevelopers.Shared/Core/Helpers/ControlsHelper.cs:230— `DesignerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isInDesignMode; e.g. `_isInDesignMode` at line 240). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ElementHelper src/WPFDevelopers.Shared/Core/Helpers/ElementHelper.cs:7— `ElementHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isMetadataOverridden; e.g. `_isMetadataOverridden` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: OSVersionHelper src/WPFDevelopers.Shared/Core/Helpers/OSVersionHelper.cs:12— `OSVersionHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isSnapLayoutSupported; e.g. `_isSnapLayoutSupported` at line 60). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: GeometryEffect src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/GeometryEffect.cs:9— `GeometryEffect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultGeometryEffect; e.g. `defaultGeometryEffect` at line 53). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Global src/WPFDevelopers.Shared/Microsoft.Expression.Media.Effects/Global.cs:6— `Global` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (assemblyShortName; e.g. `assemblyShortName` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ThumbButtonInfoCollection src/Microsoft.Windows.Shell/ThumbButtonInfoCollection.cs:5— `ThumbButtonInfoCollection` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_empty; e.g. `s_empty` at line 20). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: MessageWindow src/Microsoft.Windows.Shell/Standard/MessageWindow.cs:10— `MessageWindow` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_windowLookup; e.g. `s_windowLookup` at line 79). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Utility src/Microsoft.Windows.Shell/Standard/Utility.cs:17— `Utility` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (s_bitDepth; e.g. `s_bitDepth` at line 349). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Swallowed exception (empty catch) src/WPFDevelopers.Samples.Shared/Helpers/BrowserHelper.cs:21— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:78— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Core/Helpers/OSVersionHelper.cs:83— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:64— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:142— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:605— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:747— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:774— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Resources.cs:213— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Resources.cs:266— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/WPFDevelopers.Shared/Resources.cs:280— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Microsoft.Windows.Shell/JumpList.cs:618— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Microsoft.Windows.Shell/Standard/Utility.cs:149— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Microsoft.Windows.Shell/Standard/Utility.cs:152— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Microsoft.Windows.Shell/WindowChromeWorker.cs:218— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
MethodTooLong: MainVM.MenuItemSelection src/WPFDevelopers.Samples.Shared/ViewModels/MainVM.cs:616— MethodTooLong — MenuItemSelection runs 396 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 296 over it, 3.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainVM.GetMenuIconSource src/WPFDevelopers.Samples.Shared/ViewModels/MainVM.cs:269— MethodTooLong — GetMenuIconSource runs 262 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 162 over it, 2.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FocusCarousel.FocusCarousel_MouseLeftButtonDown src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:401— MethodTooLong — FocusCarousel_MouseLeftButtonDown runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CardCarousel.PlayCarouselWithIndexOutRange src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:1025— MethodTooLong — PlayCarouselWithIndexOutRange runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CardCarousel.PlayCarouselLeftToRight src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:474— MethodTooLong — PlayCarouselLeftToRight runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CardCarousel.PlayCarouselRightToLeft src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:735— MethodTooLong — PlayCarouselRightToLeft runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AbbreviatedGeometryParser.Parse src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:77— MethodTooLong — Parse runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LineChartExample.UserControl_Loaded src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:39— MethodTooLong — UserControl_Loaded runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BallLoading.LoadAnimationBall1Rotate src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:283— MethodTooLong — LoadAnimationBall1Rotate runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BallLoading.LoadAnimationBall1RotateBack src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:462— MethodTooLong — LoadAnimationBall1RotateBack runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MarkdownViewer.ParseMarkdown REDACTED:1154— MethodTooLong — ParseMarkdown runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FocusCarousel.OnSizeChangedCallback src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:204— MethodTooLong — OnSizeChangedCallback runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CountdownTimer.OnApplyTemplate src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:61— MethodTooLong — OnApplyTemplate runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Loading.WrapElement src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:194— MethodTooLong — WrapElement runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:651— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:651-655 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:715-719 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:651` 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/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:106— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:106-110 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/ArcGeometrySource.cs:329-333 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:108— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:108-112 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:113-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:106` calls `SetIfDifferent`, `EnsureListCount`, `ArcSegment` and `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathFigureHelper.cs:113` 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 (5 lines × 2) src/Microsoft.Windows.Shell/WindowChromeWorker.cs:469— src/Microsoft.Windows.Shell/WindowChromeWorker.cs:469-473 | src/Microsoft.Windows.Shell/WindowChromeWorker.cs:476-480 — both copies are in the same file, so extract the 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/Microsoft.Windows.Shell/WindowChromeWorker.cs:469` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/CardCarouselExample.xaml.cs:18— src/WPFDevelopers.Samples.Shared/ExampleViews/CardCarouselExample.xaml.cs:18-22 | src/WPFDevelopers.Samples.Shared/ExampleViews/CarouselExample.xaml.cs:18-22 — 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/WPFDevelopers.Net40/Window.cs:103— src/WPFDevelopers.Net40/Window.cs:103-107 | src/WPFDevelopers.Net45x/Window.cs:107-111 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) src/WPFDevelopers.Net40/Window.cs:225— src/WPFDevelopers.Net40/Window.cs:225-229 | src/WPFDevelopers.Net45x/Window.cs:229-233 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/WPFDevelopers.Net40/Window.cs:250— src/WPFDevelopers.Net40/Window.cs:250-254 | src/WPFDevelopers.Net45x/Window.cs:254-258 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Controls/BaseControls/ItemsControlBase.cs:66— src/WPFDevelopers.Shared/Controls/BaseControls/ItemsControlBase.cs:66-70 | src/WPFDevelopers.Shared/Controls/CircleMenu/CircleMenu.cs:411-415 — 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/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15— src/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15-19 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs:56-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeContentShape.cs:17— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeContentShape.cs:17-21 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeShape.cs:143-147 — 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/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15— src/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15-19 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs:56-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15— src/WPFDevelopers.Shared/Controls/AnimationAudio/AudioWindow.cs:15-19 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs:56-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:153— src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:153-157 | src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:162-166 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:153` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×12
Disposable created and abandoned in the method that made it REDACTED:195— `streamReader` is a `StreamReader`, which implements `IDisposable`, and it is created here (line 195). Every use of it in `GetCodeText` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var streamReader = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:107— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 107). Every use of it in `Loading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:138— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 138). Every use of it in `LoadingTask_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:159— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 159). Every use of it in `BtnLoading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/LoadingExample.xaml.cs:41— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 41). Every use of it in `Btn_LoadingExtClick` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:16— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 16). Every use of it in `Loading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:34— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 34). Every use of it in `LoadingTask_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:53— `task` is a `Task`, which implements `IDisposable`, and it is created here (line 53). Every use of it in `BtnLoading_Click` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var task = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs:119— `process` is a `Process`, which implements `IDisposable`, and it is created here (line 119). Every use of it in `ShowScreenShot` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var process = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it REDACTED:4308— `client` is a `WebClient`, which implements `IDisposable`, and it is created here (line 4308). Every use of it in `DownloadTileImageAsync` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var client = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:65— `regKey` is a `RegistryKey`, which implements `IDisposable`, and it is created here (line 65). Every use of it in `GetWindowOSVersion` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var regKey = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/WPFDevelopers.Shared/Core/Helpers/ControlsHelper.cs:48— `player1` is a `SoundPlayer`, which implements `IDisposable`, and it is created here (line 48). Every use of it in `WindowShake` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var player1 = …;`), which releases it at the end of the scope on every path including a throw.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:733— src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:733-739 | src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:748-754 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:124— src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:124-130 | src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:333-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:269— src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:269-275 | src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:387-393 — both copies are in the same file, so extract the block into 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) REDACTED:927— REDACTED:927-933 | REDACTED:957-963 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:298— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:298-304 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:300-306 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/Charts/ChartBar.cs:27— src/WPFDevelopers.Shared/Controls/Charts/ChartBar.cs:27-33 | src/WPFDevelopers.Shared/Controls/Charts/ChartLine.cs:49-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/Charts/ChartBar.cs:27` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:44— src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:44-50 | src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:59-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:340— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:340-346 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:686-692 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:215— src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:215-221 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelector.cs:21-27 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:215— src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:215-221 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelector.cs:21-27 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:340— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:340-346 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:686-692 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
FileTooLong: REDACTED REDACTED— FileTooLong — 2462 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1962 over it, 4.92× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ScreenCut/ScreenCut.cs src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs— FileTooLong — 1078 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 578 over it, 2.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1001 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 501 over it, 2.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ViewModels/MainVM.cs src/WPFDevelopers.Samples.Shared/ViewModels/MainVM.cs— FileTooLong — 891 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 391 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Carousel/CardCarousel.cs src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs— FileTooLong — 789 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 289 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: DateRangePicker/DateRangePicker.cs src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: MultiSelectComboBox/MultiSelectComboBox.cs src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 119 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Standard/NativeMethods.cs src/Microsoft.Windows.Shell/Standard/NativeMethods.cs— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Loadings/BallLoading.cs src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: NotifyIcon/NotifyIcon.cs src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Stateful shared instance: SampleLanguageManager src/WPFDevelopers.Samples.Shared/SampleLanguageManager.cs:22— `SampleLanguageManager` keeps one instance of itself in the static `LazyInstance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_exampleViews, _initialized; e.g. `_exampleViews` at line 89).
Stateful shared instance: ThemeManager src/WPFDevelopers.Shared/ThemeManager.cs:11— `ThemeManager` keeps one instance of itself in the static `_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_themeAnimating; e.g. `_themeAnimating` at line 90).
Stateful shared instance: LanguageManager src/WPFDevelopers.Shared/LanguageManager.cs:9— `LanguageManager` keeps one instance of itself in the static `_lazy`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_currentCulture; e.g. `_currentCulture` at line 22).
Stateful shared instance: ToastExt src/WPFDevelopers.Shared/Controls/Toast/ToastExt.cs:9— `ToastExt` is not registered, but `Toast` creates it and keeps it in the static `_toastExt`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (IsPosition; e.g. `IsPosition` at line 48).
Stateful shared instance: DefaultLoading src/WPFDevelopers.Shared/Controls/Loading/DefaultLoading.cs:7— `DefaultLoading` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_indicator; e.g. `_indicator` at line 28).
Stateful shared instance: Magnifier src/WPFDevelopers.Shared/Controls/Magnifier/Magnifier.cs:10— `Magnifier` keeps one instance of itself in the static `Default`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_factor, _adornerContainer, _border, _visualBrush; e.g. `_factor` at line 70).
Stateful shared instance: HandleType src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/Interop/HandleCollector.cs:95— `HandleType` is not registered, but `HandleCollector` creates it and keeps it in the static `handleTypes`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (threshHold; e.g. `threshHold` at line 165).
Stateful shared instance: AdornerContainer src/WPFDevelopers.Shared/Core/Utilities/AdornerContainer.cs:7— `AdornerContainer` is not registered, but the singleton `Magnifier` creates it and keeps it in `_adornerContainer`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_child; e.g. `_child` at line 21).
Hotspot: src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs:435— src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in BackToTopState.UpdateButton at line 435. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 00:53:33 +08:00' --until='2026-11-14 00:53:33 +08:00' --full-history --no-merges -- src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs`: 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/WPFDevelopers.Net40/Window.cs src/WPFDevelopers.Net40/Window.cs:386— src/WPFDevelopers.Net40/Window.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Window.WindowProc at line 386. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 00:53:33 +08:00' --until='2026-11-14 00:53:33 +08:00' --full-history --no-merges -- src/WPFDevelopers.Net40/Window.cs`: 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/WPFDevelopers.Net45x/Window.cs src/WPFDevelopers.Net45x/Window.cs:394— src/WPFDevelopers.Net45x/Window.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Window.WindowProc at line 394. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 00:53:33 +08:00' --until='2026-11-14 00:53:33 +08:00' --full-history --no-merges -- src/WPFDevelopers.Net45x/Window.cs`: 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: REDACTED REDACTED:2688— REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in MapView.UpdateMapShapesLayer at line 2688. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 00:53:33 +08:00' --until='2026-11-14 00:53:33 +08:00' --full-history --no-merges -- REDACTED`: 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/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs src/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs:103— src/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in SpacingState.Update at line 103. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 00:53:33 +08:00' --until='2026-11-14 00:53:33 +08:00' --full-history --no-merges -- src/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs`: 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.
ClassTooLong: MainVM src/WPFDevelopers.Samples.Shared/ViewModels/MainVM.cs— ClassTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 468 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CardCarousel src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs— ClassTooLong — 765 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 365 over it, 1.91× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BallLoading src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs— ClassTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 137 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DrawingPanel src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FocusCarousel src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs— ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
Members sharing a duplicated core (4 members, 50+ identical tokens) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:331— src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:331-371 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:374-415 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:418-458 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:461-502 — 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) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:596— src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:596-627 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:631-663 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:667-698 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:702-733 — 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) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:320— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:320-336 | src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:467-496 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:643-659 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:753-782 — 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) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:98— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:98-132 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:74-108 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:94-129 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:149-184 — 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) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:252— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:252-276 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:199-223 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:132-156 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:187-211 — 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 (10 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:19— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:19-28 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:18-27 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:530— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:530-539 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:717-726 — 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/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:530` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:114— src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:114-123 | src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:133-142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) REDACTED:244— REDACTED:244-253 | REDACTED:259-268 — both copies are in the same file, so extract the 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 `REDACTED:244` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `block` to `UnorderedListBlock` in one and `OrderedListBlock` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:171— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:171-180 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:217-226 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:171` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (6 lines × 2) src/WPFDevelopers.Net40/Window.cs:469— src/WPFDevelopers.Net40/Window.cs:469-474 | src/WPFDevelopers.Net45x/Window.cs:468-473 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1245— src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1245-1250 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1281-1286 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1245` 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) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1263— src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1263-1268 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1298-1303 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1263` 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 (6 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:393— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:393-398 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:301-306 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:393— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:393-398 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:301-306 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) REDACTED:3704— REDACTED:3704-3719 | REDACTED:3723-3738 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:40— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:40-55 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:17-32 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:58` calls `FindParent` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:35` 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 × 2) REDACTED:3280— REDACTED:3280-3295 | REDACTED:3394-3409 — both copies are in the same file, so extract the 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 `REDACTED:3280` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (16 lines × 2) src/Microsoft.Windows.Shell/Standard/CS.cs:5— src/Microsoft.Windows.Shell/Standard/CS.cs:5-20 | src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/CS.cs:5-20 — before extracting anything, compare `src/Microsoft.Windows.Shell/Standard/CS.cs` and `src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/CS.cs` as WHOLE FILES: 88% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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 `src/Microsoft.Windows.Shell/Standard/CS.cs:5` 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/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:39— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:39-47 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:39-47 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:360— src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:360-368 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:379-387 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:360` 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/WPFDevelopers.Shared/Controls/Toast/ToastAdorner.cs:37— src/WPFDevelopers.Shared/Controls/Toast/ToastAdorner.cs:37-45 | src/WPFDevelopers.Shared/Core/Utilities/AdornerContainer.cs:18-26 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/WPFDevelopers.Shared/Controls/Toast/ToastAdorner.cs:37— src/WPFDevelopers.Shared/Controls/Toast/ToastAdorner.cs:37-45 | src/WPFDevelopers.Shared/Core/Utilities/AdornerContainer.cs:18-26 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/WPFDevelopers.Net40/Window.cs:86— src/WPFDevelopers.Net40/Window.cs:86-93 | src/WPFDevelopers.Net45x/Window.cs:71-78 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) src/WPFDevelopers.Net40/Window.cs:331— src/WPFDevelopers.Net40/Window.cs:331-338 | src/WPFDevelopers.Net45x/Window.cs:339-346 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:51— src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:51-58 | src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:59-66 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:51` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) src/WPFDevelopers.Net40/Window.cs:240— src/WPFDevelopers.Net40/Window.cs:240-247 | src/WPFDevelopers.Net45x/Window.cs:244-251 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Swallowed exception (caught, then discarded) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:152— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) REDACTED:134— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Microsoft.Windows.Shell/JumpList.cs:582— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:69— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
BarePragmaDisable src/Microsoft.Windows.Shell/Standard/MOUSEINPUT.cs:7— #pragma warning disable 0649 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable REDACTED:4256— #pragma warning disable 0618 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable src/WPFDevelopers.Shared/LanguageManager.cs:12— #pragma warning disable CA1416 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
DeadPreprocessorBranch src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/Interop/HandleCollector.cs:135— #if DEBUG_HANDLECOLLECTOR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/Interop/HandleCollector.cs:166— #if DEBUG_HANDLECOLLECTOR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
DeadPreprocessorBranch src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/Interop/HandleCollector.cs:180— #if DEBUG_HANDLECOLLECTOR — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
Duplicated block (30 lines × 2) REDACTED:3610— REDACTED:3610-3639 | REDACTED:3642-3671 — both copies are in the same file, so extract the 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 `REDACTED:3610` 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) src/Microsoft.Windows.Shell/Standard/WS.cs:5— src/Microsoft.Windows.Shell/Standard/WS.cs:5-34 | src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WS.cs:5-34 — before extracting anything, compare `src/Microsoft.Windows.Shell/Standard/WS.cs` and `src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WS.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Microsoft.Windows.Shell/Standard/WS.cs:5` 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) src/Microsoft.Windows.Shell/Standard/WS_EX.cs:5— src/Microsoft.Windows.Shell/Standard/WS_EX.cs:5-34 | src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WS_EX.cs:5-34 — before extracting anything, compare `src/Microsoft.Windows.Shell/Standard/WS_EX.cs` and `src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WS_EX.cs` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Microsoft.Windows.Shell/Standard/WS_EX.cs:5` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:80— src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:80-90 | src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:120-130 — 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/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/WPFDevelopers.Samples.Shared/Controls/ImageCrop/ImageCrop.cs:92` calls `SetZIndex` and `src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:132` 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) src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:234— src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:234-244 | src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:270-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:234` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:231— src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:231-241 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:285-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:231` 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) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:23— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:23-35 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:23-35 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:157— src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:157-169 | src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:173-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:616— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:616-629 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:681-693 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:616` 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 × 3) REDACTED:3251— REDACTED:3251-3256 | REDACTED:3323-3328 | REDACTED:3374-3379 — 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 `REDACTED:3251` 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 × 3) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:231— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:231-236 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:178-183 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:96-101 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:231— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:231-236 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:178-183 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:96-101 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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.
Low cohesion: MapViewFeaturesWindow (LCOM4 18) src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewFeaturesWindow.xaml.cs:12— MapViewFeaturesWindow's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NotifyIconExample (LCOM4 5) src/WPFDevelopers.Samples.Shared/ExampleViews/NotifyIconExample.xaml.cs:9— NotifyIconExample's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CarouselBase (LCOM4 4) src/WPFDevelopers.Shared/Controls/Carousel/CarouselBase.cs:15— CarouselBase's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs· Both branches are identical · ×3
Both branches are identical — the condition decides nothing src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:194— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:202— The `if` and its `else` contain the same 2 statements, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Both branches are identical — the condition decides nothing src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:224— The `if` and its `else` contain the same 1 statement, so no input can make the condition matter. Implement the distinction that was intended, or drop the branch and keep the body.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:87— `AddChild` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:92— `AddText` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:212— `CreateInstanceCore` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Comparison is always false — nothing compares equal to NaN src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:214— `vHeight == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead.
Comparison is always false — nothing compares equal to NaN src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:214— `vWidth == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead.
Comparison is always false — nothing compares equal to NaN src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:269— `_displayWidth == double.NaN` is false for every value, including NaN itself: IEEE 754 leaves NaN unordered with everything, so `==` against `double.NaN` never depends on the other operand. Use `double.IsNaN(…)` — the test that was intended, and the branch this guards is dead.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×3
NuGet dependencies are not locked src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj:10— src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:14— src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
NuGet dependencies are not locked src/WPFDevelopers.Samples45x/WPFDevelopers.Samples45x.csproj:5— src/WPFDevelopers.Samples45x/WPFDevelopers.Samples45x.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:113— src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:113-129 | src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:132-148 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) REDACTED:241— REDACTED:241-253 | REDACTED:256-268 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (6 members, 50+ identical tokens) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:75— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:75-95 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:51-71 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:63-90 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:277-294 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:219-249 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:279-296 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:328— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:328-351 | src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:72-97 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:275-300 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:221-246 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:97-122 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:72-97 — 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:57— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:57-69 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:260-272 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:206-218 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:82-94 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:57-69 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) REDACTED:2938— REDACTED:2938-2976 | REDACTED:3151-3234 | REDACTED:3237-3306 | REDACTED:3309-3357 | REDACTED:3360-3420 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (32 lines × 2) src/WPFDevelopers.Net40/Window.cs:161— src/WPFDevelopers.Net40/Window.cs:161-192 | src/WPFDevelopers.Net45x/Window.cs:165-196 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (32 lines × 2) REDACTED:1732— REDACTED:1732-1763 | REDACTED:1767-1798 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:149— src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:149-176 | src/WPFDevelopers.Samples.Shared/ExampleViews/LineChartExample.xaml.cs:179-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28 lines × 2) src/Microsoft.Windows.Shell/Standard/WNDCLASSEX.cs:6— src/Microsoft.Windows.Shell/Standard/WNDCLASSEX.cs:6-33 | src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WNDCLASSEX.cs:6-33 — before extracting anything, compare `src/Microsoft.Windows.Shell/Standard/WNDCLASSEX.cs` and `src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WNDCLASSEX.cs` as WHOLE FILES: 84% 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 `src/Microsoft.Windows.Shell/Standard/WNDCLASSEX.cs:6` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) src/WPFDevelopers.Net40/Window.cs:19— src/WPFDevelopers.Net40/Window.cs:19-38 | src/WPFDevelopers.Net45x/Window.cs:18-37 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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 `src/WPFDevelopers.Net40/Window.cs: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 (20 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:205— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:205-224 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:394-413 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:205` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:202` calls `Point` and `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/PanningItems.cs:393` 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 (18 lines × 2) REDACTED:2765— REDACTED:2765-2782 | REDACTED:2788-2805 — both copies are in the same file, so extract the 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 `REDACTED:2765` 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 (18 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:277— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:277-294 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:279-296 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 4) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:74— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:74-86 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:280-292 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:230-242 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:282-294 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/ComboBoxExample.xaml.cs:11— src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/ComboBoxExample.xaml.cs:11-23 | src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/ListBoxExample.xaml.cs:11-23 | src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/ListViewExample.xaml.cs:11-23 | src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/TreeViewExample.xaml.cs:11-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/ComboBoxExample.xaml.cs:11` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 3) REDACTED:3705— REDACTED:3705-3711 | REDACTED:3724-3730 | REDACTED:3743-3749 — 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 `REDACTED:3705` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:143— src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:143-149 | src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:159-165 | src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:175-181 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:143` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (5 lines × 6) REDACTED:805— REDACTED:805-809 | REDACTED:812-816 | REDACTED:819-823 | REDACTED:826-830 | REDACTED:833-837 | REDACTED:840-844 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 6) REDACTED:805— REDACTED:805-809 | REDACTED:812-816 | REDACTED:819-823 | REDACTED:826-830 | REDACTED:833-837 | REDACTED:840-844 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
End-of-life runtime: .NET Framework net40 src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj:5— src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj declares .NET Framework net40 as this project's target framework, and .NET Framework 4.0, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net40 src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:3— src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj declares .NET Framework net40 as this project's target framework, and .NET Framework 4.0, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Condition was already decided — an earlier guard makes this test constant src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:140— Control only reaches here when `isLoading` is true, because the guard on line 129 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Condition was already decided — an earlier guard makes this test constant src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:169— Control only reaches here when `isLoading` is true, because the guard on line 129 exits otherwise. This test is therefore always true and its `else`, and any code it is meant to skip, is unreachable. Implement the distinction that was intended, or delete the test.
Weak hash algorithm src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:81— MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
Weak hash algorithm src/Microsoft.Windows.Shell/Standard/Utility.cs:520— MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
AbbreviatedGeometryParser.Parse (cyclomatic 41) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:77— AbbreviatedGeometryParser.Parse has cyclomatic complexity 41 (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.
FocusCarousel.FocusCarousel_MouseLeftButtonDown (cyclomatic 32) src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:401— FocusCarousel.FocusCarousel_MouseLeftButtonDown has cyclomatic complexity 32 (threshold 15). Of this number, 31 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
SvgViewer.ParseSvgPaths (cyclomatic 30) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:134— SvgViewer.ParseSvgPaths has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MarkdownViewer.ParseMarkdown (cyclomatic 30) REDACTED:1154— MarkdownViewer.ParseMarkdown has cyclomatic complexity 30 (threshold 15). Of this number, 26 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
MapView.UpdateMapShapesLayer (cyclomatic 28) REDACTED:2688— MapView.UpdateMapShapesLayer has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MultiSelectComboBox.OnSelectionChanged (cyclomatic 27) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:223— MultiSelectComboBox.OnSelectionChanged has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BackToTopState.UpdateButton (cyclomatic 26) src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs:435— BackToTopState.UpdateButton has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TimelinePanel.MeasureOverride (cyclomatic 26) src/WPFDevelopers.Shared/Controls/Timeline/TimelinePanel.cs:17— TimelinePanel.MeasureOverride has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MapView.UpdateMapItemsLayer (cyclomatic 26) REDACTED:3573— MapView.UpdateMapItemsLayer has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 belong to 4 function literals inside it that branch. 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.
MarkdownViewer.ClassifyCodeToken (cyclomatic 26) REDACTED:901— MarkdownViewer.ClassifyCodeToken has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScreenCutAdorner.GetResizeThumb (cyclomatic 26) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:103— ScreenCutAdorner.GetResizeThumb has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 143). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
IPEditBox.TextBox_PreviewKeyDown (cyclomatic 25) src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:203— IPEditBox.TextBox_PreviewKeyDown has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Loading.WrapElement (cyclomatic 25) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:194— Loading.WrapElement has cyclomatic complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
SampleLanguageManager.LocalizeTree (cyclomatic 23) src/WPFDevelopers.Samples.Shared/SampleLanguageManager.cs:225— SampleLanguageManager.LocalizeTree has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Window.WindowProc (cyclomatic 22) src/WPFDevelopers.Net40/Window.cs:386— Window.WindowProc has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MapItemsLayer.UpdateDefaultItems (cyclomatic 22) src/WPFDevelopers.Shared/Controls/MapView/MapItemsLayer.cs:426— MapItemsLayer.UpdateDefaultItems has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScreenCut.DrawArrowControl (cyclomatic 22) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1199— ScreenCut.DrawArrowControl has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MarkdownViewer.ClassifyMarkupToken (cyclomatic 21) REDACTED:952— MarkdownViewer.ClassifyMarkupToken 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.
GeometryHelper.PathSegmentEquals (cyclomatic 21) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/GeometryHelper.cs:320— GeometryHelper.PathSegmentEquals has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Vector2D.IsPointPolygonalArea (cyclomatic 20) src/WPFDevelopers.Samples.Shared/ExampleViews/CanvasHandWriting/Vector2D.cs:140— Vector2D.IsPointPolygonalArea has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ThumbAdorner.GetResizeThumb (cyclomatic 20) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:306— ThumbAdorner.GetResizeThumb has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 332). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ThumbAdorner2.GetResizeThumb (cyclomatic 20) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:308— ThumbAdorner2.GetResizeThumb has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 324). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
MapViewFeaturesWindow.BringCircleToFrontButton_Click (cyclomatic 20) src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewFeaturesWindow.xaml.cs:235— MapViewFeaturesWindow.BringCircleToFrontButton_Click has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CardCarousel.PlayCarouselWithIndexOutRange (cyclomatic 20) src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:1025— CardCarousel.PlayCarouselWithIndexOutRange has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScreenCut.DrawMultipleControl (cyclomatic 20) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1325— ScreenCut.DrawMultipleControl has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbbreviatedGeometryParser.ReadDouble (cyclomatic 20) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:339— AbbreviatedGeometryParser.ReadDouble has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Window.WindowProc (cyclomatic 20) src/WPFDevelopers.Net45x/Window.cs:394— Window.WindowProc has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OtpBox.TextBox_PreviewKeyDown (cyclomatic 19) src/WPFDevelopers.Shared/Controls/OtpBox/OtpBox.cs:212— OtpBox.TextBox_PreviewKeyDown has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Loading.CreateLoading (cyclomatic 19) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:114— Loading.CreateLoading has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Loading.UnwrapElement (cyclomatic 19) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:354— Loading.UnwrapElement has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScreenCut.Dispose (cyclomatic 19) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:261— ScreenCut.Dispose has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ElementAdorner.CreateThumb (cyclomatic 18) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:153— ElementAdorner.CreateThumb has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 168). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
WaterfallPanel.MeasureVirtualized (cyclomatic 18) src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:145— WaterfallPanel.MeasureVirtualized 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.
TimePicker.GetDisplayTimeFormat (cyclomatic 18) src/WPFDevelopers.Shared/Controls/TimePicker/TimePicker.cs:131— TimePicker.GetDisplayTimeFormat 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.
SpacingState.Update (cyclomatic 18) src/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs:103— SpacingState.Update 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.
MapView.CreateFeatureClickEventArgs (cyclomatic 18) REDACTED:3053— MapView.CreateFeatureClickEventArgs has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GeometryHelper.GeometryEquals (cyclomatic 18) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/GeometryHelper.cs:239— GeometryHelper.GeometryEquals has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PolylineHelper.PathMarch (cyclomatic 18) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PolylineHelper.cs:9— PolylineHelper.PathMarch 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.
TransformExtensions.TransformEquals (cyclomatic 18) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/TransformExtensions.cs:90— TransformExtensions.TransformEquals has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DateRangePicker.SetIsHighlight (cyclomatic 17) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:922— DateRangePicker.SetIsHighlight has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
Dialog.ShowAsync (cyclomatic 17) src/WPFDevelopers.Shared/Controls/Dialog/Dialog.cs:239— Dialog.ShowAsync has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BallLoading.BallMoveColor (cyclomatic 17) src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:642— BallLoading.BallMoveColor 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.
MapView.TryGetPolylineHit (cyclomatic 17) REDACTED:3150— MapView.TryGetPolylineHit 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.
MarkdownViewer.ParseInlines (cyclomatic 17) REDACTED:1422— MarkdownViewer.ParseInlines 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.
MultiSelectComboBox.SearchText (cyclomatic 17) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:694— MultiSelectComboBox.SearchText 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.
DistributionStrategy.DistributeInternal (cyclomatic 17) src/WPFDevelopers.Shared/Microsoft.Expression.Controls/DistributionStrategy.cs:75— DistributionStrategy.DistributeInternal has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
PathPanel.ArrangeOverride (cyclomatic 17) src/WPFDevelopers.Shared/Microsoft.Expression.Controls/PathPanel.cs:71— PathPanel.ArrangeOverride 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.
PolylineData.SmoothNormal (cyclomatic 17) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PolylineData.cs:55— PolylineData.SmoothNormal 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.
JumpList._BuildShellLists (cyclomatic 17) src/Microsoft.Windows.Shell/JumpList.cs:239— JumpList._BuildShellLists 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.
IPEditBox.PasteTextIPTextBox (cyclomatic 16) src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:291— IPEditBox.PasteTextIPTextBox has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SvgViewer.LoadAndRenderSvg (cyclomatic 16) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:273— SvgViewer.LoadAndRenderSvg has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TimelinePanel.OnRender (cyclomatic 16) src/WPFDevelopers.Shared/Controls/Timeline/TimelinePanel.cs:98— TimelinePanel.OnRender has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NumericBox.ContinueChangeValue (cyclomatic 16) src/WPFDevelopers.Shared/Controls/NumericBox/NumericBox.cs:678— NumericBox.ContinueChangeValue has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CircleMenu.GetVisibleBoundsInSelf (cyclomatic 16) src/WPFDevelopers.Shared/Controls/CircleMenu/CircleMenu.cs:504— CircleMenu.GetVisibleBoundsInSelf has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MapView.TryGetPolygonHit (cyclomatic 16) REDACTED:3236— MapView.TryGetPolygonHit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TaskbarItemInfo._UpdateThumbButtons (cyclomatic 16) src/Microsoft.Windows.Shell/TaskbarItemInfo.cs:480— TaskbarItemInfo._UpdateThumbButtons has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BareSuppressMessage repeated across 27 files src/Microsoft.Windows.Shell/JumpList.cs:25— The identical BareSuppressMessage (`SuppressMessage`) appears in 27 files (344 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 344 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
AbbreviatedGeometryParser.Parse (cognitive 90) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:77— AbbreviatedGeometryParser.Parse has cognitive complexity 90 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectComboBox.OnSelectionChanged (cognitive 77) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:223— MultiSelectComboBox.OnSelectionChanged has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MarkdownViewer.ParseMarkdown (cognitive 59) REDACTED:1154— MarkdownViewer.ParseMarkdown has cognitive complexity 59 (threshold 15). Of this number, 55 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusCarousel.FocusCarousel_MouseLeftButtonDown (cognitive 58) src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:401— FocusCarousel.FocusCarousel_MouseLeftButtonDown has cognitive complexity 58 (threshold 15). Of this number, 57 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SvgViewer.ParseSvgPaths (cognitive 56) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:134— SvgViewer.ParseSvgPaths has cognitive complexity 56 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Vector2D.IsPointPolygonalArea (cognitive 52) src/WPFDevelopers.Samples.Shared/ExampleViews/CanvasHandWriting/Vector2D.cs:140— Vector2D.IsPointPolygonalArea has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectComboBox.SearchText (cognitive 48) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:694— MultiSelectComboBox.SearchText has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SampleLanguageManager.LocalizeTree (cognitive 43) src/WPFDevelopers.Samples.Shared/SampleLanguageManager.cs:225— SampleLanguageManager.LocalizeTree has cognitive complexity 43 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Loading.WrapElement (cognitive 42) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:194— Loading.WrapElement has cognitive complexity 42 (threshold 15). Of this number, 35 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.UpdateMapShapesLayer (cognitive 42) REDACTED:2688— MapView.UpdateMapShapesLayer has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.UpdateMapItemsLayer (cognitive 41) REDACTED:3573— MapView.UpdateMapItemsLayer has cognitive complexity 41 (threshold 15). Of this number, 37 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SixGirdView.MeasureOverride (cognitive 41) src/WPFDevelopers.Shared/Controls/Panel/SixGirdView.cs:65— SixGirdView.MeasureOverride has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
JumpList._BuildShellLists (cognitive 40) src/Microsoft.Windows.Shell/JumpList.cs:239— JumpList._BuildShellLists has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Window.WindowProc (cognitive 39) src/WPFDevelopers.Net40/Window.cs:386— Window.WindowProc has cognitive complexity 39 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
PolylineData.SmoothNormal (cognitive 38) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PolylineData.cs:55— PolylineData.SmoothNormal has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Window.WindowProc (cognitive 37) src/WPFDevelopers.Net45x/Window.cs:394— Window.WindowProc has cognitive complexity 37 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MultiSelectionSearchComboBox.SearchText (cognitive 36) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:510— MultiSelectionSearchComboBox.SearchText has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CardCarousel.PlayCarouselWithIndexOutRange (cognitive 36) src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:1025— CardCarousel.PlayCarouselWithIndexOutRange has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BallLoading.BallMoveColor (cognitive 35) src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:642— BallLoading.BallMoveColor has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IPEditBox.TextBox_PreviewKeyDown (cognitive 34) src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:203— IPEditBox.TextBox_PreviewKeyDown has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenCut.DrawMultipleControl (cognitive 34) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1325— ScreenCut.DrawMultipleControl has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapItemsLayer.UpdateDefaultItems (cognitive 33) src/WPFDevelopers.Shared/Controls/MapView/MapItemsLayer.cs:426— MapItemsLayer.UpdateDefaultItems has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpacingState.Update (cognitive 33) src/WPFDevelopers.Shared/Core/Helpers/PanelHelper.cs:103— SpacingState.Update has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectComboBox.CreateTag (cognitive 33) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:844— MultiSelectComboBox.CreateTag has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScreenCut.DrawArrowControl (cognitive 33) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1199— ScreenCut.DrawArrowControl has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SketchGeometryEffect.UpdateSketchGeometry (cognitive 32) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/SketchGeometryEffect.cs:37— SketchGeometryEffect.UpdateSketchGeometry has cognitive complexity 32 (threshold 15). Of this number, 17 points are the body's own statements and 15 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapViewFeaturesWindow.BringCircleToFrontButton_Click (cognitive 31) src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewFeaturesWindow.xaml.cs:235— MapViewFeaturesWindow.BringCircleToFrontButton_Click has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DistributionStrategy.DistributeInternal (cognitive 31) src/WPFDevelopers.Shared/Microsoft.Expression.Controls/DistributionStrategy.cs:75— DistributionStrategy.DistributeInternal has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to one function literal inside it that branches (line 129). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Utility.UrlDecode (cognitive 31) src/Microsoft.Windows.Shell/Standard/Utility.cs:552— Utility.UrlDecode has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DateRangePicker.SetIsHighlight (cognitive 30) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:922— DateRangePicker.SetIsHighlight has cognitive complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IPEditBox.PasteTextIPTextBox (cognitive 30) src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:291— IPEditBox.PasteTextIPTextBox has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaterfallPanel.ReconcileRealizedChildren (cognitive 30) src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:374— WaterfallPanel.ReconcileRealizedChildren has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TimePicker.GetDisplayTimeFormat (cognitive 30) src/WPFDevelopers.Shared/Controls/TimePicker/TimePicker.cs:131— TimePicker.GetDisplayTimeFormat has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkdownViewer.AddInlineTokens (cognitive 30) REDACTED:662— MarkdownViewer.AddInlineTokens has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThumbAdorner.GetResizeThumb (cognitive 29) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:306— ThumbAdorner.GetResizeThumb has cognitive complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 332). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ThumbAdorner2.GetResizeThumb (cognitive 29) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:308— ThumbAdorner2.GetResizeThumb has cognitive complexity 29 (threshold 15). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 324). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
TimelinePanel.MeasureOverride (cognitive 29) src/WPFDevelopers.Shared/Controls/Timeline/TimelinePanel.cs:17— TimelinePanel.MeasureOverride has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CircleMenu.UpdateAllAnglesCore (cognitive 29) src/WPFDevelopers.Shared/Controls/CircleMenu/CircleMenu.cs:220— CircleMenu.UpdateAllAnglesCore has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CropAvatar.OnImage_MouseMove (cognitive 29) src/WPFDevelopers.Shared/Controls/CropAvatar/CropAvatar.cs:147— CropAvatar.OnImage_MouseMove has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Loading.UnwrapElement (cognitive 29) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:354— Loading.UnwrapElement has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolylineHelper.PathMarch (cognitive 29) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PolylineHelper.cs:9— PolylineHelper.PathMarch has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowChromeWorker._UpdateSystemMenu (cognitive 29) src/Microsoft.Windows.Shell/WindowChromeWorker.cs:453— WindowChromeWorker._UpdateSystemMenu has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectComboBox.ApplySelectedItemsExt (cognitive 28) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:349— MultiSelectComboBox.ApplySelectedItemsExt has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenCutAdorner.GetResizeThumb (cognitive 28) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:103— ScreenCutAdorner.GetResizeThumb has cognitive complexity 28 (threshold 15). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 143). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
DrawingPanel.OnRenderBackground (cognitive 27) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:166— DrawingPanel.OnRenderBackground has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElementAdorner.CreateThumb (cognitive 27) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:153— ElementAdorner.CreateThumb has cognitive complexity 27 (threshold 15). None of this is in the body itself: all 27 points belong to one function literal inside it that branches (line 168). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
CardCarousel.HandleSlideClick (cognitive 27) src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:150— CardCarousel.HandleSlideClick has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapTileLayer.UpdateViewport (cognitive 26) src/WPFDevelopers.Shared/Controls/MapView/MapItemsLayer.cs:85— MapTileLayer.UpdateViewport has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Loading.CreateLoading (cognitive 26) src/WPFDevelopers.Shared/Controls/Loading/Loading.cs:114— Loading.CreateLoading has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.GetActivePushpinEntriesSnapshot (cognitive 26) REDACTED:2834— MapView.GetActivePushpinEntriesSnapshot has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectionSearchComboBox.OnListBox_SelectionChanged (cognitive 25) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:390— MultiSelectionSearchComboBox.OnListBox_SelectionChanged has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilterEngine.UpdateObjectView (cognitive 24) src/WPFDevelopers.Shared/Controls/Filter/FilterEngine.cs:179— FilterEngine.UpdateObjectView has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NumericBox.ContinueChangeValue (cognitive 24) src/WPFDevelopers.Shared/Controls/NumericBox/NumericBox.cs:678— NumericBox.ContinueChangeValue has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenCut.MoveRect (cognitive 24) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1440— ScreenCut.MoveRect has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbbreviatedGeometryParser.ReadDouble (cognitive 24) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:339— AbbreviatedGeometryParser.ReadDouble has cognitive complexity 24 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EmojiHelper.ProcessInlines (cognitive 23) src/WPFDevelopers.Samples.Shared/Controls/ChatEmoji/EmojiHelper.cs:59— EmojiHelper.ProcessInlines has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectionSearchComboBox.OnListBoxSearch_SelectionChanged (cognitive 23) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:432— MultiSelectionSearchComboBox.OnListBoxSearch_SelectionChanged has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateRangePicker.UpdateEndDateFromTextBox (cognitive 23) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:582— DateRangePicker.UpdateEndDateFromTextBox has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DateRangePicker.UpdateStartDateFromTextBox) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
DateRangePicker.UpdateStartDateFromTextBox (cognitive 23) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:640— DateRangePicker.UpdateStartDateFromTextBox has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (DateRangePicker.UpdateEndDateFromTextBox) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MapView.TryGetPolylineHit (cognitive 23) REDACTED:3150— MapView.TryGetPolylineHit has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkdownViewer.ClassifyCodeToken (cognitive 23) REDACTED:901— MarkdownViewer.ClassifyCodeToken has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectComboBox.OnDataGridSearch_SelectionChanged (cognitive 23) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:599— MultiSelectComboBox.OnDataGridSearch_SelectionChanged has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VirtualizingWrapPanel.MeasureOverride (cognitive 23) src/WPFDevelopers.Shared/Controls/VirtualizingWrapPanel/VirtualizingWrapPanel.cs:80— VirtualizingWrapPanel.MeasureOverride has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Resources.UpdateResourceDictionaryColor (cognitive 23) src/WPFDevelopers.Shared/Resources.cs:376— Resources.UpdateResourceDictionaryColor has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BubbleCanvas.ArrangeOverride (cognitive 22) src/WPFDevelopers.Samples.Shared/Controls/BubbleSelection/BubbleCanvas.cs:16— BubbleCanvas.ArrangeOverride has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OtpBox.TextBox_PreviewKeyDown (cognitive 22) src/WPFDevelopers.Shared/Controls/OtpBox/OtpBox.cs:212— OtpBox.TextBox_PreviewKeyDown has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SplitButton.BuildContextMenu (cognitive 22) src/WPFDevelopers.Shared/Controls/SplitButton/SplitButton.cs:91— SplitButton.BuildContextMenu has cognitive complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusCarousel.OnItems_CollectionChanged (cognitive 22) src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:69— FocusCarousel.OnItems_CollectionChanged has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.TryStartTileDownloads (cognitive 22) REDACTED:3945— MapView.TryStartTileDownloads has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 3965). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
PathPanel.ArrangeOverride (cognitive 22) src/WPFDevelopers.Shared/Microsoft.Expression.Controls/PathPanel.cs:71— PathPanel.ArrangeOverride has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapTileLayer.TryGetBestAvailableTile (cognitive 21) src/WPFDevelopers.Shared/Controls/MapView/MapItemsLayer.cs:171— MapTileLayer.TryGetBestAvailableTile has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToastExt.GetTargetArea (cognitive 21) src/WPFDevelopers.Shared/Controls/Toast/ToastExt.cs:52— ToastExt.GetTargetArea has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.TryGetPolygonHit (cognitive 21) REDACTED:3236— MapView.TryGetPolygonHit has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkdownViewer.ClassifyMarkupToken (cognitive 21) REDACTED:952— MarkdownViewer.ClassifyMarkupToken has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MarkdownViewer.ParseInlines (cognitive 21) REDACTED:1422— MarkdownViewer.ParseInlines has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenCut.DrawText (cognitive 21) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:793— ScreenCut.DrawText has cognitive complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 828, 841). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WindowAcrylicBlur.OnWindowAcryBlurPropertyChangedCallBack (cognitive 21) src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:244— WindowAcrylicBlur.OnWindowAcryBlurPropertyChangedCallBack has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CountdownTimer.OnApplyTemplate (cognitive 20) src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:61— CountdownTimer.OnApplyTemplate has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaterfallPanel.BuildItemLayouts (cognitive 20) src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:245— WaterfallPanel.BuildItemLayouts has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusCarousel.OnSizeChangedCallback (cognitive 20) src/WPFDevelopers.Shared/Controls/Carousel/FocusCarousel.cs:204— FocusCarousel.OnSizeChangedCallback has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.OnMouseUp (cognitive 20) REDACTED:1219— MapView.OnMouseUp has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.PushpinLayers_CollectionChanged (cognitive 20) REDACTED:1800— MapView.PushpinLayers_CollectionChanged has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NotifyIcon.OpenMenu (cognitive 20) src/WPFDevelopers.Shared/Controls/NotifyIcon/NotifyIcon.cs:800— NotifyIcon.OpenMenu has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskbarItemInfo._UpdateThumbButtons (cognitive 20) src/Microsoft.Windows.Shell/TaskbarItemInfo.cs:480— TaskbarItemInfo._UpdateThumbButtons has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateRangePicker.HandleDateSelection (cognitive 19) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:511— DateRangePicker.HandleDateSelection has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapShapeLayer.UpdateShapes (cognitive 19) src/WPFDevelopers.Shared/Controls/MapView/MapItemsLayer.cs:267— MapShapeLayer.UpdateShapes has cognitive complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BackToTopState.UpdateButton (cognitive 19) src/WPFDevelopers.Shared/Controls/ScrollViewer/ScrollViewerBehavior.cs:435— BackToTopState.UpdateButton has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
CircleMenu.GetVisibleBoundsInSelf (cognitive 19) src/WPFDevelopers.Shared/Controls/CircleMenu/CircleMenu.cs:504— CircleMenu.GetVisibleBoundsInSelf has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScreenCut.Dispose (cognitive 19) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:261— ScreenCut.Dispose has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BezierCurveFlattener.FlattenCubic (cognitive 19) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/BezierCurveFlattener.cs:9— BezierCurveFlattener.FlattenCubic has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GeometryHelper.PathSegmentEquals (cognitive 19) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/GeometryHelper.cs:320— GeometryHelper.PathSegmentEquals has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AbbreviatedGeometryParser.SkipWhitespace (cognitive 19) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:440— AbbreviatedGeometryParser.SkipWhitespace has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JumpList.AddCategory (cognitive 19) src/Microsoft.Windows.Shell/JumpList.cs:456— JumpList.AddCategory has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ChartPie.OnRender (cognitive 18) src/WPFDevelopers.Shared/Controls/Charts/ChartPie.cs:143— ChartPie.OnRender has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimelinePanel.OnRender (cognitive 18) src/WPFDevelopers.Shared/Controls/Timeline/TimelinePanel.cs:98— TimelinePanel.OnRender has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CropImage.DrawImage (cognitive 18) src/WPFDevelopers.Shared/Controls/CropImage/CropImage.cs:257— CropImage.DrawImage has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CropAvatar.Dispose (cognitive 18) src/WPFDevelopers.Shared/Controls/CropAvatar/CropAvatar.cs:313— CropAvatar.Dispose has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.Polylines_CollectionChanged (cognitive 18) REDACTED:1877— MapView.Polylines_CollectionChanged has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (MapView.Polygons_CollectionChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MapView.Polygons_CollectionChanged (cognitive 18) REDACTED:1922— MapView.Polygons_CollectionChanged has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (MapView.Polylines_CollectionChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ScreenCut.OnPreviewMouseLeftButtonDown (cognitive 18) src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:740— ScreenCut.OnPreviewMouseLeftButtonDown has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JumpList.ListContainsShellObject (cognitive 18) src/Microsoft.Windows.Shell/JumpList.cs:367— JumpList.ListContainsShellObject has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WaterfallPanel.MeasureVirtualized (cognitive 17) src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:145— WaterfallPanel.MeasureVirtualized has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePicker.OnSelectedTimeChanged (cognitive 17) src/WPFDevelopers.Shared/Controls/TimePicker/TimePicker.cs:226— TimePicker.OnSelectedTimeChanged has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimeSelector.OnApplyTemplate (cognitive 17) src/WPFDevelopers.Shared/Controls/TimePicker/TimeSelector.cs:188— TimeSelector.OnApplyTemplate has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.GetPushpinAt (cognitive 17) REDACTED:2978— MapView.GetPushpinAt has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MapView.CreateFeatureClickEventArgs (cognitive 17) REDACTED:3053— MapView.CreateFeatureClickEventArgs has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MapView.DrawScaleBar (cognitive 17) REDACTED:4071— MapView.DrawScaleBar has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
StarrySky.AddOrRemoveStarLine (cognitive 17) src/WPFDevelopers.Shared/Controls/StarrySky/StarrySky.cs:251— StarrySky.AddOrRemoveStarLine has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransformExtensions.TransformEquals (cognitive 17) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/TransformExtensions.cs:90— TransformExtensions.TransformEquals has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ArcGeometrySource.ComputeAngleRanges (cognitive 17) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/ArcGeometrySource.cs:176— ArcGeometrySource.ComputeAngleRanges has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Carousel.BuildSlides (cognitive 16) src/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:216— Carousel.BuildSlides has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Carousel.CreateSlideElement (cognitive 16) src/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:288— Carousel.CreateSlideElement has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateRangePicker.ResetDate (cognitive 16) src/WPFDevelopers.Shared/Controls/DateRangePicker/DateRangePicker.cs:850— DateRangePicker.ResetDate has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GestureUnlock.TryAddPoint (cognitive 16) src/WPFDevelopers.Shared/Controls/GestureUnlock/GestureUnlock.cs:228— GestureUnlock.TryAddPoint has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgViewer.LoadAndRenderSvg (cognitive 16) src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:273— SvgViewer.LoadAndRenderSvg has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TimePicker.ContainsFormatSpecifier (cognitive 16) src/WPFDevelopers.Shared/Controls/TimePicker/TimePicker.cs:185— TimePicker.ContainsFormatSpecifier has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NumericBox.DealInputText (cognitive 16) src/WPFDevelopers.Shared/Controls/NumericBox/NumericBox.cs:581— NumericBox.DealInputText has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CardCarousel.PlayCarouselLeftToRight (cognitive 16) src/WPFDevelopers.Shared/Controls/Carousel/CardCarousel.cs:474— CardCarousel.PlayCarouselLeftToRight has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CropAvatar.InitialImage (cognitive 16) src/WPFDevelopers.Shared/Controls/CropAvatar/CropAvatar.cs:200— CropAvatar.InitialImage has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MapView.QueueViewportTiles (cognitive 16) REDACTED:3491— MapView.QueueViewportTiles has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StarrySky.StarRoamAnimation (cognitive 16) src/WPFDevelopers.Shared/Controls/StarrySky/StarrySky.cs:202— StarrySky.StarRoamAnimation has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowAcrylicBlur.EnableAcrylicBlur (cognitive 16) src/WPFDevelopers.Shared/Controls/Windows/WindowAcrylicBlur.cs:106— WindowAcrylicBlur.EnableAcrylicBlur has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PathPanel.LayoutPropertyChanged (cognitive 16) src/WPFDevelopers.Shared/Microsoft.Expression.Controls/PathPanel.cs:270— PathPanel.LayoutPropertyChanged has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GeometryHelper.GeometryEquals (cognitive 16) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/GeometryHelper.cs:239— GeometryHelper.GeometryEquals has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
JumpList.CreateLinkFromJumpTask (cognitive 16) src/Microsoft.Windows.Shell/JumpList.cs:519— JumpList.CreateLinkFromJumpTask has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HRESULT.ToString (cognitive 16) src/Microsoft.Windows.Shell/Standard/HRESULT.cs:49— HRESULT.ToString has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Near-duplicate member family (3 members, 7 shared lines) · ×1
Near-duplicate member family (3 members, 7 shared lines) src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:140— src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:140-153 | src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:156-169 | src/WPFDevelopers.Samples.Shared/ExampleViews/UsageColor.xaml.cs:172-185 — These 3 members are variants of one another: a block of 7 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 3 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 3 times.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:151— src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:151-157 | src/WPFDevelopers.Shared/Controls/MapView/MapCoordinateHelper.cs:160-166 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:695— src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:695-750 | src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:511-550 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) src/Microsoft.Windows.Shell/SystemParameters2.cs:27— src/Microsoft.Windows.Shell/SystemParameters2.cs:27-36 | src/Microsoft.Windows.Shell/SystemParameters2.cs:39-47 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) src/Microsoft.Windows.Shell/Standard/HRESULT.cs:83— src/Microsoft.Windows.Shell/Standard/HRESULT.cs:83-94 | src/Microsoft.Windows.Shell/Standard/Win32Error.cs:36-47 — 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 (133 lines × 2) src/Microsoft.Windows.Shell/Standard/WM.cs:3— src/Microsoft.Windows.Shell/Standard/WM.cs:3-135 | src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WM.cs:3-135 — before extracting anything, compare `src/Microsoft.Windows.Shell/Standard/WM.cs` and `src/WPFDevelopers.Shared/Controls/NotifyIcon/Runtimes/User32/WM.cs` as WHOLE FILES: 99% 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 `src/Microsoft.Windows.Shell/Standard/WM.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (65–68 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:330— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:330-397 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:323-387 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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 `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:330` 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 (48 lines × 2) src/WPFDevelopers.Net40/Window.cs:418— src/WPFDevelopers.Net40/Window.cs:418-465 | src/WPFDevelopers.Net45x/Window.cs:415-462 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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 `src/WPFDevelopers.Net40/Window.cs:418` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:123— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:123-144 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:172-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathGeometryHelper.cs:123` 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 (41 lines × 2) src/WPFDevelopers.Net40/Window.cs:117— src/WPFDevelopers.Net40/Window.cs:117-157 | src/WPFDevelopers.Net45x/Window.cs:121-161 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (35–36 lines × 4) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:98— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:98-132 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:74-108 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:94-129 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:149-184 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26–30 lines × 2) src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/CalloutGeometrySource.cs:136— src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/CalloutGeometrySource.cs:136-161 | src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/CalloutGeometrySource.cs:209-238 — both copies are in the same file, so extract the 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/CalloutGeometrySource.cs:208` calls `Min`, `ComputeCorners` and `src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Media/CalloutGeometrySource.cs:136` 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 (28–29 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:468— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:468-496 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:755-782 — 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/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:755` 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 (25–26 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:597— src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:597-621 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:632-657 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (25 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:64— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:64-88 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:220-244 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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 (24 lines × 4) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:253— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:253-276 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:200-223 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:133-156 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:188-211 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (21 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:155— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:155-175 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:124-144 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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 `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:155` 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 (22–23 lines × 2) src/WPFDevelopers.Net40/Window.cs:387— src/WPFDevelopers.Net40/Window.cs:387-408 | src/WPFDevelopers.Net45x/Window.cs:395-417 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 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 `src/WPFDevelopers.Net40/Window.cs:387` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 4) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:332— src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:332-349 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:375-392 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:419-436 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:462-479 — 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 `src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:332` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) src/WPFDevelopers.Shared/Core/Helpers/ScrollIntoView.cs:55— src/WPFDevelopers.Shared/Core/Helpers/ScrollIntoView.cs:55-73 | src/WPFDevelopers.Shared/Core/Helpers/ScrollIntoView.cs:77-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–20 lines × 2) src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:214— src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:214-231 | src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:248-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/Loadings/BallLoading.cs:214` 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 (18 lines × 6) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:331— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:331-348 | src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:75-92 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:278-295 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:224-241 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:100-117 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:75-92 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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 `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:331` 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–18 lines × 2) src/WPFDevelopers.Shared/Controls/Charts/ChartBase.cs:60— src/WPFDevelopers.Shared/Controls/Charts/ChartBase.cs:60-77 | src/WPFDevelopers.Shared/Controls/Charts/ChartPie.cs:63-79 — 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/WPFDevelopers.Shared/Controls/Charts/ChartBase.cs:60` 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 (15–17 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:322— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:322-336 | src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:479-495 — both copies are in the same file, so extract the 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/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs: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 (14–17 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:134— src/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:134-150 | src/WPFDevelopers.Samples.Shared/ExampleViews/Basics/LoadingBasicExample.xaml.cs:31-44 — 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/WPFDevelopers.Samples.Shared/ExampleViews/BasicControlsExample.xaml.cs:134` 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 (17 lines × 2) src/WPFDevelopers.Net40/Window.cs:61— src/WPFDevelopers.Net40/Window.cs:61-77 | src/WPFDevelopers.Net45x/Window.cs:45-61 — `src/WPFDevelopers.Net40/Window.cs` and `src/WPFDevelopers.Net45x/Window.cs` 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 13 separate duplicated blocks between them, totalling at least 226 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16–17 lines × 2) src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:112— src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:112-128 | src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:386-401 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Shared/Controls/WaterfallPanel/WaterfallPanel.Virtualization.cs:112` 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 (15–16 lines × 4) src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:322— src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:322-336 | src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs:480-495 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:645-659 | src/WPFDevelopers.Shared/Controls/MultiSelectComboBox/MultiSelectComboBox.cs:767-781 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Samples.Shared/Controls/MultiSelectionSearchComboBox/MultiSelectSearchComboBox.cs: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 (15 lines × 2) src/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:310— src/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:310-324 | src/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:329-343 — both copies are in the same file, so extract the 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/WPFDevelopers.Shared/Controls/Carousel/Carousel.cs:329` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 5) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:58— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs:58-69 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:261-272 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:207-218 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:83-94 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs:58-69 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ThumbAngle.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAngle.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 4) src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:597— src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:597-605 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:632-640 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:668-676 | src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:703-711 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:59— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:59-70 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:35-46 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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 `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:59` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:58` calls `FindParent` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:34` 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 (10 lines × 3) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:176— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:176-185 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:344-354 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:334-344 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 95 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 3) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:250— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:250-258 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:195-203 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:139-147 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 105 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 5) REDACTED:2944— REDACTED:2944-2952 | REDACTED:3159-3167 | REDACTED:3245-3253 | REDACTED:3317-3325 | REDACTED:3368-3376 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–8 lines × 3) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:89— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:89-95 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:65-71 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:242-249 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 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 `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:89` 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) src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:79— src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:79-84 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs:55-60 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:67-72 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:223-228 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ElementAdorner.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 153 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5–7 lines × 4) src/WPFDevelopers.Shared/Core/Helpers/GeometryHelper.cs:56— src/WPFDevelopers.Shared/Core/Helpers/GeometryHelper.cs:56-62 | src/WPFDevelopers.Shared/Core/Helpers/GeometryHelper.cs:63-69 | src/WPFDevelopers.Shared/Core/Helpers/GeometryHelper.cs:70-76 | src/WPFDevelopers.Shared/Core/Helpers/GeometryHelper.cs:77-81 — 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. 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–7 lines × 3) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:45— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:45-51 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:44-50 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:35-38 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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 (4–5 lines × 3) src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:54— src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:54-58 | src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs:53-57 | src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs:39-42 — before extracting anything, compare `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs` and `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 269 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 `src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:54` 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.
Duplicated block (46 lines × 2) src/WPFDevelopers.Samples.Shared/ExampleViews/ChartLineExample.xaml.cs:15— src/WPFDevelopers.Samples.Shared/ExampleViews/ChartLineExample.xaml.cs:15-60 | src/WPFDevelopers.Samples.Shared/ExampleViews/ChartPieExample.xaml.cs:15-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/WPFDevelopers.Samples.Shared/ExampleViews/ChartLineExample.xaml.cs:15` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
IC1 · Incompleteness & stubs· Guard cannot change the result · ×1
Guard cannot change the result — returns what the code already falls through to src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:287— 1 guard above `return _textBox4;` also returns `_textBox4`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Hollow method — returns a constant without doing the work src/WPFDevelopers.Shared/Core/Converts/ElementConvert.cs:9— `Convert` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Unfinished branch — throws NotImplementedException src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Core/PathSegmentHelper.cs:492— The branch `if ((result = BezierSegmentImplementation.Create(segment as BezierSegment)) == null && (result = LineSegmentImplementation.Create(segment as LineSegment)) == null && (result = ArcSegmentImplementation.Create(segment as ArcSegment)) == null && (result = PolyLineSegmentImplementation.Create(segment as PolyLineSegment)) == null && (result = PolyBezierSegmentImplementation.Create(segment as PolyBezierSegment)) == null && (result = QuadraticBezierSegmentImplementation.Create(segment as QuadraticBezierSegment)) == null && (result = PolyQuadraticBezierSegmentImplementation.Create(segment as PolyQuadraticBezierSegment)) == null)` throws `NotImplementedException` while the member's other paths do the work — the branch was never written, so every input that reaches it fails at run time. Implement the branch, or reject the input where it enters with an exception that says it is not supported.
X18 · Disposal-pattern correctness· Finalizer on a type that owns no unmanaged resource · ×1
Finalizer on a type that owns no unmanaged resource src/WPFDevelopers.Shared/Controls/CropAvatar/CropAvatar.cs:352— `CropAvatar` declares a finalizer (line 352), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
X29 · Per-element action decided by a fixed element· Per-element action decided by a fixed element · ×1
Per-element action decided by a fixed element src/Microsoft.Windows.Shell/Standard/Utility.cs:321— This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[num3]`. The test deciding whether that statement runs does not: `flag` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 317, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
Commented-out code src/Microsoft.Windows.Shell/Standard/IObjectCollection.cs:14— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/ChatEmoji/ChatEmoji.cs:125— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:95— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:96— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingControl.cs:244— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingControl.cs:252— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingControl.cs:253— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingControl.cs:261— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingControl.cs:274— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:286— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/Drawing/DrawingPanel.cs:288— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:171— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/RoundPicker/RoundPicker.cs:173— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/Controls/ScrollViewer/ScrollViewerAnimation.cs:44— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/CanvasHandWriting/ComputingHelper.cs:69— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Desktop/DesktopPlayVideo.xaml.cs:33— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Desktop/DesktopPlayVideo.xaml.cs:36— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Desktop/DesktopPlayVideo.xaml.cs:37— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/TransformThumb.cs:67— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:77— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:78— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:83— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:86— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:303— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs:304— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:214— `!_titleBarThemeSwitchButton.IsVisible || !_titleBarThemeSwitchButton.IsEnabled` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/Charts/ChartBase.cs:62— `Datas == null || Datas.Count() == 0 || isPopupOpen` appears character-identically in 2 files — src/WPFDevelopers.Shared/Controls/Charts/ChartBase.cs, src/WPFDevelopers.Shared/Controls/Charts/ChartPie.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/Loading/LoadingExt.cs:13— `Helper.GetTempPathVersionExt != null && File.Exists(Helper.GetTempPathVersionExt)` appears character-identically in 2 files — src/WPFDevelopers.Shared/Controls/Loading/LoadingExt.cs, src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCaptureExt.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/BaseControls/ItemsControlBase.cs:68— `ItemClickCommand is ICommand cmd && cmd.CanExecute(clickedItem)` appears character-identically in 2 files — src/WPFDevelopers.Shared/Controls/BaseControls/ItemsControlBase.cs, src/WPFDevelopers.Shared/Controls/CircleMenu/CircleMenu.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:441— `OSVersionHelper.IsSnapLayoutSupported() && (ResizeMode != ResizeMode.NoResize && ResizeMode != ResizeMode.CanMinimize)` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:421— `OSVersionHelper.IsSnapLayoutSupported() && ResizeMode != ResizeMode.NoResize && ResizeMode != ResizeMode.CanMinimize` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeContentShape.cs:167— `PartPath == null || PartPath.Data == null` appears character-identically in 2 files — src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeContentShape.cs, src/WPFDevelopers.Shared/Microsoft.Expression.Drawing/Controls/CompositeShape.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:358— `ResizeMode == ResizeMode.CanResize || ResizeMode == ResizeMode.CanResizeWithGrip` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:282— `TitleBarMode == TitleBarMode.Normal && e.ChangedButton == MouseButton.Left` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:125— `_themePopup == null || _themeItems == null` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:226— `_titleBarThemeSwitchButton.IsMouseOver || (_themePopupChild != null && _themePopupChild.IsMouseOver)` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Microsoft.Windows.Shell/Standard/Assert.cs:32— `actual != null && !actual.Equals(expected)` appears character-identically in 2 files — src/Microsoft.Windows.Shell/Standard/Assert.cs, src/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Microsoft.Windows.Shell/Standard/Assert.cs:49— `actual == null || actual.Equals(notExpected)` appears character-identically in 2 files — src/Microsoft.Windows.Shell/Standard/Assert.cs, src/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/Badge/Badge.cs:125— `e.NewValue is bool isShow && d is FrameworkElement parent` appears character-identically in 3 files — src/WPFDevelopers.Shared/Controls/Badge/Badge.cs, src/WPFDevelopers.Shared/Controls/Loading/Loading.cs, src/WPFDevelopers.Shared/Controls/Mask/Mask.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/Badge/Badge.cs:146— `e.NewValue is bool isVisible && sender is FrameworkElement parent` appears character-identically in 3 files — src/WPFDevelopers.Shared/Controls/Badge/Badge.cs, src/WPFDevelopers.Shared/Controls/Loading/Loading.cs, src/WPFDevelopers.Shared/Controls/Mask/Mask.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs:177— `e.Text.Length != 1 || !char.IsDigit(e.Text[0])` appears character-identically in 2 files — src/WPFDevelopers.Shared/Controls/IPEditBox/IPEditBox.cs, src/WPFDevelopers.Shared/Controls/OtpBox/OtpBox.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewFeaturesWindow.xaml.cs:366— `featureArgs.FeatureType == MapFeatureType.Circle && featureArgs.ClickedCircle != null` appears character-identically in 2 files — src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewExample.xaml.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/Map/MapViewFeaturesWindow.xaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:359— `newHeight > 0 && top + e.VerticalChange >= 0` appears character-identically in 2 files — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:180— `newHeight > 0 && top <= canvas.ActualHeight` appears character-identically in 4 files — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs, src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs:376— `newWidth > 0 && left + e.HorizontalChange >= 0` appears character-identically in 2 files — src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs:219— `newWidth > 0 && left <= canvas.ActualWidth` appears character-identically in 4 files — src/WPFDevelopers.Samples.Shared/Controls/TransformLayout/ElementAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/DrapView/Controls/ThumbAdorner2.cs, src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCutAdorner.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Net40/Window.cs:203— `sender == _titleBarThemeSwitchButton && _themePopup != null` appears character-identically in 2 files — src/WPFDevelopers.Net40/Window.cs, src/WPFDevelopers.Net45x/Window.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs:235— `storyboard != null && storyboard.Children.Count > 0` appears character-identically in 2 files — src/WPFDevelopers.Samples.Shared/Controls/CountdownTimer/CountdownTimer.cs, src/WPFDevelopers.Samples.Shared/ExampleViews/NumberCard/NumberCardExample.xaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Microsoft.Windows.Shell/Standard/Assert.cs:178— `value < lowerBoundInclusive || value > upperBoundInclusive` appears character-identically in 2 files — src/Microsoft.Windows.Shell/Standard/Assert.cs, src/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Microsoft.Windows.Shell/Standard/Assert.cs:187— `value < lowerBoundInclusive || value >= upperBoundExclusive` appears character-identically in 2 files — src/Microsoft.Windows.Shell/Standard/Assert.cs, src/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch src/WPFDevelopers.Samples.Shared/ExampleViews/Dialog/DialogUserControl.xaml.cs:37— `IsValidEmail` swallows `FormatException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Controls/SvgViewer/SvgViewer.cs:99— `GetUriFromSource` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Controls/CropImage/CropImage.cs:472— `CutBitmap` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Core/Helpers/Helper.cs:68— `KillProcessUsingFile` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch REDACTED:4181— `ResolveScaleUnit` swallows every exception into `return MapDistanceUnit.KilometersMeters;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Controls/ScreenCut/ScreenCut.cs:1089— `GetAreaAverageColor` swallows every exception into `return Colors.Gray;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Core/Helpers/AudioPlayer.cs:17— `GetSoundLength` swallows every exception into `return TimeSpan.Zero;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/WPFDevelopers.Shared/Resources.cs:179— `IsDarkMode` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Microsoft.Windows.Shell/JumpList.cs:582— `CreateLinkFromJumpTask` swallows every exception and sets `result = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Microsoft.Windows.Shell/Standard/HRESULT.cs:89— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Microsoft.Windows.Shell/Standard/RECT.cs:132— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:69— `ReleaseHandle` swallows every exception and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Microsoft.Windows.Shell/Standard/Win32Error.cs:42— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
redundant comment REDACTED:5— "where theme specific resource dictionaries are located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:6— "(used if a resource is not found in the page, or application resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:8— "where the generic resource dictionary is located" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:9— "(used if a resource is not found in the page, app, or any theme specific resource dictionaries)" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion src/WPFDevelopers.Net40/WPFDevelopers.Net40.csproj:1— `WPFDevelopers.Net40` overshoots its size bounds (55326 LoC, 521 public types across 21 namespaces). 4 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Projects may be oversized for their cohesion src/WPFDevelopers.Net45x/WPFDevelopers.Net45x.csproj:1— `WPFDevelopers.Net45x(net45)` overshoots its size bounds (46507 LoC, 521 public types across 21 namespaces). 4 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Projects may be oversized for their cohesion src/WPFDevelopers.Samples40/WPFDevelopers.Samples40.csproj:1— `WPFDevelopers.Samples40` overshoots its size bounds (16543 LoC, 267 public types across 20 namespaces). 4 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Projects may be oversized for their cohesion src/WPFDevelopers.Samples45x/WPFDevelopers.Samples45x.csproj:1— `WPFDevelopers.Samples45x(net45)` overshoots its size bounds (16543 LoC, 267 public types across 20 namespaces). 4 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: src/WPFDevelopers.Net45x/Window.cs, src/WPFDevelopers.Net40/Window.cs. Pair on, review, or document these before any departure.
Shell project: WPFDevelopers.SamplesCode(
net40) src/WPFDevelopers.SamplesCode/WPFDevelopers.SamplesCode.csproj— `WPFDevelopers.SamplesCode(
net40)` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
Documentation: no map of the repository's parts README.md:1— The repository has 5 units (`WPFDevelopers.Net40`, `WPFDevelopers.Net45x`, `WPFDevelopers.Samples40`, `WPFDevelopers.Samples45x`, `WPFDevelopers.SamplesCode`); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
No ADRs found src/WPFDevelopers.Net45x/WPFDevelopers.Net45x.csproj:5— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/WPFDevelopers.Net45x/WPFDevelopers.Net45x.csproj` makes this repository a deployable product (line 5).
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body src/Microsoft.Windows.Shell/Standard/NativeMethods.cs:361— `GetDC` has an empty body — confirm it's an intentional no-op and not an unfinished method.
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 REDACTED:7— No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 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.
No dependency-update automation src/TargetFrameworks.props:6— `src/TargetFrameworks.props` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Silent fallback default on parse failure REDACTED:3565— `ExtractTileYFromCacheKey` returns `-1` when `int.TryParse(parts[parts.Length - 1], out var tileY)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
doc comments repeat the names src/WPFDevelopers.Shared/Controls/Filter/FilterEngine.cs:264— 0 of 14 documented parameters and 0 of 68 summaries in `WPFDevelopers.Net40` only repeat the member or parameter name (e.g. "" for `propertyName`). 15 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `src/WPFDevelopers.Samples.Shared/ExampleViews/ChartRadarExample.xaml.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
Run 01a1ea61-5372-731f-a78b-ac752f41df0e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 3 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 56 · Warnings: 551 · Recommendations: 84 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 16:40 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.