Public report of MaterialDesignInXAML/MaterialDesignInXamlToolkit, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 06:48 UTC · Survey ID cd_afeaa29c9b9e4c9a882ac3b4f77f24dd
MaterialDesignInXAML/MaterialDesignInXamlToolkit
Measured 23 October 2026, 06:43 UTC, at code version 0877280
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 79,282 lines of product code in 30 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Security and Compliance, 47
Findings by how serious they are
58 critical325 serious130 minor
4 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 06:43 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
68of 72 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
486of 513 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
72dimensions across 7 lenses, read from 79,282 lines of product code in 30 projects.
MaterialDesignInXAML/MaterialDesignInXamlToolkit scores 54 out of 100 and is rated Adequate, while five of its seven lenses score higher still: Architecture at 98 and Domain Modelling at 96, both rated Exemplary, and Performance at 70, Code Health at 61 and Production Readiness at 60, all rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 47 and is rated Weak. Its Static Analysis (SAST) dimension scores 0.3 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to resolve the 4 High secret finding(s) in Secrets (history), and if Security and Compliance rose to 70, the score would rise from 54 to about 59.
58 findings are critical: 43 in Static Analysis (SAST), eight in Explicit Debt, four in Secrets (history), two in Knowledge Freshness and one in Project dependency cycles.
Watchdog couldn't measure License Compliance, IL Efficiency and Runtime evidence locked — no reproducible boot in this code, so those dimensions are left out of the score. The product code is 79,282 lines, which would take an estimated 0.8 person-years, around €110,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 5 findings
These 5 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
Static Analysis (SAST) · High: REDACTED REDACTED
Supply-chain Provenance & Signing REDACTED
Supply-chain Provenance & Signing REDACTED
Cancellation propagation · Async method without CancellationToken: ShowInternal src/MaterialDesignThemes.Wpf/DialogHost.cs
Exception handling · Swallowed exception (caught, then discarded) src/MaterialDesignThemes.Wpf/Theme.cs
Rebuild cost: about €110,000 · Estimate
Cost to rebuild
€37,000 to €190,000, for 619 to 1,966 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 54. 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: 79,282 lines of product code
Comment lines
The estimate prices 76,272 lines. Comment lines count towards the size of 79,282 lines but aren't priced as work.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
2
Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.8 person-years of work. Its weakest lens is Security and Compliance, at 47 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph 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.
35 modules, with 23 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
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.
38 pairs of types, where a type in MaterialDesignColors.Recommended uses a type in MaterialDesignColors. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MaterialDesignColors.Recommended uses MaterialDesignColors, so a change to MaterialDesignColors can break MaterialDesignColors.Recommended, while a change to MaterialDesignColors.Recommended can't break MaterialDesignColors.
Position
Below the diagonal: MaterialDesignColors.Recommended uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf.Internal uses MaterialDesignThemes.Wpf.Behaviors.Internal, so a change to MaterialDesignThemes.Wpf.Behaviors.Internal can break MaterialDesignThemes.Wpf.Internal, while a change to MaterialDesignThemes.Wpf.Internal can't break MaterialDesignThemes.Wpf.Behaviors.Internal.
Position
Below the diagonal: MaterialDesignThemes.Wpf.Internal uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf uses MaterialDesignColors, so a change to MaterialDesignColors can break MaterialDesignThemes.Wpf, while a change to MaterialDesignThemes.Wpf can't break MaterialDesignColors.
Position
Below the diagonal: MaterialDesignThemes.Wpf uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf uses MaterialDesignColors.ColorManipulation, so a change to MaterialDesignColors.ColorManipulation can break MaterialDesignThemes.Wpf, while a change to MaterialDesignThemes.Wpf can't break MaterialDesignColors.ColorManipulation.
Position
Below the diagonal: MaterialDesignThemes.Wpf uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf uses MaterialDesignThemes.Wpf.Internal, so a change to MaterialDesignThemes.Wpf.Internal can break MaterialDesignThemes.Wpf, while a change to MaterialDesignThemes.Wpf can't break MaterialDesignThemes.Wpf.Internal.
Position
Below the diagonal: MaterialDesignThemes.Wpf uses a module listed above it, which is the healthy direction.
MahMaterialDragablzMashUp uses MaterialDesignColors, so a change to MaterialDesignColors can break MahMaterialDragablzMashUp, while a change to MahMaterialDragablzMashUp can't break MaterialDesignColors.
Position
Below the diagonal: MahMaterialDragablzMashUp uses a module listed above it, which is the healthy direction.
MahMaterialDragablzMashUp uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MahMaterialDragablzMashUp, while a change to MahMaterialDragablzMashUp can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MahMaterialDragablzMashUp uses a module listed above it, which is the healthy direction.
MaterialDesign.Shared uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesign.Shared, while a change to MaterialDesign.Shared can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesign.Shared uses a module listed above it, which is the healthy direction.
MaterialDesignDemo.Shared.Domain uses MaterialDesignColors, so a change to MaterialDesignColors can break MaterialDesignDemo.Shared.Domain, while a change to MaterialDesignDemo.Shared.Domain can't break MaterialDesignColors.
Position
Below the diagonal: MaterialDesignDemo.Shared.Domain uses a module listed above it, which is the healthy direction.
MaterialDesignDemo.Shared.Domain uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignDemo.Shared.Domain, while a change to MaterialDesignDemo.Shared.Domain can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignDemo.Shared.Domain uses a module listed above it, which is the healthy direction.
28→33 MaterialDesignDemo.Shared.Domain uses MaterialDesignDemo.Domainpart of a loop✕
Connections
1 pair of types, where a type in MaterialDesignDemo.Shared.Domain uses a type in MaterialDesignDemo.Domain.
MaterialDesignDemo.Shared.Domain uses MaterialDesignDemo.Domain, so a change to MaterialDesignDemo.Domain can break MaterialDesignDemo.Shared.Domain, while a change to MaterialDesignDemo.Shared.Domain can't break MaterialDesignDemo.Domain.
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.
28→35 MaterialDesignDemo.Shared.Domain uses MaterialDesignDemopart of a loop✕
Connections
1 pair of types, where a type in MaterialDesignDemo.Shared.Domain uses a type in MaterialDesignDemo.
MaterialDesignDemo.Shared.Domain uses MaterialDesignDemo, so a change to MaterialDesignDemo can break MaterialDesignDemo.Shared.Domain, while a change to MaterialDesignDemo.Shared.Domain can't break MaterialDesignDemo.
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.
MaterialDesignThemes.MahApps uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignThemes.MahApps, while a change to MaterialDesignThemes.MahApps can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignThemes.MahApps uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf.Automation.Peers uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignThemes.Wpf.Automation.Peers, while a change to MaterialDesignThemes.Wpf.Automation.Peers can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignThemes.Wpf.Automation.Peers uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf.Converters uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignThemes.Wpf.Converters, while a change to MaterialDesignThemes.Wpf.Converters can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignThemes.Wpf.Converters uses a module listed above it, which is the healthy direction.
MaterialDesignThemes.Wpf.Converters.Internal uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignThemes.Wpf.Converters.Internal, while a change to MaterialDesignThemes.Wpf.Converters.Internal can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignThemes.Wpf.Converters.Internal uses a module listed above it, which is the healthy direction.
MaterialDesignDemo.Domain uses MaterialDesignColors, so a change to MaterialDesignColors can break MaterialDesignDemo.Domain, while a change to MaterialDesignDemo.Domain can't break MaterialDesignColors.
Position
Below the diagonal: MaterialDesignDemo.Domain uses a module listed above it, which is the healthy direction.
MaterialDesignDemo.Domain uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignDemo.Domain, while a change to MaterialDesignDemo.Domain can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignDemo.Domain uses a module listed above it, which is the healthy direction.
MaterialDesignDemo.Domain uses MaterialDesignDemo.Shared.Domain, so a change to MaterialDesignDemo.Shared.Domain can break MaterialDesignDemo.Domain, while a change to MaterialDesignDemo.Domain can't break MaterialDesignDemo.Shared.Domain.
Position
Below the diagonal: MaterialDesignDemo.Domain uses a module listed above it, which is the healthy direction.
33→35 MaterialDesignDemo.Domain uses MaterialDesignDemopart of a loop✕
Connections
1 pair of types, where a type in MaterialDesignDemo.Domain uses a type in MaterialDesignDemo.
MaterialDesignDemo.Domain uses MaterialDesignDemo, so a change to MaterialDesignDemo can break MaterialDesignDemo.Domain, while a change to MaterialDesignDemo.Domain can't break MaterialDesignDemo.
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.
MaterialDesignDemo.TransitionsDemo uses MaterialDesignDemo.Shared.Domain, so a change to MaterialDesignDemo.Shared.Domain can break MaterialDesignDemo.TransitionsDemo, while a change to MaterialDesignDemo.TransitionsDemo can't break MaterialDesignDemo.Shared.Domain.
Position
Below the diagonal: MaterialDesignDemo.TransitionsDemo uses a module listed above it, which is the healthy direction.
MaterialDesignDemo uses MaterialDesignThemes.Wpf, so a change to MaterialDesignThemes.Wpf can break MaterialDesignDemo, while a change to MaterialDesignDemo can't break MaterialDesignThemes.Wpf.
Position
Below the diagonal: MaterialDesignDemo uses a module listed above it, which is the healthy direction.
MaterialDesignDemo uses MaterialDesignDemo.Domain, so a change to MaterialDesignDemo.Domain can break MaterialDesignDemo, while a change to MaterialDesignDemo can't break MaterialDesignDemo.Domain.
Position
Below the diagonal: MaterialDesignDemo uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
59
High / Critical
A03:2025 — Software Supply Chain Failures
13
Medium
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
Begin by documenting significant design decisions in the docs/adr folder to establish a clear architectural record. Simultaneously, address critical security risks by resolving high-severity secrets in pipeline files and fixing static analysis findings related to shell injection. Finally, strengthen supply-chain integrity by scoping long-lived secrets in workflow files to ensure proper provenance and signing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 58
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 — 325
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 — 130
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 4
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 68 of 72 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 72 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, 486 of 513 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D14 License Compliance — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
D17 Explicit Debt — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/MaterialDesignThemes.MahApps/MaterialDesignThemes.MahApps.csproj' with message: The following PackageReference item(s) do not have a version specified: MahApps.Metro.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (59,716 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"]`.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/MaterialDesignToolkit.ResourceGeneration/Palette.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/MainDemo.Wpf/Domain/MainWindowViewModel.cs`, `src/MainDemo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesignColors.Wpf/ColorPair.cs`, … (+15 more) 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.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
GD1 Unfinished & placeholder code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 32 further occurrence(s) are not listed individually; the score already reflects all 72.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/MahMaterialDragablzMashUp/MahAppsDragablzDemo.csproj, src/MainDemo.Wpf/MaterialDesignDemo.csproj, src/MaterialDesign3.Demo.Wpf/MaterialDesign3Demo.csproj, src/MaterialDesignDemo.Shared/MaterialDesignDemo.Shared.csproj, src/MaterialDesign3.MaterialColorUtilities/MaterialColorUtilities.csproj and 8 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
18 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ColorSpec2021.GetTone at 50. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being FloatingHintInitialHorizontalOffsetConverter.Convert at 19 — 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/MaterialDesignThemes.Wpf/Converters/FloatingHintInitialHorizontalOffsetConverter.cs (FloatingHintInitialHorizontalOffsetConverter.Convert at 19). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ColorSpec2021.GetTone (cyclomatic 50), ColorSpec2025.GetTone (cyclomatic 44), QuantizerWsMeans.Quantize (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 3 together lifts Cyclomatic Complexity from 7.3 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 33 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 30 down to 30 or less in Cognitive Complexity — start with ColorSpec2021.GetTone (cognitive 92), ColorSpec2025.GetTone (cognitive 71), QuantizerWsMeans.Quantize (cognitive 61). — 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 7 together lifts Cognitive Complexity from 6.1 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.0 / 10Stronggated by 15 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 5 MethodTooLong finding(s) in God Classes — start with MaterialDesignAssist.cs (2), MainWindowViewModel.cs (2), QuantizerWsmeans.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with ColorSpec2025.cs, ColorSpec2021.cs, DrawerHost.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with TextFieldAssist.cs, DialogHost.cs, TimePicker.cs. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
85 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 39 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with IconPackViewModel.cs (2), Pickers.xaml.cs, MaterialDesignAssist.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Pickers.xaml.cs (2), Scheme.cs, ComboBoxes.xaml.cs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 6 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with Ripple.cs, FutureDateValidationRule.cs, FieldsLineUp.xaml.cs. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 2 serious findings✓ 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.
Off the main sequence: MaterialDesignColors.Wpf(net462) · ×2src/MaterialDesignColors.Wpf/MaterialDesignColors.Wpf.csproj:1
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling — start with MaterialDesignColors.Wpf.csproj, MaterialDesignThemes.Wpf.csproj. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
617 test methods: 617 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
5 skipped (3 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 489 tests.
Resolve the 2 Skipped test finding(s) in Test Quality — start with ThemeTests.cs, HctTests.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
10 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/MaterialDesignThemes.Wpf/PackIconDataFactory.cs. Counted over 167 of the 593 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
45 deducted debt markers + unmeasured dead symbols across 59716 LoC in the .NET projects (0.2/KLoC) → score 9.6. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 NoWarnInCsproj finding(s) in Explicit Debt — start with MaterialDesignThemes.Wpf.csproj (2), MaterialDesignThemes.UITests.csproj, Motion.csproj. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with SliderToolTipConverter.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 15 TodoComment finding(s) in Explicit Debt — start with TimePicker.cs (3), SmartHint.xaml (3), IconPackViewModel.cs (2). — One of this dimension's main actionable groups (15 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the 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.
30 projects, 1730 source files, 72251 hand-written lines of code (59716 production / 12535 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 444 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 41 inter-project edges (build status unknown — did not finish).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is comprehensive and well-structured for a project that provides Material Design themes and controls for WPF. It states the purpose of the toolkit (Material Design styles for major WPF Framework controls, Multi Action Button, Cards, Dialogs, Clock; easy palette configuration per design and runtime; full Material Design Icons; transition effects; Dragablz/MahApps compatibility; demo applications) and links to NuGet badges, a screenshot table of contents, and an extensive architecture/optimization doc set (Freezable_Object_for_Enhanced_Performance, Optimizing-WPF-Rendering-Performance, Reducing_Layout_Complexity). The README itself is clipped mid-table-of-contents summary, so the outline sections are presumed present but not flagged as missing. The visible content is clear and complete for its scope.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D24 · Comment ValueStrong◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
1 of 14 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
34 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: 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.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 4 High secret finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 43 high, 16 medium, 0 low. 28 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 20 file(s) — `src/MainDemo.Wpf/Domain/MainWindowViewModel.cs`, `src/MainDemo.Wpf/Domain/QuickSearchDialogViewModel.cs` (line 7), `src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/QuickSearchDialogViewModel.cs` (line 5), `src/MaterialDesignColors.Wpf/ColorPair.cs` (line 8), … (+15 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 9 of those file(s) — `src/MainDemo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesignColors.Wpf/ColorPair.cs`, `src/MaterialDesignThemes.Wpf/Automation/Peers/TreeListViewItemAutomationPeer.cs`, `src/MaterialDesignThemes.Wpf/Converters/BooleanConverter.cs`, … (+4 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 4 of those file(s) — `src/MainDemo.Wpf/Domain/MainWindowViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs`, `src/MaterialDesignThemes.Wpf/UpDownBase.cs`, `src/MaterialDesignToolkit.ResourceGeneration/Brushes.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 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED (3). — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 28 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 (28 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.
44 of 167 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs. Counted over 167 of the 593 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 42 Orphaned file finding(s) in Knowledge Freshness — start with HctSolver.cs, ArcSpline.cs, QuantizerWu.cs. — One of this dimension's main actionable groups (42 recommendation-level).
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with ColorSpec2025.cs, ColorSpec2021.cs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 14 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces MaterialDesignDemo ↔ MaterialDesignDemo.Domain ↔ MaterialDesignDemo.Shared.Domain depend on each other. The lightest dependency in the cycle is MaterialDesignDemo → MaterialDesignDemo.Domain (MaterialDesignDemo.Trees → MaterialDesignDemo.Domain.TreesViewModel, 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/MainDemo.Wpf/Trees.xaml.cs:1
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.
`ColorSpec` declares 100 members: `PrimaryPaletteKeyColor`, `SecondaryPaletteKeyColor`, `TertiaryPaletteKeyColor`, `NeutralPaletteKeyColor`, `NeutralVariantPaletteKeyColor`, `ErrorPaletteKeyColor`, `WarningHighPaletteKeyColor`, `WarningLowPaletteKeyColor`, `InformationPaletteKeyColor`, `SafePaletteKeyColor`, `Background`, `OnBackground`, `Surface`, `SurfaceDim`, `SurfaceBright`, `SurfaceContainerLowest`, `SurfaceContainerLow`, `SurfaceContainer`, `SurfaceContainerHigh`, `SurfaceContainerHighest`, `OnSurface`, `SurfaceVariant`, `OnSurfaceVariant`, `InverseSurface`, `InverseOnSurface`, `Outline`, `OutlineVariant`, `Shadow`, `Scrim`, `SurfaceTint`, `Primary`, `PrimaryDim`, `OnPrimary`, `PrimaryContainer`, `OnPrimaryContainer`, `InversePrimary`, `Secondary`, `SecondaryDim`, `OnSecondary`, `SecondaryContainer`, and 60 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec.cs:3
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain9.6 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
`ButtonsViewModel` reads `DateTime.Now` inside `UpdateDemoRestartCountdownText`, `Save`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. — src/MaterialDesignDemo.Shared/Domain/ButtonsViewModel.cs:86
`FutureDateValidationRule` reads `DateTime.Now` inside `Validate`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`. (×2) — src/MainDemo.Wpf/Domain/FutureDateValidationRule.cs:7, src/MaterialDesign3.Demo.Wpf/Domain/FutureDateValidationRule.cs:7
`TreesViewModel` draws from `new Random(` inside `GenerateString`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it. (×2) — src/MainDemo.Wpf/Domain/TreesViewModel.cs:231, src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:215
What to do
Take the instant and the randomness as inputs to the domain methods that need them — inject `TimeProvider` (BCL, .NET 8+) and a `Random`/seeded generator — so a test can choose both.
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. (×40) — src/MaterialDesignThemes.Wpf/Converters/BooleanAllConverter.cs:13, src/MaterialDesignThemes.Wpf/Converters/BorderClipConverter.cs:39, src/MaterialDesignThemes.Wpf/Converters/CalendarYearMonthConverter.cs:33, …
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.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×27) — src/MainDemo.Wpf/App.xaml.cs:22, src/MainDemo.Wpf/App.xaml.cs:23, src/MainDemo.Wpf/App.xaml.cs:24, …
4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). (×4) — src/MainDemo.Wpf/App.xaml.cs:30, src/MainDemo.Wpf/App.xaml.cs:41, src/MaterialDesign3.Demo.Wpf/App.xaml.cs:30, …
A placeholder value ("
Lorem ipsum dolor sit amet, consectetur…") is still in shipped code — sample/mock data that was never replaced with the real thing. — src/MainDemo.Wpf/Domain/TabsViewModel.cs:13
12 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — src/MaterialDesignThemes.Wpf/DataGridComboBoxColumn.cs:107
What to do
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 repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
51 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 14 of 14 project(s) that lack one — worth up to 2 pts.
Review the README against recent changes; refresh the parts that drifted.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Only 5/14 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README.md links to `src/web/images/screen-md2/expander.png`, but `src/web/images/screen-md2/expander.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:188
What to do
Reconcile the README with reality: README.md links to `src/web/images/screen-md2/expander.png`, but `src/web/images/screen-md2/expander.png` does not exist.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
1215/1440 types (84%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
What to do
Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
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 24285 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: 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.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · 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.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 2 use(s) across 60,893 production line(s) (~0.0/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
X1 · Async correctness4.0 / 10Weak✓ Tool-verified
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×11) — src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:67, src/MainDemo.Wpf/Dialogs.xaml.cs:45, src/MainDemo.Wpf/Dialogs.xaml.cs:80, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`SnackbarMessageQueue` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_showMessageSemaphore` itself (line 16), which makes that instance its own. But `_showMessageSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 432) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_showMessageSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:16
`SnackbarMessageQueue` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_closeSnackbarEvent` itself (line 38), which makes that instance its own. But `_closeSnackbarEvent` is named in none of the methods the disposal search covered: `Dispose` (line 432) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_closeSnackbarEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:38
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 a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/27 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×27) — src/MaterialDesignThemes.Wpf/DialogHost.cs:183, src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:67, src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:284, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped3.9 / 10Weak✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`wrap[1]+markup+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:17181
`markup` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:17188
`nodeName` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:17963
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×3) — REDACTED:18911, REDACTED:18918, REDACTED:18962
`'\uFEFF'+html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:18951
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. — src/MaterialDesignThemes.Wpf/Converters/Internal/SliderToolTipConverter.cs:17
`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. (×2) — src/MainDemo.Wpf/Pickers.xaml.cs:28, src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:28
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.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `dataGridCell`: line 399 writes `dataGridCell?.IsReadOnly`, which says `dataGridCell` can be null, but line 404 then dereferences it directly as `dataGridCell.Content` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `dataGridCell` truly cannot be null here, the `?.` is misleading. Settle it one way — test `dataGridCell` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/MaterialDesignThemes.Wpf/DataGridAssist.cs:404
~0.6 `!` suppressions per 1k syntax nodes — 162 suppression(s) across the 284999 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
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.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
X10 Duplicated predicate — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 45 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D11 Test Reliability — Test reliability not measured — no test run produced results
D14 License Compliance — Licence collector did not produce a result
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) — 20 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.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 6 value object(s); a Domain/Aggregates/ValueObjects layer
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
P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
NoWarnInCsproj tests/MaterialDesignThemes.UITests/MaterialDesignThemes.UITests.csproj:7— CA1707 — 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/MaterialDesignThemes.Wpf/MaterialDesignThemes.Wpf.csproj:13— CS1591 — 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/MaterialDesignThemes.Wpf/MaterialDesignThemes.Wpf.csproj:13— CS1574 — 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/MaterialDesign3.Motion/Motion.csproj:23— CS0618 — 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/MaterialDesign3.MaterialColorUtilities/MaterialColorUtilities.csproj:24— CS0618 — 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/MaterialDesign3.Demo.Wpf/MaterialDesign3Demo.csproj:45— NU1701 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
NoWarnInCsproj src/MainDemo.Wpf/MaterialDesignDemo.csproj:43— NU1701 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
Orphaned knowledge src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Namespace dependency cycle src/MainDemo.Wpf/Trees.xaml.cs:1— The namespaces MaterialDesignDemo ↔ MaterialDesignDemo.Domain ↔ MaterialDesignDemo.Shared.Domain depend on each other. The lightest dependency in the cycle is MaterialDesignDemo → MaterialDesignDemo.Domain (MaterialDesignDemo.Trees → MaterialDesignDemo.Domain.TreesViewModel, 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.
EmptyCatchBlock src/MaterialDesignThemes.Wpf/Converters/Internal/SliderToolTipConverter.cs:17— 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.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/BooleanAllConverter.cs:13— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/BorderClipConverter.cs:39— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/CalendarYearMonthConverter.cs:33— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/CircularProgressBar/ArcEndPointConverter.cs:53— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/CornerRadiusCloneConverter.cs:26— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/CursorConverter.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/MaterialDesignThemes.Wpf/Converters/DrawerOffsetConverter.cs:24— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/ElevationMarginConverter.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/MaterialDesignThemes.Wpf/Converters/ElevationRadiusConverter.cs:21— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/EllipseClipConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/EqualityToVisibilityConverter.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/MaterialDesignThemes.Wpf/Converters/FallbackBrushConverter.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/MaterialDesignThemes.Wpf/Converters/FirstNonNullConverter.cs:13— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/FloatingHintClippingGridConverter.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/MaterialDesignThemes.Wpf/Converters/FloatingHintContainerMarginConverter.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/MaterialDesignThemes.Wpf/Converters/FloatingHintInitialHorizontalOffsetConverter.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/MaterialDesignThemes.Wpf/Converters/FloatingHintInitialVerticalOffsetConverter.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/MaterialDesignThemes.Wpf/Converters/FloatingHintMarginConverter.cs:54— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/FloatingHintScaleTransformConverter.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/MaterialDesignThemes.Wpf/Converters/FloatingHintTranslateTransformConverter.cs:62— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/HorizontalThicknessConverter.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/MaterialDesignThemes.Wpf/Converters/HsbLinearGradientConverter.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/MaterialDesignThemes.Wpf/Converters/HsbToColorConverter.cs:33— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MaterialDesignThemes.Wpf/Converters/Internal/AutomationPropertiesNameConverter.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/MaterialDesignThemes.Wpf/Converters/Internal/DialogBackgroundBlurConverter.cs:26— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
+ 15 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×27
Async method without CancellationToken: Show src/MaterialDesignThemes.Wpf/DialogHost.cs:183— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: UiElementOnMouseLeave src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:67— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowNextAsync src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:284— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowAsync src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:337— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WaitForCompletionAsync src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:393— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InputDialog src/MahMaterialDragablzMashUp/DialogsViewModel.cs:25— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ProgressDialog src/MahMaterialDragablzMashUp/DialogsViewModel.cs:36— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sample2_DialogHost_OnDialogClosing src/MainDemo.Wpf/Dialogs.xaml.cs:45— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sample6_OpenDialog src/MainDemo.Wpf/Dialogs.xaml.cs:80— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunDialog src/MainDemo.Wpf/Domain/DialogsViewModel.cs:13— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunExtendedDialog src/MainDemo.Wpf/Domain/DialogsViewModel.cs:35— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Search src/MainDemo.Wpf/Domain/IconPackViewModel.cs:89— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OpenQuickSearchAsync src/MainDemo.Wpf/Domain/MainWindowViewModel.cs:490— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MenuPopupButton_OnClick src/MainDemo.Wpf/MainWindow.xaml.cs:71— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sample2_DialogHost_OnDialogClosing src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:31— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteRunDialog src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:23— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteRunExtendedDialog src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:41— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Search src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:90— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: OpenQuickSearchAsync src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs:521— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: MenuPopupButton_OnClick src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.cs:74— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Sample_OpenButton_Click src/MaterialDesignDemo.Shared/Examples/Dialogs/DialogHostWaitForExample.xaml.cs:18— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GenerateBrushesAsync src/MaterialDesignToolkit.ResourceGeneration/Brushes.cs:29— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RunAsync src/MaterialDesignToolkit.ResourceGeneration/IconDiff.cs:14— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: CompareNuGets src/MaterialDesignToolkit.ResourceGeneration/IconDiff.cs:36— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ProcessNuGet src/MaterialDesignToolkit.ResourceGeneration/IconDiff.cs:100— No CancellationToken parameter — this work can't be stopped early once started.
TodoComment src/MainDemo.Wpf/Domain/IconPackViewModel.cs:151— //TODO: Make this size list configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:152— //TODO: Make this size list configurable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/TimePicker.cs:210— //TODO set time — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/TimePicker.cs:551— //TODO Clock closed event — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/TimePicker.cs:568— //TODO ClockOpenedEvent — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/TreeListView.cs:12— //TODO: Implement bindable property for getting selected items — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/MaterialDesignThemes.UITests/WPF/DatePickers/DatePickerTests.cs:119— // TODO: It would be cool if a validation error could be set via XAMLTest without the need for the Binding and ValidationRules elements in the XAML above. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/MaterialDesignThemes.UITests/WPF/TimePickers/TimePickerTests.cs:327— // TODO: It would be cool if a validation error could be set via XAMLTest without the need for the Binding and ValidationRules elements in the XAML above. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/MaterialDesignThemes.Wpf.Tests/ColorPickerTests.cs:6— //TODO: Many of these tests could be moved over to MaterialDesignThemes.UITests — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MainDemo.Wpf/SmartHint.xaml:815— <!-- TODO: This is needed in order to avoid the RichTextBox only showing a single character per line?!?! There must be a bug somewhere! Min/MinWidth both "work". Also happens with default style!! --> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MainDemo.Wpf/SmartHint.xaml:879— <!-- TODO: This is needed in order to avoid the RichTextBox only showing a single character per line?!?! There must be a bug somewhere! Min/MinWidth both "work". Also happens with default style!! --> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MainDemo.Wpf/SmartHint.xaml:943— <!-- TODO: This is needed in order to avoid the RichTextBox only showing a single character per line?!?! There must be a bug somewhere! Min/MinWidth both "work". Also happens with default style!! --> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/Themes/MaterialDesignTheme.ToggleButton.xaml:307— <!-- TODO
<Trigger Property="IsFocused" Value="True">
<Setter Property="BorderBrush" TargetName="normal" Value="{Binding (Custom:ControlsHelper.FocusBorderBrush), RelativeSource={RelativeSource TemplatedParent}}" />
</Trigger>
--> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MaterialDesignThemes.Wpf/Themes/MaterialDesign3.ToggleButton.xaml:332— <!-- TODO
<Trigger Property="IsFocused" Value="True">
<Setter Property="BorderBrush" TargetName="normal" Value="{Binding (Custom:ControlsHelper.FocusBorderBrush), RelativeSource={RelativeSource TemplatedParent}}" />
</Trigger>
--> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment tests/MaterialDesignThemes.UITests/Samples/AutoSuggestBoxes/AutoSuggestTextBoxWithCollectionView.xaml:11— <!-- TODO: Selction Similar to SelectedItem="{Binding Suggestions/}" perhaps needing IsSynchronizedWithCurrentItem="True" --> — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/ComboBoxes/ComboBoxTests.cs:163— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/ComboBoxes/ComboBoxTests.cs:201— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/DatePickers/DatePickerTests.cs:144— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/DatePickers/DatePickerTests.cs:181— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/PasswordBoxes/PasswordBoxTests.cs:189— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/PasswordBoxes/PasswordBoxTests.cs:237— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/TextBoxes/TextBoxTests.cs:415— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/TextBoxes/TextBoxTests.cs:453— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/TimePickers/TimePickerTests.cs:352— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/TimePickers/TimePickerTests.cs:390— // FIXME: Tolerance needed because TextFieldAssist.TextBoxViewMargin is in play and slightly modifies the hint text placement in certain cases. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment tests/MaterialDesignThemes.UITests/WPF/TreeListViews/TreeListViewTests.cs:833— // FIXME: At this point, the expansion state is wrong. The chevron indicates expanded, but in fact it is collapsed. Expanding it then crashes with an ArgumentOutOfRangeException — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
async void method: UiElementOnMouseLeave src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:67— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Sample2_DialogHost_OnDialogClosing src/MainDemo.Wpf/Dialogs.xaml.cs:45— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Sample6_OpenDialog src/MainDemo.Wpf/Dialogs.xaml.cs:80— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Search src/MainDemo.Wpf/Domain/IconPackViewModel.cs:89— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: MenuPopupButton_OnClick src/MainDemo.Wpf/MainWindow.xaml.cs:71— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Sample2_DialogHost_OnDialogClosing src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:31— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ExecuteRunDialog src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:23— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ExecuteRunExtendedDialog src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:41— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Search src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:90— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: MenuPopupButton_OnClick src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.cs:74— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Sample_OpenButton_Click src/MaterialDesignDemo.Shared/Examples/Dialogs/DialogHostWaitForExample.xaml.cs:18— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Duplicated block (5 lines × 2) src/MainDemo.Wpf/Pickers.xaml.cs:76— src/MainDemo.Wpf/Pickers.xaml.cs:76-80 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:76-80 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:566— src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:566-570 | src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:631-635 — both copies are in the same file, so extract the 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 (5 lines × 2) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1709— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1709-1715 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1723-1727 — both copies are in the same file, so extract the 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1709` 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 (5 lines × 2) src/MaterialDesignThemes.Wpf/Transitions/CircleWipe.cs:12— src/MaterialDesignThemes.Wpf/Transitions/CircleWipe.cs:12-16 | src/MaterialDesignThemes.Wpf/Transitions/SlideOutWipe.cs:12-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/MainDemo.Wpf/Domain/IconPackViewModel.cs:73— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:73-77 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:74-78 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Domain/IconPackViewModel.cs:113— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:113-117 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:114-118 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Domain/Link.cs:10— src/MainDemo.Wpf/Domain/Link.cs:10-14 | src/MaterialDesign3.Demo.Wpf/Domain/Link.cs:10-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:40— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:40-44 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:40-44 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Dialogs.xaml.cs:46— src/MainDemo.Wpf/Dialogs.xaml.cs:46-50 | src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:32-36 — `src/MainDemo.Wpf/Dialogs.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.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 3 separate duplicated blocks between them, totalling at least 27 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/MainDemo.Wpf/Dialogs.xaml.cs:52` calls `Sample2_DialogHost_OnDialogClosed`, `WriteLine` and `src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:38` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:75— src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:75-81 | src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:118-124 — both copies are in the same file, so extract the 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/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:75` 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 (7 lines × 2) src/MainDemo.Wpf/ComboBoxes.xaml.cs:11— src/MainDemo.Wpf/ComboBoxes.xaml.cs:11-17 | src/MainDemo.Wpf/ComboBoxes.xaml.cs:28-34 — both copies are in the same file, so extract the 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/MainDemo.Wpf/ComboBoxes.xaml.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:743— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:743-749 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:818-824 — both copies are in the same file, so extract the 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:743` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) src/MainDemo.Wpf/ButtonAssist.cs:9— src/MainDemo.Wpf/ButtonAssist.cs:9-15 | src/MaterialDesign3.Demo.Wpf/ButtonAssist.cs:9-15 — `src/MainDemo.Wpf/ButtonAssist.cs` and `src/MaterialDesign3.Demo.Wpf/ButtonAssist.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 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) src/MaterialDesignThemes.Wpf/DatePickerAssist.cs:8— src/MaterialDesignThemes.Wpf/DatePickerAssist.cs:8-14 | src/MaterialDesignThemes.Wpf/TimePickerAssist.cs:8-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/MainDemo.Wpf/Domain/SimpleDateValidationRule.cs:9— src/MainDemo.Wpf/Domain/SimpleDateValidationRule.cs:9-15 | src/MaterialDesign3.Demo.Wpf/Domain/SimpleDateValidationRule.cs:9-15 — 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/MainDemo.Wpf/Pickers.xaml.cs:12— src/MainDemo.Wpf/Pickers.xaml.cs:12-18 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:12-18 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/MainDemo.Wpf/Pickers.xaml.cs:41— src/MainDemo.Wpf/Pickers.xaml.cs:41-47 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:41-47 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×7
Untrusted text written into markup unescaped REDACTED:17181— `wrap[1]+markup+wrap[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:17188— `markup` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:17963— `nodeName` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:18911— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:18918— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:18951— `'\uFEFF'+html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:18962— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Duplicated block (10 lines × 2) src/MaterialDesignThemes.Wpf/Ripple.cs:67— src/MaterialDesignThemes.Wpf/Ripple.cs:67-76 | src/MaterialDesignThemes.Wpf/Ripple.cs:82-91 — both copies are in the same file, so extract the 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/MaterialDesignThemes.Wpf/Ripple.cs:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/MainDemo.Wpf/Domain/FutureDateValidationRule.cs:9— src/MainDemo.Wpf/Domain/FutureDateValidationRule.cs:9-18 | src/MaterialDesign3.Demo.Wpf/Domain/FutureDateValidationRule.cs:9-18 — before extracting anything, compare `src/MainDemo.Wpf/Domain/FutureDateValidationRule.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/FutureDateValidationRule.cs` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. 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 (10 lines × 2) src/MainDemo.Wpf/FieldsLineUp.xaml.cs:63— src/MainDemo.Wpf/FieldsLineUp.xaml.cs:63-72 | src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.cs:63-72 — `src/MainDemo.Wpf/FieldsLineUp.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.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 3 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (10 lines × 2) src/MaterialDesign3.Demo.Wpf/PaletteHelperExtensions.cs:21— src/MaterialDesign3.Demo.Wpf/PaletteHelperExtensions.cs:21-30 | src/MaterialDesignDemo.Shared/PaletteHelperExtensions.cs:21-30 — `src/MaterialDesign3.Demo.Wpf/PaletteHelperExtensions.cs` and `src/MaterialDesignDemo.Shared/PaletteHelperExtensions.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 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) src/MainDemo.Wpf/Pickers.xaml.cs:54— src/MainDemo.Wpf/Pickers.xaml.cs:54-63 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:54-63 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (10 lines × 2) src/MainDemo.Wpf/Snackbars.xaml.cs:42— src/MainDemo.Wpf/Snackbars.xaml.cs:42-51 | src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.cs:42-51 — `src/MainDemo.Wpf/Snackbars.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.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 3 separate duplicated blocks between them, totalling at least 32 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.
MethodTooLong: MaterialDesignAssist.SetMahApps src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:12— MethodTooLong — SetMahApps runs 381 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 281 over it, 3.81× 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: MainWindowViewModel.GenerateDemoItems src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs:128— MethodTooLong — GenerateDemoItems runs 270 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 170 over it, 2.70× 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: MainWindowViewModel.GenerateDemoItems src/MainDemo.Wpf/Domain/MainWindowViewModel.cs:118— MethodTooLong — GenerateDemoItems runs 222 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 122 over it, 2.22× 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: MaterialDesignAssist.SetMahAppsBaseTheme src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:503— MethodTooLong — SetMahAppsBaseTheme 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: QuantizerWsMeans.Quantize src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWsmeans.cs:21— MethodTooLong — Quantize runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (11 lines × 2) src/MaterialDesignThemes.Wpf/TextFieldAssist.cs:574— src/MaterialDesignThemes.Wpf/TextFieldAssist.cs:574-584 | src/MaterialDesignThemes.Wpf/TextFieldAssist.cs:617-627 — both copies are in the same file, so extract the 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/MaterialDesignThemes.Wpf/TextFieldAssist.cs:574` 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/MainDemo.Wpf/Dialogs.xaml.cs:18— src/MainDemo.Wpf/Dialogs.xaml.cs:18-28 | src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:18-28 — `src/MainDemo.Wpf/Dialogs.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.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 3 separate duplicated blocks between them, totalling at least 27 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 (11 lines × 2) src/MainDemo.Wpf/Dialogs.xaml.cs:57— src/MainDemo.Wpf/Dialogs.xaml.cs:57-67 | src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:40-50 — `src/MainDemo.Wpf/Dialogs.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.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 3 separate duplicated blocks between them, totalling at least 27 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 (11 lines × 2) src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:73— src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:73-85 | src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:87-97 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:73` 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/MainDemo.Wpf/Domain/MainWindowViewModel.cs:492— src/MainDemo.Wpf/Domain/MainWindowViewModel.cs:492-502 | src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs:523-533 — 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/MainDemo.Wpf/Pickers.xaml.cs:90— src/MainDemo.Wpf/Pickers.xaml.cs:90-97 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:90-97 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:56— src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:56-63 | src/MaterialDesignThemes.Wpf/Transitions/SlideWipe.cs:66-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/MainDemo.Wpf/Domain/DemoItem.cs:49— src/MainDemo.Wpf/Domain/DemoItem.cs:49-56 | src/MaterialDesign3.Demo.Wpf/Domain/DemoItem.cs:67-74 — 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/MainDemo.Wpf/Domain/TreesViewModel.cs:18— src/MainDemo.Wpf/Domain/TreesViewModel.cs:18-25 | src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:16-23 — before extracting anything, compare `src/MainDemo.Wpf/Domain/TreesViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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 (8 lines × 2) src/MainDemo.Wpf/Snackbars.xaml.cs:11— src/MainDemo.Wpf/Snackbars.xaml.cs:11-18 | src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.cs:11-18 — `src/MainDemo.Wpf/Snackbars.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.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 3 separate duplicated blocks between them, totalling at least 32 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.
HackComment src/MainDemo.Wpf/Pickers.xaml.cs:32— //HACK: The calendar only refresh when we change the date — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:32— //HACK: The calendar only refresh when we change the date — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment src/MaterialDesignThemes.Wpf/Behaviors/Internal/TabControlHeaderScrollBehavior.cs:346— // HACK: Temporarily disable user interaction while the animated scroll is ongoing. This prevents the double-click of a tab stopping the animation prematurely. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment src/MaterialDesignThemes.Wpf/Behaviors/Internal/TabControlHeaderScrollBehavior.cs:359— // HACK: Re-enable hit test visibility — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
ClassTooLong: ColorSpec2025 src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs— ClassTooLong — 1154 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 754 over it, 2.89× 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.
ClassTooLong: ColorSpec2021 src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs— ClassTooLong — 799 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 399 over it, 2.00× 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.
ClassTooLong: DrawerHost src/MaterialDesignThemes.Wpf/DrawerHost.cs— ClassTooLong — 434 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 34 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.
ClassTooLong: PopupBox src/MaterialDesignThemes.Wpf/PopupBox.cs— ClassTooLong — 407 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 7 over it, 1.02× 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: TextFieldAssist src/MaterialDesignThemes.Wpf/TextFieldAssist.cs— TooManyMethods — 314 significant lines (blank, comment-only and punctuation-only lines excluded), 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: DialogHost src/MaterialDesignThemes.Wpf/DialogHost.cs— TooManyMethods — 455 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: TimePicker src/MaterialDesignThemes.Wpf/TimePicker.cs— TooManyMethods — 308 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: TabAssist src/MaterialDesignThemes.Wpf/TabAssist.cs— TooManyMethods — 104 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. 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.
Duplicated block (12 lines × 2) src/MainDemo.Wpf/Domain/IconPackViewModel.cs:91— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:91-102 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:92-103 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (12 lines × 2) src/MaterialDesign3.Motion/MonoSpline.cs:114— src/MaterialDesign3.Motion/MonoSpline.cs:114-125 | src/MaterialDesign3.Motion/MonoSpline.cs:214-225 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesign3.Motion/MonoSpline.cs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/MaterialDesign3.Motion/MonoSpline.cs:113` calls `Clamp` and `src/MaterialDesign3.Motion/MonoSpline.cs:212` 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 (12 lines × 2) src/MaterialDesign3.MaterialColorUtilities/Contrast/Contrast.cs:117— src/MaterialDesign3.MaterialColorUtilities/Contrast/Contrast.cs:117-129 | src/MaterialDesign3.MaterialColorUtilities/Contrast/Contrast.cs:164-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) src/MainDemo.Wpf/IconPack.xaml.cs:10— src/MainDemo.Wpf/IconPack.xaml.cs:10-21 | src/MaterialDesign3.Demo.Wpf/IconPack.xaml.cs:10-21 — `src/MainDemo.Wpf/IconPack.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/IconPack.xaml.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 1 separate duplicated blocks between them, totalling at least 12 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:106— src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:106-114 | src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:149-157 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:106` 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 (9 lines × 2) src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:79— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:79-87 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:79-87 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:98— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:98-106 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:98-106 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:117— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:117-125 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:117-125 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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/MainDemo.Wpf/Pickers.xaml.cs:22— src/MainDemo.Wpf/Pickers.xaml.cs:22-37 | src/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:22-37 — `src/MainDemo.Wpf/Pickers.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Pickers.xaml.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 6 separate duplicated blocks between them, totalling at least 53 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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/MainDemo.Wpf/Domain/TreesViewModel.cs:90— src/MainDemo.Wpf/Domain/TreesViewModel.cs:90-105 | src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:76-91 — before extracting anything, compare `src/MainDemo.Wpf/Domain/TreesViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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/MainDemo.Wpf/Domain/TreesViewModel.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/MainDemo.Wpf/Home.xaml.cs:8— src/MainDemo.Wpf/Home.xaml.cs:8-23 | src/MaterialDesign3.Demo.Wpf/Home.xaml.cs:8-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:536— src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:536-541 | src/MaterialDesignThemes.MahApps/MaterialDesignAssist.cs:601-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/MainDemo.Wpf/Domain/TreesViewModel.cs:233— src/MainDemo.Wpf/Domain/TreesViewModel.cs:233-238 | src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:217-222 — before extracting anything, compare `src/MainDemo.Wpf/Domain/TreesViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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 (6 lines × 2) src/MainDemo.Wpf/MainWindow.xaml.cs:109— src/MainDemo.Wpf/MainWindow.xaml.cs:109-114 | src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.cs:121-126 — `src/MainDemo.Wpf/MainWindow.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.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 3 separate duplicated blocks between them, totalling at least 61 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.
DM12 · Ambient inputs in the domain· Domain type reads the wall clock · ×3
Domain type reads the wall clock: ButtonsViewModel src/MaterialDesignDemo.Shared/Domain/ButtonsViewModel.cs:86— `ButtonsViewModel` reads `DateTime.Now` inside `UpdateDemoRestartCountdownText`, `Save`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: FutureDateValidationRule src/MainDemo.Wpf/Domain/FutureDateValidationRule.cs:7— `FutureDateValidationRule` reads `DateTime.Now` inside `Validate`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
Domain type reads the wall clock: FutureDateValidationRule src/MaterialDesign3.Demo.Wpf/Domain/FutureDateValidationRule.cs:7— `FutureDateValidationRule` reads `DateTime.Now` inside `Validate`. The rule this feeds is not a function of its inputs: it cannot be tested at the instant that matters without moving the machine clock, and two reads inside one operation can observe different times. Pass the instant in as a parameter, or inject `TimeProvider`.
TreesViewModel.TreesViewModel.ctor (cognitive 22) src/MainDemo.Wpf/Domain/TreesViewModel.cs:119— TreesViewModel.TreesViewModel.ctor has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 153, a function literal at line 214, CreateTestItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TreesViewModel.TreesViewModel.ctor (cognitive 22) src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:105— TreesViewModel.TreesViewModel.ctor has cognitive complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 139, a function literal at line 198, CreateTestItem, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FileTooLong: DynamicColor/ColorSpec2025.cs src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs— FileTooLong — 1155 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 655 over it, 2.31× 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: DynamicColor/ColorSpec2021.cs src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs— FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 300 over it, 1.60× 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.
Duplicated block (29 lines × 2) src/MainDemo.Wpf/FieldsLineUp.xaml.cs:76— src/MainDemo.Wpf/FieldsLineUp.xaml.cs:76-104 | src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.cs:76-104 — `src/MainDemo.Wpf/FieldsLineUp.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.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 3 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (29 lines × 2) src/MainDemo.Wpf/App.xaml.cs:19— src/MainDemo.Wpf/App.xaml.cs:19-47 | src/MaterialDesign3.Demo.Wpf/App.xaml.cs:19-47 — `src/MainDemo.Wpf/App.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/App.xaml.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 1 separate duplicated blocks between them, totalling at least 29 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 (22 lines × 2) src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:11— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:11-32 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:11-32 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:11` 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 (22 lines × 2) src/MaterialDesignThemes.Wpf/Converters/BorderClipConverter.cs:121— src/MaterialDesignThemes.Wpf/Converters/BorderClipConverter.cs:121-142 | src/MaterialDesignThemes.Wpf/Converters/BorderClipConverter.cs:145-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.
Duplicated block (21 lines × 2) src/MaterialDesignThemes.MahApps/MahAppsBundledTheme.cs:101— src/MaterialDesignThemes.MahApps/MahAppsBundledTheme.cs:101-121 | src/MaterialDesignThemes.MahApps/MahAppsCustomColorTheme.cs:94-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesignThemes.MahApps/MahAppsBundledTheme.cs:101` 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 (21 lines × 2) src/MainDemo.Wpf/Domain/IconPackViewModel.cs:138— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:138-158 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:139-159 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (20 lines × 2) src/MainDemo.Wpf/Domain/IconPackViewModel.cs:17— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:17-36 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:18-37 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (20 lines × 2) src/MainDemo.Wpf/Domain/SlidersViewModel.cs:20— src/MainDemo.Wpf/Domain/SlidersViewModel.cs:20-39 | src/MaterialDesign3.Demo.Wpf/Domain/SlidersViewModel.cs:20-39 — before extracting anything, compare `src/MainDemo.Wpf/Domain/SlidersViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/SlidersViewModel.cs` as WHOLE FILES: 90% 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/MainDemo.Wpf/Domain/SlidersViewModel.cs:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) src/MaterialDesignThemes.Wpf/ResourceDictionaryExtensions.cs:172— src/MaterialDesignThemes.Wpf/ResourceDictionaryExtensions.cs:172-190 | src/MaterialDesignThemes.Wpf/ResourceDictionaryExtensions.cs:200-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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/MainDemo.Wpf/Domain/IconPackViewModel.cs:160— src/MainDemo.Wpf/Domain/IconPackViewModel.cs:160-178 | src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs:161-179 — before extracting anything, compare `src/MainDemo.Wpf/Domain/IconPackViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/IconPackViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (15 lines × 2) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:957— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:957-971 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:983-997 — both copies are in the same file, so extract the 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:957` 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:982` calls `FromHueAndChroma`, `SanitizeDegreesDouble` and `src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:956` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) src/MainDemo.Wpf/Domain/DialogsViewModel.cs:56— src/MainDemo.Wpf/Domain/DialogsViewModel.cs:56-70 | src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:61-75 — 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/MainDemo.Wpf/Domain/DialogsViewModel.cs:56` 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/MainDemo.Wpf/Domain/DialogsViewModel.cs:55` calls `WriteLine` and `src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.cs:60` 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.
Off the main sequence: MaterialDesignColors.Wpf(net462) src/MaterialDesignColors.Wpf/MaterialDesignColors.Wpf.csproj:1— MaterialDesignColors.Wpf(net462): abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: MaterialDesignThemes.Wpf(net462) src/MaterialDesignThemes.Wpf/MaterialDesignThemes.Wpf.csproj:1— MaterialDesignThemes.Wpf(net462): abstractness 0.04, instability 0.20, distance 0.76 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
DM12 · Ambient inputs in the domain· Domain type reads a global random source · ×2
Domain type reads a global random source: TreesViewModel src/MainDemo.Wpf/Domain/TreesViewModel.cs:231— `TreesViewModel` draws from `new Random(` inside `GenerateString`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it.
Domain type reads a global random source: TreesViewModel src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:215— `TreesViewModel` draws from `new Random(` inside `GenerateString`. The outcome is not a function of the inputs, so no test can assert which result this produces, and the same inputs replay differently. Take the randomness as a parameter — an injected `Random`, a seeded generator, or the already-chosen value — so a caller (and a test) can decide it.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×2
Owned disposable field is never released src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:16— `SnackbarMessageQueue` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_showMessageSemaphore` itself (line 16), which makes that instance its own. But `_showMessageSemaphore` is named in none of the methods the disposal search covered: `Dispose` (line 432) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_showMessageSemaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Owned disposable field is never released src/MaterialDesignThemes.Wpf/SnackbarMessageQueue.cs:38— `SnackbarMessageQueue` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_closeSnackbarEvent` itself (line 38), which makes that instance its own. But `_closeSnackbarEvent` is named in none of the methods the disposal search covered: `Dispose` (line 432) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_closeSnackbarEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
Swallowed exception (caught, then discarded) src/MainDemo.Wpf/Pickers.xaml.cs:28— `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/MaterialDesign3.Demo.Wpf/Pickers.xaml.cs:28— `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.
ColorSpec2021.GetTone (cyclomatic 50) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:775— ColorSpec2021.GetTone has cyclomatic complexity 50 (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.
ColorSpec2025.GetTone (cyclomatic 44) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1571— ColorSpec2025.GetTone has cyclomatic complexity 44 (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.
QuantizerWsMeans.Quantize (cyclomatic 32) src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWsmeans.cs:21— QuantizerWsMeans.Quantize has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FloatingHintTextBlockMarginConverter.Convert (cyclomatic 26) src/MaterialDesignThemes.Wpf/Converters/Internal/FloatingHintTextBlockMarginConverter.cs:10— FloatingHintTextBlockMarginConverter.Convert has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TabControlHeaderScrollBehavior.TabControlHeaderScrollBehavior.ctor (cyclomatic 21) src/MaterialDesignThemes.Wpf/Behaviors/Internal/TabControlHeaderScrollBehavior.cs:125— TabControlHeaderScrollBehavior.TabControlHeaderScrollBehavior.ctor has cyclomatic 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 5 function items inside it that branch (a function literal at line 134, a function literal at line 151, TryGetNextTabIndex, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PreviewIndicatorTransformXConverter.Convert (cyclomatic 19) src/MaterialDesignThemes.Wpf/RatingBar.cs:444— PreviewIndicatorTransformXConverter.Convert has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PreviewIndicatorTransformYConverter.Convert (cyclomatic 19) src/MaterialDesignThemes.Wpf/RatingBar.cs:494— PreviewIndicatorTransformYConverter.Convert has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TreeListView.ItemsChildrenChanged (cyclomatic 18) src/MaterialDesignThemes.Wpf/TreeListView.cs:118— TreeListView.ItemsChildrenChanged has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Score.ScoreColors (cyclomatic 18) src/MaterialDesign3.MaterialColorUtilities/Score/Score.cs:26— Score.ScoreColors 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.
DayOfWeekStyle.Parse (cyclomatic 17) src/MaterialDesignThemes.Wpf/CalendarFormatInfo.cs:257— DayOfWeekStyle.Parse has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item 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.
TreeListViewItemsCollection.ItemsSource_CollectionChanged (cyclomatic 17) src/MaterialDesignThemes.Wpf/Internal/TreeListViewItemsCollection.cs:248— TreeListViewItemsCollection.ItemsSource_CollectionChanged has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PopupBox.AnimateChildrenIn (cyclomatic 17) src/MaterialDesignThemes.Wpf/PopupBox.cs:647— PopupBox.AnimateChildrenIn 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.
IndexedItemOffsetMultiplierExtension.ProvideValue (cyclomatic 17) src/MaterialDesignThemes.Wpf/Transitions/IndexedItemOffsetMultiplierExtension.cs:23— IndexedItemOffsetMultiplierExtension.ProvideValue 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.
ArcSpline.GetPos (cyclomatic 17) src/MaterialDesign3.Motion/ArcSpline.cs:84— ArcSpline.GetPos 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.
FloatingHintMarginConverter.Convert (cyclomatic 16) src/MaterialDesignThemes.Wpf/Converters/FloatingHintMarginConverter.cs:12— FloatingHintMarginConverter.Convert has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DataGridAssist.ApplyMaterialDesignColumnStyleForColumn (cyclomatic 16) src/MaterialDesignThemes.Wpf/DataGridAssist.cs:243— DataGridAssist.ApplyMaterialDesignColumnStyleForColumn 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.
ColorSpec2025.PrimaryContainer.get (cyclomatic 16) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:567— ColorSpec2025.PrimaryContainer.get has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 572, 582, 588, …). 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.
ColorSpec2025.TertiaryContainer.get (cyclomatic 16) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:797— ColorSpec2025.TertiaryContainer.get has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 802, 829, 835, …). 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.
ColorSpec2021.GetTone (cognitive 92) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:775— ColorSpec2021.GetTone has cognitive complexity 92 (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.
ColorSpec2025.GetTone (cognitive 71) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1571— ColorSpec2025.GetTone has cognitive complexity 71 (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.
QuantizerWsMeans.Quantize (cognitive 61) src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWsmeans.cs:21— QuantizerWsMeans.Quantize has cognitive complexity 61 (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.
ArcSpline.GetPos (cognitive 37) src/MaterialDesign3.Motion/ArcSpline.cs:84— ArcSpline.GetPos has cognitive complexity 37 (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.
ColorAssist.EnsureContrastRatio (cognitive 35) src/MaterialDesignColors.Wpf/ColorManipulation/ColorAssist.cs:74— ColorAssist.EnsureContrastRatio 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.
Score.ScoreColors (cognitive 32) src/MaterialDesign3.MaterialColorUtilities/Score/Score.cs:26— Score.ScoreColors has cognitive complexity 32 (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.
ColorSpec2025.TertiaryContainer.get (cognitive 31) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:797— ColorSpec2025.TertiaryContainer.get has cognitive complexity 31 (threshold 15). None of this is in the body itself: all 31 points belong to 4 function literals inside it that branch (lines 802, 829, 835, …). 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.
TreeListView.ItemsChildrenChanged (cognitive 29) src/MaterialDesignThemes.Wpf/TreeListView.cs:118— TreeListView.ItemsChildrenChanged has cognitive complexity 29 (threshold 15). Of this number, 21 points are the body's own statements and 8 belong to one function item 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.
ColorSpec2025.OnSurface.get (cognitive 27) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:269— ColorSpec2025.OnSurface.get has cognitive complexity 27 (threshold 15). None of this is in the body itself: all 27 points belong to 5 function literals inside it that branch (lines 297, 283, 307, …). 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.
ColorSpec2025.Primary.get (cognitive 27) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:479— ColorSpec2025.Primary.get has cognitive complexity 27 (threshold 15). None of this is in the body itself: all 27 points belong to 4 function literals inside it that branch (lines 484, 516, 521, …). 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.
PopupBox.OnLostMouseCapture (cognitive 26) src/MaterialDesignThemes.Wpf/PopupBox.cs:759— PopupBox.OnLostMouseCapture has cognitive complexity 26 (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.
TreeListViewItemsCollection.ItemsSource_CollectionChanged (cognitive 23) src/MaterialDesignThemes.Wpf/Internal/TreeListViewItemsCollection.cs:248— TreeListViewItemsCollection.ItemsSource_CollectionChanged has cognitive complexity 23 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
DayOfWeekStyle.Parse (cognitive 22) src/MaterialDesignThemes.Wpf/CalendarFormatInfo.cs:257— DayOfWeekStyle.Parse has cognitive complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColorSpec2025.PrimaryContainer.get (cognitive 22) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:567— ColorSpec2025.PrimaryContainer.get has cognitive complexity 22 (threshold 15). None of this is in the body itself: all 22 points belong to 4 function literals inside it that branch (lines 572, 582, 588, …). 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.
DialogHost.IsOpenPropertyChangedCallback (cognitive 21) src/MaterialDesignThemes.Wpf/DialogHost.cs:348— DialogHost.IsOpenPropertyChangedCallback 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.
ResourceDictionaryExtensions.AdjustColors (cognitive 21) src/MaterialDesignThemes.Wpf/ResourceDictionaryExtensions.cs:166— ResourceDictionaryExtensions.AdjustColors has cognitive complexity 21 (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.
ColorSpec2025.OnSurfaceVariant.get (cognitive 21) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:335— ColorSpec2025.OnSurfaceVariant.get has cognitive complexity 21 (threshold 15). None of this is in the body itself: all 21 points belong to 3 function literals inside it that branch (lines 340, 350, 361). 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.
HctSolver.BisectToLimit (cognitive 21) src/MaterialDesign3.MaterialColorUtilities/Hct/HctSolver.cs:275— HctSolver.BisectToLimit 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.
TemperatureCache.GetAnalogousColors (cognitive 20) src/MaterialDesign3.MaterialColorUtilities/Temperature/TemperatureCache.cs:77— TemperatureCache.GetAnalogousColors has cognitive complexity 20 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MonoSpline.MonoSpline.ctor (cognitive 20) src/MaterialDesign3.Motion/MonoSpline.cs:9— MonoSpline.MonoSpline.ctor 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.
DataGridAssist.ApplyMaterialDesignColumnStyleForColumn (cognitive 19) src/MaterialDesignThemes.Wpf/DataGridAssist.cs:243— DataGridAssist.ApplyMaterialDesignColumnStyleForColumn has cognitive complexity 19 (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.
IndexedItemOffsetMultiplierExtension.ProvideValue (cognitive 19) src/MaterialDesignThemes.Wpf/Transitions/IndexedItemOffsetMultiplierExtension.cs:23— IndexedItemOffsetMultiplierExtension.ProvideValue 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.
ColorSpec2025.SurfaceContainerLow.get (cognitive 19) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:136— ColorSpec2025.SurfaceContainerLow.get has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 153, 141). 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. This shape REPEATS in the file: 2 other methods here (ColorSpec2025.SurfaceContainer.get, ColorSpec2025.SurfaceContainerHigh.get) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
ColorSpec2025.SurfaceContainer.get (cognitive 19) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:171— ColorSpec2025.SurfaceContainer.get has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 188, 176). 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. This shape REPEATS in the file: 2 other methods here (ColorSpec2025.SurfaceContainerLow.get, ColorSpec2025.SurfaceContainerHigh.get) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
ColorSpec2025.SurfaceContainerHigh.get (cognitive 19) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:206— ColorSpec2025.SurfaceContainerHigh.get has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 2 function literals inside it that branch (lines 223, 211). 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. This shape REPEATS in the file: 2 other methods here (ColorSpec2025.SurfaceContainerLow.get, ColorSpec2025.SurfaceContainer.get) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 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.
ColorSpec2025.Outline.get (cognitive 19) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:400— ColorSpec2025.Outline.get has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 405, 415, 426). 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. This shape REPEATS in the file: one other method here (ColorSpec2025.OutlineVariant.get) 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.
ColorSpec2025.OutlineVariant.get (cognitive 19) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:434— ColorSpec2025.OutlineVariant.get has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 3 function literals inside it that branch (lines 439, 449, 460). 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. This shape REPEATS in the file: one other method here (ColorSpec2025.Outline.get) 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.
ColorSpec2025.Tertiary.get (cognitive 18) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:732— ColorSpec2025.Tertiary.get has cognitive complexity 18 (threshold 15). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 737, 753, 758, …). 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.
QuantizerWu.CreateBoxes (cognitive 18) src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWu.cs:105— QuantizerWu.CreateBoxes 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.
ArcSpline.GetSlope (cognitive 17) src/MaterialDesign3.Motion/ArcSpline.cs:220— ArcSpline.GetSlope 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.
SpringEstimation.EstimateCriticallyDamped (cognitive 17) src/MaterialDesign3.Motion/SpringEstimation.cs:76— SpringEstimation.EstimateCriticallyDamped 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.
TabControlHeaderScrollBehavior.TabControlHeaderScrollBehavior.ctor (cognitive 16) src/MaterialDesignThemes.Wpf/Behaviors/Internal/TabControlHeaderScrollBehavior.cs:125— TabControlHeaderScrollBehavior.TabControlHeaderScrollBehavior.ctor has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 134, a function literal at line 151, TryGetNextTabIndex, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClearText.OnHandlesClearCommandChanged (cognitive 16) src/MaterialDesignThemes.Wpf/Internal/ClearText.cs:16— ClearText.OnHandlesClearCommandChanged has cognitive complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextBlockForegroundConverter.Convert (cognitive 16) src/MaterialDesignThemes.Wpf/RatingBar.cs:381— TextBlockForegroundConverter.Convert has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HctSolver.FindResultByJ (cognitive 16) src/MaterialDesign3.MaterialColorUtilities/Hct/HctSolver.cs:337— HctSolver.FindResultByJ 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.
KeyColor.Create (cognitive 16) src/MaterialDesign3.MaterialColorUtilities/Palettes/TonalPalette.cs:108— KeyColor.Create 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.
ArcSpline.GetSlope (cognitive 16) src/MaterialDesign3.Motion/ArcSpline.cs:178— ArcSpline.GetSlope 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· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:74— src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:74-114 | src/MaterialDesign3.MaterialColorUtilities/Scheme/Scheme.cs:117-157 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:61— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:61-86 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:92-117 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:137-166 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:172-201 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:207-236 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:242-264 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:270-321 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:336-367 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:401-429 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:435-463 — These 10 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 10 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 10 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:932— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:932-945 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:948-971 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:974-997 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1000-1013 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1016-1029 — 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 (73 lines × 2) src/MainDemo.Wpf/Domain/TreesViewModel.cs:121— src/MainDemo.Wpf/Domain/TreesViewModel.cs:121-193 | src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:107-179 — before extracting anything, compare `src/MainDemo.Wpf/Domain/TreesViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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/MainDemo.Wpf/Domain/TreesViewModel.cs:194` calls `Add` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:181` 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 (42–43 lines × 2) src/MainDemo.Wpf/MainWindow.xaml.cs:13— src/MainDemo.Wpf/MainWindow.xaml.cs:13-55 | src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.cs:14-55 — `src/MainDemo.Wpf/MainWindow.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.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 3 separate duplicated blocks between them, totalling at least 61 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 (37 lines × 2) src/MainDemo.Wpf/FieldsLineUp.xaml.cs:23— src/MainDemo.Wpf/FieldsLineUp.xaml.cs:23-59 | src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.cs:23-59 — `src/MainDemo.Wpf/FieldsLineUp.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/FieldsLineUp.xaml.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 3 separate duplicated blocks between them, totalling at least 76 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (33 lines × 2) src/MainDemo.Wpf/Domain/TreesViewModel.cs:197— src/MainDemo.Wpf/Domain/TreesViewModel.cs:197-229 | src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:181-213 — before extracting anything, compare `src/MainDemo.Wpf/Domain/TreesViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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/MainDemo.Wpf/Domain/TreesViewModel.cs:197` 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/MainDemo.Wpf/Domain/TreesViewModel.cs:194` calls `Add` and `src/MaterialDesign3.Demo.Wpf/Domain/TreesViewModel.cs:179` 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 (21–26 lines × 2) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:900— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:900-920 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1672-1697 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:900` 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. 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 (17 lines × 3) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:140— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:140-156 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:175-191 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:210-226 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 4) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:299— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:299-318 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:342-362 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:407-426 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:441-460 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:299` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/MaterialDesignThemes.Wpf/RatingBar.cs:446— src/MaterialDesignThemes.Wpf/RatingBar.cs:446-458 | src/MaterialDesignThemes.Wpf/RatingBar.cs:496-508 — both copies are in the same file, so extract the 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/MaterialDesignThemes.Wpf/RatingBar.cs:446` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/MainDemo.Wpf/Snackbars.xaml.cs:22— src/MainDemo.Wpf/Snackbars.xaml.cs:22-35 | src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.cs:22-35 — `src/MainDemo.Wpf/Snackbars.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/Snackbars.xaml.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 3 separate duplicated blocks between them, totalling at least 32 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 (11 lines × 3) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:64— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:64-74 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:95-105 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:245-255 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–13 lines × 2) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:873— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:873-883 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:1645-1657 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:873` 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 (11 lines × 5) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:75— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:75-85 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:106-116 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:155-165 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:190-200 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:225-235 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:75` 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. 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–10 lines × 3) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:514— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:514-523 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:638-647 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:751-759 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:514` 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 (7–10 lines × 2) src/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs:221— src/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs:221-230 | src/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs:253-259 — both copies are in the same file, so extract the 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/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs:221` 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 (9 lines × 3) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:937— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:937-945 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1005-1013 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1021-1029 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:937` 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 (8 lines × 7) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:152— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:152-159 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:187-194 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:222-229 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:296-303 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:339-346 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:404-411 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:438-445 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:152` 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 (6 lines × 4) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:936— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:936-941 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:952-957 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1004-1009 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:1020-1025 — 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:952` 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 (5 lines × 6) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:76— src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:76-80 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:107-111 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:156-160 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:191-195 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:226-230 | src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:255-259 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.cs:76` 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 (27 lines × 3) src/MahMaterialDragablzMashUp/AnotherCommandImplementation.cs:13— src/MahMaterialDragablzMashUp/AnotherCommandImplementation.cs:13-40 | src/MaterialDesign3.Demo.Wpf/Domain/AnotherCommandImplementation.cs:13-39 | src/MaterialDesignDemo.Shared/Domain/AnotherCommandImplementation.cs:13-39 — before extracting anything, compare `src/MahMaterialDragablzMashUp/AnotherCommandImplementation.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/AnotherCommandImplementation.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) src/MainDemo.Wpf/Domain/PaletteSelectorViewModel.cs:14— src/MainDemo.Wpf/Domain/PaletteSelectorViewModel.cs:14-39 | src/MaterialDesign3.Demo.Wpf/Domain/PaletteSelectorViewModel.cs:14-39 — before extracting anything, compare `src/MainDemo.Wpf/Domain/PaletteSelectorViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/PaletteSelectorViewModel.cs` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (32 lines × 2) src/MainDemo.Wpf/Domain/SelectableViewModel.cs:18— src/MainDemo.Wpf/Domain/SelectableViewModel.cs:18-61 | src/MaterialDesign3.Demo.Wpf/Domain/SelectableViewModel.cs:16-47 — before extracting anything, compare `src/MainDemo.Wpf/Domain/SelectableViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/SelectableViewModel.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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/MainDemo.Wpf/Domain/SelectableViewModel.cs:18` 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 (79 lines × 2) src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs:15— src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs:15-93 | src/MaterialDesignThemes.Wpf/NavigationRailAssist.cs:15-113 — before extracting anything, compare `src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs` and `src/MaterialDesignThemes.Wpf/NavigationRailAssist.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (29 lines × 3) src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs:15— src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs:15-93 | src/MaterialDesignThemes.Wpf/NavigationDrawerAssist.cs:15-43 | src/MaterialDesignThemes.Wpf/NavigationRailAssist.cs:15-113 — before extracting anything, compare `src/MaterialDesignThemes.Wpf/NavigationBarAssist.cs` and `src/MaterialDesignThemes.Wpf/NavigationRailAssist.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) src/MahMaterialDragablzMashUp/MainWindow.xaml.cs:17— src/MahMaterialDragablzMashUp/MainWindow.xaml.cs:17-28 | src/MainDemo.Wpf/MainWindow.xaml.cs:83-94 | src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.cs:86-97 — `src/MainDemo.Wpf/MainWindow.xaml.cs` and `src/MaterialDesign3.Demo.Wpf/MainWindow.xaml.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 3 separate duplicated blocks between them, totalling at least 61 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 × 3) src/MahMaterialDragablzMashUp/NotEmptyValidationRule.cs:8— src/MahMaterialDragablzMashUp/NotEmptyValidationRule.cs:8-12 | src/MainDemo.Wpf/Domain/NotEmptyValidationRule.cs:8-12 | src/MaterialDesign3.Demo.Wpf/Domain/NotEmptyValidationRule.cs:8-12 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 × 2) src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:53— src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:53-70 | src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs:53-70 — before extracting anything, compare `src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs` and `src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: this repository runs its tests on Microsoft.Testing.Platform (its global.json opts in), where coverage comes from a coverage extension the test project references — and none is wired up: no build file names `Microsoft.Testing.Extensions.CodeCoverage` or `coverlet.MTP`. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment. Add one of those PackageReferences to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
M1 · Documentation (README)· README may be stale · ×1
README may be stale — 51 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
Swallowed exception (empty catch) src/MaterialDesignThemes.Wpf/Converters/Internal/SliderToolTipConverter.cs:17— 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.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×1
Symbol treated as nullable, then dereferenced unguarded src/MaterialDesignThemes.Wpf/DataGridAssist.cs:404— This method contradicts itself about `dataGridCell`: line 399 writes `dataGridCell?.IsReadOnly`, which says `dataGridCell` can be null, but line 404 then dereferences it directly as `dataGridCell.Content` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `dataGridCell` truly cannot be null here, the `?.` is misleading. Settle it one way — test `dataGridCell` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Hct/HctSolver.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.Motion/ArcSpline.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWu.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/DynamicColor/DynamicColor.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MainDemo.Wpf/Domain/SmartHintViewModel.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/DynamicColor/MaterialDynamicColors.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/SmartHint.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Temperature/TemperatureCache.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Contrast/Contrast.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.Motion/SpringEstimation.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Utils/ColorUtils.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWsmeans.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.Motion/MonoSpline.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/DynamicColor/DynamicScheme.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/SplitButton.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MainDemo.Wpf/SmartHint.xaml.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Palettes/TonalPalette.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/PasswordBoxAssist.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Score/Score.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/Behaviors/PasswordBoxRevealTextBoxBehavior.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MainDemo.Wpf/Domain/TabsViewModel.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/Converters/Internal/FloatingHintTextBlockMarginConverter.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesignThemes.Wpf/BehaviorsAssist.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/MaterialDesign3.MaterialColorUtilities/Utils/MathUtils.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Commented-out code src/MainDemo.Wpf/App.xaml.cs:22— 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/MainDemo.Wpf/App.xaml.cs:23— 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/MainDemo.Wpf/App.xaml.cs:24— 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/MainDemo.Wpf/App.xaml.cs:25— 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/MainDemo.Wpf/App.xaml.cs:30— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/MainDemo.Wpf/App.xaml.cs:41— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/MainDemo.Wpf/Dialogs.xaml.cs:21— 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/MainDemo.Wpf/Dialogs.xaml.cs:35— 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/MainDemo.Wpf/Dialogs.xaml.cs:60— 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/MaterialDesign3.Demo.Wpf/App.xaml.cs:22— 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/MaterialDesign3.Demo.Wpf/App.xaml.cs:23— 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/MaterialDesign3.Demo.Wpf/App.xaml.cs:24— 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/MaterialDesign3.Demo.Wpf/App.xaml.cs:25— 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/MaterialDesign3.Demo.Wpf/App.xaml.cs:30— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/MaterialDesign3.Demo.Wpf/App.xaml.cs:41— 4 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:21— 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/MaterialDesign3.Demo.Wpf/Dialogs.xaml.cs:43— 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/MaterialDesignThemes.Wpf/DataGridComboBoxColumn.cs:107— 12 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
Commented-out code src/MaterialDesignThemes.Wpf/PopupEx.cs:169— 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/MaterialDesignThemes.Wpf/TimePicker.cs:211— 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/MaterialDesignThemes.Wpf/TimePicker.cs:356— 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/MaterialDesignThemes.Wpf/TimePicker.cs:357— 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/MaterialDesignThemes.Wpf/TimePicker.cs:552— 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/MaterialDesignThemes.Wpf/TimePicker.cs:569— 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/MaterialDesignThemes.Wpf/TreeHelper.cs:56— 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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:911— `Contrast.RatioOfTones(upper, answer) >= desiredRatio && Contrast.RatioOfTones(lower, answer) >= desiredRatio` appears character-identically in 2 files — src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.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/MainDemo.Wpf/Buttons.xaml.cs:25— `CountingBadge.Badge == null || Equals(CountingBadge.Badge, string.Empty)` appears character-identically in 2 files — src/MainDemo.Wpf/Buttons.xaml.cs, src/MaterialDesign3.Demo.Wpf/Buttons.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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:917— `DynamicColor.TonePrefersLightForeground(bgTone1) || DynamicColor.TonePrefersLightForeground(bgTone2)` appears character-identically in 2 files — src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.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/MainDemo.Wpf/Pickers.xaml.cs:90— `Equals(eventArgs.Parameter, "1") && CombinedCalendar.SelectedDate is DateTime selectedDate` appears character-identically in 2 files — src/MainDemo.Wpf/Pickers.xaml.cs, src/MaterialDesign3.Demo.Wpf/Pickers.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/MainDemo.Wpf/Domain/DemoItem.cs:50— `_dataContext != null && content is FrameworkElement element` appears character-identically in 2 files — src/MainDemo.Wpf/Domain/DemoItem.cs, src/MaterialDesign3.Demo.Wpf/Domain/DemoItem.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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:878— `color.background == null || color.background(scheme) == null || color.contrastCurve == null || color.contrastCurve(scheme) == null` appears character-identically in 2 files — src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.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/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs:903— `color.secondBackground == null || color.secondBackground(scheme) == null` appears character-identically in 2 files — src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2021.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec2025.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/MainDemo.Wpf/Domain/DialogsViewModel.cs:56— `eventArgs.Parameter is bool parameter && parameter == false` appears character-identically in 2 files — src/MainDemo.Wpf/Domain/DialogsViewModel.cs, src/MaterialDesign3.Demo.Wpf/Domain/DialogsViewModel.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/web/jsx/PaletteBuilder.js:142— `this.state.generatedFrom.primaryColorIndices.indexOf(colorIndex) > -1 && isChecked` appears character-identically in 2 files — src/web/jsx/PaletteBuilder.js, src/web/scripts/PaletteBuilder.js. 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/MaterialDesignThemes.Wpf/Converters/Internal/TabControlNavButtonVisibilityConverter.cs:27— `sourceType == typeof(string) || base.CanConvertFrom(context, sourceType)` appears character-identically in 2 files — src/MaterialDesignThemes.Wpf/Converters/Internal/TabControlNavButtonVisibilityConverter.cs, src/MaterialDesignThemes.Wpf/Converters/SnackbarMessageTypeConverter.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/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs:83— `theme is Theme internalTheme && internalTheme.ColorAdjustment != null` appears character-identically in 2 files — src/MainDemo.Wpf/Domain/ThemeSettingsViewModel.cs, src/MaterialDesign3.Demo.Wpf/Domain/ThemeSettingsViewModel.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/MainDemo.Wpf/Domain/Link.cs:10— `url is not null && RuntimeInformation.IsOSPlatform(OSPlatform.Windows)` appears character-identically in 2 files — src/MainDemo.Wpf/Domain/Link.cs, src/MaterialDesign3.Demo.Wpf/Domain/Link.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/MaterialDesignThemes.Wpf/Converters/ElevationMarginConverter.cs:11— `value is Elevation elevation && elevation != Elevation.Dp0` appears character-identically in 2 files — src/MaterialDesignThemes.Wpf/Converters/ElevationMarginConverter.cs, src/MaterialDesignThemes.Wpf/Converters/ElevationRadiusConverter.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/MainDemo.Wpf/FieldsLineUp.xaml.cs:14— `value is string errorMessage && !string.IsNullOrWhiteSpace(errorMessage)` appears character-identically in 2 files — src/MainDemo.Wpf/FieldsLineUp.xaml.cs, src/MaterialDesign3.Demo.Wpf/FieldsLineUp.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.
Silent fallback default in catch src/MaterialDesignThemes.Wpf/Converters/MathConverter.cs:33— `Convert` swallows `FormatException` into `return Binding.DoNothing;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/MaterialDesignThemes.Wpf/PopupEx.cs:320— `Equals` swallows `InvalidCastException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Fat interface: ColorSpec (100 members) src/MaterialDesign3.MaterialColorUtilities/DynamicColor/ColorSpec.cs:3— `ColorSpec` declares 100 members: `PrimaryPaletteKeyColor`, `SecondaryPaletteKeyColor`, `TertiaryPaletteKeyColor`, `NeutralPaletteKeyColor`, `NeutralVariantPaletteKeyColor`, `ErrorPaletteKeyColor`, `WarningHighPaletteKeyColor`, `WarningLowPaletteKeyColor`, `InformationPaletteKeyColor`, `SafePaletteKeyColor`, `Background`, `OnBackground`, `Surface`, `SurfaceDim`, `SurfaceBright`, `SurfaceContainerLowest`, `SurfaceContainerLow`, `SurfaceContainer`, `SurfaceContainerHigh`, `SurfaceContainerHighest`, `OnSurface`, `SurfaceVariant`, `OnSurfaceVariant`, `InverseSurface`, `InverseOnSurface`, `Outline`, `OutlineVariant`, `Shadow`, `Scrim`, `SurfaceTint`, `Primary`, `PrimaryDim`, `OnPrimary`, `PrimaryContainer`, `OnPrimaryContainer`, `InversePrimary`, `Secondary`, `SecondaryDim`, `OnSecondary`, `SecondaryContainer`, and 60 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 3 significant file(s) lose their only recent owner: src/MaterialDesignThemes.Wpf/DrawerHost.cs, src/MaterialDesignThemes.Wpf/NavigationRailAssist.cs, src/MainDemo.Wpf/Domain/ListsAndGridsViewModel.cs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (10 single-owned of 167 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 167 of the 593 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/MaterialDesignThemes.Wpf/PackIconDataFactory.cs, src/MaterialDesignThemes.Wpf/PackIconKind.cs, src/MaterialDesignThemes.Wpf/DialogSession.cs, src/MaterialDesignThemes.Wpf/Internal/VisualStateMonitor.cs, src/MaterialDesignThemes.Wpf/Behaviors/Internal/TabControlHeaderScrollBehavior.cs, src/MaterialDesignThemes.Wpf/ColorPicker.cs.
Documentation: no project overview README.md— The opening paragraph lists features (Material Design styles for Framework controls, Multi Action Button, Cards, Dialogs, Clock; easy palette configuration per design and runtime) but does not state what the project is or what it does overall. Add a one-line overview sentence stating that this toolkit provides Material Design themes and control components optimized for WPF desktop applications.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 14 project(s) overshoot their size bounds, lowering Project Cohesion to 8.6/10. The most over is `MaterialDesignThemes.Wpf(net462)` (39956 LoC, 276 public types across 10 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 42 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: src/MaterialDesign3.MaterialColorUtilities/Hct/HctSolver.cs, src/MainDemo.Wpf/Domain/SmartHintViewModel.cs, src/MaterialDesign3.Motion/ArcSpline.cs, src/MaterialDesign3.MaterialColorUtilities/Quantize/QuantizerWu.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/DynamicColor.cs, src/MaterialDesign3.MaterialColorUtilities/Hct/Cam16.cs, src/MaterialDesign3.MaterialColorUtilities/DynamicColor/MaterialDynamicColors.cs, src/MaterialDesignThemes.Wpf/SmartHint.cs (and 34 more) (44 orphaned of 167 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 167 of the 593 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×1
Placeholder data left in code src/MainDemo.Wpf/Domain/TabsViewModel.cs:13— A placeholder value ("
Lorem ipsum dolor sit amet, consectetur…") is still in shipped code — sample/mock data that was never replaced with the real thing.
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.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
README/code drift README.md:188— README.md links to `src/web/images/screen-md2/expander.png`, but `src/web/images/screen-md2/expander.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 1215/1440 types (84%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 125 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
No SAST — 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 24285 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 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.)
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 0/27 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.6 `!` suppressions per 1k syntax nodes — 162 suppression(s) across the 284999 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Skipped (documented): PasswordBox_WithRevealedPassword_RespectsKeyboardTabNavigation tests/MaterialDesignThemes.UITests/WPF/PasswordBoxes/PasswordBoxTests.cs:272— Skipped with a documented reason — a deferral, not lazy debt: Ignoring until I can figure out why this doesn't work on the GitHub Actions runner
Skipped (documented): NumericUpDown_ValueSetGreaterThanMaximum_CoercesToMaximum tests/MaterialDesignThemes.UITests/WPF/UpDownControls/NumericUpDownTests.cs:141— Skipped with a documented reason — a deferral, not lazy debt: Needs XAMLTest 1.2.3 or later
Skipped (documented): DraggingTheThumbChangesSaturation tests/MaterialDesignThemes.Wpf.Tests/ColorPickerTests.cs:146— Skipped with a documented reason — a deferral, not lazy debt: This test never entered the while loop before the MTP conversion
Outdated: TUnit — TUnit 1.72.10 → 1.76.0 available (referenced by MaterialDesignColors.Wpf.Tests).
Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.10.1 → 18.11.0 available (referenced by MaterialDesignThemes.UITests).
Outdated: System.CommandLine — System.CommandLine 2.0.12 → 2.0.13 available (referenced by MaterialDesignDemo).
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 20 file(s) — `src/MainDemo.Wpf/Domain/MainWindowViewModel.cs`, `src/MainDemo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/MainWindowViewModel.cs`, `src/MaterialDesign3.Demo.Wpf/Domain/QuickSearchDialogViewModel.cs`, `src/MaterialDesignColors.Wpf/ColorPair.cs`, … (+15 more) — 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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a1677f-b040-7cd2-9618-62d3e98d9f2e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 58 · Warnings: 325 · Recommendations: 114 · Info: 16 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 06:43 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.