Public report of HandyOrg/HandyControl, 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, 10:07 UTC · Survey ID cd_0d2c1f0bb072493d98005c97f3ad32de
HandyOrg/HandyControl
Measured 23 October 2026, 10:02 UTC, at code version e9ad3d7
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.
Test distribution is not measured: No automated tests.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 72,037 lines of product code in 67 projects, tests not counted · Estimated rebuild effort: about 0.9 person-years · Weakest lens: Security and Compliance, 36
Findings by how serious they are
80 critical252 serious81 minor
7 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, 10:02 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 ▸
70of 74 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.
391of 413 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
74dimensions across 6 lenses, read from 72,037 lines of product code in 67 projects.
HandyOrg/HandyControl scores 42 out of 100 and is rated Weak, while four of its six lenses score higher still: Architecture at 92, Performance at 70 and Maturity at 52, all rated Adequate, and Code Health at 49, rated Weak.
The score is lower than those four because the weakest lens counts most, and here that is Security and Compliance, which scores 36 and is rated Weak. Its Supply-chain Provenance & Signing dimension scores 0 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 automated tests finding(s) in Code Coverage and to resolve the 1 No tests found finding(s) in Test Distribution, and if Security and Compliance rose to 70, the score would rise from 42 to about 48.
80 findings are critical: 50 in Explicit Debt, 17 in Static Analysis (SAST), eight in Secrets (history), two in Incompleteness & stubs, one in Code Coverage, one in Project dependency cycles and one in REDACTED Scanning.
Watchdog couldn't measure Dependency Hygiene, 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 72,037 lines, which would take an estimated 0.9 person-years, around €120,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Exception handling · Swallowed exception (caught, then discarded) src/Shared/Microsoft.Windows.Shell/Standard/Win32Error.cs
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: 16 findings
These 16 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.
Coupling · Off the main sequence: HandyControlDemo_Code(netcoreapp3.0)
Coupling · Off the main sequence: HandyControl_Net_GE45(netcoreapp3.0)
Coupling · Off the main sequence: HandyControl_Net_40
Coupling · Off the main sequence: HandyControl_Avalonia
Supply-chain Provenance & Signing REDACTED
Documentation (README) · README may be stale
Cancellation propagation · Async method without CancellationToken: ShowInteractiveDialog src/Shared/HandyControlDemo_Shared/ViewModel/Controls/DialogDemoViewModel.cs
Cancellation propagation · Async method without CancellationToken: SwitchImage src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs
Exception handling · Swallowed exception (caught, then discarded) src/Shared/HandyControl_Shared/Tools/Extension/StringExtension.cs
Exception handling · Swallowed exception (caught, then discarded) src/Shared/HandyControl_Shared/Tools/Extension/StringExtension.cs
Exception handling · Swallowed exception (caught, then discarded) src/Shared/HandyControl_Shared/Controls/Image/ImageViewer.cs
Exception handling · Swallowed exception (caught, then discarded) src/Shared/HandyControl_Shared/Tools/Converter/Color2ChannelAConverter.cs
Exception handling · Swallowed exception (caught, then discarded) src/Shared/HandyControlDemo_Shared/Tools/Helper/AssemblyHelper.cs
Exception handling · Swallowed exception (caught, then discarded) src/Avalonia/HandyControlDemo_Avalonia/Tools/Converter/StringToBitmapConverter.cs
Exception handling · Swallowed exception (caught, then discarded) src/Avalonia/HandyControlDemo_Avalonia/Tools/Helper/AssemblyHelper.cs
Rebuild cost: about €120,000 · Estimate
Cost to rebuild
€41,000 to €210,000, for 679 to 2,193 hours of work, about 0.9 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 42. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 72,037 lines of product code
Comment lines
The estimate prices 68,145 lines. Comment lines count towards the size of 72,037 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 automated tests finding(s) in Code Coverage.
Raises the score by about 5 points · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
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 €120,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 36 (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 automated tests finding(s) in Code Coverage. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Code Coverage findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
38 modules, with 36 dependencies between them. One loop runs through 4 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.
HandyControl.Data uses HandyControl.Tools.Interop, so a change to HandyControl.Tools.Interop can break HandyControl.Data, while a change to HandyControl.Data can't break HandyControl.Tools.Interop.
Position
Below the diagonal: HandyControl.Data uses a module listed above it, which is the healthy direction.
20→31 HandyControl.Data uses HandyControl.Controlspart of a loop✕
Connections
3 pairs of types, where a type in HandyControl.Data uses a type in HandyControl.Controls.
HandyControl.Data uses HandyControl.Controls, so a change to HandyControl.Controls can break HandyControl.Data, while a change to HandyControl.Data can't break HandyControl.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
HandyControl.Expression.Media uses HandyControl.Expression.Drawing, so a change to HandyControl.Expression.Drawing can break HandyControl.Expression.Media, while a change to HandyControl.Expression.Media can't break HandyControl.Expression.Drawing.
Position
Below the diagonal: HandyControl.Expression.Media uses a module listed above it, which is the healthy direction.
Microsoft.Windows.Shell uses Standard, so a change to Standard can break Microsoft.Windows.Shell, while a change to Microsoft.Windows.Shell can't break Standard.
Position
Below the diagonal: Microsoft.Windows.Shell uses a module listed above it, which is the healthy direction.
HandyControl.Expression.Shapes uses HandyControl.Expression.Media, so a change to HandyControl.Expression.Media can break HandyControl.Expression.Shapes, while a change to HandyControl.Expression.Shapes can't break HandyControl.Expression.Media.
Position
Below the diagonal: HandyControl.Expression.Shapes uses a module listed above it, which is the healthy direction.
HandyControl.Themes uses HandyControl.Data, so a change to HandyControl.Data can break HandyControl.Themes, while a change to HandyControl.Themes can't break HandyControl.Data.
Position
Below the diagonal: HandyControl.Themes uses a module listed above it, which is the healthy direction.
HandyControl.Tools uses HandyControl.Tools.Interop, so a change to HandyControl.Tools.Interop can break HandyControl.Tools, while a change to HandyControl.Tools can't break HandyControl.Tools.Interop.
Position
Below the diagonal: HandyControl.Tools uses a module listed above it, which is the healthy direction.
HandyControl.Tools uses HandyControl.Data, so a change to HandyControl.Data can break HandyControl.Tools, while a change to HandyControl.Tools can't break HandyControl.Data.
Position
Below the diagonal: HandyControl.Tools uses a module listed above it, which is the healthy direction.
25→31 HandyControl.Tools uses HandyControl.Controlspart of a loop✕
Connections
4 pairs of types, where a type in HandyControl.Tools uses a type in HandyControl.Controls.
HandyControl.Tools uses HandyControl.Controls, so a change to HandyControl.Controls can break HandyControl.Tools, while a change to HandyControl.Tools can't break HandyControl.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
HandyControl.Tools.Extension uses HandyControl.Data, so a change to HandyControl.Data can break HandyControl.Tools.Extension, while a change to HandyControl.Tools.Extension can't break HandyControl.Data.
Position
Below the diagonal: HandyControl.Tools.Extension uses a module listed above it, which is the healthy direction.
26→31 HandyControl.Tools.Extension uses HandyControl.Controlspart of a loop✕
Connections
1 pair of types, where a type in HandyControl.Tools.Extension uses a type in HandyControl.Controls.
HandyControl.Tools.Extension uses HandyControl.Controls, so a change to HandyControl.Controls can break HandyControl.Tools.Extension, while a change to HandyControl.Tools.Extension can't break HandyControl.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
HandyControl.Tools.Helper uses HandyControl.Tools.Interop, so a change to HandyControl.Tools.Interop can break HandyControl.Tools.Helper, while a change to HandyControl.Tools.Helper can't break HandyControl.Tools.Interop.
Position
Below the diagonal: HandyControl.Tools.Helper uses a module listed above it, which is the healthy direction.
HandyControl.Tools.Helper uses HandyControl.Data, so a change to HandyControl.Data can break HandyControl.Tools.Helper, while a change to HandyControl.Tools.Helper can't break HandyControl.Data.
Position
Below the diagonal: HandyControl.Tools.Helper uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in HandyControlDemo uses a type in HandyControl.Data.
The types involved
HandyControlDemo.App → HandyControl.Data.SkinType
Direction
HandyControlDemo uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo, while a change to HandyControlDemo can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo uses a module listed above it, which is the healthy direction.
HandyControlDemo.Data uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo.Data, while a change to HandyControlDemo.Data can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo.Data uses a module listed above it, which is the healthy direction.
HandyControlDemo.Tools uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo.Tools, while a change to HandyControlDemo.Tools can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo.Tools uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Data.Enum, so a change to HandyControl.Data.Enum can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Data.Enum.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Interactivity, so a change to HandyControl.Interactivity can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Interactivity.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Tools.Interop, so a change to HandyControl.Tools.Interop can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Tools.Interop.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
60 pairs of types, where a type in HandyControl.Controls uses a type in HandyControl.Data. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
HandyControl.Controls uses HandyControl.Data, so a change to HandyControl.Data can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Data.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Expression.Shapes, so a change to HandyControl.Expression.Shapes can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Expression.Shapes.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Tools, so a change to HandyControl.Tools can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Tools.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Controls uses HandyControl.Tools.Extension, so a change to HandyControl.Tools.Extension can break HandyControl.Controls, while a change to HandyControl.Controls can't break HandyControl.Tools.Extension.
Position
Below the diagonal: HandyControl.Controls uses a module listed above it, which is the healthy direction.
HandyControl.Tools.Converter uses HandyControl.Tools.Extension, so a change to HandyControl.Tools.Extension can break HandyControl.Tools.Converter, while a change to HandyControl.Tools.Converter can't break HandyControl.Tools.Extension.
Position
Below the diagonal: HandyControl.Tools.Converter uses a module listed above it, which is the healthy direction.
HandyControlDemo.Resources uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo.Resources, while a change to HandyControlDemo.Resources can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo.Resources uses a module listed above it, which is the healthy direction.
HandyControlDemo.Resources uses HandyControl.Themes, so a change to HandyControl.Themes can break HandyControlDemo.Resources, while a change to HandyControlDemo.Resources can't break HandyControl.Themes.
Position
Below the diagonal: HandyControlDemo.Resources uses a module listed above it, which is the healthy direction.
HandyControlDemo.Service uses HandyControlDemo.Data, so a change to HandyControlDemo.Data can break HandyControlDemo.Service, while a change to HandyControlDemo.Service can't break HandyControlDemo.Data.
Position
Below the diagonal: HandyControlDemo.Service uses a module listed above it, which is the healthy direction.
HandyControlDemo.Tools.Converter uses HandyControl.Tools, so a change to HandyControl.Tools can break HandyControlDemo.Tools.Converter, while a change to HandyControlDemo.Tools.Converter can't break HandyControl.Tools.
Position
Below the diagonal: HandyControlDemo.Tools.Converter uses a module listed above it, which is the healthy direction.
HandyControlDemo.Tools.Extension uses HandyControl.Tools.Extension, so a change to HandyControl.Tools.Extension can break HandyControlDemo.Tools.Extension, while a change to HandyControlDemo.Tools.Extension can't break HandyControl.Tools.Extension.
Position
Below the diagonal: HandyControlDemo.Tools.Extension uses a module listed above it, which is the healthy direction.
HandyControlDemo.UserControl uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo.UserControl, while a change to HandyControlDemo.UserControl can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo.UserControl uses a module listed above it, which is the healthy direction.
HandyControlDemo.UserControl uses HandyControlDemo.Data, so a change to HandyControlDemo.Data can break HandyControlDemo.UserControl, while a change to HandyControlDemo.UserControl can't break HandyControlDemo.Data.
Position
Below the diagonal: HandyControlDemo.UserControl uses a module listed above it, which is the healthy direction.
HandyControlDemo.ViewModel uses HandyControl.Collections, so a change to HandyControl.Collections can break HandyControlDemo.ViewModel, while a change to HandyControlDemo.ViewModel can't break HandyControl.Collections.
Position
Below the diagonal: HandyControlDemo.ViewModel uses a module listed above it, which is the healthy direction.
HandyControlDemo.ViewModel uses HandyControl.Data, so a change to HandyControl.Data can break HandyControlDemo.ViewModel, while a change to HandyControlDemo.ViewModel can't break HandyControl.Data.
Position
Below the diagonal: HandyControlDemo.ViewModel uses a module listed above it, which is the healthy direction.
HandyControlDemo.ViewModel uses HandyControl.Tools.Extension, so a change to HandyControl.Tools.Extension can break HandyControlDemo.ViewModel, while a change to HandyControlDemo.ViewModel can't break HandyControl.Tools.Extension.
Position
Below the diagonal: HandyControlDemo.ViewModel uses a module listed above it, which is the healthy direction.
HandyControlDemo.ViewModel uses HandyControlDemo.Data, so a change to HandyControlDemo.Data can break HandyControlDemo.ViewModel, while a change to HandyControlDemo.ViewModel can't break HandyControlDemo.Data.
Position
Below the diagonal: HandyControlDemo.ViewModel uses a module listed above it, which is the healthy direction.
HandyControlDemo.ViewModel uses HandyControlDemo.Service, so a change to HandyControlDemo.Service can break HandyControlDemo.ViewModel, while a change to HandyControlDemo.ViewModel can't break HandyControlDemo.Service.
Position
Below the diagonal: HandyControlDemo.ViewModel uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49% · Weak · gated by X3 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
19
High / Critical
A03:2025 — Software Supply Chain Failures
11
Medium
A07:2025 — Authentication Failures
10
High / Critical
Roadmap
Immediately encrypt sensitive data at rest and manage keys in a vault, while resolving the leaked secret in REDACTED. Upgrade the two end-of-life runtimes in the project files and ensure all code is covered by automated tests to eliminate gaps in test distribution and coverage.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 80
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 — 252
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 — 81
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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. 70 of 74 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.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 74 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, 391 of 413 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: error: The imported file "$(MSBuildExtensionsPath32)/Microsoft/VisualStudio/v$(VisualStudioVersion)/CodeSharing/Microsoft.CodeSharing.Common.Default.props" does not exist and appears to be part of a Visual Studio component. This file may require MSBuild.exe in order to be imported successfully, and ….
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — 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. Single-maintainer repository — bus factor is not applicable (50 contributor(s) across 2130 commit(s) sampled, automation and bot accounts excluded). One of them holds 85% of the history; the other 49 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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/Net_GE45/HandyControl_Net_GE45/HandyControl_Net_GE45.csproj' with message: Unknown build error, 'Could not find assembly 'mscorlib, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'. Either explicitly load this assembly using a method such as LoadFromAssemblyPath() or use a MetadataAssem….
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. `dotnet build` reported 3 error(s), and the diagnostics it printed were: MSB4019: The imported project "/root/.nuget/packages/microsoft.vssdk.buildtools/17.0.5232/tools/VSSDK/Microsoft.VsSDK.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/VSSDK/Microsoft.VsSDK.targets", which evaluated to "/root/.nuget/packages/microsoft.vssdk.buildtools/17.0.5232/build/../tools/VSSDK/Microsoft.VsSDK.targets", is correct, and that the file exists on disk.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/VSSDK/Microsoft.VsSDK.targets" was not found. Confirm that the expression in the Import declaration "$(VSToolsPath)/VSSDK/Microsoft.VsSDK.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/VisualStudio/v18.0/VSSDK/Microsoft.VsSDK.targets", is correct, and that the file exists on disk.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
D18 Solution Shape — measured, with a gap in what it reached — 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 scored solution `src/HandyControl.sln`, `extension/visual studio/HandyControl_VS_Templates.sln` is not representative of this repository — it references only 321 of 1102 discovered C# files (29 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. You can widen what we reach: point the scan at the product solution, or scan its directory directly, so the whole codebase is analyzed rather than a build-tooling sub-solution.
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 (70,241 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/Shared/HandyControlDemo_Shared/Data/DemoInfo.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.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
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. `extension/visual studio/WpfApp/App.xaml.cs`, `extension/visual studio/WpfApp/MainWindow.xaml.cs`, `extension/visual studio/WpfCoreApp/App.xaml.cs`, `extension/visual studio/WpfCoreApp/MainWindow.xaml.cs`, `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannonContainer.cs`, … (+6 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 own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. 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: a native UI project (extension/visual studio/WpfApp/MainWindow.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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.
28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Graph.MeasureChild at 53. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Gdip.StatusException at 22 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs (Gdip.StatusException at 22), src/Shared/HandyControl_Shared/Controls/PropertyGrid/PropertyResolver.cs (PropertyResolver.CreateDefaultEditor at 20), src/Shared/HandyControl_Shared/Controls/Block/ToggleBlock.cs (ToggleBlock.OnMouseDown at 16). 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.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Graph.MeasureChild (cyclomatic 53), FlexPanel.ArrangeOverride (cyclomatic 41), FlexPanel.ArrangeLine (cyclomatic 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 28 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 74 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cognitive Complexity — start with DashedBorder.OnRender (cognitive 120), Graph.MeasureChild (cognitive 82), FlexPanel.ArrangeOverride (cognitive 79). — 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 6 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 13 TooManyMethods finding(s) in God Classes — start with NativeMethods.cs, InteropMethods.cs, Growl.cs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 6 FileTooLong finding(s) in God Classes — start with InteropValues.cs, ExtendedVisualStateManager.cs, NativeMethods.cs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 MethodTooLong finding(s) in God Classes — start with FlexPanel.cs (4), DashedBorder.cs (2). — One of this dimension's main actionable groups (6 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.
51 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 21 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GPStream.cs (6), FlexPanel.cs, UniformSpacingPanel.cs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MouseDragElementBehaviorEx.cs (2), SearchBar.cs (2), Drawer.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with PathSegmentHelper.cs (2), FullScreenHelper.cs, GPStream.cs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with SystemParameters2.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ 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.
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.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 240 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 222 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
428 deducted debt markers + unmeasured dead symbols across 70241 LoC in the .NET projects (2.0/KLoC) → score 6.1. 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 22 EmptyCatchBlock finding(s) in Explicit Debt — start with GifImage.cs (6), Utility.cs (2), EventTriggerBase.cs (2). — One of this dimension's main actionable groups (22 issue-level).
Resolve the 21 NoWarnInCsproj finding(s) in Explicit Debt — start with HandyControlDemo_Avalonia.csproj (6), HandyControl_Net_40.csproj (5), HandyControlDemo_Net_GE45.csproj (4). — One of this dimension's main actionable groups (21 issue-level).
Resolve the 7 WriteOnlyPrivateField finding(s) in Explicit Debt — start with InteropMethods.cs (3), PKEY.cs (2), GlowEdge.cs. — One of this dimension's main actionable groups (7 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the 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.
67 projects, 12726 source files, 70241 hand-written lines of code (70241 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 5115 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 41 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.) Measured across 2 solutions loaded as one workspace: `src/HandyControl.sln`, `extension/visual studio/HandyControl_VS_Templates.sln`.
Thin analysable surface across projects: HandyControl_VS_Templates · ×4extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj
✓ On the Gold path — maintain.
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: 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 a well-written English-facing project overview with an excellent Chinese translation (README-cn.md), a strong branding section showing the Nuget, myget, GitHub build status badges, and links to the blogroll and Slack community. The accompanying architecture/Docs markdown files are comprehensive: 161 documents covering every tier of documentation for the repository plus the NexT theme docs, making this an extremely well-structured single-document set. The README itself is a clear overview (HandyControl — WPF control library that rewrites native styles and contains 80+ custom controls) with installation, usage, contribution guidance, and links to the Chinese documentation; it is not the root README but its own document, so no defect falls under the repository-wide categories. The only unstructured element is a single draft.md scaffold file (title-only), which does not affect quality.
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.
Resolve the 2 redundant comment finding(s) in Comment Value — start with ExtendedVisualStateManager.cs, InteropValues.cs. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
6 of 12 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
19 finding(s): 0 critical, 17 high, 2 medium, 0 low. 11 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 12 file(s) — `doc/themes/next/languages/zh-CN.yml`, `extension/visual studio/WpfApp/App.xaml.cs` (line 1), `extension/visual studio/WpfApp/MainWindow.xaml.cs` (line 1), `extension/visual studio/WpfCoreApp/App.xaml.cs` (line 1), `extension/visual studio/WpfCoreApp/MainWindow.xaml.cs` (line 1), … (+7 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 3 of those file(s) — `src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs`, `src/Shared/HandyControl_Shared/Controls/Other/VisualAdornerContainer.cs`, `src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs` — 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. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
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).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 11 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 (11 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 any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 47 of the 188 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change coupling finding(s) in Change Coupling — start with DateTimePicker.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 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 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
2 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 2 End-of-life runtime finding(s) in Platform End-of-Life — start with ProjectTemplate.csproj, HandyControl_Net_40.csproj. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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 HandyControl.Controls ↔ HandyControl.Data ↔ HandyControl.Tools ↔ HandyControl.Tools.Extension depend on each other. The lightest dependency in the cycle is HandyControl.Controls → HandyControl.Tools.Extension (HandyControl.Controls.Col → HandyControl.Tools.Extension.ColLayout, 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/Shared/HandyControl_Shared/Controls/Panel/Grid/Col.cs:5
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
C1 · Data Protection0.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:907, src/Avalonia/HandyControl_Avalonia/Tools/Converter/CornerRadiusSplitConverter.cs:35, src/Avalonia/HandyControl_Avalonia/Tools/Converter/DoubleExpandConverter.cs:24
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.
`NotImplemented` is a shipped member whose body only throws — and it is REACHED: src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:60 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:123
`NotImplemented` is a shipped member whose body only throws — and it is REACHED: src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:855 references it (2 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:907
`Main` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/Shared/HandyControlDemo_Code/DemoHelper.cs:7
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Shared/HandyControlDemo_Shared/App.xaml.cs:40
`GetDC` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/Shared/Microsoft.Windows.Shell/Standard/NativeMethods.cs:359
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 10 of 10 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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 3/12 projects share a common root namespace — the code's module identity is inconsistent.
What to do
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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.
doc/themes/next/README.md changes into `themes/next`, but no such folder exists. 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. — doc/themes/next/README.md:75
doc/themes/next/README.md installs `hexo-util` (`npm install --save-dev hexo-util`), but no package.json declares it. 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. — doc/themes/next/README.md:89
What to do
Reconcile the README with reality: doc/themes/next/README.md changes into `themes/next`, but no such folder exists; doc/themes/next/README.md installs `hexo-util` (`npm install --save-dev hexo-util`), but no package.json declares it.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
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.
7516/10546 types (71%) 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.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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 6 use(s) across 76,811 production line(s) (~0.1/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.
Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. (×2) — src/Shared/HandyControl_Shared/Tools/Generator/GithubGravatarGenerator.cs:68, src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:520
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `src/Shared/HandyControl_Shared/Tools/Generator/GithubGravatarGenerator.cs:68` (MD5), `src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:520` (MD5). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Do you agree with this assessment?
X1 · Async correctness4.3 / 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. — src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:53
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.
`DisposableObject` declares a finalizer (line 17), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Shared/HandyControl_Shared/Data/DisposableObject.cs:17
`ColorPicker` declares a finalizer (line 365), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Shared/HandyControl_Shared/Controls/ColorPicker/ColorPicker.cs:365
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/1 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. — src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs:32
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 unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. (×21) — src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:268, src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs:372, src/Shared/HandyControl_Shared/Interactivity/Commands/OpenLinkCommand.cs:24, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:133
`catch (OverflowException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Shared/HandyControl_Shared/Controls/Window/Window.cs:377
`catch (ArgumentException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs:166
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Shared/Microsoft.Windows.Shell/JumpList.cs:582
`catch (InvalidCastException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:89, src/Shared/Microsoft.Windows.Shell/Standard/RECT.cs:132, src/Shared/Microsoft.Windows.Shell/Standard/Win32Error.cs:42
`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/Shared/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:67, src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:83
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 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 `mergedIntervals`: line 119 writes `mergedIntervals?.Any`, which says `mergedIntervals` can be null, but line 125 then dereferences it directly as `mergedIntervals.First` 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 `mergedIntervals` truly cannot be null here, the `?.` is misleading. Settle it one way — test `mergedIntervals` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Shared/HandyControl_Shared/Controls/Text/HighlightTextBlock.cs:125
This method contradicts itself about `intervals`: line 148 writes `intervals?.Any`, which says `intervals` can be null, but line 150 then dereferences it directly as `intervals.Sort` 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 `intervals` truly cannot be null here, the `?.` is misleading. Settle it one way — test `intervals` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Shared/HandyControl_Shared/Controls/Text/HighlightTextBlock.cs:150
~0.5 `!` suppressions per 1k syntax nodes — 29 suppression(s) across the 55280 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 39 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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
D27 Navigability — symbol resolution incomplete — navigability not assessed
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) — 11 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock src/Avalonia/HandyControl_Avalonia/Controls/Loading/LoadingBase.cs:103— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControlDemo_Shared/App.xaml.cs:175— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:133— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:217— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:291— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:294— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:301— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:494— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:580— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:624— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs:372— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:232— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Controls/Window/PopupWindow.cs:94— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Interactivity/Commands/OpenLinkCommand.cs:24— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:268— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/Microsoft.Windows.Shell/JumpList.cs:618— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:149— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:152— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs:218— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/System.Windows.Interactivity/DefaultTriggerAttribute.cs:42— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/System.Windows.Interactivity/EventTriggerBase.cs:115— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/System.Windows.Interactivity/EventTriggerBase.cs:143— 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.
NoWarnInCsproj — 8 warning codes suppressed in one element src/Net_GE45/HandyControl_Net_GE45/HandyControl_Net_GE45.csproj:9— A single <NoWarn> suppresses 8 warning codes (0067;0649;1591;MSB3061;SYSLIB0003;SYSLIB0004;SYSLIB0032;CA2022) in one stroke — one team-wide decision, not 8 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
NoWarnInCsproj src/Shared/HandyControlDemo_Code/HandyControlDemo_Code.csproj:7— MSB3026 — 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/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj:8— MSB3026 — 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/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj:8— MSB3026 — 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/Shared/HandyControlDemo_Code/HandyControlDemo_Code.csproj:7— MSB3061 — 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/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj:8— MSB3061 — 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/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj:8— MSB3061 — 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/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj:8— 0108 — 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/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:9— 0108 — 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/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj:8— 0108 — 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/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj:8— SYSLIB0014 — 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/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:9— 0067 — 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/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:9— 0649 — 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/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:9— 1591 — 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/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:9— 1717 — 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/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:12— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:15— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:12— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:15— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:12— NETSDK1138 — 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/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:15— NETSDK1138 — 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.
WriteOnlyPrivateField src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:22— private InteropValues.WndProc _sharedWndProc — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs:551— private int GdiplusVersion — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs:555— private bool SuppressBackgroundThread — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs:557— private bool SuppressExternalCodecs — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/Microsoft.Expression.Drawing/Media/DrawingPropertyMetadata.cs:9— private DrawingPropertyMetadataOptions options — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/Microsoft.Windows.Shell/Standard/PKEY.cs:15— private Guid _fmtid — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
WriteOnlyPrivateField src/Shared/Microsoft.Windows.Shell/Standard/PKEY.cs:17— private uint _pid — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
Unfinished stub — throws a "not implemented" exception src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:123— `NotImplemented` is a shipped member whose body only throws — and it is REACHED: src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:60 references it (1 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Unfinished stub — throws NotImplementedException src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:907— `NotImplemented` is a shipped member whose body only throws — and it is REACHED: src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:855 references it (2 further site(s) in this project). This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
Namespace dependency cycle src/Shared/HandyControl_Shared/Controls/Panel/Grid/Col.cs:5— The namespaces HandyControl.Controls ↔ HandyControl.Data ↔ HandyControl.Tools ↔ HandyControl.Tools.Extension depend on each other. The lightest dependency in the cycle is HandyControl.Controls → HandyControl.Tools.Extension (HandyControl.Controls.Col → HandyControl.Tools.Extension.ColLayout, 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.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:268— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs:372— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Interactivity/Commands/OpenLinkCommand.cs:24— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:133— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:217— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:291— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:294— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:301— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs:494— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:580— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:624— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:232— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControl_Shared/Controls/Window/PopupWindow.cs:94— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/System.Windows.Interactivity/DefaultTriggerAttribute.cs:42— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/System.Windows.Interactivity/EventTriggerBase.cs:115— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/System.Windows.Interactivity/EventTriggerBase.cs:143— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/HandyControlDemo_Shared/App.xaml.cs:175— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/Microsoft.Windows.Shell/JumpList.cs:618— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:149— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:152— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs:218— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Avalonia/HandyControl_Avalonia/Controls/Loading/LoadingBase.cs:103— 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.
TooManyMethods: NativeMethods src/Shared/Microsoft.Windows.Shell/Standard/NativeMethods.cs— TooManyMethods — 562 significant lines (blank, comment-only and punctuation-only lines excluded), 136 methods. The bar is 30 methods; this is 106 over it, 4.53× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: InteropMethods src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs— TooManyMethods — 338 significant lines (blank, comment-only and punctuation-only lines excluded), 114 methods. The bar is 30 methods; this is 84 over it, 3.80× 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: Growl src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs— TooManyMethods — 509 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 30 methods; this is 40 over it, 2.33× 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: ExtendedVisualStateManager src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs— TooManyMethods — 654 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WindowChromeWorker src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs— TooManyMethods — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Utility src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs— TooManyMethods — 421 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ImageViewer src/Shared/HandyControl_Shared/Controls/Image/ImageViewer.cs— TooManyMethods — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TimePicker src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs— TooManyMethods — 342 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: RangeSlider src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeSlider.cs— TooManyMethods — 317 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DateTimePicker src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs— TooManyMethods — 316 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DataGridAttach src/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs— TooManyMethods — 194 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× 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: RelativePanel src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs— TooManyMethods — 135 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NotifyIcon src/Shared/HandyControl_Shared/Controls/Other/NotifyIcon.cs— TooManyMethods — 376 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (5 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:519— src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:519-523 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:555-559 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:519` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:140— src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:140-144 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:163-167 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:19— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:19-23 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:19-23 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:345— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:345-349 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:328-332 — 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. 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/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130-134 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:911-915 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210-214 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:983-987 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 (5 lines × 2) src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130-134 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:911-915 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210-214 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:983-987 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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 (5 lines × 2) src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:130-134 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:911-915 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:210-214 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:983-987 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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.
Swallowed exception (caught, then discarded) src/Shared/HandyControl_Shared/Controls/Window/Window.cs:377— `catch (OverflowException)` 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/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs:166— `catch (ArgumentException)` 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/Shared/Microsoft.Windows.Shell/JumpList.cs:582— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:89— `catch (InvalidCastException)` 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/Shared/Microsoft.Windows.Shell/Standard/RECT.cs:132— `catch (InvalidCastException)` 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/Shared/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:67— `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/Shared/Microsoft.Windows.Shell/Standard/Win32Error.cs:42— `catch (InvalidCastException)` 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/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:83— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
FileTooLong: Interop/InteropValues.cs src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs— FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 308 over it, 1.62× 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: Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs— FileTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 203 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Standard/NativeMethods.cs src/Shared/Microsoft.Windows.Shell/Standard/NativeMethods.cs— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Growl/Growl.cs src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× 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: Interop/InteropMethods.cs src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× 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: Image/ImageViewer.cs src/Shared/HandyControl_Shared/Controls/Image/ImageViewer.cs— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
MethodTooLong: DashedBorder.Render src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:169— MethodTooLong — Render runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FlexPanel.ArrangeOverride src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:209— MethodTooLong — ArrangeOverride runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FlexPanel.ArrangeOverride src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:220— MethodTooLong — ArrangeOverride runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DashedBorder.OnRender src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:381— MethodTooLong — OnRender runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: FlexPanel.ArrangeLine src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:428— MethodTooLong — ArrangeLine runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FlexPanel.ArrangeLine src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:448— MethodTooLong — ArrangeLine runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (6 lines × 2) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:135— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:135-140 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:105-110 — 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/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:135` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Shared/HandyControl_Shared/Controls/Drawer/Drawer.cs:393— src/Shared/HandyControl_Shared/Controls/Drawer/Drawer.cs:393-398 | src/Shared/HandyControl_Shared/Controls/Other/NotifyIcon.cs:687-692 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:70— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:70-77 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:71-76 — 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. 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 (6 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/SearchBar.cs:124— src/Shared/HandyControl_Shared/Controls/Input/SearchBar.cs:124-129 | src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenuItem.cs:210-215 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/SearchBar.cs:124— src/Shared/HandyControl_Shared/Controls/Input/SearchBar.cs:124-129 | src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenuItem.cs:210-215 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:594— src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:594-602 | src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:695-703 — both copies are in the same file, so extract the 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/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:594` 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 (9 lines × 2) src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:150— src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:150-158 | src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:253-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:150` 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/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:187— src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:187-195 | src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:215-223 — both copies are in the same file, so extract the 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/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:187` 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 × 2) src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:48— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:48-56 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:843-851 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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.
BarePragmaDisable src/Shared/HandyControlDemo_Shared/App.xaml.cs:23— #pragma warning disable IDE0052 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable src/Shared/Microsoft.Expression.Drawing/Media/DrawingPropertyMetadata.cs:8— #pragma warning disable 414 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable src/Shared/System.Windows.Interactivity/TriggerAction`1.cs:12— #pragma warning disable 108,114 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
Duplicated block (22 lines × 2) src/Shared/System.Windows.Interactivity/AttachableCollection`1.cs:83— src/Shared/System.Windows.Interactivity/AttachableCollection`1.cs:83-104 | src/Shared/System.Windows.Interactivity/AttachableCollection`1.cs:129-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) src/Shared/HandyControl_Shared/Controls/Base/SimpleItemsControl.cs:139— src/Shared/HandyControl_Shared/Controls/Base/SimpleItemsControl.cs:139-160 | src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenuItem.cs:43-64 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22 lines × 2) src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:385— src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:385-406 | src/Shared/HandyControl_Shared/Controls/Cover/CoverView/CoverView.cs:250-271 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (19 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:216— src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:216-234 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:246-264 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:340— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:340-358 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:394-412 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:340` 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 (19 lines × 2) src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:411— src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:411-429 | src/Shared/HandyControl_Shared/Controls/Cover/CoverView/CoverView.cs:367-385 — 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/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:411` 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 (10 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:598— src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:598-607 | src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:625-634 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:598` 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 (10 lines × 2) src/Shared/HandyControl_Shared/Controls/Text/OutlineText.cs:199— src/Shared/HandyControl_Shared/Controls/Text/OutlineText.cs:199-208 | src/Shared/HandyControl_Shared/Controls/Text/SimpleText.cs:127-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/Shared/HandyControl_Shared/Tools/Hook/KeyboardHook.cs:33— src/Shared/HandyControl_Shared/Tools/Hook/KeyboardHook.cs:33-42 | src/Shared/HandyControl_Shared/Tools/Hook/MouseHook.cs:21-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Unfinished stub — throws NotImplementedException src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:907— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Avalonia/HandyControl_Avalonia/Tools/Converter/CornerRadiusSplitConverter.cs:35— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/Avalonia/HandyControl_Avalonia/Tools/Converter/DoubleExpandConverter.cs:24— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
FlexPanel.ArrangeOverride (cyclomatic 41) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:220— FlexPanel.ArrangeOverride has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlexPanel.ArrangeOverride (cyclomatic 41) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:209— FlexPanel.ArrangeOverride has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlexPanel.ArrangeLine (cyclomatic 41) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:448— FlexPanel.ArrangeLine has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FlexPanel.ArrangeLine (cyclomatic 41) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:428— FlexPanel.ArrangeLine has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TodoComment src/Shared/HandyControl_Shared/Controls/Ribbon/Ribbon.cs:16— // TODO: this control is a work-in-progress, it needs to support things like automatic resizing. — 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/Shared/HandyControl_Shared/Tools/Helper/TokenizerHelper.cs:177— // !!!Todo: if more than one argSet throw an exception — 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.
FlexPanel.ArrangeOverride (cognitive 79) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:220— FlexPanel.ArrangeOverride has cognitive complexity 79 (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.
FlexPanel.ArrangeOverride (cognitive 79) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:209— FlexPanel.ArrangeOverride has cognitive complexity 79 (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.
FlexPanel.ArrangeLine (cognitive 60) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:448— FlexPanel.ArrangeLine has cognitive complexity 60 (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.
FlexPanel.ArrangeLine (cognitive 60) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:428— FlexPanel.ArrangeLine has cognitive complexity 60 (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.
AxleCanvas.ArrangeOverride (cognitive 22) src/Shared/HandyControl_Shared/Controls/Panel/AxleCanvas.cs:17— AxleCanvas.ArrangeOverride has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AxleCanvas.ArrangeOverride (cognitive 22) src/Avalonia/HandyControl_Avalonia/Controls/Panel/AxleCanvas.cs:19— AxleCanvas.ArrangeOverride has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlexPanel.MeasureOverride (cognitive 19) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:145— FlexPanel.MeasureOverride has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlexPanel.MeasureOverride (cognitive 19) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:136— FlexPanel.MeasureOverride has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassTooLong: MessageBox src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 36 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: InteropValues src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 10 over it, 1.03× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (26 lines × 2) src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:82— src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:82-107 | src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:872-897 — before extracting anything, compare `src/Shared/HandyControl_Shared/Data/Gif/GPStream.cs` and `src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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/Shared/HandyControl_Shared/Data/Gif/GPStream.cs:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `pstm` to `InteropValues.IStream` in one and `IStream` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (26 lines × 2) src/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:78— src/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:78-103 | src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:489-514 — 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/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:78` 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 (23 lines × 2) src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:20— src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:20-42 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:256-278 — 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/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:44` calls `Size`, `Max` and `src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:281` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:460— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:460-482 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:500-522 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:460` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Shared/HandyControl_Shared/Controls/Text/OutlineText.cs:229— src/Shared/HandyControl_Shared/Controls/Text/OutlineText.cs:229-242 | src/Shared/HandyControl_Shared/Controls/Text/SimpleText.cs:140-153 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:671— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:671-684 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:710-723 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:671` 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 (11 lines × 2) src/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:65— src/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:65-75 | src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:476-486 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/WaterfallPanel.cs:74— src/Shared/HandyControl_Shared/Controls/Panel/WaterfallPanel.cs:74-84 | src/Shared/HandyControl_Shared/Controls/Panel/WaterfallPanel.cs:110-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Shared/HandyControl_Shared/Controls/Slider/CompareSlider/CompareTrack.cs:18— src/Shared/HandyControl_Shared/Controls/Slider/CompareSlider/CompareTrack.cs:18-24 | src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeTrack.cs:226-232 — 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/Shared/HandyControl_Shared/Controls/Slider/CompareSlider/CompareTrack.cs:18` 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/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:286— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:286-292 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:319-325 — 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.
End-of-life runtime: .NET netcoreapp3.0 extension/visual studio/WpfCoreApp/ProjectTemplate.csproj:7— extension/visual studio/WpfCoreApp/ProjectTemplate.csproj declares .NET netcoreapp3.0 as this project's target framework, and .NET Core 3.0, support ended 2020-03-03. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2020-03-03 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
End-of-life runtime: .NET Framework net40 src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:5— src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj declares .NET Framework net40 as this project's target framework, and .NET Framework 4.0, support ended 2016-01-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2016-01-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Weak hash algorithm src/Shared/HandyControl_Shared/Tools/Generator/GithubGravatarGenerator.cs:68— MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
Weak hash algorithm src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:520— MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
X18 · Disposal-pattern correctness· Finalizer on a type that owns no unmanaged resource · ×2
Finalizer on a type that owns no unmanaged resource src/Shared/HandyControl_Shared/Data/DisposableObject.cs:17— `DisposableObject` declares a finalizer (line 17), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource src/Shared/HandyControl_Shared/Controls/ColorPicker/ColorPicker.cs:365— `ColorPicker` declares a finalizer (line 365), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×2
Symbol treated as nullable, then dereferenced unguarded src/Shared/HandyControl_Shared/Controls/Text/HighlightTextBlock.cs:125— This method contradicts itself about `mergedIntervals`: line 119 writes `mergedIntervals?.Any`, which says `mergedIntervals` can be null, but line 125 then dereferences it directly as `mergedIntervals.First` 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 `mergedIntervals` truly cannot be null here, the `?.` is misleading. Settle it one way — test `mergedIntervals` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Symbol treated as nullable, then dereferenced unguarded src/Shared/HandyControl_Shared/Controls/Text/HighlightTextBlock.cs:150— This method contradicts itself about `intervals`: line 148 writes `intervals?.Any`, which says `intervals` can be null, but line 150 then dereferences it directly as `intervals.Sort` 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 `intervals` truly cannot be null here, the `?.` is misleading. Settle it one way — test `intervals` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
Graph.MeasureChild (cyclomatic 53) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:468— Graph.MeasureChild has cyclomatic complexity 53 (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.
DashedBorder.OnRender (cyclomatic 33) src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:381— DashedBorder.OnRender has cyclomatic complexity 33 (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.
DashedBorder.Render (cyclomatic 29) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:169— DashedBorder.Render has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RangeSlider.MoveToNextTick (cyclomatic 27) src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeSlider.cs:262— RangeSlider.MoveToNextTick has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExtendedVisualStateManager.FindTargetElements (cyclomatic 27) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:341— ExtendedVisualStateManager.FindTargetElements has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FluidMoveBehavior.UpdateLayoutTransitionCore (cyclomatic 24) src/Shared/Microsoft.Expression.Interactions/FluidMoveBehavior.cs:307— FluidMoveBehavior.UpdateLayoutTransitionCore has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniformSpacingPanel.MeasureOverride (cyclomatic 23) src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:178— UniformSpacingPanel.MeasureOverride has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GeometryAnimationUsingKeyFrames.ResolveKeyTimes (cyclomatic 22) src/Shared/HandyControl_Shared/Media/Animation/GeometryAnimationUsingKeyFrames.cs:345— GeometryAnimationUsingKeyFrames.ResolveKeyTimes has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
js.cookie.init::api (cyclomatic 22) doc/themes/next/source/js/js.cookie.js:41— js.cookie.init::api has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UniformSpacingPanel.MeasureOverride (cyclomatic 21) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:128— UniformSpacingPanel.MeasureOverride has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ColorPicker.UpdateStatus (cyclomatic 19) src/Shared/HandyControl_Shared/Controls/ColorPicker/ColorPicker.cs:500— ColorPicker.UpdateStatus has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Pagination.Update (cyclomatic 19) src/Avalonia/HandyControl_Avalonia/Controls/Other/Pagination.cs:293— Pagination.Update has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GraphNode.GetBoundingSize (cyclomatic 18) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:323— GraphNode.GetBoundingSize 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.
SideMenu.SideMenuItemSelected (cyclomatic 18) src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenu.cs:37— SideMenu.SideMenuItemSelected 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.
ArithmeticHelper.GetLayoutRect (cyclomatic 18) src/Shared/HandyControl_Shared/Tools/Helper/ArithmeticHelper.cs:61— ArithmeticHelper.GetLayoutRect 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.
PolylineHelper.PathMarch (cyclomatic 18) src/Shared/Microsoft.Expression.Drawing/Drawing/PolylineHelper.cs:26— PolylineHelper.PathMarch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExtendedVisualStateManager.GetLayoutRect (cyclomatic 18) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:472— ExtendedVisualStateManager.GetLayoutRect 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.
GlowWindow.HwndSourceHook (cyclomatic 17) src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs:72— GlowWindow.HwndSourceHook has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PolylineData.SmoothNormal (cyclomatic 17) src/Shared/Microsoft.Expression.Drawing/Drawing/PolylineData.cs:110— PolylineData.SmoothNormal has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExtendedVisualStateManager.CreateLayoutTransitionStoryboard (cyclomatic 17) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:191— ExtendedVisualStateManager.CreateLayoutTransitionStoryboard 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.
ExtendedVisualStateManager.LayoutPropertyFromTimeline (cyclomatic 17) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:753— ExtendedVisualStateManager.LayoutPropertyFromTimeline has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JumpList._BuildShellLists (cyclomatic 17) src/Shared/Microsoft.Windows.Shell/JumpList.cs:239— JumpList._BuildShellLists has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TaskbarItemInfo._UpdateThumbButtons (cyclomatic 16) src/Shared/Microsoft.Windows.Shell/TaskbarItemInfo.cs:468— TaskbarItemInfo._UpdateThumbButtons has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tabs.postTabs (cyclomatic 16) doc/themes/next/scripts/tags/tabs.js:9— tabs.postTabs has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BareSuppressMessage repeated across 41 files src/Shared/HandyControlDemo_Shared/App.xaml.cs:24— The identical BareSuppressMessage (`SuppressMessage`) appears in 41 files (364 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 364 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
DashedBorder.OnRender (cognitive 120) src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:381— DashedBorder.OnRender has cognitive complexity 120 (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.
Graph.MeasureChild (cognitive 82) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:468— Graph.MeasureChild has cognitive complexity 82 (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.
DashedBorder.Render (cognitive 64) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:169— DashedBorder.Render has cognitive complexity 64 (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.
ExtendedVisualStateManager.FindTargetElements (cognitive 61) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:341— ExtendedVisualStateManager.FindTargetElements has cognitive complexity 61 (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.
UniformSpacingPanel.MeasureOverride (cognitive 55) src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:178— UniformSpacingPanel.MeasureOverride has cognitive complexity 55 (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.
UniformSpacingPanel.MeasureOverride (cognitive 53) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:128— UniformSpacingPanel.MeasureOverride has cognitive complexity 53 (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.
SideMenu.SideMenuItemSelected (cognitive 46) src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenu.cs:37— SideMenu.SideMenuItemSelected has cognitive complexity 46 (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.
ExtendedVisualStateManager.LayoutPropertyFromTimeline (cognitive 43) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:753— ExtendedVisualStateManager.LayoutPropertyFromTimeline has cognitive complexity 43 (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.
RangeSlider.MoveToNextTick (cognitive 40) src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeSlider.cs:262— RangeSlider.MoveToNextTick has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
JumpList._BuildShellLists (cognitive 40) src/Shared/Microsoft.Windows.Shell/JumpList.cs:239— JumpList._BuildShellLists has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FluidMoveBehavior.UpdateLayoutTransitionCore (cognitive 39) src/Shared/Microsoft.Expression.Interactions/FluidMoveBehavior.cs:307— FluidMoveBehavior.UpdateLayoutTransitionCore has cognitive complexity 39 (threshold 15). Of this number, 33 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
GeometryAnimationUsingKeyFrames.ResolveKeyTimes (cognitive 38) src/Shared/HandyControl_Shared/Media/Animation/GeometryAnimationUsingKeyFrames.cs:345— GeometryAnimationUsingKeyFrames.ResolveKeyTimes has cognitive complexity 38 (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.
ColorPicker.UpdateStatus (cognitive 38) src/Shared/HandyControl_Shared/Controls/ColorPicker/ColorPicker.cs:500— ColorPicker.UpdateStatus has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SideMenu.OnExpandModeChanged (cognitive 37) src/Shared/HandyControl_Shared/Controls/SideMenu/SideMenu.cs:163— SideMenu.OnExpandModeChanged has cognitive complexity 37 (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.
js.cookie.init::api (cognitive 36) doc/themes/next/source/js/js.cookie.js:41— js.cookie.init::api has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (24 pts), error handling 3 (7 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphNode.GetBoundingSize (cognitive 35) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:323— GraphNode.GetBoundingSize 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.
ExtendedVisualStateManager.CreateLayoutTransitionStoryboard (cognitive 35) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:191— ExtendedVisualStateManager.CreateLayoutTransitionStoryboard 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.
PolylineData.SmoothNormal (cognitive 32) src/Shared/Microsoft.Expression.Drawing/Drawing/PolylineData.cs:110— PolylineData.SmoothNormal 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.
SketchGeometryEffect.UpdateSketchGeometry (cognitive 32) src/Shared/Microsoft.Expression.Drawing/Media/SketchGeometryEffect.cs:68— SketchGeometryEffect.UpdateSketchGeometry has cognitive complexity 32 (threshold 15). Of this number, 17 points are the body's own statements and 15 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FluidMoveBehaviorBase.AssociatedObject_LayoutUpdated (cognitive 32) src/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs:69— FluidMoveBehaviorBase.AssociatedObject_LayoutUpdated has cognitive complexity 32 (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.
Utility.UrlDecode (cognitive 31) src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:552— Utility.UrlDecode has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScreenshotWindow.UpdateStatus (cognitive 30) src/Shared/HandyControl_Shared/Controls/Screenshot/ScreenshotWindow.cs:379— ScreenshotWindow.UpdateStatus has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FullScreenHelper.KeepFullScreenHook (cognitive 29) src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs:174— FullScreenHelper.KeepFullScreenHook has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PolylineHelper.PathMarch (cognitive 29) src/Shared/Microsoft.Expression.Drawing/Drawing/PolylineHelper.cs:26— PolylineHelper.PathMarch has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowChromeWorker._UpdateSystemMenu (cognitive 29) src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs:450— WindowChromeWorker._UpdateSystemMenu has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TabControl.ButtonOverflow_Click (cognitive 28) src/Shared/HandyControl_Shared/Controls/TabControl/TabControl.cs:339— TabControl.ButtonOverflow_Click has cognitive complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniformSpacingPanel.ArrangeOverride (cognitive 27) src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:312— UniformSpacingPanel.ArrangeOverride has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ArcToBezierHelper.ArcToBezier (cognitive 27) src/Shared/Microsoft.Expression.Drawing/Drawing/PathSegmentHelper.cs:274— ArcToBezierHelper.ArcToBezier has cognitive complexity 27 (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.
MouseDragElementBehaviorEx.ApplyTranslationTransform (cognitive 26) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:172— MouseDragElementBehaviorEx.ApplyTranslationTransform 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.
GlowWindow.HwndSourceHook (cognitive 26) src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs:72— GlowWindow.HwndSourceHook has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtendedVisualStateManager.GoToStateCore (cognitive 26) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:659— ExtendedVisualStateManager.GoToStateCore has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UniformSpacingPanel.ArrangeOverride (cognitive 26) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:237— UniformSpacingPanel.ArrangeOverride has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComboBox.UpdateSearchItems (cognitive 25) src/Shared/HandyControl_Shared/Controls/Input/ComboBox.cs:261— ComboBox.UpdateSearchItems has cognitive complexity 25 (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.
DateTimePicker.SetSelectedDateTime (cognitive 25) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:614— DateTimePicker.SetSelectedDateTime has cognitive complexity 25 (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.
PreviewSlider.OnMouseMove (cognitive 23) src/Shared/HandyControl_Shared/Controls/Slider/PreviewSlider.cs:87— PreviewSlider.OnMouseMove has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeTrack.ArrangeOverride (cognitive 22) src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeTrack.cs:219— RangeTrack.ArrangeOverride has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RunningBlock.UpdateContent (cognitive 22) src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBlock.cs:136— RunningBlock.UpdateContent has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Ribbon.NotifyMouseClickedOnTabHeader (cognitive 21) src/Shared/HandyControl_Shared/Controls/Ribbon/Ribbon.cs:152— Ribbon.NotifyMouseClickedOnTabHeader has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ImageViewer.ScaleImg (cognitive 21) src/Shared/HandyControl_Shared/Controls/Image/ImageViewer.cs:727— ImageViewer.ScaleImg 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.
TimePicker.SetSelectedTime (cognitive 21) src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:658— TimePicker.SetSelectedTime has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TaskbarItemInfo._UpdateThumbButtons (cognitive 21) src/Shared/Microsoft.Windows.Shell/TaskbarItemInfo.cs:468— TaskbarItemInfo._UpdateThumbButtons 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.
Dialog.Show (cognitive 21) src/Avalonia/HandyControl_Avalonia/Controls/Dialog/Dialog.cs:70— Dialog.Show has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Growl.InitGrowlInfo (cognitive 20) src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs:485— Growl.InitGrowlInfo 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.
TokenizerHelper.NextToken (cognitive 20) src/Shared/HandyControl_Shared/Tools/Helper/TokenizerHelper.cs:74— TokenizerHelper.NextToken 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.
ExtendedVisualStateManager.GetOldOpacities (cognitive 20) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:521— ExtendedVisualStateManager.GetOldOpacities 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.
ImageSelector.ParseFilterPatterns (cognitive 20) src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:176— ImageSelector.ParseFilterPatterns 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.
merge-configs.hexo.on("generateBefore") (cognitive 20) doc/themes/next/scripts/merge-configs.js:7— merge-configs.hexo.on("generateBefore") has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GridAttach.OnRowNameChanged (cognitive 19) src/Shared/HandyControl_Shared/Controls/Attach/GridAttach.cs:21— GridAttach.OnRowNameChanged has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (GridAttach.OnColumnNameChanged) 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.
GridAttach.OnColumnNameChanged (cognitive 19) src/Shared/HandyControl_Shared/Controls/Attach/GridAttach.cs:60— GridAttach.OnColumnNameChanged has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (GridAttach.OnRowNameChanged) 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.
AttachableCollection.OnCollectionChanged (cognitive 19) src/Shared/System.Windows.Interactivity/AttachableCollection`1.cs:77— AttachableCollection.OnCollectionChanged 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.
JumpList.AddCategory (cognitive 19) src/Shared/Microsoft.Windows.Shell/JumpList.cs:456— JumpList.AddCategory has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenshotWindow.OnPreviewMouseMove (cognitive 18) src/Shared/HandyControl_Shared/Controls/Screenshot/ScreenshotWindow.cs:273— ScreenshotWindow.OnPreviewMouseMove 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.
GlowEdge.WndProc (cognitive 18) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:179— GlowEdge.WndProc 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.
CompareTrack.ArrangeOverride (cognitive 18) src/Shared/HandyControl_Shared/Controls/Slider/CompareSlider/CompareTrack.cs:10— CompareTrack.ArrangeOverride has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JumpList.ListContainsShellObject (cognitive 18) src/Shared/Microsoft.Windows.Shell/JumpList.cs:367— JumpList.ListContainsShellObject has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
affix.Affix.getState (cognitive 18) doc/themes/next/source/js/affix.js:45— affix.Affix.getState has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 5 (6 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PinBox.PasswordBoxsPasswordChanged (cognitive 17) src/Shared/HandyControl_Shared/Controls/Input/PinBox.cs:85— PinBox.PasswordBoxsPasswordChanged has cognitive complexity 17 (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.
RangeTrack.UpdateComponent (cognitive 17) src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeTrack.cs:414— RangeTrack.UpdateComponent 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.
GlowEdge.WmNcHitTest (cognitive 17) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:223— GlowEdge.WmNcHitTest has cognitive complexity 17 (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.
RateItem.OnMouseLeftButtonUp (cognitive 17) src/Shared/HandyControl_Shared/Controls/Rate/RateItem.cs:183— RateItem.OnMouseLeftButtonUp has cognitive complexity 17 (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.
ArcGeometrySource.ComputeAngleRanges (cognitive 17) src/Shared/Microsoft.Expression.Drawing/Media/ArcGeometrySource.cs:22— ArcGeometrySource.ComputeAngleRanges has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LeftMainContent.FilterItems (cognitive 17) src/Shared/HandyControlDemo_Shared/UserControl/Main/LeftMainContent.xaml.cs:63— LeftMainContent.FilterItems has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePicker.SetSelectedTime (cognitive 17) src/Avalonia/HandyControl_Avalonia/Controls/Input/TimePicker.cs:332— TimePicker.SetSelectedTime 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.
tabs.postTabs (cognitive 17) doc/themes/next/scripts/tags/tabs.js:9— tabs.postTabs has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, ternaries 2 (4 pts), loops 2 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PinBox.OnApplyTemplate (cognitive 16) src/Shared/HandyControl_Shared/Controls/Input/PinBox.cs:440— PinBox.OnApplyTemplate has cognitive complexity 16 (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.
SelectableItem.OnMouseLeftButtonUp (cognitive 16) src/Shared/HandyControl_Shared/Controls/Base/SelectableItem.cs:26— SelectableItem.OnMouseLeftButtonUp has cognitive complexity 16 (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.
Pagination.Update (cognitive 16) src/Shared/HandyControl_Shared/Controls/Other/Pagination.cs:313— Pagination.Update has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Long2FileSizeConverter.Convert (cognitive 16) src/Shared/HandyControl_Shared/Tools/Converter/Long2FileSizeConverter.cs:9— Long2FileSizeConverter.Convert 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.
ExtendedVisualStateManager.control_LayoutUpdated (cognitive 16) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:139— ExtendedVisualStateManager.control_LayoutUpdated has cognitive complexity 16 (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.
MouseDragElementBehavior.ApplyTranslation (cognitive 16) src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:101— MouseDragElementBehavior.ApplyTranslation has cognitive complexity 16 (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.
MouseDragElementBehavior.ApplyTranslationTransform (cognitive 16) src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:145— MouseDragElementBehavior.ApplyTranslationTransform 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.
JumpList.CreateLinkFromJumpTask (cognitive 16) src/Shared/Microsoft.Windows.Shell/JumpList.cs:519— JumpList.CreateLinkFromJumpTask has cognitive complexity 16 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
HRESULT.ToString (cognitive 16) src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:49— HRESULT.ToString has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePicker.OnApplyTemplate (cognitive 16) src/Avalonia/HandyControl_Avalonia/Controls/Input/TimePicker.cs:196— TimePicker.OnApplyTemplate 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.
next-url.hexo.extend.helper.register("next_url") (cognitive 16) doc/themes/next/scripts/helpers/next-url.js:9— next-url.hexo.extend.helper.register("next_url") has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Change coupling: DateTimePicker.cs ↔ TimePicker.cs src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:1— `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dd6c83a5` refactor: DateTimePicker and TimePicker formatting.; `10437a6c` chore: close #1441; `bf127239` fix: close #1149 — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:413— src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:413-448 | src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:451-486 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:489— src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:489-512 | src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:515-538 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (41–44 lines × 2) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:232— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:232-275 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:190-230 — 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. 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 (33 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:300— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:300-332 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:354-386 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:419— src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:419-448 | src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:457-486 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:419` 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 (29 lines × 2) src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:142— src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:142-170 | src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.cs:114-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:142` 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 (20 lines × 2) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:493— src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:493-512 | src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:519-538 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:493` 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 (20 lines × 3) src/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs:78— src/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs:78-97 | src/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs:145-164 | src/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs:212-231 — 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/Shared/HandyControl_Shared/Controls/Attach/DataGridAttach.cs:78` 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 (17 lines × 2) src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:351— src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:351-367 | src/Shared/HandyControl_Shared/Controls/Cover/CoverView/CoverView.cs:319-335 — 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/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs:351` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:24— src/Shared/HandyControl_Shared/Controls/Block/RunningBlock/RunningBorder.cs:24-34 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:260-270 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:299-309 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (13 lines × 2) src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:245— src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:245-257 | src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:355-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs:245` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–14 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:610— src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:610-623 | src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:636-647 — both copies are in the same file, so extract the 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/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:610` 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 (5–11 lines × 4) src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:214— src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:214-224 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:225-235 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:236-246 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:247-251 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:429— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:429-438 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:469-478 | src/Shared/HandyControl_Shared/Controls/Time/CalendarWithClock.cs:175-184 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:508— src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:508-515 | src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:548-555 — before extracting anything, compare `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs` and `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 112 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs:557` calls `Clock_SelectedTimeChanged`, `Clock_Confirmed`, `TogglePopup` and `src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:517` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Low cohesion: SystemParameters2 (LCOM4 11) src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs:13— SystemParameters2's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
async void method: SwitchImage src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:53— `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.
X2 · Cancellation propagation· Async method without CancellationToken · ×1
Async method without CancellationToken: ShowInteractiveDialog src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs:32— No CancellationToken parameter — this work can't be stopped early once started.
Duplicated predicate src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:215— `!MathHelper.IsZero(radiusX) || !MathHelper.IsZero(radiusY)` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs, src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.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/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:430— `!borderThickness.IsZero() && borderBrush != null` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs, src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.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/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:266— `!isFirst && MathHelper.GreaterThan(curLineSize.U + sz.U + spacingSize.U, uvConstraint.U)` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.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/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:346— `!isFirst && MathHelper.GreaterThan(curLineSize.U + sz.U + spacingSize.U, uvFinalSize.U)` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.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/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:171— `!item.Value.TryGetTarget(out var target) || !ReferenceEquals(control, target)` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs, src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.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/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:703— `FlexDirection == FlexDirection.Row || FlexDirection == FlexDirection.RowReverse` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.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/Shared/HandyControl_Shared/Controls/Cover/CoverView/CoverView.cs:345— `IsLoaded && !_isRefresh && _itemsSourceInternal != null` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Controls/Carousel/Carousel.cs, src/Shared/HandyControl_Shared/Controls/Cover/CoverView/CoverView.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/Shared/HandyControl_Shared/Tools/Extension/ValueExtension.cs:17— `MathHelper.AreClose(thickness.Left, thickness.Top) && MathHelper.AreClose(thickness.Left, thickness.Right) && MathHelper.AreClose(thickness.…` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Tools/Extension/ValueExtension.cs, src/Shared/HandyControl_Shared/Tools/Extension/ValueExtension.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/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:147— `MathHelper.AreClose(topLeft, borderRadii.TopRight) && MathHelper.AreClose(topLeft, borderRadii.BottomLeft) && MathHelper.AreClose(topLeft, b…` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs, src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.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/Shared/HandyControl_Shared/Tools/Extension/ValueExtension.cs:11— `MathHelper.IsZero(thickness.Left) && MathHelper.IsZero(thickness.Top) && MathHelper.IsZero(thickness.Right) && MathHelper.IsZero(thickness.B…` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Tools/Extension/ValueExtension.cs, src/Shared/HandyControl_Shared/Tools/Extension/ValueExtension.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/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:227— `MathHelper.IsZero(uvFinalSize.U) || MathHelper.IsZero(uvFinalSize.V)` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.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/Shared/HandyControl_Shared/Controls/Other/Pagination.cs:354— `PageIndex > 1 && PageIndex < MaxPageCount` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Other/Pagination.cs, src/Shared/HandyControl_Shared/Controls/Other/Pagination.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/Shared/HandyControl_Shared/Controls/Drawer/Drawer.cs:394— `ReferenceEquals(this, target.DataContext) || Equals(oldValue, target.DataContext)` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Controls/Drawer/Drawer.cs, src/Shared/HandyControl_Shared/Controls/Other/NotifyIcon.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/Shared/HandyControl_Shared/Controls/Other/Pagination.cs:305— `_buttonLeft == null || _buttonRight == null || _buttonFirst == null || _moreLeft == null || _panelMain == null || _moreRight == null || _but…` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Other/Pagination.cs, src/Shared/HandyControl_Shared/Controls/Other/Pagination.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/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:84— `_cachedRenderTransform == null || !ReferenceEquals(_cachedRenderTransform, AssociatedObject.RenderTransform)` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs, src/Shared/Microsoft.Expression.Interactions/MouseDragElementBehavior.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/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:403— `_dropDownButton == null || _popup == null || _textBox == null` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs, src/Shared/HandyControl_Shared/Controls/Input/TimePicker.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/Shared/HandyControl_Shared/Controls/Time/Clock/ListClock.cs:140— `_hourList.SelectedIndex >= 0 && _hourList.SelectedIndex < 24 && _minuteList.SelectedIndex >= 0 && _minuteList.SelectedIndex < 60 && _secondL…` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/ListClock.cs, src/Shared/HandyControl_Shared/Controls/Time/Clock/ListClock.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/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:503— `_isHandlerSuspended != null && _isHandlerSuspended.ContainsKey(property)` appears character-identically in 3 files — src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs, src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs, src/Shared/HandyControl_Shared/Controls/Time/CalendarWithClock.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/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:613— `_lineCount == 1 && flexWrap == FlexWrap.NoWrap` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.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/Shared/HandyControl_Shared/Controls/ProgressBar/WaveProgressBar.cs:59— `_waveElement != null && clipElement != null` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Controls/ProgressBar/WaveProgressBar.cs, src/Shared/HandyControl_Shared/Controls/ProgressBar/WaveProgressBar.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/Shared/Microsoft.Windows.Shell/Standard/Assert.cs:32— `actual != null && !actual.Equals(expected)` appears character-identically in 2 files — src/Shared/Microsoft.Windows.Shell/Standard/Assert.cs, src/Shared/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Shared/Microsoft.Windows.Shell/Standard/Assert.cs:49— `actual == null || actual.Equals(notExpected)` appears character-identically in 2 files — src/Shared/Microsoft.Windows.Shell/Standard/Assert.cs, src/Shared/Microsoft.Windows.Shell/Standard/Verify.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:141— `child == null || child.Visibility == Visibility.Collapsed` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs, src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.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/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeTrack.cs:213— `componentLength > trackLength || double.IsNaN(componentLength)` appears character-identically in 2 files — src/Shared/HandyControl_Shared/Controls/Slider/CompareSlider/CompareTrack.cs, src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeTrack.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/Shared/HandyControl_Shared/Tools/StyleSelector/TabItemCapsuleStyleSelector.cs:11— `container is not TabItem tabItem || VisualHelper.GetParent<TabControl>(tabItem) is not { } tabControl` appears character-identically in 2 files — src/Avalonia/HandyControl_Avalonia/Tools/StyleSelector/TabItemCapsuleStyleSelector.cs, src/Shared/HandyControl_Shared/Tools/StyleSelector/TabItemCapsuleStyleSelector.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/Shared/HandyControl_Shared/Tools/Extension/StringExtension.cs:14— `Value` swallows every exception into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/HandyControl_Shared/Tools/Extension/StringExtension.cs:26— `Value` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/HandyControl_Shared/Controls/Image/ImageViewer.cs:988— `OnUriChanged` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/HandyControlDemo_Shared/Data/GlobalData.cs:17— `Init` swallows every exception and sets `Config = new AppConfig();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/HandyControlDemo_Shared/Tools/Helper/AssemblyHelper.cs:31— `CreateInternalInstance` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/Microsoft.Windows.Shell/JumpList.cs:582— `CreateLinkFromJumpTask` swallows every exception and sets `result = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:89— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/Microsoft.Windows.Shell/Standard/RECT.cs:132— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/Microsoft.Windows.Shell/Standard/SafeConnectionPointCookie.cs:67— `ReleaseHandle` swallows every exception and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/Microsoft.Windows.Shell/Standard/Win32Error.cs:42— `Equals` swallows `InvalidCastException` and sets `result = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Avalonia/HandyControl_Avalonia/Controls/Input/ImageSelector.cs:83— `SwitchImage` swallows every exception and sets `PreviewBrush = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Avalonia/HandyControlDemo_Avalonia/Tools/Converter/StringToBitmapConverter.cs:25— `Convert` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Avalonia/HandyControlDemo_Avalonia/Tools/Helper/AssemblyHelper.cs:31— `CreateInternalInstance` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch doc/themes/next/source/lib/velocity/velocity.js:88— `$.isPlainObject` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Thin analysable surface across projects: HandyControl_VS_Templates extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj— 4 project(s) carry only a thin slice of real code; `HandyControl_VS_Templates` has 13 significant line(s). The mean analysable-surface weight is 93 %; this project lowers Solution Shape by about 0.16 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: WpfApp extension/visual studio/WpfApp/WpfApp.csproj— 4 project(s) carry only a thin slice of real code; `WpfApp` has 13 significant line(s). The mean analysable-surface weight is 93 %; this project lowers Solution Shape by about 0.16 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: WpfCoreApp extension/visual studio/WpfCoreApp/WpfCoreApp.csproj— 4 project(s) carry only a thin slice of real code; `WpfCoreApp` has 13 significant line(s). The mean analysable-surface weight is 93 %; this project lowers Solution Shape by about 0.16 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Thin analysable surface across projects: ProjectTemplate extension/visual studio/WpfApp/ProjectTemplate.csproj— 4 project(s) carry only a thin slice of real code; `ProjectTemplate` has 29 significant line(s). The mean analysable-surface weight is 93 %; this project lowers Solution Shape by about 0.09 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
Documentation: no project overview README.md— The opening paragraph describes SimpleFactoryGenerator and WpfExtensions as standalone projects, but the README never states what HandyControl itself is or how to use its 80+ controls. Replace the single-line banner with a one-paragraph overview: 'HandyControl is a WPF control library that rewrites native styles and contains 80+ custom controls.' then link to the main index.md.
Documentation: no installation or build instructions README.md— There are no installation or build instructions in the README. Add a short Install/Build section covering how to clone, restore via Nuget, and run the demos.
Documentation: no usage examples README.md— Usage examples are sparse; the README mentions 'run it' but does not show how to start the demo. Add a Usage section with a live preview link or a one-code-block example of App.xaml resource dictionary setup.
Documentation: no contributor guidance README.md— The README has no guidance for contributors, unlike the NexT theme docs that do. Add Contributing notes covering pull request structure and how to run the demos locally.
redundant comment src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:67— "Methods" — delete - the comment is generated from the method signature and restates Method.
redundant comment src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs:867— "one page" — delete - the const-line already states this. The comment is a non-obvious restatement of bufsize=4096, not a WHY.
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body src/Shared/HandyControlDemo_Code/DemoHelper.cs:7— `Main` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body src/Shared/Microsoft.Windows.Shell/Standard/NativeMethods.cs:359— `GetDC` has an empty body — confirm it's an intentional no-op and not an unfinished method.
README/code drift doc/themes/next/README.md:75— doc/themes/next/README.md changes into `themes/next`, but no such folder exists. 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/code drift doc/themes/next/README.md:89— doc/themes/next/README.md installs `hexo-util` (`npm install --save-dev hexo-util`), but no package.json declares it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No 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 — 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. The most over is `HandyControl_Net_40` (53170 LoC, 374 public types across 16 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
Commented-out code src/Shared/HandyControlDemo_Shared/App.xaml.cs:40— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
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.
Inconsistent root namespaces — Only 3/12 projects share a common root namespace — the code's module identity is inconsistent.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 7516/10546 types (71%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
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/1 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.5 `!` suppressions per 1k syntax nodes — 29 suppression(s) across the 55280 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, 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 11 file(s) — `extension/visual studio/WpfApp/App.xaml.cs`, `extension/visual studio/WpfApp/MainWindow.xaml.cs`, `extension/visual studio/WpfCoreApp/App.xaml.cs`, `extension/visual studio/WpfCoreApp/MainWindow.xaml.cs`, `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannonContainer.cs`, … (+6 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a16836-5292-79fb-a59d-9e49b168c951 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 3 field(s) across 2 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 80 · Warnings: 252 · Recommendations: 73 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 10:02 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.