Public report of KlausLoeffelmann/MvvmForms, published 15 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.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 02:45 UTC · Survey ID cd_edb24160148f44fe9059bf457ed08158

KlausLoeffelmann/MvvmForms

Measured 15 November 2026, 02:45 UTC, at code version 1b4c8ef

Code coverage is not measured: The repo's test suite did not build.

Test reliability is not measured: No test run produced results.

Bus factor is not measured: No living knowledge left to concentrate.

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

CAI score 73out of 100 Strong
CriticalWeakAdequateStrongExemplary
Up 5 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: 39,587 lines of product code in 28 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Architecture, 65

Findings by how serious they are

28 critical 272 serious 92 minor

17 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
15 November 2026, 02:45 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 ▸

32of 32 dimensions measured by tools.
387of 392 findings point to an exact file and line, so you can open each one in the code. The other 5 concern the repository as a whole, such as missing documentation.
32dimensions across 6 lenses, read from 39,587 lines of product code in 28 projects.
Chapters

Executive summary

KlausLoeffelmann/MvvmForms meets our standard for a template or a sample. It scores 73 out of 100 and is rated Strong, and seven of its 28 critical findings are security problems in the packages it uses.

Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is making the shared services safe, worth about 7 points. Clearing the acknowledged debt comes next, worth about 2 points.

Seven known security holes in the packages the code depends on can be used by attackers. Thirteen errors are caught and ignored, so failures can go unnoticed, and three parts of the code are no longer understood by anyone working on it. Updating the vulnerable packages, handling or logging the ignored errors and having someone learn the forgotten files would close these risks. The two data fields that are written but never read need removing.

The product code is 39,587 lines, about €67,000 to rebuild.

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.
Architecture 65 · counts for 46%Production Readiness 74 · counts for 25%Code Health 78 · counts for 14%Maturity 84 · counts for 8%Security and Compliance 100 · counts for 4%Performance 100 · counts for 2%

Every lens already scores high enough to be rated Strong, so no single lens holds the score back.

Code composition: what the lines of code are
Business logic 6%Supporting code 16%Tests 26%Generated by tools 51%
New since the last survey: 34 findings

These 34 critical or serious findings weren't in the previous survey, on 29 October 2026.

  • Code Duplication · Edited copy of a member (55 corresponding lines) src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb
  • Code Duplication · Edited copy of a member (67 corresponding lines) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs
  • Code Duplication · Edited copy of a member (75 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb
  • Code Duplication · Edited copy of a member (63 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb
  • Code Duplication · Edited copy of a member (56 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb
  • Code Duplication · Edited copy of a member (14 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb
  • Code Duplication · Edited copy of a member (44 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb
  • Code Duplication · Edited copy of a member (33 corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb
  • Code Duplication · Edited copy of a member (27 corresponding lines) src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb
  • Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb
  • Code Duplication · Edited copy of a member (26 corresponding lines) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs
  • Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb
  • Code Duplication · Edited copy of a member (27 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb
  • Code Duplication · Edited copy of a member (27 corresponding lines) src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb
  • Code Duplication · Edited copy of a member (20 corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb
  • Code Duplication · Edited copies of one member (5 members, 42+ corresponding lines) src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb
  • Code Duplication · Edited copy of a member (19 corresponding lines) src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb
  • Code Duplication · Edited copy of a member (28 corresponding lines) src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) src/dev/Core/NullableValueControlCollection.vb
  • Code Duplication · Edited copy of a member (18 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb
  • Code Duplication · Edited copy of a member (24 corresponding lines) src/dev/Core/Controls/NullableControls/NullableOptionButton.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) src/dev/Core/Controls/NullableControls/NullableDateValue.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) src/dev/Core/Controls/NullableControls/NullableIntValue.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) src/dev/Core/Controls/NullableControls/NullableIntValue.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb
  • Code Duplication · Edited copy of a member (6 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb
  • Code Duplication · Edited copy of a member (3 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb
  • Code Duplication · Edited copy of a member (4 corresponding lines) src/dev/Core/Controls/NullableControls/NullableOptionButton.vb
  • Code Duplication · Edited copy of a member (39 corresponding lines) src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs
  • Dependency Vulnerabilities · REDACTED

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: 2 findings

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

  • Cohesion (LCOM4) · Low cohesion: BindableAsyncLazy (LCOM4 4) src/dev/MvvmBaseLib/MvvmBaseLibShared/Async/BindableAsyncLazy.cs
  • Cancellation propagation · Async method without CancellationToken: ValidateAsync src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/Experimental/ValidatableBase.cs
Rebuild cost: about €67,000 · Estimate
Cost to rebuild€22,000 to €110,000, for 373 to 1,184 hours of work, about 0.5 person-years for one engineer
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×1.1 at a score of 73. 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: 39,587 lines of product code
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
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.
Raises the score by about 7 points · Medium effort · Stateful singletons
2
Resolve the 1 InvertedNullGuard finding(s) in Explicit Debt — start with WinFormsMvvmPageNavigator.vb.
Raises the score by about 2 points · Low effort · Explicit Debt
3
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Timer.cs, MvvmViewModelBase.cs.
Raises the score by about 2 points · Low effort · Explicit Debt

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.

If you do one thing first · First action
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. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 305 lines over the last 90 days, which is about 1,237 lines a year. At that pace, the extra work comes to an estimated 0.1 to 0.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch ArtHorizViewModel ArtHorizViewModel ArtificalHorizonOffRoadIoC ArtificalHorizonOffRoadIoC ArtificalHorizonOffRoadIoC->ArtHorizViewModel UWP.MvvmServiceLocatorBase MvvmServiceLocatorBase ArtificalHorizonOffRoadIoC->UWP.MvvmServiceLocatorBase EFLViewModelBase EFLViewModelBase MRViewModelLibrary MRViewModelLibrary MrModelLibrary MrModelLibrary MRViewModelLibrary->MrModelLibrary MvvmFormsWebApiClientSupport MvvmFormsWebApiClientSupport MRViewModelLibrary->MvvmFormsWebApiClientSupport MRWebApiSelfHost MRWebApiSelfHost MRWebApiSelfHost->MrModelLibrary MeterReaderMvvmForms MeterReaderMvvmForms MeterReaderMvvmForms->MRViewModelLibrary MvvmForms MvvmForms MeterReaderMvvmForms->MvvmForms MeterReaderMvvmForms->MvvmFormsWebApiClientSupport MvvmAutheticationLocator MvvmAutheticationLocator MvvmServiceLocatorBase MvvmServiceLocatorBase MvvmAutheticationLocator->MvvmServiceLocatorBase MvvmBaseLib.NetStandard NetStandard MvvmCalculator MvvmCalculator MvvmCalculatorVMLib MvvmCalculatorVMLib MvvmCalculator->MvvmCalculatorVMLib WinForms.MvvmServiceLocatorBase MvvmServiceLocatorBase MvvmCalculator->WinForms.MvvmServiceLocatorBase MvvmCalculatorVMLib->MvvmServiceLocatorBase MvvmForms->MvvmBaseLib.NetStandard MvvmFormsAnalyzer MvvmFormsAnalyzer MvvmFormsAnalyzer.Vsix Vsix MvvmFormsAnalyzer.Vsix->MvvmFormsAnalyzer MvvmFormsCSharpDemos MvvmFormsCSharpDemos MvvmFormsCSharpDemos->MvvmBaseLib.NetStandard MvvmFormsCSharpDemos->MvvmForms UWP.MvvmAuthenticationLocator MvvmAuthenticationLocator UWP.MvvmAuthenticationLocator->MvvmAutheticationLocator UWP.MvvmAuthenticationLocator->MvvmServiceLocatorBase UWP.MvvmAuthenticationLocator->UWP.MvvmServiceLocatorBase UWP.MvvmServiceLocatorBase->MvvmServiceLocatorBase WinForms.MvvmServiceLocatorBase->MvvmServiceLocatorBase __more__ +3 more projects

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.

28 modules, with 9 dependencies between them. One loop runs through 2 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 ActiveDevelop.EntitiesFormsLib.My3 ActiveDevelop.EntitiesFormsLib.ViewModelBase4 ActiveDevelop.EntitiesFormsLib.ViewModelBase.My5 ActiveDevelop.Generic6 ActiveDevelop.IoC.Authentication.My7 ActiveDevelop.IoC.Generic8 ActiveDevelop.IoC.Generic.My9 ActiveDevelop.IoC.UWP.Authentication.My10 ActiveDevelop.IoC.UWP.My11 ActiveDevelop.MvvmBaseLib.FormulaEvaluator12 ActiveDevelop.MvvmBaseLib.Threading13 ActiveDevelop.MvvmForms.WebApiClientSupport14 ActiveDevelop.MvvmForms.WebApiClientSupport.My15 Microsoft.VisualBasic16 MvvmBaseLibShared.MvvmBaseClasses.Experimental17 MvvmFormsAnalyzer18 MvvmFormsAnalyzer.My19 MvvmFormsCSharpDemos20 WinForms.MvvmServiceLocatorBase.My21 ActiveDevelop.IoC.Authentication22 ActiveDevelop.IoC.UWP23 ActiveDevelop.MvvmBaseLib24 WinForms.MvvmServiceLocatorBase25 ActiveDevelop.IoC.UWP.Authentication26 ActiveDevelop.MvvmBaseLib.Mvvm27 ActiveDevelop.EntitiesFormsLib28 MvvmFormsCSharpDemos.RxCollectionView
1 (global)
2 ActiveDevelop.EntitiesFormsLib.My
3 ActiveDevelop.EntitiesFormsLib.ViewModelBase
4 ActiveDevelop.EntitiesFormsLib.ViewModelBase.My
5 ActiveDevelop.Generic
6 ActiveDevelop.IoC.Authentication.My
7 ActiveDevelop.IoC.Generic
8 ActiveDevelop.IoC.Generic.My
9 ActiveDevelop.IoC.UWP.Authentication.My
10 ActiveDevelop.IoC.UWP.My
11 ActiveDevelop.MvvmBaseLib.FormulaEvaluator
12 ActiveDevelop.MvvmBaseLib.Threading
13 ActiveDevelop.MvvmForms.WebApiClientSupport
14 ActiveDevelop.MvvmForms.WebApiClientSupport.My
15 Microsoft.VisualBasic
16 MvvmBaseLibShared.MvvmBaseClasses.Experimental
17 MvvmFormsAnalyzer
18 MvvmFormsAnalyzer.My
19 MvvmFormsCSharpDemos
20 WinForms.MvvmServiceLocatorBase.My
21 ActiveDevelop.IoC.Authentication1
22 ActiveDevelop.IoC.UWP9
23 ActiveDevelop.MvvmBaseLib1
24 WinForms.MvvmServiceLocatorBase9
25 ActiveDevelop.IoC.UWP.Authentication2
26 ActiveDevelop.MvvmBaseLib.Mvvm1
27 ActiveDevelop.EntitiesFormsLib1
28 MvvmFormsCSharpDemos.RxCollectionView21
Uses a module listed above itPart of a loopThe module itself
1 (global)2 ActiveDevelop.EntitiesFormsLib.My3 ActiveDevelop.EntitiesFormsLib.ViewModelBase4 ActiveDevelop.EntitiesFormsLib.ViewModelBase.My5 ActiveDevelop.Generic6 ActiveDevelop.IoC.Authentication.My7 ActiveDevelop.IoC.Generic8 ActiveDevelop.IoC.Generic.My9 ActiveDevelop.IoC.UWP.Authentication.My10 ActiveDevelop.IoC.UWP.My11 ActiveDevelop.MvvmBaseLib.FormulaEvaluator12 ActiveDevelop.MvvmBaseLib.Threading13 ActiveDevelop.MvvmForms.WebApiClientSupport14 ActiveDevelop.MvvmForms.WebApiClientSupport.My15 Microsoft.VisualBasic16 MvvmBaseLibShared.MvvmBaseClasses.Experimental17 MvvmFormsAnalyzer18 MvvmFormsAnalyzer.My19 MvvmFormsCSharpDemos20 WinForms.MvvmServiceLocatorBase.My21 ActiveDevelop.IoC.Authentication22 ActiveDevelop.IoC.UWP23 ActiveDevelop.MvvmBaseLib24 WinForms.MvvmServiceLocatorBase25 ActiveDevelop.IoC.UWP.Authentication26 ActiveDevelop.MvvmBaseLib.Mvvm27 ActiveDevelop.EntitiesFormsLib28 MvvmFormsCSharpDemos.RxCollectionView(global)1ActiveDevelop.EntitiesFormsLib.My2ActiveDevelop.EntitiesFormsLib.ViewModelBase3ActiveDevelop.EntitiesFormsLib.ViewModelBase.My4ActiveDevelop.Generic5ActiveDevelop.IoC.Authentication.My6ActiveDevelop.IoC.Generic7ActiveDevelop.IoC.Generic.My8ActiveDevelop.IoC.UWP.Authentication.My9ActiveDevelop.IoC.UWP.My10ActiveDevelop.MvvmBaseLib.FormulaEvaluator11ActiveDevelop.MvvmBaseLib.Threading12ActiveDevelop.MvvmForms.WebApiClientSupport13ActiveDevelop.MvvmForms.WebApiClientSupport.My14Microsoft.VisualBasic15MvvmBaseLibShared.MvvmBaseClasses.Experimental16MvvmFormsAnalyzer17MvvmFormsAnalyzer.My18MvvmFormsCSharpDemos19WinForms.MvvmServiceLocatorBase.My20ActiveDevelop.IoC.Authentication21ActiveDevelop.IoC.UWP22ActiveDevelop.MvvmBaseLib23WinForms.MvvmServiceLocatorBase24ActiveDevelop.IoC.UWP.Authentication25ActiveDevelop.MvvmBaseLib.Mvvm26ActiveDevelop.EntitiesFormsLib27MvvmFormsCSharpDemos.RxCollectionView28191921121

At a glance — Code Health · 78% · Strong ·

At a glance — Architecture · 65% · Adequate · gated by AX2 ·

At a glance — Maturity · 84% · Exemplary ·

At a glance — Readiness · 74% · Exemplary ·

At a glance — Security · 100% · Exemplary ·

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
A03:2025 — Software Supply Chain Failures7High / Critical

Roadmap

Top priorities: 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; Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf; Resolve the 1 InvertedNullGuard finding(s) in Explicit Debt — start with WinFormsMvvmPageNavigator.vb.

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

Do thisHelpsEffortDimension
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.+7.1 ptsMediumStateful singletons
Resolve the 1 InvertedNullGuard finding(s) in Explicit Debt — start with WinFormsMvvmPageNavigator.vb.+1.9 ptsLowExplicit Debt
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Timer.cs, MvvmViewModelBase.cs.+1.9 ptsLowExplicit Debt
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+1.2 ptsLowDocumentation Quality
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.+2.4 ptsMediumObservability
Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with MvvmDataGrid.vb (3), BindingManager.vb (2), NullableValueRelationPopup.vb (2).+1.9 ptsMediumExplicit Debt
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with MvvmForms.vbproj.+0.8 ptsLowProject Cohesion
Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with MvvmDataGrid.vb, NullableValueComboBox.vb, BindableTreeView.vb.+0.8 ptsLowKnowledge Freshness

File quality

Per-file score 0–10 — a quality signature. Of 125 files carrying findings, judged against the Template bar: 1% slop · 5% mixed · 94% near-clean.

FileScoreBandWorst signal
src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb1.0SlopExplicit Debt: EmptyCatchBlock
src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb2.1MixedExplicit Debt: EmptyCatchBlock
src/dev/Core/Components/BindingManager/BindingManager.vb3.4MixedExplicit Debt: EmptyCatchBlock
src/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb4.6MixedExplicit Debt: EmptyCatchBlock
src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs4.7MixedExplicit Debt: WriteOnlyPrivateField
src/dev/Core/Components/MvvmManager/UI/frmManageBindings.vb5.3MixedExplicit Debt: EmptyCatchBlock
src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb5.6MixedCyclomatic Complexity: BindableDataGridView.Value.Set (cyclomatic 22)
src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/AuxilliaryTypes/ReflectionHelper.vb6.0Near-cleanExplicit Debt: BarePragmaDisable
src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Components/MvvmManager/MvvmManager.vb6.0Near-cleanExplicit Debt: BarePragmaDisable
src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Controls/NullableControls/NullableNumValue.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Controls/NullableControls/NullableValueBase.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/Core/Controls/TooltipEx/TooltipEx.vb6.0Near-cleanExplicit Debt: TodoComment
src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb6.0Near-cleanExplicit Debt: HackComment

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

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

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

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

Could not be resolved — 17

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 32 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 32 dimensions across the health lenses
D1D2D3D4D5D6D13D14D15D17D18D19D24D26D28D29D30D34D35D43D44AX10AX2AX3AX5GD1M1M3P2P6PF3X20

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, 387 of 392 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 01a1dd18-278b-7ee8-8d6c-0be8b725d793.

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.

  • D11 Test Reliability — 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. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
  • 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 project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.VisualBasic.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.VisualBasic.tar….
  • 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. Every one of the 138 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
  • 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/dev/Core/MvvmForms.vbproj' with message: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\Microsoft.Diagnostics.Trac….
  • 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. MSBuild could not load MvvmFormsWebApiClientSupport.vbproj, MvvmBaseLib.NET45W81WP81CP.csproj, MvvmServiceLocatorBase.vbproj, UWP.MvvmServiceLocatorBase.vbproj, ModernMvvmCalculator.csproj, MvvmCalculatorVMLib.vbproj in the analyzer: the project imports a .targets file that ships with Visual Studio rather than with the .NET SDK. It therefore produced no assembly, and every compiler error in the build comes from a project that references it (MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.VisualBasic.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.VisualBasic.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.VisualBasic.targets", is correct, and that the file exists on disk.; MSB4019: The imported project "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets" was not found. Confirm that the expression in the Import declaration "$(MSBuildExtensionsPath32)/Microsoft/Portable/$(TargetFrameworkVersion)/Microsoft.Portable.CSharp.targets", which evaluated to "/usr/share/dotnet/sdk/10.0.400/Microsoft/Portable/v4.5/Microsoft.Portable.CSharp.targets", is correct, and that the file exists on disk.; CS0246: The type or namespace name 'MvvmCalculatorVMLib' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'Autofac' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'WinForms' could not be found (are you missing a using directive or an assembly reference?); CS0246: The type or namespace name 'MainViewModel' could not be found (are you missing a using directive or an assembly reference?)) — members that DO exist wherever that project builds. An analyzer-environment gap, NOT a code defect: Solution Shape is scored on structure and is NOT capped. We track the missing Windows/VS build components so the gap can be closed.
  • 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. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `src/dev/CoreTestAndDev.sln`, `src/dev/MeterReaderMvvmForms.sln`, `src/dev/MvvmCalculator.sln`, `src/dev/ArtificalHorizonOffRoadIoC.sln`, `src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln`; 1 further solution(s) found in this tree (`src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
  • 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 — 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D21 Naming Consistency — 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. 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 (39,587 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • 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/dev/MvvmFormsPlatformServices/UWP/MvvmServiceLocatorBase/project.json`, `src/dev/MvvmFormsPlatformServices/UWP/UWP.MvvmAuthenticationLocator/project.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. 1 of 2 declared ecosystem(s) (nuget REDACTED) 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.
  • AX6 Interface segregation — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • IC1 Incompleteness & stubs — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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.
  • X1 Async correctness — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X12 Unreachable branch — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X18 Disposal-pattern correctness — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X27 Collection changed while being enumerated — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X29 Per-element action decided by a fixed element — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — 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. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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.
  • 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.
  • 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 Complexity7.2 / 10Strong✓ 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 7.2 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BindingManager.UpdateSourcePropertyInternal at 38. A further 2 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 SimpleCalculator.ProcessKeyDown at 65 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmMessageBox.vb (WinFormsMvvmMessageBox.ShowMessageBox at 22). 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.

BindingManager.UpdateSourcePropertyInternal (cyclomatic 38)src/dev/Core/Components/BindingManager/BindingManager.vb:424
GridPanelLayout.Layout (cyclomatic 28)src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:21
BindingManager.UpdateTargetPropertyInternal (cyclomatic 25)src/dev/Core/Components/BindingManager/BindingManager.vb:291
BindingManager.HandleFullPathDataErrorsChangedInternal (cyclomatic 23)src/dev/Core/Components/BindingManager/BindingManager.vb:604
BindableDataGridView.Value.Set (cyclomatic 22)src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:515

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with BindingManager.UpdateSourcePropertyInternal (cyclomatic 38). — Refactoring it lifts Cyclomatic Complexity from 7.2 to about 7.4/10.

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

D2 · Cognitive Complexity6.3 / 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 6.3 / 10 · rule-coverage 100% · ceiling Prevented

55 method(s) exceeded the cognitive complexity threshold of 15; the worst was MvvmDataGrid.Initialize at 78.

MvvmDataGrid.Initialize (cognitive 78)src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1066
BindingManager.UpdateSourcePropertyInternal (cognitive 68)src/dev/Core/Components/BindingManager/BindingManager.vb:424
BindableDataGridView.Value.Set (cognitive 66)src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:515
DataSourceTypeUIForm.UpdateTreeView (cognitive 57)src/dev/Core/Components/MvvmManager/UI/DataSourceTypeUIForm.vb:114
GridPanelLayout.Layout (cognitive 53)src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:21

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

What to do

  1. Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with MvvmDataGrid.Initialize (cognitive 78), BindingManager.UpdateSourcePropertyInternal (cognitive 68), BindableDataGridView.Value.Set (cognitive 66). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.3 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.1 / 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.1 / 10 · rule-coverage 100% · ceiling Prevented

26 god class(es) detected.

FileTooLong: NullableRelationPopup/NullableValueRelationPopup.vb · ×8src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb
MethodTooLong: BindingManager.UpdateSourcePropertyInternal · ×7src/dev/Core/Components/BindingManager/BindingManager.vb:424
ClassTooLong: ColoredTextPanel · ×6src/dev/Core/Controls/StandardControls/ColoredTextPanel.vb
TooManyMethods: NullableValueRelationPopup · ×5src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb

What to do

  1. Resolve the 8 FileTooLong finding(s) in God Classes — start with NullableValueRelationPopup.vb, NullableValueBase.vb, MvvmDataGrid.vb. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 MethodTooLong finding(s) in God Classes — start with BindingManager.vb (2), RangeClockGauge.vb, DemoData.cs. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 6 ClassTooLong finding(s) in God Classes — start with ColoredTextPanel.vb, BindableDataGridView.vb, BindingManager.vb. — 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 Duplication7.8 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

34 duplicated block group(s) detected. 5.4 % of the production lines (2,133 of 39,587) are in a reported copy. A further 39 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 73 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (13 lines × 2) · ×4src/dev/Core/Controls/NullableControls/NullableIntValue.vb:339
Edited copy of a member (27 corresponding lines) · ×3src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:62
Edited copy of a member (5 corresponding lines) · ×3src/dev/Core/Controls/NullableControls/NullableIntValue.vb:288
Edited copy of a member (12 corresponding lines) · ×2src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:2420
Duplicated block (21 lines × 3) · ×2src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:81

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

What to do

  1. Resolve the 4 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with NullableValueBase.vb (2), NullableIntValue.vb, ResizablePopup.vb. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Edited copy of a member (27 corresponding lines) finding(s) in Code Duplication — start with CodeFixProvider.vb, frmMvvmPropertyAssignmentEx.vb, ObjectEventAssignmentsClasses.vb. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with NullableIntValue.vb (2), TextBoxButtonBase.vb. — One of this dimension's main actionable groups (3 warning-level).

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

D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: MvvmBaseLib.NetStandardsrc/dev/MvvmBaseLib/MvvmBaseLib.NetStandard/MvvmBaseLib.NetStandard.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with MvvmBaseLib.NetStandard.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

D6 · Cohesion (LCOM4)8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Verified

11 of 100 classes have LCOM4 above 3.

Low cohesion: ObservableBindingList (LCOM4 9) · ×11src/dev/Core/AuxilliaryTypes/ObservableBindingList.vb:45

What to do

  1. Resolve the 11 Low cohesion finding(s) in Cohesion (LCOM4) — start with ObservableBindingList.vb, FormulaEvaluator.cs, NullableValueRelationPopup.vb. — One of this dimension's main actionable groups (11 warning-level).

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

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.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 139 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 5 direct `PackageReference`(s), and 108 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.

✓ 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 Debt7.9 / 10Adequategated by 17 critical findings✓ 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 7.9 / 10 · rule-coverage 100% · ceiling Prevented

112 deducted debt markers + unmeasured dead symbols across 39587 LoC in the .NET projects (1.0/KLoC) → score 7.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×13src/dev/Core/BaseForms/AnimationFormBase.vb:342
WriteOnlyPrivateField · ×2src/dev/MvvmBaseLib/MvvmBaseLibShared/Async/Timer.cs:12
InvertedNullGuardsrc/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmPageNavigator.vb:37
NoWarnInCsproj repeated 12 times in 2 filessrc/dev/Samples/MvvmCalculator/ModernMvvmCalculator/ModernMvvmCalculator.csproj:26
TodoComment · ×52src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:278

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

What to do

  1. Resolve the 13 EmptyCatchBlock finding(s) in Explicit Debt — start with MvvmDataGrid.vb (3), BindingManager.vb (2), NullableValueRelationPopup.vb (2). — One of this dimension's main actionable groups (13 issue-level).
  2. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with Timer.cs, MvvmViewModelBase.cs. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 InvertedNullGuard finding(s) in Explicit Debt — start with WinFormsMvvmPageNavigator.vb. — One of this dimension's main actionable groups (1 issue-level).

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

D18 · Solution Shape9.6 / 10Stronggated by 2 serious findings✓ 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.6 / 10 · rule-coverage 100% · ceiling Documented

28 projects, 490 source files, 42210 hand-written lines of code (39587 production / 2623 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 9356 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 29 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 5 solutions loaded as one workspace: `src/dev/CoreTestAndDev.sln`, `src/dev/MeterReaderMvvmForms.sln`, `src/dev/MvvmCalculator.sln`, `src/dev/ArtificalHorizonOffRoadIoC.sln`, `src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln`.

Solution references a project that does not existsrc/dev/MeterReaderMvvmForms.sln
Solution references 3 projects that do not existsrc/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln
Thin analysable surface across projects: MvvmViewModelCalculatorTest · ×3src/dev/Samples/MvvmCalculator/MvvmViewModelCalculatorTest/MvvmViewModelCalculatorTest.vbproj

What to do

  1. Resolve the 3 Thin analysable surface across projects finding(s) in Solution Shape — start with MvvmViewModelCalculatorTest.vbproj, MvvmAutheticationLocator.vbproj, ArtHorizViewModel.vbproj. — One of this dimension's main actionable groups (3 recommendation-level).
  2. Resolve the 1 Solution references a project that does not exist finding(s) in Solution Shape — start with MeterReaderMvvmForms.sln. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Solution references 3 projects that do not exist finding(s) in Solution Shape — start with MvvmFormsAnalyzer.sln. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality5.0 / 10Adequate✓ Tool-verified

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 5.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 2 documentation facets pass in full; short on: F2 example. 2 document(s) read across 6 unit(s).

Documentation: no build, run or usage exampleREADME.md:1

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 29% · ceiling Documented

65 of 228 judged comments only repeat the code they sit on (28.5 %). 843 comment(s) in another language or script were not judged.

redundant comment · ×65src/dev/Core/BaseForms/AnimationFormBase.vb:162
doc comments repeat the names · ×6src/dev/Legacy.EFLViewModelBase/MvvmViewModelClasses/IMvvmViewModel.vb:12

What to do

  1. Resolve the 65 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (29), AssemblyInfo.cs (12), AnimationFormBase.vb (2). — One of this dimension's main actionable groups (65 recommendation-level).

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

D26 · Project Cohesion9.3 / 10Exemplary✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 28 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/dev/Core/MvvmForms.vbproj:1

✓ On the Gold path — maintain.

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D30 · Dependency Vulnerabilities6.2 / 10Adequate✓ Tool-verified

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 6.2 / 10 · rule-coverage 100% · ceiling Documented

7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (nuget REDACTED), 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.

REDACTED

What to do

  1. Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).

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

D34 · Knowledge Freshness9.3 / 10Adequategated by 3 critical findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

10 of 138 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb. Counted over 138 of the 279 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×3src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1
Orphaned file · ×7src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:1
Further orphaned files (smaller)

What to do

  1. Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with MvvmDataGrid.vb, NullableValueComboBox.vb, BindableTreeView.vb. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with frmMvvmPropertyAssignmentRev.vb, SimpleCalculator.vb, ucBindingTreeview.xaml.vb. — One of this dimension's main actionable groups (7 recommendation-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_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-Life10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.9 / 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.

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.

  • `FormulaEvaluator` 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 (myXVariable, myYVariable, myZVariable; e.g. `myXVariable` at line 144). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/dev/MvvmBaseLib/MvvmBaseLibShared/FormulaEvaluator/FormulaEvaluator.cs:13

What to do

  • 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 ActiveDevelop.MvvmBaseLib ↔ ActiveDevelop.MvvmBaseLib.Mvvm depend on each other. The lightest dependency in the cycle is ActiveDevelop.MvvmBaseLib → ActiveDevelop.MvvmBaseLib.Mvvm (ActiveDevelop.MvvmBaseLib.BindableAsyncLazy → ActiveDevelop.MvvmBaseLib.Mvvm.IDiscoverableValue, 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/dev/MvvmBaseLib/MvvmBaseLibShared/Async/BindableAsyncLazy.cs:6

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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.

GD1 · Unfinished & placeholder code9.9 / 10Exemplary✓ Tool-verified

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. (×5) — src/dev/Samples/MvvmCalculator/MvvmCalculator/Converter/StringNotEmptyToColorConverter.cs:22, src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBooleanConverter.cs:13, src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBrushConverter.cs:22, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
M1 · Documentation (README)6.6 / 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.

  • This repository declares its own end of life: `README.md` line 14 reads “Note: We never ported MvvmForms to .NET (Core, .NET 3.1+) - so, it's only available for NetFx. Also note, that this repo is no longer actively maintained, but feel free to port it and use it in any shape and form you like.”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on. — README.md:14

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M3 · Folder & project structure10.0 / 10Exemplary✓ 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.

P2 · Observability5.6 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 9/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
P6 · Release Hygiene8.0 / 10Exemplary✓ 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.

  • The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
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.

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 (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

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 Health78%StrongSolid.
Architecture65%Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity84%ExemplarySolid.
Readiness74%ExemplarySolid.
Security100%ExemplaryStrongest area.
Performance100%ExemplarySolid.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
  • AX6 Interface segregation — AX6 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — This is a dotnet-new template — at-rest encryption and key-vaulting are deferred to the application you build from it. Add ASP.NET Data Protection / column encryption + a key vault for your real data store when you productionise.
  • C2 Access Controls — This is a dotnet-new template — authorization is deferred to the application you build from it. Add [Authorize]/policies (or imperative guards) when you wire up real users; until then there are no real endpoints to protect.
  • D10 Test Quality — ~4858 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not measured — no test run produced results
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D21 Naming Consistency — Naming consistency does not read Visual Basic yet; not measured.
  • 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) — 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.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
  • 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
  • IC1 Incompleteness & stubs — IC1 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • M2 Architecture documentation — This repo declares itself a template / kata / sample / demo — formal architecture documentation (ADRs, C4 diagrams) is deferred to a real application built from it, so its absence is not a defect here.
  • M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
  • P1 CI/CD gates — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. Automated CI/CD gates are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P12 CI test-gate honesty — no CI workflow found
  • P3 Security & performance tooling — This repo declares itself a template / kata / sample / demo — code meant to be read or copied, not operated. SAST, secret/dependency scanning and performance benchmarks are deferred to the application you build from it, so their absence is not a defect here. The dimension reactivates once the repo becomes a real app.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X1 Async correctness — X1 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X12 Unreachable branch — X12 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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
  • X18 Disposal-pattern correctness — X18 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — X2 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X27 Collection changed while being enumerated — X27 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — X29 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X3 Exception handling — X3 reached only 6% of this repository's production lines — vbnet (35,782 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X30 Support guard that admits what it rejects — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X5 Nullable reference types — no NRT-eligible projects
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 28 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×13
  • EmptyCatchBlock src/dev/Core/BaseForms/AnimationFormBase.vb:342 — 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/dev/Core/Components/BindingManager/BindingManager.vb:495 — 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/dev/Core/Components/BindingManager/BindingManager.vb:651 — 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/dev/Core/Components/MvvmManager/UI/frmManageBindings.vb:127 — 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/dev/Core/ContainerAndPanels/GridPanel/GridPanel.vb:33 — 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/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1494 — 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/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1502 — 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/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1509 — 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/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:773 — 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/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:802 — 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/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb:366 — 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/dev/Samples/MvvmCalculator/MvvmCalculator/FunctionPlotter/FunctionPlotterRenderer.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/dev/Samples/MvvmCalculator/MvvmCalculatorVMLib/FunctionPlotterViewModel.vb:164 — 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.
D30 · Dependency Vulnerabilities · High CVE · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×3
  • Orphaned knowledge src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge src/dev/Core/Controls/MvvmControls/NullableValueComboBox/NullableValueComboBox.vb:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge src/dev/Core/Controls/MvvmControls/BindableTreeView.vb:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField src/dev/MvvmBaseLib/MvvmBaseLibShared/Async/Timer.cs:12 — private Task myTimerTask — 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/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:20 — private Dictionary<string, string> myErrorDictionary — 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.
AX3 · Project dependency cycles · Namespace dependency cycle · ×1
  • Namespace dependency cycle src/dev/MvvmBaseLib/MvvmBaseLibShared/Async/BindableAsyncLazy.cs:6 — The namespaces ActiveDevelop.MvvmBaseLib ↔ ActiveDevelop.MvvmBaseLib.Mvvm depend on each other. The lightest dependency in the cycle is ActiveDevelop.MvvmBaseLib → ActiveDevelop.MvvmBaseLib.Mvvm (ActiveDevelop.MvvmBaseLib.BindableAsyncLazy → ActiveDevelop.MvvmBaseLib.Mvvm.IDiscoverableValue, 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.
D17 · Explicit Debt · InvertedNullGuard · ×1
  • InvertedNullGuard src/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmPageNavigator.vb:37 — If newForm IsNot Nothing Then … newForm.GetType — the guard has already decided this variable is null on the way into this branch, and nothing here gives it another value, so this dereference cannot run without throwing a NullReferenceException. It survives because the branch is the uncommon one: the code is correct on every input where the variable is set, and crashes on exactly the case the branch was written to handle. Decide which the line meant — if it is reporting the absence, it must not read through the missing value (use the other variable that identifies it, or a literal); if it is meant to work on a value, it belongs in the other branch.
D17 · Explicit Debt · NoWarnInCsproj repeated 12 times in 2 files · ×1
  • NoWarnInCsproj repeated 12 times in 2 files src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/ModernMvvmCalculator.csproj:26 — The identical NoWarnInCsproj (`2008`) appears 12 times in 2 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 12 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
Serious — 272 finding(s)
D17 · Explicit Debt · TodoComment · ×52
  • TodoComment src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:278 — 'TODO: Sicherstellen, dass beim Initialen binden ebenfalls die Werte neu geschrieben werden, nicht nur beim ersten PropertyChange. — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:299 — 'TODO: Bereits vorhandene Bindungen lösen. — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:449 — 'TODO: Tritt dieser Fall auf? — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:464 — 'TODO: Tritt dieser Fall auf? — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:472 — 'TODO: Tritt dieser Fall auf? — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:511 — 'TODO: Tritt dieser Fall auf? — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:524 — 'TODO: Tritt dieser Fall auf? — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/PropertyBindingClasses.vb:128 — 'TODO: Converter ist ein Type - das wird nicht funktionieren. — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/PropertyBindingClasses.vb:146 — 'TODO: Hier müsste der Timer neu gesetzt werden für die verzögerte Auslösung von PropertyChanged. — 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/dev/Core/Components/MvvmManager/MvvmManager.vb:789 — ' 'TODO: Feststellen, ob es ein UserControl ist, und im Bedarfsfall ein Wrapper-Form zurückliefern. — 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/dev/Core/Components/MvvmManager/UI/ViewModelPropertyComboBox.vb:102 — 'TODO: wieso muss hier ne neue angelegt werden, mit obs.col sollte dorch das auch gehen?!?! — 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/dev/Core/Components/MvvmManager/UI/frmManageBindings.vb:118 — ' TODO: works. -> Check for further corner cases, though! — 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/dev/Core/Components/MvvmManager/UI/frmMvvmEventAssignment.vb:38 — 'TODO: This feature has not implemented, yet. It is just a basic skeleton, based on the PropertyBindings. — 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/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:405 — 'TODO: Fill out! — 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/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:450 — 'TODO: Load Tree only selective (via Path)! — 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/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:48 — 'TODO: Müssen wir hier irgendwas machen? — 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/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:202 — 'TODO: Draw via DrawString. — 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/dev/Core/Controls/Interfaces/IPermissionManageableElements.vb:118 — 'TODO: Rekursiv alle betroffenen Steuerelemente im Formular einkassieren und zurückliefern. — 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/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb:279 — 'TODO: SelectedValuePath fehlt. — 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/dev/Core/Controls/MvvmControls/MvvmDataGrid/Designer/MvvmDataGridDesigner.vb:67 — 'TODO: Column-Editor aufrufen. — 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/dev/Core/Controls/MvvmControls/NullableValueComboBox/NullableValueComboBox.vb:71 — 'TODO: Überprüfen, ob es nicht doch Fälle gibt, bei dem der Fokus erzwungener Maßen erhalten bleiben soll. — 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/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:184 — 'TODO: Überprüfen, ob es nicht doch Fälle gibt, bei dem der Fokus erzwungener Maßen erhalten bleiben soll. — 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/dev/Core/Controls/MvvmControls/NullableValueComboBox/NullableValueComboBox.vb:126 — 'TODO: noch implementieren — 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/dev/Core/Controls/MvvmControls/NullableValueComboBox/NullableValueComboBox.vb:452 — 'TODO: Was soll ich denn hier setzen? (Später vielleicht wenn die Lisete bei EIngaeb keliner werden soll...) — 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/dev/Core/Controls/NullableControls/NullableDateValue.vb:239 — 'TODO: Naming-Problem? Soll es DisplayFormat oder Format heißen? — 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.
  • + 27 more in this group — see findings.md.
D6 · Cohesion (LCOM4) · Low cohesion · ×11
  • Low cohesion: ObservableBindingList (LCOM4 9) src/dev/Core/AuxilliaryTypes/ObservableBindingList.vb:45 — ObservableBindingList's methods fall into 9 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 9 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: FormulaEvaluator (LCOM4 8) src/dev/MvvmBaseLib/MvvmBaseLibShared/FormulaEvaluator/FormulaEvaluator.cs:13 — FormulaEvaluator's methods fall into 8 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 8 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: NullableValueRelationPopup (LCOM4 7) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:20 — NullableValueRelationPopup's methods fall into 7 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 7 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: BindableDataGridView (LCOM4 5) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:13 — BindableDataGridView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: NullableDateValue (LCOM4 5) src/dev/Core/Controls/NullableControls/NullableDateValue.vb:11 — NullableDateValue's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: MonthCalendarEx (LCOM4 5) src/dev/Core/Controls/StandardControls/MonthCalendarEx.vb:5 — MonthCalendarEx's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: TooltipEx (LCOM4 4) src/dev/Core/Controls/TooltipEx/TooltipEx.vb:11 — TooltipEx'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.
  • Low cohesion: NullableNumValue (LCOM4 4) src/dev/Core/Controls/NullableControls/NullableNumValue.vb:9 — NullableNumValue'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.
  • Low cohesion: NullableValueBase (LCOM4 4) src/dev/Core/Controls/NullableControls/NullableValueBase.vb:29 — NullableValueBase'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.
  • Low cohesion: BindableBase (LCOM4 4) src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:11 — BindableBase'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.
  • Low cohesion: MvvmViewModelBase (LCOM4 4) src/dev/Legacy.EFLViewModelBase/MvvmViewModelClasses/MvvmViewModelBase.vb:8 — MvvmViewModelBase'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.
D17 · Explicit Debt · CommentedOutCode · ×9
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBooleanConverter.cs:26 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBooleanConverter.cs:31 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBrushConverter.cs:38 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBooleanConverter.cs:26 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBooleanConverter.cs:31 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBrushConverter.cs:38 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/FunctionPlotter/FunctionPlotterRenderer.xaml.cs:88 — 4 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBrushConverter.cs:30 — 7 consecutive commented-code lines
  • CommentedOutCode src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBrushConverter.cs:30 — 7 consecutive commented-code lines
D3 · God Classes · FileTooLong · ×8
  • FileTooLong: NullableRelationPopup/NullableValueRelationPopup.vb src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb — FileTooLong — 1711 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1211 over it, 3.42× 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: NullableControls/NullableValueBase.vb src/dev/Core/Controls/NullableControls/NullableValueBase.vb — FileTooLong — 1297 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 797 over it, 2.59× 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: MvvmDataGrid/MvvmDataGrid.vb src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb — FileTooLong — 954 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 454 over it, 1.91× 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: Column/MvvmDataGridColumn.vb src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb — FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 270 over it, 1.54× 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: NullableRelationPopup/BindableDataGridView.vb src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb — FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 173 over it, 1.35× 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: BindingManager/BindingManager.vb src/dev/Core/Components/BindingManager/BindingManager.vb — FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 149 over it, 1.30× 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: NullableControls/NullableNumValue.vb src/dev/Core/Controls/NullableControls/NullableNumValue.vb — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× 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: MvvmForms.UnitTests/MvvmPropertyBindingAssignmentTest.vb src/dev/MvvmForms.UnitTests/MvvmPropertyBindingAssignmentTest.vb — FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 36 over it, 1.07× 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.
D17 · Explicit Debt · BarePragmaDisable · ×7
  • BarePragmaDisable src/dev/Core/AuxilliaryTypes/ReflectionHelper.vb:142 — #Disable Warning — 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/dev/Core/Components/MvvmManager/ClassesAndStructures/PropertyBindingClasses.vb:38 — #Disable Warning — 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/dev/Core/Components/MvvmManager/MvvmManager.vb:543 — #Disable Warning — 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/dev/MvvmForms.UnitTests/TestDataClasses/DemoData.vb:37 — #Disable Warning — 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/dev/MvvmForms.UnitTests/TestDataClasses/DemoData.vb:110 — #Disable Warning — 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/dev/MvvmForms.UnitTests/TestDataClasses/DemoData.vb:147 — #Disable Warning — 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/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/Experimental/RxCollectionView.cs:118 — #pragma warning disable 1591 — 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.
D3 · God Classes · MethodTooLong · ×7
  • MethodTooLong: BindingManager.UpdateSourcePropertyInternal src/dev/Core/Components/BindingManager/BindingManager.vb:424 — MethodTooLong — UpdateSourcePropertyInternal runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: RangeClockGauge.DrawClockInternally src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:25 — MethodTooLong — DrawClockInternally runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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: Contact.RandomContacts src/dev/MvvmFormsCSharpDemos/DemoData/DemoData.cs:184 — MethodTooLong — RandomContacts runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× 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: GridPanelLayout.Layout src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:21 — MethodTooLong — Layout runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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: BindingManager.UpdateTargetPropertyInternal src/dev/Core/Components/BindingManager/BindingManager.vb:291 — MethodTooLong — UpdateTargetPropertyInternal runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: NullableValueRelationPopup.New(…) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:200 — MethodTooLong — New(…) runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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: ObjectAnalyser.GetValMethods src/dev/Core/AuxilliaryTypes/ObjectAnalyzer.vb:253 — MethodTooLong — GetValMethods runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · ClassTooLong · ×6
  • ClassTooLong: ColoredTextPanel src/dev/Core/Controls/StandardControls/ColoredTextPanel.vb — ClassTooLong — 889 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 489 over it, 2.22× 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: BindableDataGridView src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb — ClassTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 259 over it, 1.65× 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: BindingManager src/dev/Core/Components/BindingManager/BindingManager.vb — ClassTooLong — 595 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 195 over it, 1.49× 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: NullableNumValue src/dev/Core/Controls/NullableControls/NullableNumValue.vb — ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 150 over it, 1.38× 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: ResizablePopup src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 12 over it, 1.03× 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: BindableTreeView src/dev/Core/Controls/MvvmControls/BindableTreeView.vb — ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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.
D17 · Explicit Debt · ObsoleteWithCallers · ×5
  • ObsoleteWithCallers src/dev/Core/Components/MvvmManager/ClassesAndStructures/CodeSerializing/PropertyBindingsCodeDomeSerializer.vb:38 — <Obsolete> PropertyBindingsCodeDomSerializer
  • ObsoleteWithCallers src/dev/Core/Controls/Interfaces/IPermissionManageableElements.vb:66 — <Obsolete> PermissionManageableControlInfo
  • ObsoleteWithCallers src/dev/Legacy.EFLViewModelBase/DataContextAssigner.vb:3 — <Obsolete> PropertyAssignmentAttributeBase
  • ObsoleteWithCallers src/dev/Legacy.EFLViewModelBase/MvvmViewModelClasses/IMvvmViewModel.vb:34 — <Obsolete> InitializeViewModel
  • ObsoleteWithCallers src/dev/MvvmBaseLib/MvvmBaseLibShared/IoCPlatformDependend/IMvvmViewModelNotifyBindingProcess.cs:9 — [Obsolete] IMvvmViewModelNotifyBindingProcess
D17 · Explicit Debt · HackComment · ×5
  • HackComment src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:562 — 'HACK: Dieses Handling benötigen wir, da eine aufgeklappte Instanz des Popups "verloren" gehen kamm. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:1075 — 'HACK: Das könnte an dieser Stelle schon redundant sein: — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:187 — 'Hack: that's not safe enough. Only if method's name ends with it, remove it. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/dev/MvvmForms.UnitTests/Calculator/SimpleCalcTests.vb:13 — ' HACK wegen der Exception: — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/dev/Samples/MeterReaderMvvmForms/MRViewModelLibrary/ViewModels/BuildingViewModel.vb:47 — 'Hack: Here, we have to return the proper next ID! :-S — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: NullableValueRelationPopup src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb — TooManyMethods — 1691 significant lines (blank, comment-only and punctuation-only lines excluded), 79 methods. The bar is 30 methods; this is 49 over it, 2.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: NullableValueBase src/dev/Core/Controls/NullableControls/NullableValueBase.vb — TooManyMethods — 1289 significant lines (blank, comment-only and punctuation-only lines excluded), 78 methods. The bar is 30 methods; this is 48 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MvvmDataGrid src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb — TooManyMethods — 940 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextBoxPopup src/dev/Core/Controls/StandardControls/TextBoxPopup/TextBoxPopup.vb — TooManyMethods — 387 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 30 methods; this is 7 over it, 1.23× 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: MvvmDataGridColumn src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb — TooManyMethods — 756 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 30 methods; this is 1 over it, 1.03× 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×5
  • Unfinished stub — throws NotImplementedException src/dev/Samples/MvvmCalculator/MvvmCalculator/Converter/StringNotEmptyToColorConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBooleanConverter.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/Converter/StringNotEmptyToBrushConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBooleanConverter.cs:13 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/Converter/StringNotEmptyToBrushConverter.cs:22 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×4
  • Duplicated block (13 lines × 2) src/dev/Core/Controls/NullableControls/NullableIntValue.vb:339 — src/dev/Core/Controls/NullableControls/NullableIntValue.vb:339-351 | src/dev/Core/Controls/NullableControls/NullableNumValue.vb:238-250 — before extracting anything, compare `src/dev/Core/Controls/NullableControls/NullableIntValue.vb` and `src/dev/Core/Controls/NullableControls/NullableNumValue.vb` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) src/dev/Core/Controls/NullableControls/NullableValueBase.vb:313 — src/dev/Core/Controls/NullableControls/NullableValueBase.vb:313-325 | src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:244-256 — 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 (13 lines × 2) src/dev/Core/Controls/NullableControls/NullableValueBase.vb:437 — src/dev/Core/Controls/NullableControls/NullableValueBase.vb:437-449 | src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:349-361 — 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 (13 lines × 2) src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:358 — src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:358-370 | src/dev/Core/Controls/TooltipEx/TooltipEx.vb:214-226 — 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 · Edited copy of a member (27 corresponding lines) · ×3
  • Edited copy of a member (27 corresponding lines) src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:62 — src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:62-88 | src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:174-208 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:136 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:136-162 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:126-152 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb:188 — src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb:188-224 | src/dev/Core/ExtenderMethods/GroupFunctionalityExtender.vb:208-234 — These two members are one piece of code written twice and then edited apart: 27 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 (5 corresponding lines) · ×3
  • Edited copy of a member (5 corresponding lines) src/dev/Core/Controls/NullableControls/NullableIntValue.vb:288 — src/dev/Core/Controls/NullableControls/NullableIntValue.vb:288-292 | src/dev/Core/Controls/NullableControls/NullableNumValue.vb:453-457 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/dev/Core/Controls/NullableControls/NullableIntValue.vb:319 — src/dev/Core/Controls/NullableControls/NullableIntValue.vb:319-323 | src/dev/Core/Controls/NullableControls/NullableNumValue.vb:483-487 — These two members are one piece of code written twice and then edited apart: 5 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 (5 corresponding lines) src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:147 — src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:147-151 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:276-280 — These two members are one piece of code written twice and then edited apart: 5 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) · ×2
  • Edited copy of a member (12 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:2420 — src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:2420-2431 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:1804-1816 — 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.
  • Edited copy of a member (12 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb:260 — src/dev/Core/Controls/TooltipEx/TooltipEx.vb:260-271 | src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:532-543 — 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 (21 lines × 3) · ×2
  • Duplicated block (21 lines × 3) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:81 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:81-101 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:81-101 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:110-130 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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 (21 lines × 3) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:256 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:256-276 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:262-282 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:155-175 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb:199 — src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb:199-220 | src/dev/Core/ExtenderMethods/GroupFunctionalityExtender.vb:210-231 — 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/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmMessageBox.vb:22 — src/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmMessageBox.vb:22-43 | src/dev/WinForms.MvvmServiceLocatorBase/UI/WinFormsMvvmMessageBox.vb:113-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) src/dev/Core/AuxilliaryTypes/ObservableBindingList.vb:124 — src/dev/Core/AuxilliaryTypes/ObservableBindingList.vb:124-143 | src/dev/Core/AuxilliaryTypes/ObservableCollectionBindingListAdapter.vb:47-66 — 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 (20 lines × 2) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:126 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:126-145 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:136-155 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:344 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:344-354 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:350-360 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:243-253 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:344` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 3) src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64 — src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64-75 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridCustomColumnTemplateTypeUIEditor.vb:28-38 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridDataSourceTypeUIEditor.vb:37-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:63` calls `EditValue` and `src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridCustomColumnTemplateTypeUIEditor.vb:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:212 — src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:212-219 | src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:326-333 — 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/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:212` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:137 — src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:137-144 | src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:145-152 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridCustomColumnTemplateTypeUIEditor.vb:39 — src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridCustomColumnTemplateTypeUIEditor.vb:39-43 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridDataSourceTypeUIEditor.vb:49-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:426 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:426-430 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:438-442 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
AX2 · Stateful singletons · Process-global static state · ×1
  • Process-global static state: FormulaEvaluator src/dev/MvvmBaseLib/MvvmBaseLibShared/FormulaEvaluator/FormulaEvaluator.cs:13 — `FormulaEvaluator` 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 (myXVariable, myYVariable, myZVariable; e.g. `myXVariable` at line 144). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D1 · Cyclomatic Complexity · BindingManager.UpdateSourcePropertyInternal (cyclomatic 38) · ×1
  • BindingManager.UpdateSourcePropertyInternal (cyclomatic 38) src/dev/Core/Components/BindingManager/BindingManager.vb:424 — BindingManager.UpdateSourcePropertyInternal has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: src/dev/Core/Components/BindingManager/BindingManager.vb holds 3 of the 23 methods over the threshold — including the worst — and 41 of the 124 points over it (33%), 3.2× the next-largest file (src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · GridPanelLayout.Layout (cyclomatic 28) · ×1
  • GridPanelLayout.Layout (cyclomatic 28) src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:21 — GridPanelLayout.Layout has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · BindingManager.UpdateTargetPropertyInternal (cyclomatic 25) · ×1
  • BindingManager.UpdateTargetPropertyInternal (cyclomatic 25) src/dev/Core/Components/BindingManager/BindingManager.vb:291 — BindingManager.UpdateTargetPropertyInternal has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: src/dev/Core/Components/BindingManager/BindingManager.vb holds 3 of the 23 methods over the threshold — including the worst — and 41 of the 124 points over it (33%), 3.2× the next-largest file (src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · BindingManager.HandleFullPathDataErrorsChangedInternal (cyclomatic 23) · ×1
  • BindingManager.HandleFullPathDataErrorsChangedInternal (cyclomatic 23) src/dev/Core/Components/BindingManager/BindingManager.vb:604 — BindingManager.HandleFullPathDataErrorsChangedInternal has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: src/dev/Core/Components/BindingManager/BindingManager.vb holds 3 of the 23 methods over the threshold — including the worst — and 41 of the 124 points over it (33%), 3.2× the next-largest file (src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb at 13). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · BindableDataGridView.Value.Set (cyclomatic 22) · ×1
  • BindableDataGridView.Value.Set (cyclomatic 22) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:515 — BindableDataGridView.Value.Set has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ReflectionHelper.CreateSubPropsAsList (cyclomatic 21) · ×1
  • ReflectionHelper.CreateSubPropsAsList (cyclomatic 21) src/dev/Core/AuxilliaryTypes/ReflectionHelper.vb:81 — ReflectionHelper.CreateSubPropsAsList has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MvvmDataGridColumn.InitializeColumn (cyclomatic 21) · ×1
  • MvvmDataGridColumn.InitializeColumn (cyclomatic 21) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb:128 — MvvmDataGridColumn.InitializeColumn has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MvvmDataGrid.Initialize (cyclomatic 21) · ×1
  • MvvmDataGrid.Initialize (cyclomatic 21) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1066 — MvvmDataGrid.Initialize has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler (cyclomatic 20) · ×1
  • frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler (cyclomatic 20) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:163 — frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NullableValueRelationPopup.GetPreferredWidthInternal (cyclomatic 20) · ×1
  • NullableValueRelationPopup.GetPreferredWidthInternal (cyclomatic 20) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:895 — NullableValueRelationPopup.GetPreferredWidthInternal has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TimeRange.OverlappingSpanInfo (cyclomatic 20) · ×1
  • TimeRange.OverlappingSpanInfo (cyclomatic 20) src/dev/MvvmBaseLib/MvvmBaseLibShared/TimeLib/TimeRange.cs:132 — TimeRange.OverlappingSpanInfo has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler (cyclomatic 19) · ×1
  • frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler (cyclomatic 19) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:174 — frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MvvmDataGrid.CreateColumnsDataSourceType (cyclomatic 19) · ×1
  • MvvmDataGrid.CreateColumnsDataSourceType (cyclomatic 19) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:818 — MvvmDataGrid.CreateColumnsDataSourceType has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · MvvmBindingItemsCodeDomSerializer.SerializeCollection (cyclomatic 18) · ×1
  • MvvmBindingItemsCodeDomSerializer.SerializeCollection (cyclomatic 18) src/dev/Core/Components/MvvmManager/ClassesAndStructures/CodeSerializing/MvvmBindingItemsCodeDomSerializer.vb:42 — MvvmBindingItemsCodeDomSerializer.SerializeCollection has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · DataSourceTypeUIForm.UpdateTreeView (cyclomatic 18) · ×1
  • DataSourceTypeUIForm.UpdateTreeView (cyclomatic 18) src/dev/Core/Components/MvvmManager/UI/DataSourceTypeUIForm.vb:114 — DataSourceTypeUIForm.UpdateTreeView has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · frmEntityObjectSelector.ShowDialog (cyclomatic 18) · ×1
  • frmEntityObjectSelector.ShowDialog (cyclomatic 18) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:35 — frmEntityObjectSelector.ShowDialog has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewPanel.OnPaint (cyclomatic 18) · ×1
  • ViewPanel.OnPaint (cyclomatic 18) src/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb:248 — ViewPanel.OnPaint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SimpleCalculator.SetResultInternal (cyclomatic 18) · ×1
  • SimpleCalculator.SetResultInternal (cyclomatic 18) src/dev/Core/Controls/StandardControls/SimpleCalculator.vb:135 — SimpleCalculator.SetResultInternal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: SimpleCalculator.ProcessKeyDown (cyclomatic 65) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · MvvmDataGrid.AddNewColumn (cyclomatic 18) · ×1
  • MvvmDataGrid.AddNewColumn (cyclomatic 18) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:719 — MvvmDataGrid.AddNewColumn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ObjectAnalyser.GetValMethods (cyclomatic 16) · ×1
  • ObjectAnalyser.GetValMethods (cyclomatic 16) src/dev/Core/AuxilliaryTypes/ObjectAnalyzer.vb:253 — ObjectAnalyser.GetValMethods has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · frmEntityObjectSelector.FillEntityOrBusinessObjects (cyclomatic 16) · ×1
  • frmEntityObjectSelector.FillEntityOrBusinessObjects (cyclomatic 16) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:146 — frmEntityObjectSelector.FillEntityOrBusinessObjects has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RangeClockGauge.DrawClockInternally (cyclomatic 16) · ×1
  • RangeClockGauge.DrawClockInternally (cyclomatic 16) src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:25 — RangeClockGauge.DrawClockInternally has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NullableValueRelationPopup.OnPopupClosing (cyclomatic 16) · ×1
  • NullableValueRelationPopup.OnPopupClosing (cyclomatic 16) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:574 — NullableValueRelationPopup.OnPopupClosing has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D18 · Solution Shape · Solution references a project that does not exist · ×1
  • Solution references a project that does not exist src/dev/MeterReaderMvvmForms.sln — `src/dev/MeterReaderMvvmForms.sln` declares 1 project file(s) that are missing from the tree (`src/dev/MvvmBaseLib/MvvmBase/MvvmBaseLib.NET45.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
D18 · Solution Shape · Solution references 3 projects that do not exist · ×1
  • Solution references 3 projects that do not exist src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln — `src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer.sln` declares 3 project file(s) that are missing from the tree (`src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/MvvmFormsAnalyzer.Test/MvvmFormsAnalyzer.Test.vbproj`, `src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/MvvmFormsAnalyzer.Vsix/MvvmFormsAnalyzer.Vsix.vbproj`, `src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/MvvmFormsAnalyzer/MvvmFormsAnalyzer.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
D2 · Cognitive Complexity · MvvmDataGrid.Initialize (cognitive 78) · ×1
  • MvvmDataGrid.Initialize (cognitive 78) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1066 — MvvmDataGrid.Initialize has cognitive complexity 78 (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 · BindingManager.UpdateSourcePropertyInternal (cognitive 68) · ×1
  • BindingManager.UpdateSourcePropertyInternal (cognitive 68) src/dev/Core/Components/BindingManager/BindingManager.vb:424 — BindingManager.UpdateSourcePropertyInternal has cognitive complexity 68 (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 · BindableDataGridView.Value.Set (cognitive 66) · ×1
  • BindableDataGridView.Value.Set (cognitive 66) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:515 — BindableDataGridView.Value.Set has cognitive complexity 66 (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 · DataSourceTypeUIForm.UpdateTreeView (cognitive 57) · ×1
  • DataSourceTypeUIForm.UpdateTreeView (cognitive 57) src/dev/Core/Components/MvvmManager/UI/DataSourceTypeUIForm.vb:114 — DataSourceTypeUIForm.UpdateTreeView has cognitive complexity 57 (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 · GridPanelLayout.Layout (cognitive 53) · ×1
  • GridPanelLayout.Layout (cognitive 53) src/dev/Core/ContainerAndPanels/GridPanel/GridPanelLayout.vb:21 — GridPanelLayout.Layout has cognitive complexity 53 (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 · ReflectionHelper.CreateSubPropsAsList (cognitive 46) · ×1
  • ReflectionHelper.CreateSubPropsAsList (cognitive 46) src/dev/Core/AuxilliaryTypes/ReflectionHelper.vb:81 — ReflectionHelper.CreateSubPropsAsList 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 · frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler (cognitive 43) · ×1
  • frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler (cognitive 43) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:163 — frmMvvmPropertyAssignment.AddOrChangePropertyItemHandler 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 · MvvmDataGrid.UpdateFilterAddons (cognitive 42) · ×1
  • MvvmDataGrid.UpdateFilterAddons (cognitive 42) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1218 — MvvmDataGrid.UpdateFilterAddons has cognitive complexity 42 (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 · ValidatableBase.ValidateAsync (cognitive 41) · ×1
  • ValidatableBase.ValidateAsync (cognitive 41) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/Experimental/ValidatableBase.cs:14 — ValidatableBase.ValidateAsync has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MvvmBindingItemsCodeDomSerializer.SerializeCollection (cognitive 39) · ×1
  • MvvmBindingItemsCodeDomSerializer.SerializeCollection (cognitive 39) src/dev/Core/Components/MvvmManager/ClassesAndStructures/CodeSerializing/MvvmBindingItemsCodeDomSerializer.vb:42 — MvvmBindingItemsCodeDomSerializer.SerializeCollection has cognitive complexity 39 (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 · frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler (cognitive 39) · ×1
  • frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler (cognitive 39) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:174 — frmMvvmPropertyAssignmentEx.AddOrChangePropertyItemHandler has cognitive complexity 39 (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 · NullableValueRelationPopup.HandleSelectedValueChanged (cognitive 38) · ×1
  • NullableValueRelationPopup.HandleSelectedValueChanged (cognitive 38) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:455 — NullableValueRelationPopup.HandleSelectedValueChanged 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 · ViewPanel.OnPaint (cognitive 37) · ×1
  • ViewPanel.OnPaint (cognitive 37) src/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb:248 — ViewPanel.OnPaint 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 · BindingManager.HandleFullPathDataErrorsChangedInternal (cognitive 36) · ×1
  • BindingManager.HandleFullPathDataErrorsChangedInternal (cognitive 36) src/dev/Core/Components/BindingManager/BindingManager.vb:604 — BindingManager.HandleFullPathDataErrorsChangedInternal has cognitive complexity 36 (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 · BindingManager.UpdateTargetPropertyInternal (cognitive 35) · ×1
  • BindingManager.UpdateTargetPropertyInternal (cognitive 35) src/dev/Core/Components/BindingManager/BindingManager.vb:291 — BindingManager.UpdateTargetPropertyInternal has cognitive complexity 35 (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 · NullableValueRelationPopup.HandleKeyDownInternally (cognitive 34) · ×1
  • NullableValueRelationPopup.HandleKeyDownInternally (cognitive 34) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:812 — NullableValueRelationPopup.HandleKeyDownInternally has cognitive complexity 34 (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 · MvvmDataGrid.CreateColumnsDataSourceType (cognitive 34) · ×1
  • MvvmDataGrid.CreateColumnsDataSourceType (cognitive 34) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:818 — MvvmDataGrid.CreateColumnsDataSourceType has cognitive complexity 34 (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 · ObjectAnalyser.SearchExpression (cognitive 33) · ×1
  • ObjectAnalyser.SearchExpression (cognitive 33) src/dev/Core/AuxilliaryTypes/ObjectAnalyzer.vb:199 — ObjectAnalyser.SearchExpression has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ObjectAnalyser.GetValMethods (cognitive 33) · ×1
  • ObjectAnalyser.GetValMethods (cognitive 33) src/dev/Core/AuxilliaryTypes/ObjectAnalyzer.vb:253 — ObjectAnalyser.GetValMethods has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MvvmDataGrid.Columns_CollectionChanged (cognitive 32) · ×1
  • MvvmDataGrid.Columns_CollectionChanged (cognitive 32) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:659 — MvvmDataGrid.Columns_CollectionChanged 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 · NullableValueRelationPopup.GetPreferredWidthInternal (cognitive 30) · ×1
  • NullableValueRelationPopup.GetPreferredWidthInternal (cognitive 30) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:895 — NullableValueRelationPopup.GetPreferredWidthInternal 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 · frmEntityObjectSelector.ShowDialog (cognitive 29) · ×1
  • frmEntityObjectSelector.ShowDialog (cognitive 29) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:35 — frmEntityObjectSelector.ShowDialog 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 · BindableTreeView.DataSource_CollectionChanged (cognitive 29) · ×1
  • BindableTreeView.DataSource_CollectionChanged (cognitive 29) src/dev/Core/Controls/MvvmControls/BindableTreeView.vb:389 — BindableTreeView.DataSource_CollectionChanged 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 · MvvmViewModelBase.CopyPropertiesFromDifferentType (cognitive 29) · ×1
  • MvvmViewModelBase.CopyPropertiesFromDifferentType (cognitive 29) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:221 — MvvmViewModelBase.CopyPropertiesFromDifferentType 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 · BindingManager.AddControlsPropertyChangeEvents (cognitive 28) · ×1
  • BindingManager.AddControlsPropertyChangeEvents (cognitive 28) src/dev/Core/Components/BindingManager/BindingManager.vb:113 — BindingManager.AddControlsPropertyChangeEvents has cognitive complexity 28 (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 · MvvmViewModelBase.CopyPropertiesToDifferentType (cognitive 28) · ×1
  • MvvmViewModelBase.CopyPropertiesToDifferentType (cognitive 28) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:335 — MvvmViewModelBase.CopyPropertiesToDifferentType has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SimpleCalculator.SetResultInternal (cognitive 26) · ×1
  • SimpleCalculator.SetResultInternal (cognitive 26) src/dev/Core/Controls/StandardControls/SimpleCalculator.vb:135 — SimpleCalculator.SetResultInternal 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 · NullableValueRelationPopup.OnPopupClosing (cognitive 25) · ×1
  • NullableValueRelationPopup.OnPopupClosing (cognitive 25) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:574 — NullableValueRelationPopup.OnPopupClosing 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 · MvvmDataGrid.AddNewColumn (cognitive 25) · ×1
  • MvvmDataGrid.AddNewColumn (cognitive 25) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:719 — MvvmDataGrid.AddNewColumn 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 · frmEntityObjectSelector.FillEntityOrBusinessObjects (cognitive 23) · ×1
  • frmEntityObjectSelector.FillEntityOrBusinessObjects (cognitive 23) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:146 — frmEntityObjectSelector.FillEntityOrBusinessObjects has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MultiPurposeButtonBase.PaintSpinButton (cognitive 23) · ×1
  • MultiPurposeButtonBase.PaintSpinButton (cognitive 23) src/dev/Core/Controls/BaseAndHelperControls/UpDownComboBase.vb:230 — MultiPurposeButtonBase.PaintSpinButton has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AutoReportView.GetColumnNames (cognitive 23) · ×1
  • AutoReportView.GetColumnNames (cognitive 23) src/dev/Core/Controls/StandardControls/AutoReportView.vb:160 — AutoReportView.GetColumnNames has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MvvmManager.DataContext.Set (cognitive 22) · ×1
  • MvvmManager.DataContext.Set (cognitive 22) src/dev/Core/Components/MvvmManager/MvvmManager.vb:492 — MvvmManager.DataContext.Set has cognitive complexity 22 (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 · RangeClockGauge.DrawClockInternally (cognitive 22) · ×1
  • RangeClockGauge.DrawClockInternally (cognitive 22) src/dev/Core/Controls/DecoratingControls/RangeClockGauge/RangeClockGauge.vb:25 — RangeClockGauge.DrawClockInternally has cognitive complexity 22 (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 · FormulaEvaluator.Parse (cognitive 21) · ×1
  • FormulaEvaluator.Parse (cognitive 21) src/dev/MvvmBaseLib/MvvmBaseLibShared/FormulaEvaluator/FormulaEvaluator.cs:115 — FormulaEvaluator.Parse 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 · ObjectEventsAssignments.Add (cognitive 20) · ×1
  • ObjectEventsAssignments.Add (cognitive 20) src/dev/Core/Components/BindingManager/ObjectEventAssignmentsClasses.vb:60 — ObjectEventsAssignments.Add has cognitive complexity 20 (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 · ColoredTextPanel.doWrite (cognitive 20) · ×1
  • ColoredTextPanel.doWrite (cognitive 20) src/dev/Core/Controls/StandardControls/ColoredTextPanel.vb:394 — ColoredTextPanel.doWrite has cognitive complexity 20 (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 · MvvmDataGridColumn.InitializeColumn (cognitive 20) · ×1
  • MvvmDataGridColumn.InitializeColumn (cognitive 20) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb:128 — MvvmDataGridColumn.InitializeColumn has cognitive complexity 20 (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 · MvvmDataGridColumnsCodeDomSerializer.SerializeCollection (cognitive 20) · ×1
  • MvvmDataGridColumnsCodeDomSerializer.SerializeCollection (cognitive 20) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Common/MvvmDataGridColumnsCodeDomSerializer.vb:22 — MvvmDataGridColumnsCodeDomSerializer.SerializeCollection has cognitive complexity 20 (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 · PropertyBindingManager.WireUpPropertyChangeEvents (cognitive 19) · ×1
  • PropertyBindingManager.WireUpPropertyChangeEvents (cognitive 19) src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:487 — PropertyBindingManager.WireUpPropertyChangeEvents 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.
D2 · Cognitive Complexity · NullableNumValue.ToggleCalculator (cognitive 19) · ×1
  • NullableNumValue.ToggleCalculator (cognitive 19) src/dev/Core/Controls/NullableControls/NullableNumValue.vb:581 — NullableNumValue.ToggleCalculator 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.
D2 · Cognitive Complexity · TimeRange.OverlappingSpanInfo (cognitive 19) · ×1
  • TimeRange.OverlappingSpanInfo (cognitive 19) src/dev/MvvmBaseLib/MvvmBaseLibShared/TimeLib/TimeRange.cs:132 — TimeRange.OverlappingSpanInfo has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DataSourceTypeUIForm.UpdateFilter (cognitive 18) · ×1
  • DataSourceTypeUIForm.UpdateFilter (cognitive 18) src/dev/Core/Components/MvvmManager/UI/DataSourceTypeUIForm.vb:325 — DataSourceTypeUIForm.UpdateFilter has cognitive complexity 18 (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 · ColoredTextPanel.WriterThreadRun (cognitive 18) · ×1
  • ColoredTextPanel.WriterThreadRun (cognitive 18) src/dev/Core/Controls/StandardControls/ColoredTextPanel.vb:341 — ColoredTextPanel.WriterThreadRun has cognitive complexity 18 (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 · ResizablePopup.PreFilterMessage (cognitive 18) · ×1
  • ResizablePopup.PreFilterMessage (cognitive 18) src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:213 — ResizablePopup.PreFilterMessage has cognitive complexity 18 (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 · MvvmDataGrid.FilterColumnValue (cognitive 18) · ×1
  • MvvmDataGrid.FilterColumnValue (cognitive 18) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:1443 — MvvmDataGrid.FilterColumnValue has cognitive complexity 18 (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 · BindingManager.ViewModel.Set (cognitive 17) · ×1
  • BindingManager.ViewModel.Set (cognitive 17) src/dev/Core/Components/BindingManager/BindingManager.vb:245 — BindingManager.ViewModel.Set 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 · BindableTreeView.RemoveAllChilds (cognitive 17) · ×1
  • BindableTreeView.RemoveAllChilds (cognitive 17) src/dev/Core/Controls/MvvmControls/BindableTreeView.vb:361 — BindableTreeView.RemoveAllChilds 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 · MvvmDataGridColumn.AddSerializedColumn (cognitive 17) · ×1
  • MvvmDataGridColumn.AddSerializedColumn (cognitive 17) src/dev/Core/Controls/MvvmControls/MvvmDataGrid/Column/MvvmDataGridColumn.vb:1109 — MvvmDataGridColumn.AddSerializedColumn 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 · MvvmFormsAnalyzerCodeFixProvider.GetCodeFixActionFromClassType (cognitive 17) · ×1
  • MvvmFormsAnalyzerCodeFixProvider.GetCodeFixActionFromClassType (cognitive 17) src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:253 — MvvmFormsAnalyzerCodeFixProvider.GetCodeFixActionFromClassType 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 · PropertyPathBoundSourceItemProxy.WireUpPropertyChangeEvents (cognitive 16) · ×1
  • PropertyPathBoundSourceItemProxy.WireUpPropertyChangeEvents (cognitive 16) src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:276 — PropertyPathBoundSourceItemProxy.WireUpPropertyChangeEvents 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 · ViewModelPropertyComboBox.OnTextChanged (cognitive 16) · ×1
  • ViewModelPropertyComboBox.OnTextChanged (cognitive 16) src/dev/Core/Components/MvvmManager/UI/ViewModelPropertyComboBox.vb:90 — ViewModelPropertyComboBox.OnTextChanged 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 · BindableDataGridView.SetValueFromValueMember (cognitive 16) · ×1
  • BindableDataGridView.SetValueFromValueMember (cognitive 16) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:727 — BindableDataGridView.SetValueFromValueMember 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 · NullableValueRelationPopup.FilterBindingViewAsync (cognitive 16) · ×1
  • NullableValueRelationPopup.FilterBindingViewAsync (cognitive 16) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:672 — NullableValueRelationPopup.FilterBindingViewAsync 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 · Extender.GetChangedValues (cognitive 16) · ×1
  • Extender.GetChangedValues (cognitive 16) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/Extender.cs:11 — Extender.GetChangedValues 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.
D4 · Code Duplication · Edited copy of a member (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:308 — src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:308-362 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:394-450 — These two members are one piece of code written twice and then edited apart: 55 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 (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:222 — src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:222-293 | src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:336-402 — These two members are one piece of code written twice and then edited apart: 67 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 (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:176 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:176-251 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:165-239 — These two members are one piece of code written twice and then edited apart: 75 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 (63 corresponding lines) · ×1
  • Edited copy of a member (63 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:211 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:211-273 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:318-380 — These two members are one piece of code written twice and then edited apart: 63 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 (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:66 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:66-131 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:66-121 — These two members are one piece of code written twice and then edited apart: 56 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 (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb:299 — src/dev/Core/Controls/TooltipEx/TooltipEx.vb:299-312 | src/dev/Core/Controls/TooltipEx/TooltipEx.vb:320-333 — These two members are one piece of code written twice and then edited apart: 14 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 (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb:142 — src/dev/Core/Controls/TooltipEx/TooltipEx.vb:142-185 | src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:215-268 — These two members are one piece of code written twice and then edited apart: 44 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 (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:60 — src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:60-92 | src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:106-144 — These two members are one piece of code written twice and then edited apart: 33 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 copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64 — src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64-91 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridCustomColumnTemplateTypeUIEditor.vb:28-64 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridDataSourceTypeUIEditor.vb:37-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:191 — src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:191-219 | src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:308-333 — These two members are one piece of code written twice and then edited apart: 26 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 copies of one member (3 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 27+ corresponding lines) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:250 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:250-276 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:256-282 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:146-175 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:297 — src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:297-316 | src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:320-340 — 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 · Edited copies of one member (5 members, 42+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 42+ corresponding lines) src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:73 — src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:73-122 | src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:128-177 | src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:185-239 | src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:245-294 | src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:302-343 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 42 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:214 — src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:214-234 | src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:280-298 — These two members are one piece of code written twice and then edited apart: 19 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:242 — src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:242-269 | src/dev/Legacy.EFLViewModelBase/BaseClasses/BindableBase.vb:305-332 — These two members are one piece of code written twice and then edited apart: 28 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 copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) src/dev/Core/NullableValueControlCollection.vb:24 — src/dev/Core/NullableValueControlCollection.vb:24-35 | src/dev/Core/NullableValueControlCollection.vb:61-73 | src/dev/Core/NullableValueControlCollection.vb:99-110 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:176 — src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:176-193 | src/dev/Core/Controls/NullableControls/NullableRelationPopup/BindableDataGridView.vb:221-238 — These two members are one piece of code written twice and then edited apart: 18 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:110 — src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:110-125 | src/dev/Core/Components/MvvmManager/ClassesAndStructures/BoundSourceItemProxy.vb:148-157 — These two members are one piece of code written twice and then edited apart: 10 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) src/dev/Core/Controls/NullableControls/NullableOptionButton.vb:119 — src/dev/Core/Controls/NullableControls/NullableOptionButton.vb:119-142 | src/dev/Core/Controls/NullableControls/NullableCheckBox.vb:120-144 — These two members are one piece of code written twice and then edited apart: 24 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 copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) src/dev/Core/Controls/NullableControls/NullableDateValue.vb:167 — src/dev/Core/Controls/NullableControls/NullableDateValue.vb:167-177 | src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:360-370 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:196-204 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:1349 — src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:1349-1350 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:966-967 — These two members are one piece of code written twice and then edited apart: 2 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 (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) src/dev/Core/Controls/TooltipEx/TooltipEx.vb:126 — src/dev/Core/Controls/TooltipEx/TooltipEx.vb:126-131 | src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:198-203 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×1
  • Edited copy of a member (3 corresponding lines) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:781 — src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:781-783 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:330-332 — These two members are one piece of code written twice and then edited apart: 3 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 (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) src/dev/Core/Controls/NullableControls/NullableOptionButton.vb:27 — src/dev/Core/Controls/NullableControls/NullableOptionButton.vb:27-30 | src/dev/Core/Controls/NullableControls/NullableCheckBox.vb:28-31 — These two members are one piece of code written twice and then edited apart: 4 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 (60 lines × 2) · ×1
  • Duplicated block (60 lines × 2) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:180 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:180-239 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:191-250 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (37–52 lines × 2) · ×1
  • Duplicated block (37–52 lines × 2) src/dev/Core/Components/BindingManager/BindingManager.vb:449 — src/dev/Core/Components/BindingManager/BindingManager.vb:449-500 | src/dev/Core/Components/BindingManager/BindingManager.vb:621-657 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (43 lines × 2) · ×1
  • Duplicated block (43 lines × 2) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:338 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:338-380 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:231-273 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 147 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.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:66 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:66-103 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:66-103 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:88 — src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:88-122 | src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:143-177 — 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.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:314 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:314-340 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:320-346 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:213-239 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) src/dev/Core/Controls/NullableControls/NullableValueBase.vb:412 — src/dev/Core/Controls/NullableControls/NullableValueBase.vb:412-435 | src/dev/Core/Controls/StandardControls/TextBoxButtonBase.vb:324-347 — 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 (24 lines × 3) · ×1
  • Duplicated block (24 lines × 3) src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:281 — src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb:281-304 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb:287-310 | src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:180-203 — before extracting anything, compare `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignment.vb` and `src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentEx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 227 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:70 — src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:70-92 | src/dev/Core/Components/FormToBusinessClassManager/FormToBusinessClassManagerExtender.vb:122-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:1234 — src/dev/Core/Controls/NullableControls/NullableRelationPopup/NullableValueRelationPopup.vb:1234-1254 | src/dev/Core/Controls/NullableControls/NullableValueBase.vb:589-609 — 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 (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:233 — src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:233-253 | src/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:342-363 — 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/dev/MvvmBaseLib/MvvmBaseLibShared/MvvmBaseClasses/MvvmViewModelBase.cs:233` 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 (20–21 lines × 2) · ×1
  • Duplicated block (20–21 lines × 2) src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:69 — src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:69-88 | src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:188-208 — 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/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/CodeFixProviders/CodeFixProvider.vb:69` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64 — src/dev/Core/Components/FormToBusinessClassManager/Designer/DataSourceType.vb:64-80 | src/dev/Core/Controls/MvvmControls/MvvmDataGrid/TypeEditor/MvvmDataGridDataSourceTypeUIEditor.vb:37-53 — 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 (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:276 — src/dev/Core/Controls/StandardControls/TextBoxPopup/ResizablePopup.vb:276-293 | src/dev/Core/Controls/TooltipEx/TooltipEx.vb:193-210 — 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 (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:301 — src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:301-309 | src/dev/Core/Components/FormToBusinessClassManager/Designer/frmEntityObjectSelector.vb:325-333 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) src/dev/Core/Controls/NullableControls/NullableMaskTextValue.vb:75 — src/dev/Core/Controls/NullableControls/NullableMaskTextValue.vb:75-86 | src/dev/Core/Controls/NullableControls/NullableTextValue.vb:80-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) src/dev/Core/Controls/NullableControls/NullableCheckBox.vb:35 — src/dev/Core/Controls/NullableControls/NullableCheckBox.vb:35-44 | src/dev/Core/Controls/NullableControls/NullableOptionButton.vb:34-43 — before extracting anything, compare `src/dev/Core/Controls/NullableControls/NullableCheckBox.vb` and `src/dev/Core/Controls/NullableControls/NullableOptionButton.vb` as WHOLE FILES: 95% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs:47 — src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs:47-89 | src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs:50-88 — These two members are one piece of code written twice and then edited apart: 39 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 (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs:66 — src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs:66-88 | src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs:66-89 — `src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs` and `src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 24 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/dev/Samples/MvvmCalculator/ModernMvvmCalculator/App.xaml.cs:66` calls `RegisterTypes` and `src/dev/Samples/MvvmCalculator/ModernMvvmCalculator (RC-Ver)/App.xaml.cs:66` does not — after which the two agree again for 5 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: MvvmBaseLib.NetStandard src/dev/MvvmBaseLib/MvvmBaseLib.NetStandard/MvvmBaseLib.NetStandard.csproj:1 — MvvmBaseLib.NetStandard: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — test suite did not build — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
M1 · Documentation (README) · Repository declared end-of-life · ×1
  • Repository declared end-of-life README.md:14 — This repository declares its own end of life: `README.md` line 14 reads “Note: We never ported MvvmForms to .NET (Core, .NET 3.1+) - so, it's only available for NetFx. Also note, that this repo is no longer actively maintained, but feel free to port it and use it in any shape and form you like.”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on.
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.
Minor — 86 finding(s)
D24 · Comment Value · redundant comment · ×65
  • redundant comment src/dev/Core/BaseForms/AnimationFormBase.vb:162 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/BaseForms/AnimationFormBase.vb:165 — "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Components/MvvmManager/UI/ControlBindingGrid.vb:42 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Components/MvvmManager/UI/ControlBindingGrid.vb:45 — "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Components/MvvmManager/UI/DataSourceTypeUIForm.vb:64 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Components/MvvmManager/UI/frmManageBindings.vb:51 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:36 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/MvvmControls/MvvmDataGrid/MvvmDataGrid.vb:39 — "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/MvvmControls/NullableValueComboBox/NullableValueComboBox.vb:26 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/MvvmControls/NullableValueComboBox/WPFComboBoxWrapper.xaml.vb:9 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb:70 — "KopierenToolStripMenuItem" repeats the code it sits on: 5 of its 5 words (kopieren, tool, strip, menu, item) are already in `Me.myKopierenToolStripMenuItem.Name = "KopierenToolStripMenuItem"`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/StandardControls/ColoredTextPanelPartial/ViewPanel.vb:76 — "AllessLöschenToolStripMenuItem" repeats the code it sits on: 6 of its 6 words (alless, löschen, tool, strip, menu, item) are already in `Me.myAllesLöschenToolStripMenuItem.Name = "AllesLöschenToolStripMenuItem"`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/StandardControls/SimpleCalculator.vb:50 — "This call is required by the designer." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/Controls/StandardControls/SimpleCalculator.vb:53 — "Add any initialization after the InitializeComponent() call." is Visual Studio form constructor template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Core/ETW/MvvmFormsEtw.vb:37 — "Tasks" only labels `End Class`, the end of the Class block Tasks. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/EFLWebApiClientSupport/My Project/AssemblyInfo.vb:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/EFLWebApiClientSupport/My Project/AssemblyInfo.vb:9 — "Review the values of the assembly attributes" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/EFLWebApiClientSupport/My Project/AssemblyInfo.vb:19 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Legacy.EFLViewModelBase/My Project/AssemblyInfo.vb:5 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Legacy.EFLViewModelBase/My Project/AssemblyInfo.vb:9 — "Review the values of the assembly attributes" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/Legacy.EFLViewModelBase/My Project/AssemblyInfo.vb:19 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/MvvmBaseLib/MvvmBase/Properties/AssemblyInfo.cs:7 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/MvvmBaseLib/MvvmBase/Properties/AssemblyInfo.cs:21 — "Version information for an assembly consists of the following four values: Major Version Minor Version Build Number Revision You can specify all the values or y …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/MvvmBaseLib/MvvmBaseLib.NET451/Properties/AssemblyInfo.cs:6 — "General Information about an assembly is controlled through the following set of attributes. Change these attribute values to modify the information associated …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/dev/MvvmBaseLib/MvvmBaseLib.NET451/Properties/AssemblyInfo.cs:18 — "Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type in this assembly from COM, set the ComV …" is Visual Studio AssemblyInfo template text, left in place. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 40 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×7
  • Orphaned file src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Controls/StandardControls/SimpleCalculator.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Components/MvvmManager/Controls/ucBindingTreeview.xaml.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Components/MvvmManager/Controls/ucBindingSetting.xaml.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Components/MvvmManager/Controls/ucPropertySelector.xaml.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Components/MvvmManager/UI/PropertyBindingNodeDefinition.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/dev/Core/Controls/MvvmControls/MvvmDataGrid/ExtDataGrid.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×6
  • ObsoleteWithoutCallers src/dev/Core/Controls/Interfaces/IPermissionManageableElements.vb:49 — <Obsolete> PermissionManageableUIElementParams
  • ObsoleteWithoutCallers src/dev/Core/Controls/Interfaces/IPermissionManageableElements.vb:110 — <Obsolete> HasPermissionManageableUIElementsAttribute
  • ObsoleteWithoutCallers src/dev/Legacy.EFLViewModelBase/Attributes/MvvmViewModelIncludeAttribute.vb:8 — <Obsolete> MvvmViewModelIncludeAttribute
  • ObsoleteWithoutCallers src/dev/Legacy.EFLViewModelBase/DataContextAssigner.vb:8 — <Obsolete> HighPriorityAssignmentAttribute
  • ObsoleteWithoutCallers src/dev/Legacy.EFLViewModelBase/DataContextAssigner.vb:13 — <Obsolete> LowPriorityAssignmentAttribute
  • ObsoleteWithoutCallers src/dev/Legacy.EFLViewModelBase/DataContextAssigner.vb:26 — <Obsolete> DataContextAssigner
D18 · Solution Shape · Thin analysable surface across projects · ×3
  • Thin analysable surface across projects: MvvmViewModelCalculatorTest src/dev/Samples/MvvmCalculator/MvvmViewModelCalculatorTest/MvvmViewModelCalculatorTest.vbproj — 3 project(s) carry only a thin slice of real code; `MvvmViewModelCalculatorTest` has 28 significant line(s). The mean analysable-surface weight is 95 %; 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: MvvmAutheticationLocator src/dev/MvvmFormsPlatformServices/Generic/MvvmAutheticationLocator/MvvmAutheticationLocator.vbproj — 3 project(s) carry only a thin slice of real code; `MvvmAutheticationLocator` has 34 significant line(s). The mean analysable-surface weight is 95 %; this project lowers Solution Shape by about 0.12 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
  • Thin analysable surface across projects: ArtHorizViewModel src/dev/Samples/ArtificalHorizonOffRoadIoC/ArtHorizViewModel/ArtHorizViewModel.vbproj — 3 project(s) carry only a thin slice of real code; `ArtHorizViewModel` has 36 significant line(s). The mean analysable-surface weight is 95 %; this project lowers Solution Shape by about 0.1 point(s). Consolidate it or grow it into a substantial, well-scoped assembly.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/dev/Core/MvvmForms.vbproj:1 — `MvvmForms` overshoots its size bounds (30713 LoC, 410 public types across 1 namespaces). 1 of 28 project(s) overshoot their size bounds, lowering Project Cohesion to 9.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 7 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: src/dev/Core/Components/MvvmManager/UI/frmMvvmPropertyAssignmentRev.vb, src/dev/Core/Controls/StandardControls/SimpleCalculator.vb, src/dev/Core/Components/MvvmManager/Controls/ucBindingTreeview.xaml.vb, src/dev/Core/Components/MvvmManager/Controls/ucBindingSetting.xaml.vb, src/dev/Core/Components/MvvmManager/Controls/ucPropertySelector.xaml.vb, src/dev/Core/Components/MvvmManager/UI/PropertyBindingNodeDefinition.vb, src/dev/Core/Controls/MvvmControls/MvvmDataGrid/ExtDataGrid.vb (10 orphaned of 138 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 138 of the 279 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 9/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
Minor — 6 finding(s)
D24 · Comment Value · doc comments repeat the names · ×6
  • doc comments repeat the names src/dev/Legacy.EFLViewModelBase/MvvmViewModelClasses/IMvvmViewModel.vb:12 — 0 of 12 documented parameters and 0 of 2 summaries in `EFLViewModelBase` only repeat the member or parameter name (e.g. "" for `sender`). 12 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/dev/Test/EFL_CodedUITestContainer/EFL_CodedUITestContainer/MvvmDataGridExample/MvvmDataGridExample/Model/Buchung.vb:8 — 0 of 0 documented parameters and 0 of 16 summaries in `EFL_CodedUITestContainer` only repeat the member or parameter name (e.g. "" for `Url`). 16 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/dev/MvvmBaseLib/MvvmBaseLibShared/Attributes/MvvmViewAttribute.cs:50 — 0 of 42 documented parameters and 2 of 70 summaries in `MvvmBaseLib.NetStandard` only repeat the member or parameter name (e.g. "The ContextGuid." for `ContextGuid`). 16 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/dev/Core/Controls/DecoratingControls/RangeClockGauge/PolarCoordinate.vb:77 — 0 of 118 documented parameters and 1 of 63 summaries in `MvvmForms` only repeat the member or parameter name (e.g. "The Angle." for `Angle`). 111 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/dev/MvvmFormsAnalyzer/MvvmFormsAnalyzer/ExtensionMethods/AnalyzerExtensionMethods.vb:36 — 1 of 2 documented parameters and 0 of 1 summaries in `MvvmFormsAnalyzer` only repeat the member or parameter name (e.g. "Name of the Event." for `eventName`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/dev/EFLWebApiClientSupport/WebApiAccess/WebApiAccess.vb:14 — 0 of 1 documented parameters and 0 of 3 summaries in `MvvmFormsWebApiClientSupport` only repeat the member or parameter name (e.g. "" for `baseAddress`). 1 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-dfb5401c78aa44518285dcdc785f69c0/history.json --exit-code 0 --source .0artifacts/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-dfb5401c78aa44518285dcdc785f69c0/tree.json --exit-code 0 --source .0artifacts/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 .0artifacts/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 Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7b32e0ccad3a45c096fb3e56bc94d9b07artifacts/raw/osv-scanner.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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.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 Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-7b32e0ccad3a45c096fb3e56bc94d9b00artifacts/raw/osv-scanner.json

Run 01a1dd18-278b-7ee8-8d6c-0be8b725d793 · 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 — 10 field(s) across 3 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.

Name — 8 field(s)
  • Contact.LastName src/dev/MvvmFormsCSharpDemos/DemoData/DemoData.cs:173
  • Contact.FirstName src/dev/MvvmFormsCSharpDemos/DemoData/DemoData.cs:174
  • SimpleContact.LastName src/dev/MvvmFormsCSharpDemos/DemoData/SimpleContactData.cs:12
  • SimpleContact.FirstName src/dev/MvvmFormsCSharpDemos/DemoData/SimpleContactData.cs:13
  • TinyContact.LastName src/dev/MvvmFormsCSharpDemos/DemoData/SimpleContactData.cs:41
  • TinyContact.FirstName src/dev/MvvmFormsCSharpDemos/DemoData/SimpleContactData.cs:42
  • ContactItem.Lastname src/dev/Samples/MeterReaderMvvmForms/MrModelLibrary/DataObjects/ContactItem.cs:12
  • ContactItem.Firstname src/dev/Samples/MeterReaderMvvmForms/MrModelLibrary/DataObjects/ContactItem.cs:13
Date of birth — 1 field(s)
  • SimpleContact.DateOfBirth src/dev/MvvmFormsCSharpDemos/DemoData/SimpleContactData.cs:17
Phone — 1 field(s)
  • ContactItem.Phone src/dev/Samples/MeterReaderMvvmForms/MrModelLibrary/DataObjects/ContactItem.cs:14

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