Public report of HandyOrg/HandyControl, published 12 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 12 November 2026, 01:57 UTC · Survey ID cd_93ae1bec165542a98209cb4def7ff056

HandyOrg/HandyControl

Measured 12 November 2026, 01:56 UTC, at code version e9ad3d7

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 42out of 100 Weak
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, 34

Findings by how serious they are

75 critical 352 serious 95 minor

6 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
12 November 2026, 01:56 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

60of 60 dimensions measured by tools.
506of 522 findings point to an exact file and line, so you can open each one in the code. The other 16 concern the repository as a whole, such as missing documentation.
60dimensions across 6 lenses, read from 72,037 lines of product code in 67 projects.
Chapters

Executive summary

HandyOrg/HandyControl falls short of our standard for production, in part because we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 42 out of 100 and is rated Weak, and 21 of its 75 critical findings are security problems.

Security and Compliance, at 34, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the three runtimes or frameworks that no longer get security updates, worth about 4 points. Encrypting the sensitive stored data and keeping its keys in a vault would lift Security and Compliance itself, worth about 7 points. Raising Security and Compliance to 70 would lift the score to about 50.

Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and twenty-two errors are caught and ignored, so failures can go unnoticed. Replacing each exposed password or key, pinning each tool to an exact version and handling or logging the ignored errors would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and the two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The 21 sets of compiler warnings switched off in projects need turning back on in the build file.

The product code is 72,037 lines, about €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 for The 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.
Security and Compliance 34 · counts for 46%Production Readiness 40 · counts for 25%Maturity 52 · counts for 14%Code Health 53 · counts for 8%Architecture 68 · counts for 4%Performance 100 · counts for 2%

If Security and Compliance rose from 34 to 70, the lowest score rated Strong, the score would rise from 42 to about 50.

Code composition: what the lines of code are
Business logic 36%Supporting code 57%Generated by tools 7%
New since the last survey: 104 findings

These 104 critical or serious findings weren't in the previous survey, on 23 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · js.cookie.init.api (cyclomatic 22) doc/themes/next/source/js/js.cookie.js
  • Cognitive Complexity · js.cookie.init.api (cognitive 36) doc/themes/next/source/js/js.cookie.js
  • Code Duplication · Near-duplicate member pair (136 shared lines) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs
  • Code Duplication · Edited copy of a member (31 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs
  • Code Duplication · Edited copy of a member (21 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs
  • Code Duplication · Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Controls/Other/AnimationPath.cs
  • Code Duplication · Edited copy of a member (25 corresponding lines) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs
  • Code Duplication · Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs
  • Code Duplication · Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs
  • Code Duplication · Edited copy of a member (9 corresponding lines) src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs
  • Code Duplication · Edited copy of a member (12 corresponding lines) src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs
  • Code Duplication · Duplicated block (369 lines × 3) src/Avalonia/HandyControlDemo_Avalonia/Data/ResourceToken.cs
  • Code Duplication · Duplicated block (184–189 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (100–103 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (47 lines × 2) src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList3.cs
  • Code Duplication · Duplicated block (41–43 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (40–41 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/DialogExtension.cs
  • Code Duplication · Duplicated block (34–36 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs
  • Code Duplication · Duplicated block (30 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs
  • Code Duplication · Duplicated block (27 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs
  • Code Duplication · Duplicated block (26–27 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs
  • Code Duplication · Duplicated block (25 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Code Duplication · Duplicated block (24 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Code Duplication · Duplicated block (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/Col.cs
  • Code Duplication · Duplicated block (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs
  • Code Duplication · Duplicated block (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs
  • Code Duplication · Duplicated block (21–22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs
  • Code Duplication · Duplicated block (36 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs
  • Code Duplication · Duplicated block (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs
  • Code Duplication · Duplicated block (16 lines × 3) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs
  • Code Duplication · Duplicated block (18 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs
  • Code Duplication · Duplicated block (12–18 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs
  • Code Duplication · Duplicated block (17 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (16 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Input/PinBox.cs
  • Code Duplication · Duplicated block (13 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs
  • Code Duplication · Duplicated block (15 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/Row.cs
  • Code Duplication · Duplicated block (14 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs
  • Code Duplication · Duplicated block (13–14 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs
  • Code Duplication · Duplicated block (11 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Code Duplication · Duplicated block (12 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs
  • Code Duplication · Duplicated block (11 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs
  • Code Duplication · Duplicated block (11 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs
  • Code Duplication · Duplicated block (11 lines × 3) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs
  • Code Duplication · Duplicated block (9 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/ListClock.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs
  • Code Duplication · Duplicated block (6 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs
  • Code Duplication · Duplicated block (16 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Attach/IconElement.cs
  • Code Duplication · Duplicated block (25 lines × 2) src/Shared/HandyControlDemo_Shared/UserControl/Basic/Avatar.xaml.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Code Duplication · Duplicated block (13 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs
  • Code Duplication · Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Generator/GithubGravatarGenerator.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs
  • Cohesion (LCOM4) · Low cohesion: ConfigHelper (LCOM4 4) src/Shared/HandyControl_Shared/Tools/Helper/ConfigHelper.cs
  • Platform End-of-Life · End-of-life runtime: .NET Framework net40 src/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj
  • Platform End-of-Life · End-of-life runtime: .NET Framework net40 src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj
  • Stateful singletons · Stateful shared instance: ControlTokenManager src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs
  • Stateful singletons · Stateful shared instance: ConfettiCannon src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs
  • Stateful singletons · Stateful shared instance: Dialog src/Shared/HandyControl_Shared/Controls/Dialog/Dialog.cs
  • Stateful singletons · Stateful shared instance: GeometryKeyFrameCollection src/Shared/HandyControl_Shared/Media/Animation/GeometryKeyFrameCollection.cs
  • Stateful singletons · Stateful shared instance: ConfettiCannon src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs
  • Stateful singletons · Stateful shared instance: ConfigHelper src/Shared/HandyControl_Shared/Tools/Helper/ConfigHelper.cs
  • Stateful singletons · Stateful shared instance: HighlightingProvider REDACTED
  • Stateful singletons · Stateful shared instance: ControlTokenManager src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs
  • Stateful singletons · Stateful shared instance: ControlTokenManager src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs
  • Stateful singletons · Stateful shared instance: ConfettiCannon src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs
  • Stateful singletons · Stateful shared instance: Dialog src/Avalonia/HandyControl_Avalonia/Controls/Dialog/Dialog.cs
  • Stateful singletons · Stateful shared instance: AdornerContainer src/Shared/Microsoft.Expression.Interactions/AdornerContainer.cs
  • Stateful singletons · Stateful shared instance: ConfettiOverlay src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs
  • Stateful singletons · Process-global static state: LangProvider src/Shared/HandyControl_Shared/Properties/Langs/LangProvider.cs
  • Stateful singletons · Process-global static state: Growl src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs
  • Stateful singletons · Process-global static state: TabItem src/Shared/HandyControl_Shared/Controls/TabControl/TabItem.cs
  • Stateful singletons · Process-global static state: GlowEdge src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs
  • Stateful singletons · Process-global static state: GlobalShortcut src/Shared/HandyControl_Shared/Tools/GlobalShortcut.cs
  • Stateful singletons · Process-global static state: ImageAnimator src/Shared/HandyControl_Shared/Tools/GifImageAnimator.cs
  • Stateful singletons · Process-global static state: DesignerHelper src/Shared/HandyControl_Shared/Tools/Helper/DesignerHelper.cs
  • Stateful singletons · Process-global static state: DpiHelper src/Shared/HandyControl_Shared/Tools/Helper/DpiHelper.cs
  • Stateful singletons · Process-global static state: IconHelper src/Shared/HandyControl_Shared/Tools/Helper/IconHelper.cs
  • Stateful singletons · Process-global static state: ResourceHelper src/Shared/HandyControl_Shared/Tools/Helper/ResourceHelper.cs
  • Stateful singletons · Process-global static state: SecurityHelper src/Shared/HandyControl_Shared/Tools/Helper/SecurityHelper.cs
  • Stateful singletons · Process-global static state: SingleOpenHelper src/Shared/HandyControl_Shared/Tools/Helper/SingleOpenHelper.cs
  • Stateful singletons · Process-global static state: ClipboardHook src/Shared/HandyControl_Shared/Tools/Hook/ClipboardHook.cs
  • Stateful singletons · Process-global static state: KeyboardHook src/Shared/HandyControl_Shared/Tools/Hook/KeyboardHook.cs
  • Stateful singletons · Process-global static state: MouseHook src/Shared/HandyControl_Shared/Tools/Hook/MouseHook.cs
  • Stateful singletons · Process-global static state: SystemMenuHook src/Shared/HandyControl_Shared/Tools/Hook/SystemMenuHook.cs
  • Stateful singletons · Process-global static state: ExceptionStringTable src/Shared/Microsoft.Expression.Interactions/ExceptionStringTable.cs
  • Stateful singletons · Process-global static state: ExtendedVisualStateManager src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs
  • Stateful singletons · Process-global static state: FluidMoveBehavior src/Shared/Microsoft.Expression.Interactions/FluidMoveBehavior.cs
  • Stateful singletons · Process-global static state: FluidMoveBehaviorBase src/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs
  • Stateful singletons · Process-global static state: SharedResourceDictionary src/Shared/HandyControl_Shared/Themes/SharedResourceDictionary.cs
  • Stateful singletons · Process-global static state: ExceptionStringTable src/Shared/Microsoft.Expression.Drawing/Drawing/ExceptionStringTable.cs
  • Stateful singletons · Process-global static state: GeometryEffect src/Shared/Microsoft.Expression.Drawing/Media/GeometryEffect.cs

We compare 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: 12 findings

These 12 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one.

  • Cyclomatic Complexity · js.cookie.init::api (cyclomatic 22) doc/themes/next/source/js/js.cookie.js
  • Cognitive Complexity · js.cookie.init::api (cognitive 36) doc/themes/next/source/js/js.cookie.js
  • Code Duplication · Edited copy of a member (31 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs
  • Code Duplication · Edited copy of a member (21 corresponding lines) src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs
  • Code Duplication · Duplicated block (5 lines × 2) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs
  • Secrets (history) · REDACTED: REDACTED HandyControlDemo/UserControl/Controls/ShieldDemoCtl.xaml
  • Secrets (history) · REDACTED: REDACTED Net35/HandyControlDemo_Net35/UserControl/Controls/ShieldDemoCtl.xaml
  • Secrets (history) · REDACTED: REDACTED Net40/HandyControlDemo_Net40/UserControl/Controls/ShieldDemoCtl.xaml
  • Secrets (history) · REDACTED: REDACTED src/Shared/HandyControlDemo_Shared/UserControl/Controls/ShieldDemoCtl.xaml
  • Secrets (history) · REDACTED: REDACTED src/Shared/HandyControlDemo_Shared/UserControl/Main/OverView.xaml
  • Platform End-of-Life · End-of-life runtime: .NET Framework net40 src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj
  • Cancellation propagation · Async method without CancellationToken: ShowInteractiveDialog src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs
Rebuild cost: about €120,000 · Estimate
Cost to rebuild€41,000 to €210,000, for 681 to 2,197 hours of work, about 0.9 person-years for 1 to 2 engineers
Difficulty of the problemStandard, 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.
SizeMedium: 72,037 lines of product code
Comment linesThe estimate prices 68,145 lines. Comment lines count towards the size of 72,037 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with ProjectTemplate.csproj, HandyControlDemo_Net_40.csproj, HandyControl_Net_40.csproj.
Raises the score by about 4 points · Low effort · Platform End-of-Life
2
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 4 points · Low effort · REDACTED Scanning
3
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault.
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 7 points · Medium effort · Data Protection

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.9 person-years of work. Its weakest lens is Security and Compliance, at 34 (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 3 End-of-life runtime finding(s) in Platform End-of-Life. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 3 Platform End-of-Life 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.

arch HandyControlDemo_Avalonia HandyControlDemo_Avalonia ctx:Avalonia Avalonia HandyControl_Avalonia HandyControlDemo_Avalonia->ctx:Avalonia HandyControlDemo_Net_40 HandyControlDemo_Net_40 ctx:Net_40 Net_40 HandyControl_Net_40 HandyControlDemo_Net_40->ctx:Net_40 ctx:Shared Shared HandyControlDemo_Code HandyControlDemo_Net_40->ctx:Shared ProjectTemplate (extension/visual studio/WpfApp) ProjectTemplate (extension/visual studio/WpfApp) ProjectTemplate (extension/visual studio/WpfCoreApp) ProjectTemplate (extension/visual studio/WpfCoreApp) ctx:Net_GE45 Net_GE45 HandyControlDemo_Net_GE45 · HandyControl_Net_GE45 ctx:Net_GE45->ctx:Shared __more__ +1 more contexts

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.
uses →1 (global)2 HandyControl.Collections3 HandyControl.Data.Enum4 HandyControl.Expression.Drawing5 HandyControl.Input6 HandyControl.Interactivity7 HandyControl.Media.Animation8 HandyControl.Media.Effects9 HandyControl.Properties.Langs10 HandyControl.Tools.Interop11 HandyControlDemo.Properties.Langs12 HandyControlDemo.Window13 Standard14 doc.themes.next.scripts15 doc.themes.next.scripts.filters16 doc.themes.next.scripts.helpers17 doc.themes.next.scripts.tags18 doc.themes.next.source.js19 doc.themes.next.source.lib.velocity20 HandyControl.Data21 HandyControl.Expression.Media22 Microsoft.Windows.Shell23 HandyControl.Expression.Shapes24 HandyControl.Themes25 HandyControl.Tools26 HandyControl.Tools.Extension27 HandyControl.Tools.Helper28 HandyControlDemo29 HandyControlDemo.Data30 HandyControlDemo.Tools31 HandyControl.Controls32 HandyControl.Tools.Converter33 HandyControlDemo.Resources34 HandyControlDemo.Service35 HandyControlDemo.Tools.Converter36 HandyControlDemo.Tools.Extension37 HandyControlDemo.UserControl38 HandyControlDemo.ViewModel
1 (global)
2 HandyControl.Collections
3 HandyControl.Data.Enum
4 HandyControl.Expression.Drawing
5 HandyControl.Input
6 HandyControl.Interactivity
7 HandyControl.Media.Animation
8 HandyControl.Media.Effects
9 HandyControl.Properties.Langs
10 HandyControl.Tools.Interop
11 HandyControlDemo.Properties.Langs
12 HandyControlDemo.Window
13 Standard
14 doc.themes.next.scripts
15 doc.themes.next.scripts.filters
16 doc.themes.next.scripts.helpers
17 doc.themes.next.scripts.tags
18 doc.themes.next.source.js
19 doc.themes.next.source.lib.velocity
20 HandyControl.Data53
21 HandyControl.Expression.Media2
22 Microsoft.Windows.Shell18
23 HandyControl.Expression.Shapes7
24 HandyControl.Themes1
25 HandyControl.Tools4114
26 HandyControl.Tools.Extension11
27 HandyControl.Tools.Helper11
28 HandyControlDemo1
29 HandyControlDemo.Data3
30 HandyControlDemo.Tools1
31 HandyControl.Controls26660151
32 HandyControl.Tools.Converter1
33 HandyControlDemo.Resources11
34 HandyControlDemo.Service8
35 HandyControlDemo.Tools.Converter1
36 HandyControlDemo.Tools.Extension1
37 HandyControlDemo.UserControl34
38 HandyControlDemo.ViewModel15178
Uses a module listed above itPart of a loopThe module itself
1 (global)2 HandyControl.Collections3 HandyControl.Data.Enum4 HandyControl.Expression.Drawing5 HandyControl.Input6 HandyControl.Interactivity7 HandyControl.Media.Animation8 HandyControl.Media.Effects9 HandyControl.Properties.Langs10 HandyControl.Tools.Interop11 HandyControlDemo.Properties.Langs12 HandyControlDemo.Window13 Standard14 doc.themes.next.scripts15 doc.themes.next.scripts.filters16 doc.themes.next.scripts.helpers17 doc.themes.next.scripts.tags18 doc.themes.next.source.js19 doc.themes.next.source.lib.velocity20 HandyControl.Data21 HandyControl.Expression.Media22 Microsoft.Windows.Shell23 HandyControl.Expression.Shapes24 HandyControl.Themes25 HandyControl.Tools26 HandyControl.Tools.Extension27 HandyControl.Tools.Helper28 HandyControlDemo29 HandyControlDemo.Data30 HandyControlDemo.Tools31 HandyControl.Controls32 HandyControl.Tools.Converter33 HandyControlDemo.Resources34 HandyControlDemo.Service35 HandyControlDemo.Tools.Converter36 HandyControlDemo.Tools.Extension37 HandyControlDemo.UserControl38 HandyControlDemo.ViewModel(global)1HandyControl.Collections2HandyControl.Data.Enum3HandyControl.Expression.Drawing4HandyControl.Input5HandyControl.Interactivity6HandyControl.Media.Animation7HandyControl.Media.Effects8HandyControl.Properties.Langs9HandyControl.Tools.Interop10HandyControlDemo.Properties.Langs11HandyControlDemo.Window12Standard13doc.themes.next.scripts14doc.themes.next.scripts.filters15doc.themes.next.scripts.helpers16doc.themes.next.scripts.tags17doc.themes.next.source.js18doc.themes.next.source.lib.velocity19HandyControl.Data20HandyControl.Expression.Media21Microsoft.Windows.Shell22HandyControl.Expression.Shapes23HandyControl.Themes24HandyControl.Tools25HandyControl.Tools.Extension26HandyControl.Tools.Helper27HandyControlDemo28HandyControlDemo.Data29HandyControlDemo.Tools30HandyControl.Controls31HandyControl.Tools.Converter32HandyControlDemo.Resources33HandyControlDemo.Service34HandyControlDemo.Tools.Converter35HandyControlDemo.Tools.Extension36HandyControlDemo.UserControl37HandyControlDemo.ViewModel38532187141141111131266601511118113415178

At a glance — Code Health · 53% · Adequate · gated by X3 ·

At a glance — Architecture · 68% · Adequate · gated by D26, AX2 ·

At a glance — Maturity · 52% · Adequate · gated by M2 ·

At a glance — Readiness · 40% · Weak · gated by D8, P3 ·

At a glance — Security · 34% · Weak · gated by D29, D36, D44, C1 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection19High / Critical
A03:2025 — Software Supply Chain Failures11Medium
A07:2025 — Authentication Failures5High / Critical

Roadmap

Top priorities: 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.); Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with ProjectTemplate.csproj, HandyControlDemo_Net_40.csproj, HandyControl_Net_40.csproj.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with ProjectTemplate.csproj, HandyControlDemo_Net_40.csproj, HandyControl_Net_40.csproj.+4.3 ptsLowPlatform End-of-Life
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+4.1 ptsLowREDACTED Scanning
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.).+7.2 ptsMediumData Protection
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.+2.5 ptsLowSupply-chain Provenance & Signing
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.7 ptsLowADR Quality
Resolve the 1 No automated tests finding(s) in Code Coverage.+5.7 ptsHighCode Coverage
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.4 ptsLowSecrets (history)
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2).+1.4 ptsLowSecrets (history)

File quality

Per-file score 0–10 — a quality signature. Of 130 files carrying findings, judged against the Production bar: 7% slop · 58% mixed · 35% near-clean.

FileScoreBandWorst signal
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj2.8SlopExplicit Debt: NoWarnInCsproj
src/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs3.1SlopExplicit Debt: EmptyCatchBlock
src/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj3.2SlopExplicit Debt: NoWarnInCsproj
src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs3.6SlopExplicit Debt: EmptyCatchBlock
src/Shared/HandyControl_Shared/Tools/Interop/InteropMethods.cs3.6SlopExplicit Debt: WriteOnlyPrivateField
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs4.7MixedExplicit Debt: WriteOnlyPrivateField
src/Shared/Microsoft.Windows.Shell/JumpList.cs4.7MixedExplicit Debt: EmptyCatchBlock
src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj4.8MixedExplicit Debt: NoWarnInCsproj
src/Shared/HandyControlDemo_Shared/App.xaml.cs4.9MixedExplicit Debt: EmptyCatchBlock
src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs5.0MixedExplicit Debt: EmptyCatchBlock
src/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj5.0MixedExplicit Debt: NoWarnInCsproj
src/Shared/HandyControl_Shared/Controls/Image/GifImage.cs5.3MixedExplicit Debt: EmptyCatchBlock
src/Shared/HandyControl_Shared/Controls/Window/GlowWindow.cs5.4MixedExplicit Debt: EmptyCatchBlock
src/Shared/HandyControl_Shared/Tools/Helper/FullScreenHelper.cs5.4MixedExplicit Debt: EmptyCatchBlock
src/Shared/HandyControl_Shared/Controls/Input/TimePicker.cs5.4MixedExplicit Debt: EmptyCatchBlock

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 75

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 — 352

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 — 95

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 6

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 60 dimensions across the health lenses
D1D2D3D4D5D6D8D13D14D15D17D18D19D20D21D24D26D28D29D30D34D35D36D37D43D44AX1AX10AX2AX3AX4AX5AX6C1GD1IC1M1M2M3P1P10P3P4P6PF3S1X1X12X13X16X18X20X21X23X27X28X29X3X30X5

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
  1. 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, 506 of 522 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1cd78-6112-75d9-a6da-d26720b44914.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 3 error(s), and the diagnostics it printed were: MSB4019: The imported project "/tmp/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 "/tmp/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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The scored solution `src/HandyControl.sln`, `extension/visual studio/HandyControl_VS_Templates.sln` is not representative of this repository — it references only 192 of 973 discovered C# files (20 %). Lenses that need the product's source (domain modelling, event-driven, event sourcing) abstain because the aggregates, EF configs, and domain events under the product tree were not loaded. You can widen what we reach: point the scan at the product solution, or scan its directory directly, so the whole codebase is analyzed rather than a build-tooling sub-solution.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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.
  • AX2 Stateful singletons — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (src/Shared/HandyControl_Shared/Themes/Lang.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.

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

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D13 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.7 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.7 / 10 · rule-coverage 100% · ceiling Prevented

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.

FlexPanel.ArrangeOverride (cyclomatic 41) · ×2src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:220
FlexPanel.ArrangeLine (cyclomatic 41) · ×2src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:448
Graph.MeasureChild (cyclomatic 53)src/Shared/HandyControl_Shared/Controls/Panel/RelativePanel.cs:468
DashedBorder.OnRender (cyclomatic 33)src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:381
DashedBorder.Render (cyclomatic 29)src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:169

+ 21 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity5.8 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.8 / 10 · rule-coverage 100% · ceiling Prevented

83 method(s) exceeded the cognitive complexity threshold of 15; the worst was DashedBorder.OnRender at 120.

FlexPanel.ArrangeOverride (cognitive 79) · ×2src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:220
FlexPanel.ArrangeLine (cognitive 60) · ×2src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:448
AxleCanvas.ArrangeOverride (cognitive 22) · ×2src/Shared/HandyControl_Shared/Controls/Panel/AxleCanvas.cs:17
FlexPanel.MeasureOverride (cognitive 19) · ×2src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:145
DashedBorder.OnRender (cognitive 120)src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:381

+ 74 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 8.7 / 10 · rule-coverage 100% · ceiling Prevented

27 god class(es) detected.

TooManyMethods: NativeMethods · ×13src/Shared/Microsoft.Windows.Shell/Standard/NativeMethods.cs
FileTooLong: Interop/InteropValues.cs · ×6src/Shared/HandyControl_Shared/Tools/Interop/InteropValues.cs
MethodTooLong: DashedBorder.Render · ×6src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:169
ClassTooLong: MessageBox · ×2src/Shared/HandyControl_Shared/Controls/Window/MessageBox.cs

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication9.3 / 10Stronggated by 109 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Verified

100 duplicated block group(s) detected. A further 11 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (5 lines × 2) · ×16src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:140
Duplicated block (10 lines × 2) · ×7src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:74
Duplicated block (22 lines × 2) · ×6src/Shared/System.Windows.Interactivity/AttachableCollection`1.cs:83
Duplicated block (19 lines × 2) · ×6src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:314
Duplicated block (6 lines × 2) · ×6src/Shared/HandyControl_Shared/Interactivity/MouseDragElementBehaviorEx.cs:135

+ 45 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 16 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with GPStream.cs (6), DashedBorder.cs (3), UniformSpacingPanel.cs. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 7 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with HoneycombPanel.cs, UniformSpacingPanel.cs, ConfettiOverlay.cs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 6 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with AttachableCollection`1.cs, SimpleItemsControl.cs, Carousel.cs. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

67 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Verified

2 of 137 classes have LCOM4 above 3.

Low cohesion: SystemParameters2 (LCOM4 11) · ×2src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs:13

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with SystemParameters2.cs, ConfigHelper.cs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt6.1 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.1 / 10 · rule-coverage 100% · ceiling Prevented

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.

EmptyCatchBlock · ×22src/Avalonia/HandyControl_Avalonia/Controls/Loading/LoadingBase.cs:103
NoWarnInCsproj — 8 warning codes suppressed in one element · ×21src/Net_GE45/HandyControl_Net_GE45/HandyControl_Net_GE45.csproj:9
WriteOnlyPrivateField · ×7src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:22
BarePragmaDisable · ×3src/Shared/HandyControlDemo_Shared/App.xaml.cs:23
TodoComment · ×2src/Shared/HandyControl_Shared/Controls/Ribbon/Ribbon.cs:16

+ 2 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. 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).
  3. 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).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Documented

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.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 2 documentation facets pass in full. 163 document(s) read across 13 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies among 6 declarations measured against a convention their peers follow.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D24 · Comment Value8.9 7.1 / 10Strong✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 7.1 / 10 · rule-coverage 80% · ceiling Documented

2 of 180 judged comments only repeat the code they sit on (1.1 %). 88 comment(s) in another language or script were not judged.

redundant comment · ×2src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeSlider.cs:46
doc comments repeat the names · ×2src/Shared/HandyControl_Shared/Controls/Cover/CoverFlow/CoverFlow.cs:153

What to do

  1. Resolve the 2 redundant comment finding(s) in Comment Value — start with RangeSlider.cs, TokenizerHelper.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.

D26 · Project Cohesion0.9 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 0.9 / 10 · rule-coverage 100% · ceiling Documented

6 of 12 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion · ×6src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:1

What to do

  1. Resolve the 6 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with HandyControl_Net_40.csproj, HandyControl_Net_GE45.csproj, HandyControl_Avalonia.csproj. — One of this dimension's main actionable groups (6 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. 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.

D29 · Static Analysis (SAST)3.2 / 10Weak✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 3.2 / 10 · rule-coverage 100% · ceiling Documented

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

  1. 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).
  2. 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).
  3. 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.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: DateTimePicker.cs↔TimePicker.cs 50%

Change coupling: DateTimePicker.cs ↔ TimePicker.cssrc/Shared/HandyControl_Shared/Controls/Input/DateTimePicker.cs:1

What to do

  1. 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.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. 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).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life2.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

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.

End-of-life runtime: .NET netcoreapp3.0 · ×3extension/visual studio/WpfCoreApp/ProjectTemplate.csproj:7

What to do

  1. Resolve the 3 End-of-life runtime finding(s) in Platform End-of-Life — start with ProjectTemplate.csproj, HandyControlDemo_Net_40.csproj, HandyControl_Net_40.csproj. — One of this dimension's main actionable groups (3 warning-level).

Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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.

AX10 · Code composition9.4 / 10Exemplary✓ Tool-verified

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.
AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

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.

  • `ControlTokenManager` is not registered, but `ConfettiCannon` creates it and keeps it in the static `TokenManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_controlDict; e.g. `_controlDict` at line 131). — src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:7
  • `ConfettiCannon` keeps one instance of itself in the static `ConfettiCannons`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderRect, _currentAdornerLayer; e.g. `_renderRect` at line 295). — src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:14
  • `Dialog` keeps one instance of itself in the static `DialogDict`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_backElement; e.g. `_backElement` at line 143). — src/Shared/HandyControl_Shared/Controls/Dialog/Dialog.cs:13
  • `GeometryKeyFrameCollection` keeps one instance of itself in the static `s_emptyCollection`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_keyFrames; e.g. `_keyFrames` at line 51). — src/Shared/HandyControl_Shared/Media/Animation/GeometryKeyFrameCollection.cs:9
  • `ConfettiCannon` keeps one instance of itself in the static `DefaultConfettiCannon`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderRect, _currentAdornerLayer; e.g. `_renderRect` at line 295). — src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:14
  • `ConfigHelper` keeps one instance of itself in the static `InstanceInternal`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_lang; e.g. `_lang` at line 36). — src/Shared/HandyControl_Shared/Tools/Helper/ConfigHelper.cs:16
  • `HighlightingProvider` keeps one instance of itself in the static `DefaultInternal`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Definition; e.g. `Definition` at line 63). — REDACTED:11
  • `ControlTokenManager` is not registered, but `ConfettiCannon` creates it and keeps it in the static `TokenManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_controlDict; e.g. `_controlDict` at line 23). (×2) — src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:7, src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:8
  • `ConfettiCannon` keeps one instance of itself in the static `DefaultConfettiCannon`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderingHooked, _renderRect, _hostPanel, _overlay; e.g. `_renderingHooked` at line 132). — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:18
  • `Dialog` keeps one instance of itself in the static `DialogDict`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_hostPanel, _backElement; e.g. `_hostPanel` at line 162). — src/Avalonia/HandyControl_Avalonia/Controls/Dialog/Dialog.cs:15
  • `AdornerContainer` is not registered, but the singleton `Dialog` creates it and keeps it in `_container`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_child; e.g. `_child` at line 24). — src/Shared/Microsoft.Expression.Interactions/AdornerContainer.cs:7
  • `ConfettiOverlay` is not registered, but the singleton `ConfettiCannon` creates it and keeps it in `_overlay`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_renderRect, _renderList; e.g. `_renderRect` at line 24). — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:10
  • `LangProvider` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CultureInfoStr; e.g. `CultureInfoStr` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. (×2) — src/Shared/HandyControl_Shared/Properties/Langs/LangProvider.cs:9, src/Shared/HandyControlDemo_Shared/Properties/Langs/LangProvider.cs:9
  • `Growl` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (GrowlPanel, GrowlWindow; e.g. `GrowlPanel` at line 278). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs:20
  • `TabItem` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ItemIsDragging; e.g. `ItemIsDragging` at line 328). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Controls/TabControl/TabItem.cs:16
  • `GlowEdge` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sharedWndProc, _sharedWindowClassAtom, DisposedGlowEdges; e.g. `_sharedWndProc` at line 78). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:11
  • `GlobalShortcut` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CommandDic, KeyBindingCollection; e.g. `CommandDic` at line 54). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/GlobalShortcut.cs:10
  • `ImageAnimator` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ThreadWriterLockWaitCount, AnyFrameDirty; e.g. `ThreadWriterLockWaitCount` at line 71). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/GifImageAnimator.cs:11
  • `DesignerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isInDesignMode; e.g. `_isInDesignMode` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/DesignerHelper.cs:6
  • `DpiHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_transformToDip; e.g. `_transformToDip` at line 59). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/DpiHelper.cs:9
  • `IconHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SmallIconSize, IconSize, SystemBitDepth; e.g. `SmallIconSize` at line 274). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/IconHelper.cs:13
  • `ResourceHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_theme; e.g. `_theme` at line 75). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/ResourceHelper.cs:11
  • `SecurityHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_allWindowsUIPermission; e.g. `_allWindowsUIPermission` at line 15). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/SecurityHelper.cs:7
  • `SingleOpenHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (OpenDic; e.g. `OpenDic` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Helper/SingleOpenHelper.cs:11
  • `ClipboardHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, HWndSource, Count; e.g. `HookId` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Hook/ClipboardHook.cs:7
  • `KeyboardHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, Count, VirtualKey; e.g. `HookId` at line 35). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Hook/KeyboardHook.cs:9
  • `MouseHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, Count; e.g. `HookId` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Hook/MouseHook.cs:9
  • `SystemMenuHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DataDic; e.g. `DataDic` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/Hook/SystemMenuHook.cs:9
  • `ExceptionStringTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ResourceMan; e.g. `ResourceMan` at line 12). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Interactions/ExceptionStringTable.cs:7
  • `ExtendedVisualStateManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (MovingElements, LayoutTransitionStoryboard, LayoutProperties; e.g. `MovingElements` at line 712). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:15
  • `FluidMoveBehavior` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TransitionStoryboardDictionary; e.g. `TransitionStoryboardDictionary` at line 375). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Interactions/FluidMoveBehavior.cs:14
  • `FluidMoveBehaviorBase` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TagDictionary, NextToLastPurgeTick, LastPurgeTick; e.g. `TagDictionary` at line 85). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs:12
  • `SharedResourceDictionary` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SharedDictionaries; e.g. `SharedDictionaries` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Themes/SharedResourceDictionary.cs:8
  • `ExceptionStringTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ResourceMan; e.g. `ResourceMan` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Drawing/Drawing/ExceptionStringTable.cs:10
  • `GeometryEffect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultGeometryEffect; e.g. `defaultGeometryEffect` at line 36). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/Microsoft.Expression.Drawing/Media/GeometryEffect.cs:9
  • `ImageAnimator` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (AnyFrameDirty; e.g. `AnyFrameDirty` at line 219). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControl_Shared/Tools/GifImageAnimator.cs:11
  • `App` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (AppMutex; e.g. `AppMutex` at line 115). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControlDemo_Shared/App.xaml.cs:21
  • `GlobalData` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Config; e.g. `Config` at line 15). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Shared/HandyControlDemo_Shared/Data/GlobalData.cs:6

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

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.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.
IC1 · Incompleteness & stubs6.4 / 10Adequate✓ Tool-verified

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.
M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Describe the projects a newcomer cannot place from the root README: 10 of 10 have no README of their own, in their folder or in their family's project (`src/Net_GE45/HandyControl_Net_GE45`, `src/Net_GE45/HandyControlDemo_Net_GE45`, `src/Net_40/HandyControl_Net_40`, `src/Net_40/HandyControlDemo_Net_40`, `src/Shared/HandyControlDemo_Code` and 5 more).
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

What to do

  • Give the main body of the product a test surface of its own, where its build system looks for one — the tests that exist cover only a small part of the code.
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.
P10 · Library API & versioning8.2 / 10Strong✓ 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's code 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.

  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.1)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net45)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net451)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net452)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net46)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net461)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net47)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net471)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net5.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_40`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9
  • `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7
  • `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.1)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7
  • `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net45)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7
  • `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net451)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7
  • `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net452)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7

What to do

  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.BorderElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.PanelElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.PanelElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.PanelElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.PanelElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
  • Make `HandyControl.Controls.PanelElement` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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.

  • `extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj:59

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.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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 each language's code 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.

S1 · Cryptographic Hygiene8.0 / 10Strong✓ Tool-verified

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.
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

What to do

  • async void method: SwitchImage
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X18 · Disposal-pattern correctness6.2 / 10Adequate✓ Tool-verified

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.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

X29 · Per-element action decided by a fixed element6.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

  • This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[i]`. The test deciding whether that statement runs does not: `isBitmapIconDecoder` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 201, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — src/Shared/HandyControl_Shared/Tools/Helper/IconHelper.cs:205
  • This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[num3]`. The test deciding whether that statement runs does not: `flag` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 317, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out. — src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:321

What to do

  • Each finding names the test and the statement it guards, which index the same collection at two different subscripts — one fixed, one the loop variable. Confirm from the two, then decide which subscript the test meant. If it was meant to be per-element, give it the loop variable so each element is judged on itself. If it really is one answer for the whole collection, hoist the test OUT of the loop, where a reader can see it is asked once and where it is not re-evaluated on every pass — leaving it inside, reading a fixed element, is the one arrangement that cannot be right under either reading.
X3 · Exception handling3.3 / 10Weak✓ Tool-verified

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)
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.

X5 · Nullable reference types9.6 / 10Exemplary✓ Tool-verified

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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

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 `!`.

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.

LensScoreRatingImpact
Code Health53%Adequate — gated by X3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture68%Adequate — gated by D26, AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity52%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness40%Weak — gated by D8, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security34%Weak — gated by D29, D36, D44, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 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 — 50 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.
  • 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
  • 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
  • M4 Documentation accuracy — Not applicable: the 163 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (install 1, cd 1); M4 checks only links and versions and artefact counts.
  • 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
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's C# was read, and every log call in it goes through a logger that takes one finished message — its own wrapper, log4net, Console or Debug — so an interpolated message there loses nothing the API could have kept. Calls through Microsoft.Extensions.Logging, Serilog, NLog or ZLogger, or any logger with a message-template overload, would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 75 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×22
  • 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.
D17 · Explicit Debt · NoWarnInCsproj · ×21
  • 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/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.
  • 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_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_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/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/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/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_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 — 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/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_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/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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · WriteOnlyPrivateField · ×7
  • 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.
D28 · Secrets (history) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • 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.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • 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.
D13 · REDACTED Scanning · Leaked secret · ×1
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 352 finding(s)
AX2 · Stateful singletons · Process-global static state · ×27
  • Process-global static state: LangProvider src/Shared/HandyControl_Shared/Properties/Langs/LangProvider.cs:9 — `LangProvider` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CultureInfoStr; e.g. `CultureInfoStr` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: Growl src/Shared/HandyControl_Shared/Controls/Growl/Growl.cs:20 — `Growl` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (GrowlPanel, GrowlWindow; e.g. `GrowlPanel` at line 278). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: TabItem src/Shared/HandyControl_Shared/Controls/TabControl/TabItem.cs:16 — `TabItem` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ItemIsDragging; e.g. `ItemIsDragging` at line 328). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GlowEdge src/Shared/HandyControl_Shared/Data/GlowWindow/GlowEdge.cs:11 — `GlowEdge` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_sharedWndProc, _sharedWindowClassAtom, DisposedGlowEdges; e.g. `_sharedWndProc` at line 78). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GlobalShortcut src/Shared/HandyControl_Shared/Tools/GlobalShortcut.cs:10 — `GlobalShortcut` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CommandDic, KeyBindingCollection; e.g. `CommandDic` at line 54). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ImageAnimator src/Shared/HandyControl_Shared/Tools/GifImageAnimator.cs:11 — `ImageAnimator` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ThreadWriterLockWaitCount, AnyFrameDirty; e.g. `ThreadWriterLockWaitCount` at line 71). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DesignerHelper src/Shared/HandyControl_Shared/Tools/Helper/DesignerHelper.cs:6 — `DesignerHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isInDesignMode; e.g. `_isInDesignMode` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: DpiHelper src/Shared/HandyControl_Shared/Tools/Helper/DpiHelper.cs:9 — `DpiHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_transformToDip; e.g. `_transformToDip` at line 59). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: IconHelper src/Shared/HandyControl_Shared/Tools/Helper/IconHelper.cs:13 — `IconHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SmallIconSize, IconSize, SystemBitDepth; e.g. `SmallIconSize` at line 274). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ResourceHelper src/Shared/HandyControl_Shared/Tools/Helper/ResourceHelper.cs:11 — `ResourceHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_theme; e.g. `_theme` at line 75). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SecurityHelper src/Shared/HandyControl_Shared/Tools/Helper/SecurityHelper.cs:7 — `SecurityHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_allWindowsUIPermission; e.g. `_allWindowsUIPermission` at line 15). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SingleOpenHelper src/Shared/HandyControl_Shared/Tools/Helper/SingleOpenHelper.cs:11 — `SingleOpenHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (OpenDic; e.g. `OpenDic` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ClipboardHook src/Shared/HandyControl_Shared/Tools/Hook/ClipboardHook.cs:7 — `ClipboardHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, HWndSource, Count; e.g. `HookId` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: KeyboardHook src/Shared/HandyControl_Shared/Tools/Hook/KeyboardHook.cs:9 — `KeyboardHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, Count, VirtualKey; e.g. `HookId` at line 35). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: MouseHook src/Shared/HandyControl_Shared/Tools/Hook/MouseHook.cs:9 — `MouseHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (HookId, Count; e.g. `HookId` at line 23). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SystemMenuHook src/Shared/HandyControl_Shared/Tools/Hook/SystemMenuHook.cs:9 — `SystemMenuHook` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (DataDic; e.g. `DataDic` at line 21). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ExceptionStringTable src/Shared/Microsoft.Expression.Interactions/ExceptionStringTable.cs:7 — `ExceptionStringTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ResourceMan; e.g. `ResourceMan` at line 12). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ExtendedVisualStateManager src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:15 — `ExtendedVisualStateManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (MovingElements, LayoutTransitionStoryboard, LayoutProperties; e.g. `MovingElements` at line 712). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: FluidMoveBehavior src/Shared/Microsoft.Expression.Interactions/FluidMoveBehavior.cs:14 — `FluidMoveBehavior` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TransitionStoryboardDictionary; e.g. `TransitionStoryboardDictionary` at line 375). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: FluidMoveBehaviorBase src/Shared/Microsoft.Expression.Interactions/FluidMoveBehaviorBase.cs:12 — `FluidMoveBehaviorBase` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TagDictionary, NextToLastPurgeTick, LastPurgeTick; e.g. `TagDictionary` at line 85). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: SharedResourceDictionary src/Shared/HandyControl_Shared/Themes/SharedResourceDictionary.cs:8 — `SharedResourceDictionary` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (SharedDictionaries; e.g. `SharedDictionaries` at line 30). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ExceptionStringTable src/Shared/Microsoft.Expression.Drawing/Drawing/ExceptionStringTable.cs:10 — `ExceptionStringTable` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (ResourceMan; e.g. `ResourceMan` at line 29). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: GeometryEffect src/Shared/Microsoft.Expression.Drawing/Media/GeometryEffect.cs:9 — `GeometryEffect` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (defaultGeometryEffect; e.g. `defaultGeometryEffect` at line 36). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: ImageAnimator src/Shared/HandyControl_Shared/Tools/GifImageAnimator.cs:11 — `ImageAnimator` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (AnyFrameDirty; e.g. `AnyFrameDirty` at line 219). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: App src/Shared/HandyControlDemo_Shared/App.xaml.cs:21 — `App` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (AppMutex; e.g. `AppMutex` at line 115). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • + 2 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×22
  • 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×16
  • 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/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:494 — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:494-498 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:223-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:505 — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:505-509 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:234-238 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:505` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:516 — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:516-520 | src/Shared/HandyControl_Shared/Controls/Other/DashedBorder.cs:245-249 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:516` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) src/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/Microsoft.Windows.Shell/WindowChromeWorker.cs:466 — src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs:466-470 | src/Shared/Microsoft.Windows.Shell/WindowChromeWorker.cs:473-477 — 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.Windows.Shell/WindowChromeWorker.cs:466` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:56 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:56-60 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:49-53 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 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/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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:628 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:628-632 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:653-657 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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.
  • Duplicated block (5 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:54 — src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:54-58 | src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs:53-57 — before extracting anything, compare `src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs` and `src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 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.
AX2 · Stateful singletons · Stateful shared instance · ×13
  • Stateful shared instance: ControlTokenManager src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:7 — `ControlTokenManager` is not registered, but `ConfettiCannon` creates it and keeps it in the static `TokenManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_controlDict; e.g. `_controlDict` at line 131).
  • Stateful shared instance: ConfettiCannon src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:14 — `ConfettiCannon` keeps one instance of itself in the static `ConfettiCannons`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderRect, _currentAdornerLayer; e.g. `_renderRect` at line 295).
  • Stateful shared instance: Dialog src/Shared/HandyControl_Shared/Controls/Dialog/Dialog.cs:13 — `Dialog` keeps one instance of itself in the static `DialogDict`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_backElement; e.g. `_backElement` at line 143).
  • Stateful shared instance: GeometryKeyFrameCollection src/Shared/HandyControl_Shared/Media/Animation/GeometryKeyFrameCollection.cs:9 — `GeometryKeyFrameCollection` keeps one instance of itself in the static `s_emptyCollection`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_keyFrames; e.g. `_keyFrames` at line 51).
  • Stateful shared instance: ConfettiCannon src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:14 — `ConfettiCannon` keeps one instance of itself in the static `DefaultConfettiCannon`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderRect, _currentAdornerLayer; e.g. `_renderRect` at line 295).
  • Stateful shared instance: ConfigHelper src/Shared/HandyControl_Shared/Tools/Helper/ConfigHelper.cs:16 — `ConfigHelper` keeps one instance of itself in the static `InstanceInternal`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_lang; e.g. `_lang` at line 36).
  • Stateful shared instance: HighlightingProvider REDACTED:11 — `HighlightingProvider` keeps one instance of itself in the static `DefaultInternal`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (Definition; e.g. `Definition` at line 63).
  • Stateful shared instance: ControlTokenManager src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:7 — `ControlTokenManager` is not registered, but `ConfettiCannon` creates it and keeps it in the static `TokenManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_controlDict; e.g. `_controlDict` at line 23).
  • Stateful shared instance: ControlTokenManager src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:8 — `ControlTokenManager` is not registered, but `ConfettiCannon` creates it and keeps it in the static `TokenManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_controlDict; e.g. `_controlDict` at line 23).
  • Stateful shared instance: ConfettiCannon src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:18 — `ConfettiCannon` keeps one instance of itself in the static `DefaultConfettiCannon`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_renderingHooked, _renderRect, _hostPanel, _overlay; e.g. `_renderingHooked` at line 132).
  • Stateful shared instance: Dialog src/Avalonia/HandyControl_Avalonia/Controls/Dialog/Dialog.cs:15 — `Dialog` keeps one instance of itself in the static `DialogDict`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_hostPanel, _backElement; e.g. `_hostPanel` at line 162).
  • Stateful shared instance: AdornerContainer src/Shared/Microsoft.Expression.Interactions/AdornerContainer.cs:7 — `AdornerContainer` is not registered, but the singleton `Dialog` creates it and keeps it in `_container`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_child; e.g. `_child` at line 24).
  • Stateful shared instance: ConfettiOverlay src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:10 — `ConfettiOverlay` is not registered, but the singleton `ConfettiCannon` creates it and keeps it in `_overlay`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_renderRect, _renderList; e.g. `_renderRect` at line 24).
D3 · God Classes · TooManyMethods · ×13
  • 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×8
  • 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×7
  • Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:74 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:74-83 | src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs:73-82 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:74` 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 (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:265 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:265-274 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:341-350 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:113 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:113-122 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:165-174 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `confetti` to `ConfettiCannon.Confetti` in one and `Confetti` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (10 lines × 2) src/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.
  • Duplicated block (10 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Generator/GithubGravatarGenerator.cs:81 — src/Avalonia/HandyControl_Avalonia/Tools/Generator/GithubGravatarGenerator.cs:81-90 | src/Shared/HandyControl_Shared/Tools/Generator/GithubGravatarGenerator.cs:81-90 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Tools/Generator/GithubGravatarGenerator.cs` and `src/Shared/HandyControl_Shared/Tools/Generator/GithubGravatarGenerator.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D3 · God Classes · FileTooLong · ×6
  • 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.
D3 · God Classes · MethodTooLong · ×6
  • 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×6
  • 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 (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/Col.cs:67 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/Col.cs:67-88 | src/Shared/HandyControl_Shared/Controls/Panel/Grid/Col.cs:55-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:185 — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:185-206 | src/Shared/HandyControl_Shared/Controls/Time/Clock/Clock.cs:252-273 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (22 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs:79 — src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs:79-100 | src/Shared/HandyControl_Shared/Tools/Extension/ColLayout.cs:80-101 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×6
  • Duplicated block (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:314 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:314-332 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:336-354 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (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 (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:61 — src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:61-79 | src/Shared/HandyControl_Shared/Tools/Helper/ControlTokenManager`1.cs:169-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `control` to `T?` in one and `T` 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 (19 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:103 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:103-121 | src/Shared/HandyControl_Shared/Controls/Panel/WaterfallPanel.cs:129-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:103` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×6
  • 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/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:83 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:83-88 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:131-136 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `confetti` to `ConfettiCannon.Confetti` in one and `Confetti` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:90` calls `PushOpacity` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:138` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×5
  • 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/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:180 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:180-190 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:250-260 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 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 (11 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:33 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:33-43 | src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs:33-43 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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 (11 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs:34 — src/Avalonia/HandyControlDemo_Avalonia/ViewModel/Controls/DialogDemoViewModel.cs:34-44 | src/Shared/HandyControlDemo_Shared/ViewModel/Controls/DialogDemoViewModel.cs:64-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • 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/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/ListClock.cs:106 — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/ListClock.cs:106-114 | src/Shared/HandyControl_Shared/Controls/Time/Clock/ListClock.cs:140-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/ListClock.cs:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) src/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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · BarePragmaDisable · ×3
  • 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.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×3
  • Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Controls/Other/AnimationPath.cs:375 — src/Avalonia/HandyControl_Avalonia/Controls/Other/AnimationPath.cs:375-398 | src/Avalonia/HandyControl_Avalonia/Controls/Other/AnimationPath.cs:404-423 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:324 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:324-344 | src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:354-373 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:28 — src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:28-51 | src/Avalonia/HandyControl_Avalonia/Tools/Helper/ControlTokenManager`1.cs:82-101 — These two members are one piece of code written twice and then edited apart: 20 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 · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:180 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:180-192 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:231-243 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:180` 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 (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 (13 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:164 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:164-176 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:234-246 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×3
  • 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 (14 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:16 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs:16-29 | src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs:16-29 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/HoneycombPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/HoneycombPanel.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • 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 (11 lines × 3) 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 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11 lines × 3) src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:485 — src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:485-495 | src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:496-506 | src/Avalonia/HandyControl_Avalonia/Controls/Other/DashedBorder.cs:507-517 — 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. 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.
D44 · Platform End-of-Life · End-of-life runtime · ×3
  • 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/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj:6 — src/Net_40/HandyControlDemo_Net_40/HandyControlDemo_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.
  • 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×3
  • 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.
D1 · Cyclomatic Complexity · FlexPanel.ArrangeOverride (cyclomatic 41) · ×2
  • 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.
D1 · Cyclomatic Complexity · FlexPanel.ArrangeLine (cyclomatic 41) · ×2
  • 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.
D17 · Explicit Debt · TodoComment · ×2
  • 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.
D2 · Cognitive Complexity · FlexPanel.ArrangeOverride (cognitive 79) · ×2
  • 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.
D2 · Cognitive Complexity · FlexPanel.ArrangeLine (cognitive 60) · ×2
  • 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.
D2 · Cognitive Complexity · AxleCanvas.ArrangeOverride (cognitive 22) · ×2
  • 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.
D2 · Cognitive Complexity · FlexPanel.MeasureOverride (cognitive 19) · ×2
  • 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.
D3 · God Classes · ClassTooLong · ×2
  • 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2
  • 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×2
  • 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 (30 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs:13 — src/Avalonia/HandyControl_Avalonia/Tools/Extension/ColLayout.cs:13-42 | src/Shared/HandyControl_Shared/Tools/Extension/ColLayout.cs:14-43 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:376 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs:376-400 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:398-422 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiCannon.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 73 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (25 lines × 2) src/Shared/HandyControlDemo_Shared/UserControl/Basic/Avatar.xaml.cs:13 — src/Shared/HandyControlDemo_Shared/UserControl/Basic/Avatar.xaml.cs:13-37 | src/Shared/HandyControlDemo_Shared/UserControl/Controls/ButtonGroupDemo.xaml.cs:13-37 — 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/HandyControlDemo_Shared/UserControl/Basic/Avatar.xaml.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • 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 (17 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:635 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:635-651 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:660-676 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:635` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Input/PinBox.cs:351 — src/Avalonia/HandyControl_Avalonia/Controls/Input/PinBox.cs:351-366 | src/Avalonia/HandyControl_Avalonia/Controls/Input/PinBox.cs:370-385 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Attach/IconElement.cs:11 — src/Avalonia/HandyControl_Avalonia/Controls/Attach/IconElement.cs:11-26 | src/Avalonia/HandyControl_Avalonia/Controls/Attach/IconSwitchElement.cs:11-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • 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.
  • Low cohesion: ConfigHelper (LCOM4 4) src/Shared/HandyControl_Shared/Tools/Helper/ConfigHelper.cs:16 — ConfigHelper's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
S1 · Cryptographic Hygiene · Weak hash algorithm · ×2
  • 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.
X29 · Per-element action decided by a fixed element · Per-element action decided by a fixed element · ×2
  • Per-element action decided by a fixed element src/Shared/HandyControl_Shared/Tools/Helper/IconHelper.cs:205 — This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[i]`. The test deciding whether that statement runs does not: `isBitmapIconDecoder` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 201, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
  • Per-element action decided by a fixed element src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:321 — This loop runs once per element of `frames`, and the statement it guards acts on the element it is on — `frames[num3]`. The test deciding whether that statement runs does not: `flag` reads `frames[0]`, a subscript that does not move, so whatever it answers for that one element it answers for ALL of them. One `if` names the same collection at two different subscripts — the fixed one at line 317, which is the contradiction: either the test was meant to be per-element, in which case every element that differs from the fixed one is handled wrongly and all in the same direction, or it really is one answer for the whole collection, in which case it is being re-asked on every pass and belongs above the loop. The `if` is in the wrong place under both readings. Give the test the loop variable, or hoist it out.
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.
D1 · Cyclomatic Complexity · Graph.MeasureChild (cyclomatic 53) · ×1
  • 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.
D1 · Cyclomatic Complexity · DashedBorder.OnRender (cyclomatic 33) · ×1
  • 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.
D1 · Cyclomatic Complexity · DashedBorder.Render (cyclomatic 29) · ×1
  • 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.
D1 · Cyclomatic Complexity · RangeSlider.MoveToNextTick (cyclomatic 27) · ×1
  • 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.
D1 · Cyclomatic Complexity · ExtendedVisualStateManager.FindTargetElements (cyclomatic 27) · ×1
  • 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.
D1 · Cyclomatic Complexity · FluidMoveBehavior.UpdateLayoutTransitionCore (cyclomatic 24) · ×1
  • 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.
D1 · Cyclomatic Complexity · UniformSpacingPanel.MeasureOverride (cyclomatic 23) · ×1
  • 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.
D1 · Cyclomatic Complexity · GeometryAnimationUsingKeyFrames.ResolveKeyTimes (cyclomatic 22) · ×1
  • 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.
D1 · Cyclomatic Complexity · js.cookie.init.api (cyclomatic 22) · ×1
  • 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.
D1 · Cyclomatic Complexity · UniformSpacingPanel.MeasureOverride (cyclomatic 21) · ×1
  • 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.
D1 · Cyclomatic Complexity · ColorPicker.UpdateStatus (cyclomatic 19) · ×1
  • 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.
D1 · Cyclomatic Complexity · Pagination.Update (cyclomatic 19) · ×1
  • 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.
D1 · Cyclomatic Complexity · GraphNode.GetBoundingSize (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · SideMenu.SideMenuItemSelected (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · ArithmeticHelper.GetLayoutRect (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · PolylineHelper.PathMarch (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · ExtendedVisualStateManager.GetLayoutRect (cyclomatic 18) · ×1
  • 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.
D1 · Cyclomatic Complexity · GlowWindow.HwndSourceHook (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · PolylineData.SmoothNormal (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · ExtendedVisualStateManager.CreateLayoutTransitionStoryboard (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · ExtendedVisualStateManager.LayoutPropertyFromTimeline (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · JumpList._BuildShellLists (cyclomatic 17) · ×1
  • 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.
D1 · Cyclomatic Complexity · TaskbarItemInfo._UpdateThumbButtons (cyclomatic 16) · ×1
  • 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.
D1 · Cyclomatic Complexity · tabs.postTabs (cyclomatic 16) · ×1
  • 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.
D17 · Explicit Debt · BareSuppressMessage repeated across 41 files · ×1
  • 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.)
D2 · Cognitive Complexity · DashedBorder.OnRender (cognitive 120) · ×1
  • 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.
D2 · Cognitive Complexity · Graph.MeasureChild (cognitive 82) · ×1
  • 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.
D2 · Cognitive Complexity · DashedBorder.Render (cognitive 64) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.FindTargetElements (cognitive 61) · ×1
  • 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.
D2 · Cognitive Complexity · UniformSpacingPanel.MeasureOverride (cognitive 55) · ×1
  • 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.
D2 · Cognitive Complexity · UniformSpacingPanel.MeasureOverride (cognitive 53) · ×1
  • 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.
D2 · Cognitive Complexity · SideMenu.SideMenuItemSelected (cognitive 46) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.LayoutPropertyFromTimeline (cognitive 43) · ×1
  • 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.
D2 · Cognitive Complexity · RangeSlider.MoveToNextTick (cognitive 40) · ×1
  • 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.
D2 · Cognitive Complexity · JumpList._BuildShellLists (cognitive 40) · ×1
  • 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.
D2 · Cognitive Complexity · FluidMoveBehavior.UpdateLayoutTransitionCore (cognitive 39) · ×1
  • 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.
D2 · Cognitive Complexity · GeometryAnimationUsingKeyFrames.ResolveKeyTimes (cognitive 38) · ×1
  • 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.
D2 · Cognitive Complexity · ColorPicker.UpdateStatus (cognitive 38) · ×1
  • 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.
D2 · Cognitive Complexity · SideMenu.OnExpandModeChanged (cognitive 37) · ×1
  • 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.
D2 · Cognitive Complexity · js.cookie.init.api (cognitive 36) · ×1
  • 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.
D2 · Cognitive Complexity · GraphNode.GetBoundingSize (cognitive 35) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.CreateLayoutTransitionStoryboard (cognitive 35) · ×1
  • 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.
D2 · Cognitive Complexity · PolylineData.SmoothNormal (cognitive 32) · ×1
  • 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.
D2 · Cognitive Complexity · SketchGeometryEffect.UpdateSketchGeometry (cognitive 32) · ×1
  • 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.
D2 · Cognitive Complexity · FluidMoveBehaviorBase.AssociatedObject_LayoutUpdated (cognitive 32) · ×1
  • 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.
D2 · Cognitive Complexity · Utility.UrlDecode (cognitive 31) · ×1
  • 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.
D2 · Cognitive Complexity · ScreenshotWindow.UpdateStatus (cognitive 30) · ×1
  • 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.
D2 · Cognitive Complexity · FullScreenHelper.KeepFullScreenHook (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · PolylineHelper.PathMarch (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · WindowChromeWorker._UpdateSystemMenu (cognitive 29) · ×1
  • 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.
D2 · Cognitive Complexity · TabControl.ButtonOverflow_Click (cognitive 28) · ×1
  • 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.
D2 · Cognitive Complexity · UniformSpacingPanel.ArrangeOverride (cognitive 27) · ×1
  • 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.
D2 · Cognitive Complexity · ArcToBezierHelper.ArcToBezier (cognitive 27) · ×1
  • 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.
D2 · Cognitive Complexity · MouseDragElementBehaviorEx.ApplyTranslationTransform (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · GlowWindow.HwndSourceHook (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.GoToStateCore (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · UniformSpacingPanel.ArrangeOverride (cognitive 26) · ×1
  • 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.
D2 · Cognitive Complexity · ComboBox.UpdateSearchItems (cognitive 25) · ×1
  • 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.
D2 · Cognitive Complexity · DateTimePicker.SetSelectedDateTime (cognitive 25) · ×1
  • 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.
D2 · Cognitive Complexity · PreviewSlider.OnMouseMove (cognitive 23) · ×1
  • 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.
D2 · Cognitive Complexity · RangeTrack.ArrangeOverride (cognitive 22) · ×1
  • 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.
D2 · Cognitive Complexity · RunningBlock.UpdateContent (cognitive 22) · ×1
  • 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.
D2 · Cognitive Complexity · Ribbon.NotifyMouseClickedOnTabHeader (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · ImageViewer.ScaleImg (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · TimePicker.SetSelectedTime (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · TaskbarItemInfo._UpdateThumbButtons (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · Dialog.Show (cognitive 21) · ×1
  • 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.
D2 · Cognitive Complexity · Growl.InitGrowlInfo (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · TokenizerHelper.NextToken (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.GetOldOpacities (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · ImageSelector.ParseFilterPatterns (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · merge-configs.hexo.on("generateBefore") (cognitive 20) · ×1
  • 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.
D2 · Cognitive Complexity · GridAttach.OnRowNameChanged (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · GridAttach.OnColumnNameChanged (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · AttachableCollection.OnCollectionChanged (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · JumpList.AddCategory (cognitive 19) · ×1
  • 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.
D2 · Cognitive Complexity · ScreenshotWindow.OnPreviewMouseMove (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · GlowEdge.WndProc (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · CompareTrack.ArrangeOverride (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · JumpList.ListContainsShellObject (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · affix.Affix.getState (cognitive 18) · ×1
  • 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.
D2 · Cognitive Complexity · PinBox.PasswordBoxsPasswordChanged (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · RangeTrack.UpdateComponent (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · GlowEdge.WmNcHitTest (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · RateItem.OnMouseLeftButtonUp (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · ArcGeometrySource.ComputeAngleRanges (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · LeftMainContent.FilterItems (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · TimePicker.SetSelectedTime (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · tabs.postTabs (cognitive 17) · ×1
  • 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.
D2 · Cognitive Complexity · PinBox.OnApplyTemplate (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · SelectableItem.OnMouseLeftButtonUp (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · Pagination.Update (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · Long2FileSizeConverter.Convert (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · ExtendedVisualStateManager.control_LayoutUpdated (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · MouseDragElementBehavior.ApplyTranslation (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · MouseDragElementBehavior.ApplyTranslationTransform (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · JumpList.CreateLinkFromJumpTask (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · HRESULT.ToString (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · TimePicker.OnApplyTemplate (cognitive 16) · ×1
  • 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.
D2 · Cognitive Complexity · next-url.hexo.extend.helper.register("next_url") (cognitive 16) · ×1
  • 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (136 shared lines) · ×1
  • Near-duplicate member pair (136 shared lines) src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:221 — src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:221-446 | src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:210-426 — These two members are variants of one another: 136 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · 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.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:983 — src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:983-1007 | src/Shared/Microsoft.Expression.Interactions/ExtendedVisualStateManager.cs:1011-1043 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs:27 — src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs:27-36 | src/Shared/Microsoft.Windows.Shell/SystemParameters2.cs:39-47 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:83 — src/Shared/Microsoft.Windows.Shell/Standard/HRESULT.cs:83-94 | src/Shared/Microsoft.Windows.Shell/Standard/Win32Error.cs:36-47 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (369 lines × 3) · ×1
  • Duplicated block (369 lines × 3) src/Avalonia/HandyControlDemo_Avalonia/Data/ResourceToken.cs:3 — src/Avalonia/HandyControlDemo_Avalonia/Data/ResourceToken.cs:3-371 | src/Avalonia/HandyControl_Avalonia/Data/ResourceToken.cs:4-372 | src/Shared/HandyControl_Shared/Data/ResourceToken.cs:3-371 — before extracting anything, compare `src/Avalonia/HandyControlDemo_Avalonia/Data/ResourceToken.cs` and `src/Avalonia/HandyControl_Avalonia/Data/ResourceToken.cs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControlDemo_Avalonia/Data/ResourceToken.cs:3` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (184–189 lines × 2) · ×1
  • Duplicated block (184–189 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:430 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:430-613 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:450-638 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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.
D4 · Code Duplication · Duplicated block (100–103 lines × 2) · ×1
  • Duplicated block (100–103 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:250 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:250-349 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:263-365 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:250` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (47 lines × 2) · ×1
  • Duplicated block (47 lines × 2) src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList3.cs:11 — src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList3.cs:11-57 | src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList4.cs:11-57 — before extracting anything, compare `src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList3.cs` and `src/Shared/Microsoft.Windows.Shell/Standard/ITaskbarList4.cs` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.
D4 · Code Duplication · Duplicated block (41–44 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (41–43 lines × 2) · ×1
  • Duplicated block (41–43 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:167 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:167-207 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:176-218 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:167` 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.
D4 · Code Duplication · Duplicated block (40–41 lines × 2) · ×1
  • Duplicated block (40–41 lines × 2) src/Avalonia/HandyControl_Avalonia/Tools/Extension/DialogExtension.cs:19 — src/Avalonia/HandyControl_Avalonia/Tools/Extension/DialogExtension.cs:19-58 | src/Shared/HandyControl_Shared/Tools/Extension/DialogExtension.cs:18-58 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Tools/Extension/DialogExtension.cs` and `src/Shared/HandyControl_Shared/Tools/Extension/DialogExtension.cs` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (34–36 lines × 2) · ×1
  • Duplicated block (34–36 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:78 — src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:78-111 | src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs:77-112 — before extracting anything, compare `src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs` and `src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `o` to `object?` in one and `object` 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.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:48 — src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs:48-74 | src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs:102-128 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/ConfettiCannon/ConfettiOverlay.cs` and `src/Shared/HandyControl_Shared/Controls/ConfettiCannon/ConfettiCannon.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `confetti` to `ConfettiCannon.Confetti` in one and `Confetti` 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:180 — src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs:180-205 | src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs:181-207 — before extracting anything, compare `src/Avalonia/HandyControlDemo_Avalonia/UserControl/Controls/ConfettiCannonDemo.axaml.cs` and `src/Shared/HandyControlDemo_Shared/UserControl/Controls/ConfettiCannonDemo.xaml.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 68 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:359 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:359-382 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:377-400 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:359` 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.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:211 — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:211-232 | src/Shared/HandyControl_Shared/Controls/Time/Clock/Clock.cs:281-301 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:211` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:200 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:200-235 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:251-286 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:200` 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:198 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/UniformSpacingPanel.cs:198-213 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:219-234 | src/Shared/HandyControl_Shared/Controls/Panel/UniformSpacingPanel.cs:249-264 — 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.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:140 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:140-157 | src/Shared/HandyControl_Shared/Controls/Panel/WaterfallPanel.cs:89-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/WaterfallPanel.cs:140` 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.
D4 · Code Duplication · Duplicated block (12–18 lines × 2) · ×1
  • Duplicated block (12–18 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:20 — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:20-31 | src/Shared/HandyControl_Shared/Controls/Time/Clock/Clock.cs:19-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.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. 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/Row.cs:64 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/Row.cs:64-78 | src/Shared/HandyControl_Shared/Controls/Panel/Grid/Row.cs:62-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Panel/Row.cs:64` 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:244 — src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:244-257 | src/Shared/HandyControl_Shared/Controls/Time/Clock/Clock.cs:314-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Avalonia/HandyControl_Avalonia/Controls/Time/Clock/Clock.cs:244` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:232 — src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:232-243 | src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs:245-256 — before extracting anything, compare `src/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs` and `src/Shared/HandyControl_Shared/Controls/Panel/FlexPanel.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 393 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/Avalonia/HandyControl_Avalonia/Controls/Panel/FlexPanel.cs:232` 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • 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.
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.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1
  • JavaScript dependencies are not locked doc/themes/next/package.json:29 — doc/themes/next/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X1 · Async correctness · async void method · ×1
  • 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.
Minor — 93 finding(s)
P10 · Library API & versioning · Public type used only inside its own library · ×25
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.1)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net45)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net451)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net452)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net46)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net461)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net47)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net471)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net472)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net48)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net481)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net5.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net6.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net7.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net8.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net9.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net10.0-windows)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9 — `HandyControl.Controls.BorderElement` (src/Shared/HandyControl_Shared/Controls/Attach/BorderElement.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_40`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7 — `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7 — `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(netcoreapp3.1)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7 — `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net45)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7 — `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net451)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
  • Public type used only inside its own library src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7 — `HandyControl.Controls.PanelElement` (src/Shared/HandyControl_Shared/Controls/Attach/PanelElement.cs:7) is public, and the library's own code uses it, but no other project in this repository uses it (read: `HandyControlDemo_Net_GE45(net452)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • 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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×14
  • 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.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×6
  • Projects may be oversized for their cohesion src/Net_40/HandyControl_Net_40/HandyControl_Net_40.csproj:1 — `HandyControl_Net_40` overshoots its size bounds (53170 LoC, 374 public types across 16 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion src/Net_GE45/HandyControl_Net_GE45/HandyControl_Net_GE45.csproj:1 — `HandyControl_Net_GE45(netcoreapp3.0)` overshoots its size bounds (44559 LoC, 374 public types across 16 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion src/Avalonia/HandyControl_Avalonia/HandyControl_Avalonia.csproj:1 — `HandyControl_Avalonia` overshoots its size bounds (8566 LoC, 374 public types across 16 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion src/Net_40/HandyControlDemo_Net_40/HandyControlDemo_Net_40.csproj:1 — `HandyControlDemo_Net_40` overshoots its size bounds (6510 LoC, 186 public types across 11 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion src/Net_GE45/HandyControlDemo_Net_GE45/HandyControlDemo_Net_GE45.csproj:1 — `HandyControlDemo_Net_GE45(netcoreapp3.0)` overshoots its size bounds (6510 LoC, 186 public types across 11 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
  • Projects may be oversized for their cohesion src/Avalonia/HandyControlDemo_Avalonia/HandyControlDemo_Avalonia.csproj:1 — `HandyControlDemo_Avalonia` overshoots its size bounds (1917 LoC, 186 public types across 11 namespaces). 6 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 0.9/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D18 · Solution Shape · Thin analysable surface across projects · ×4
  • 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.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×2
  • ObsoleteWithoutCallers src/Shared/Microsoft.Windows.Shell/Standard/Assert.cs:21 — [Obsolete] Equals
  • ObsoleteWithoutCallers src/Shared/Microsoft.Windows.Shell/Standard/Utility.cs:475 — [Obsolete] GenerateToString
D24 · Comment Value · redundant comment · ×2
  • redundant comment src/Shared/HandyControl_Shared/Controls/Slider/RangeSlider/RangeSlider.cs:46 — "Register Event Handler for the Thumb" repeats the code it sits on: 4 of its 4 words (register, event, handler, thumb) are already in `EventManager.RegisterClassHandler(typeof(RangeSlider), Thumb.DragStartedEvent, new DragStartedEventHandler(OnThumbDragSt …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Shared/HandyControl_Shared/Tools/Helper/TokenizerHelper.cs:95 — "increment quote count" repeats the code it sits on: 3 of its 3 words (increment, quote, count) are already in `quoteCount++; // increment quote count`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
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.
D20 · ADR Quality · No ADRs found · ×1
  • 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/`.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×1
  • 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).
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj:59 — `extension/visual studio/HandyControl_VS_Templates/HandyControl_VS_Templates.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • 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.)
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~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. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Minor — 2 finding(s)
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names src/Shared/HandyControl_Shared/Controls/Cover/CoverFlow/CoverFlow.cs:153 — 0 of 100 documented parameters and 0 of 34 summaries in `HandyControl_Net_GE45(netcoreapp3.0)` only repeat the member or parameter name (e.g. "" for `contentList`). 100 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names doc/themes/next/scripts/tags/group-pictures.js:97 — 0 of 2 documented parameters and 0 of 7 summaries in `hexo-theme-next` only repeat the member or parameter name (e.g. "" for `pictures`). 2 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fe9e340ef73d46cab6078735a767effa/history.json --exit-code 0 --source .11artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fe9e340ef73d46cab6078735a767effa/tree.json --exit-code 0 --source .2artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude doc/themes/next/source/lib .19artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—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 scan0—
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1cd78-6112-75d9-a6da-d26720b44914 · 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.

Email — 2 field(s)
  • LangProvider.Email src/Shared/HandyControlDemo_Shared/Properties/Langs/LangProvider.cs:596
  • LangProvider.PlsEnterEmail src/Shared/HandyControlDemo_Shared/Properties/Langs/LangProvider.cs:1021
Phone — 1 field(s)
  • LangProvider.IsNotPhone src/Shared/HandyControlDemo_Shared/Properties/Langs/LangProvider.cs:801

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md