Public report — simpleide, published 1 Oct 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.18 (frozen) · verify this surveyFiledcd_37eeea4409634fb7a0d9c137b30eb7ff
Filed 1 October 2026, 13:52 UTC
Public
Large · 102,785 LoC · 1 projects · rebuild ~0.5 person-years · weakest lens: Readiness (23%)
Findings by grade
41 critical614 serious12 minor40 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
1 October 2026, 13:50 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
654findings with an exact file:lineof 667 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
37/118dimensions across the health lenses102785 LoC · 1 projects — wide & deep
The system is a large, valuable asset currently operating with significant operational risk, reflected in an overall health score of 46%. While the code logic itself is sound, the lack of operational safeguards means the business is exposed to preventable outages and slow delivery. With nearly 103,000 lines of production code and a rebuild cost of approximately €78,000, the stakes are high. The primary danger lies not in the code’s structure, but in its inability to be safely modified or deployed without human intervention.
The most critical vulnerability is the system’s readiness. At only 23%, the platform lacks the testing and automation required for reliable operation. This creates a heavy velocity tax on every change, where developers likely spend 4–10% more time navigating complexity and avoiding regressions. This inefficiency compounds annually, costing the business significantly more than the effort required to fix it. The top priority is implementing a continuous integration workflow that builds and tests every change. This single action pays for itself within two months by reducing the annual drag on the team’s capacity, effectively turning a recurring cost into a one-time investment.
Despite these risks, the codebase demonstrates genuine strength in its architectural design and security posture. The underlying logic is clean, with no boilerplate or security flaws detected, providing a solid foundation for future growth. However, the absence of automated tests means the team cannot confidently evolve the system. The picture is partial, as several key areas like performance and domain modeling were not measured, but the existing data is sufficient to identify the immediate path forward. Focus first on establishing automated testing to unlock the system’s potential and secure its operational integrity.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
0.7× (at 46% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.5 person-years of build effort (about ~€78,000 to rebuild). Its weakest lens is Readiness at 23% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Low (×0.9) — library/CLI × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~0.5 person-years to rebuild), and its weakest lens is Readiness at 23%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
The top fix pays for itself · High · Economics
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 23.3–140 engineer-days every year, paid as drag on the ~220,541 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 1–2 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 4–10% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 54,380 line(s) changed over a 90-day window ⇒ ~220,541/year · D1/D2/D4/D6 code quality: averaging 6.3/10 ⇒ a 4–10% drag on each change · top-ranked remediation: Low effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 2 months.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.3/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 4–10% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4/D6 code quality: averaging 6.3/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
13 modules, 48 dependencies. 1 dependency cycle across 9 modules, marked above the diagonal.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
SimpleIDE.Widgets uses SimpleIDE.Utilities. Changing SimpleIDE.Utilities can break SimpleIDE.Widgets, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
6→7 SimpleIDE.Widgets depends on SimpleIDE.Modelscycle✕
Type pairs
51 distinct (type in SimpleIDE.Widgets → type in SimpleIDE.Models) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
SimpleIDE.Managers uses SimpleIDE.Widgets. Changing SimpleIDE.Widgets can break SimpleIDE.Managers, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
9→7 SimpleIDE.Managers depends on SimpleIDE.Models✕
Type pairs
41 distinct (type in SimpleIDE.Managers → type in SimpleIDE.Models) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Establish a CI workflow to build and test every push, while immediately addressing the single gaps in automated code coverage and test distribution. Maintain release hygiene by keeping a changelog that records what ships in each version. Finally, document significant architectural decisions in a consistent, discoverable format to preserve design context and consequences.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Per-file score 0–10 — a quality signature. Of 146 files carrying findings, judged against the Production bar: 5% slop · 68% mixed · 27% near-clean.
File
Score
Band
Worst signal
Models/SourceFileInfo.AtomicOperations.vb
1.0
Slop
Explicit Debt: EmptyCatchBlock
MainWindow.Keyboard.vb
1.2
Slop
Explicit Debt: EmptyCatchBlock
Widgets/ThemeEditor.vb
1.4
Slop
Explicit Debt: EmptyCatchBlock
Models/DocumentModel.vb
1.6
Slop
Explicit Debt: EmptyCatchBlock
Widgets/CustomDrawObjectExplorer.Events.vb
2.8
Slop
Explicit Debt: EmptyCatchBlock
Syntax/CodeSenseEngine.vb
3.1
Slop
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.TextManipulation.vb
3.4
Slop
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.Mouse.vb
3.5
Slop
Explicit Debt: EmptyCatchBlock
MainWindow.Editor.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Widgets/CustomDrawDataGrid.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Managers/ProjectManager.Parser.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.Editing.vb
4.6
Mixed
Explicit Debt: EmptyCatchBlock
Widgets/CustomDrawProjectExplorer.ContextMenu.vb
4.7
Mixed
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.Search.vb
4.7
Mixed
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.HoverTooltip.vb
4.8
Mixed
Explicit Debt: EmptyCatchBlock
Editors/CustomDrawingEditor.Dispose.vb
4.9
Mixed
Explicit Debt: EmptyCatchBlock
Widgets/CustomDrawObjectExplorer.ContextMenu.vb
4.9
Mixed
Explicit Debt: EmptyCatchBlock
Models/SourceFileInfo.InternalOperations.vb
5.0
Mixed
Explicit Debt: EmptyCatchBlock
Editors/ManifestEditor.vb
5.4
Mixed
Explicit Debt: EmptyCatchBlock
Managers/BuildManager.vb
5.4
Mixed
Explicit Debt: EmptyCatchBlock
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 41
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 — 614
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 — 12
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 40
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 33 of 37 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 37 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 654 of 667 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 436 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D39 IL Efficiency — 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. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P2 Observability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Observability was not assessed: this check recognises the logging, tracing/metrics and health-check idioms of .NET, the JVM, Go, Python, JavaScript/TypeScript, Rust, Ruby, PHP, Swift, Dart, Elixir and Erlang, and most of this repository's production source is in none of them. Absence of an idiom this check recognises is NOT evidence that this repo lacks structured logging. This is a gap in the analyzer, 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.
PF2 Allocation hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Those languages have allocation-aware idioms of their own, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that the code is careless with allocations.
PF3 Async & latency hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP and Rust source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java and Kotlin syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java or Kotlin was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
114 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CustomDrawingEditor.OnKeyPress at 119. A further 13 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 ProjectParser.ConvertTokenType at 99 — 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: Widgets/TODOPanel.vb (TODOEditDialog.PopulateFields at 21). 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.
+ 109 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 CustomDrawingEditor.OnKeyPress (cyclomatic 119) finding(s) in Cyclomatic Complexity — start with CustomDrawingEditor.Keyboard.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 KeyboardHelper.GetKeyString (cyclomatic 118) finding(s) in Cyclomatic Complexity — start with KeyboardHelper.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 VBTokenizer.TokenizeLine (cyclomatic 90) finding(s) in Cyclomatic Complexity — start with VBTokenizer.vb. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 209 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 VBTokenizer.TokenizeLine (cognitive 161) finding(s) in Cognitive Complexity — start with VBTokenizer.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ProjectManager.ProcessNodeInContext (cognitive 119) finding(s) in Cognitive Complexity — start with ProjectManager.Extension.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 RoslynConverter.ParseXmlDocumentation (cognitive 114) finding(s) in Cognitive Complexity — start with RoslynConverter.vb. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.8 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 47 FileTooLong finding(s) in God Classes — start with CodeSenseEngine.vb, PreferencesTab.vb, CustomDrawProjectExplorer.AddNewItem.vb. — One of this dimension's main actionable groups (47 warning-level).
Resolve the 23 TooManyMethods finding(s) in God Classes — start with MainWindow.AI.vb, CustomDrawingEditor.AutoEndConstruct.vb, CustomDrawProjectExplorer.AddNewItem.vb. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 22 MethodTooLong finding(s) in God Classes — start with PreferencesTab.vb (4), CustomDrawingEditor.Keyboard.vb, KeyboardHelper.vb. — One of this dimension's main actionable groups (22 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
68 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 40 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with GitManager.vb, CustomDrawObjectExplorer.Drawing.vb, FindReplacePanel.SortableResults.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CustomDrawObjectExplorer.Events.vb (2), ReferenceManager.vb, ScratchpadPanel.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MainWindow.Toolbar.vb, OpenAICompatibleProvider.vb, CustomDrawObjectExplorer.Events.vb. — One of this dimension's main actionable groups (4 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 10 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainWindow.vb, ProjectManager.vb, CustomDrawProjectExplorer.vb. — One of this dimension's main actionable groups (10 warning-level).
Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 129 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 8 direct `PackageReference`(s), and 121 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: Editors/CustomDrawingEditor.Keyboard.vb (14×119=1666); Editors/CustomDrawingEditor.Drawing.vb (14×72=1008); Widgets/ThemeEditor.vb (19×40=760) Repeated repair below the complexity floor: MainWindow.vb (16 of 31 changes were fixes); MainWindow.Events.vb (10 of 15 changes were fixes); Widgets/HelpBrowser.vb (8 of 15 changes were fixes)
Resolve the 42 Hotspot finding(s) in Churn × Complexity Hotspots — start with CustomDrawingEditor.Keyboard.vb, CustomDrawingEditor.Drawing.vb, ThemeEditor.vb. — One of this dimension's main actionable groups (42 warning-level).
Resolve the 9 Repeated repair finding(s) in Churn × Complexity Hotspots — start with MainWindow.vb, MainWindow.Events.vb, HelpBrowser.vb. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
Resolve the 40 EmptyCatchBlock finding(s) in Explicit Debt — start with SourceFileInfo.AtomicOperations.vb (3), AssemblyBrowser.vb (3), CustomDrawObjectExplorer.Events.vb (3). — One of this dimension's main actionable groups (40 issue-level).
Resolve the 49 TodoComment finding(s) in Explicit Debt — start with Program.vb (16), MainWindow.Integration.vb (11), MainWindow.Keyboard.vb (5). — One of this dimension's main actionable groups (49 warning-level).
Resolve the 1 ObsoleteWithCallers finding(s) in Explicit Debt — start with CustomDrawNotebook.vb. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape8.0 / 10Strong✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
1 projects, 245 source files, 102785 hand-written lines of code (102785 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 0 inter-project edges (build status unknown — did not finish).
Solution references 2 projects that do not existSimpleIDE.sln
Single-project monolith
What to do
Resolve the 1 Solution references 2 projects that do not exist finding(s) in Solution Shape — start with SimpleIDE.sln. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Single-project monolith finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README (readme.md) is a comprehensive project overview with an excellent features list and a dedicated Coding Conventions document for style rules plus a separate Project Architecture doc. The architecture covers the single-codebase cross-platform model, verified platforms, platform-specific considerations, and core component breakdowns; all sections are present in the outline. The README itself lacks installation/usage/contribution guidance but is scoped to its directory (the IDE), so those belong to the root README and are not flagged here.
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 of 1 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability5.6 / 10Adequate✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
70 % of calls cross a namespace and 3 % go through an interface, but 62 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 5.6/10. — 70 % of calls cross a namespace and 3 % go through an interface, but 62 % of collaborators are co-located — so following a call takes several hops. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 224 of the 252 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
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. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
~102.8k production LoC (422 types) across 1 project(s) / 13 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. Deterministic, type-level.
`IEditor` declares 112 members: `FilePath`, `IsModified`, `IsReadOnly`, `CanUndo`, `CanRedo`, `CanCut`, `CanCopy`, `CanPaste`, `Text`, `TextLines`, `LineCount`, `CharCount`, `CurrentLine`, `CurrentColumn`, `HasSelection`, `SelectionStart`, `SelectionEnd`, `SelectedText`, `Widget`, `SupportsLineNumbers`, `SupportsSyntaxHighlighting`, `SupportsNavigation`, `RootNode`, `SourceFileInfo`, `Modified`, `CursorPositionChanged`, `SelectionChanged`, `TextChanged`, `UndoRedoStateChanged`, `DocumentParsed`, `LineExited`, `ProjectManagerRequested`, `RequestGotoDefinition`, `RequestFindAllReferences`, `CodeSenseRequested`, `CodeSenseCancelled`, `FindRequested`, `ReplaceRequested`, `SetThemeManager`, `Undo`, and 72 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 112 declarations carry 111 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 111 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Interfaces/IEditor.vb:20
`IObjectExplorer` declares 20 members: `NodeSelected`, `NodeDoubleClicked`, `NodeActivated`, `NavigateToFile`, `CloseRequested`, `UpdateStructure`, `LoadProjectStructure`, `SetProjectStructure`, `ClearStructure`, `RefreshStructure`, `SetCurrentEditor`, `InitializeWithProjectManager`, `NavigateToNode`, `SetRefreshEnabled`, `OnPageActivated`, `DiagnoseTreeViewStatus`, `TestTreeViewVisibility`, `TestWithSimpleContent`, `DiagnoseWithLabel`, `CheckTreeViewContent`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Interfaces/IObjectExplorer.vb:20
`ICustomNotebook` declares 21 members: `CurrentPage`, `NPages`, `AppendPage`, `RemovePage`, `GetNthPage`, `GetTabLabel`, `SetTabLabel`, `SetTabLabelText`, `PageNum`, `SetTabModified`, `SetTabIcon`, `ShowTabContextMenu`, `SwitchToNextTab`, `SwitchToPreviousTab`, `TabClosing`, `CurrentTabChanged`, `TabClosed`, `TabReordered`, `TabContextMenuRequested`, `TabModifiedChanged`, `HidePanelRequested`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Interfaces/ICustomNotebook.vb:11
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README advertises Docker containerisation, but no Dockerfile/compose file exists — searched for: `dockerfile`, `docker-compose`, `compose.yaml`, `compose.yml`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
What to do
Reconcile the README with reality: README advertises Docker containerisation, but no Dockerfile/compose file exists.
Do you agree with this assessment?
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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 — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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 — 75 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — At only 1 project (and 102k LoC) this is a tiny single-purpose codebase that requires no boundaries. No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D39 IL Efficiency — IL not measured — the target did not build
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P2 Observability — Observability was not assessed: this check recognises the logging, tracing/metrics and health-check idioms of .NET, the JVM, Go, Python, JavaScript/TypeScript, Rust, Ruby, PHP, Swift, Dart, Elixir and Erlang, and most of this repository's production source is in none of them. Absence of an idiom this check recognises is NOT evidence that this repo lacks structured logging. This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Allocation awareness was not assessed: this repository holds Visual Basic, whose allocation-aware idioms this check does not model yet. That is a gap in the analyzer's language reach, not a finding about your code.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock Editors/CustomDrawingEditor.Dispose.vb:90— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.Dispose.vb:101— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.DragDrop.vb:528— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.Editing.vb:580— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.HoverTooltip.vb:88— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.Mouse.vb:558— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.Mouse.vb:639— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.Search.vb:359— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.TextManipulation.vb:647— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/CustomDrawingEditor.TextManipulation.vb:833— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Editors/ManifestEditor.vb:525— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.DesktopIntegration.vb:173— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.Editor.vb:1412— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.Keyboard.vb:486— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.Project.vb:325— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.Run.vb:256— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock MainWindow.StatusBar.vb:377— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Managers/BuildManager.vb:525— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Managers/ProjectManager.Parser.vb:215— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/DocumentModel.vb:343— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/DocumentModel.vb:376— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/SourceFileInfo.AtomicOperations.vb:143— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/SourceFileInfo.AtomicOperations.vb:269— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/SourceFileInfo.AtomicOperations.vb:548— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock Models/SourceFileInfo.InternalOperations.vb:234— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
TodoComment Editors/CustomDrawingEditor.ImplementInterface.vb:3— ' "Implements IFoo.Member" clause and a "' TODO:" marker in the body, so it surfaces — 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 Editors/CustomDrawingEditor.ImplementInterface.vb:4— ' automatically in the existing TODO panel) for every member not yet implemented. — 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 Editors/CustomDrawingEditor.ScrollManual.vb:851— ' TODO: Auto-expand — 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 Editors/FileComparisonPanel.vb:217— ' TODO: Implement a proper diff algorithm (e.g., Myers' algorithm) — 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 Editors/FileComparisonPanel.vb:260— ' TODO: Highlight differences in the editors — 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 Editors/FileComparisonPanel.vb:454— ' TODO: Connect to the CustomDrawingEditor's scroll events when they're exposed — 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 Editors/FileComparisonPanel.vb:495— ' TODO: Update highlighting in editors — 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 MainWindow.Events.vb:433— ' TODO: Implement external tools — 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 MainWindow.Integration.vb:50— ' TODO: Implement Dropbox backup — 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 MainWindow.Integration.vb:64— ' TODO: Implement OneDrive backup — 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 MainWindow.Integration.vb:78— ' TODO: Implement Google Drive backup — 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 MainWindow.Integration.vb:119— ' TODO: Implement HTML documentation generation — 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 MainWindow.Integration.vb:130— ' TODO: Implement XML documentation generation — 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 MainWindow.Integration.vb:141— ' TODO: Implement Markdown documentation generation — 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 MainWindow.Integration.vb:296— ' TODO: Implement GitHub Actions trigger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment MainWindow.Integration.vb:309— ' TODO: Implement GitLab CI trigger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment MainWindow.Integration.vb:322— ' TODO: Implement Azure DevOps trigger — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment MainWindow.Integration.vb:337— ' TODO: Create integration settings dialog — 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 MainWindow.Integration.vb:339— ' TODO: OnPreferences(Nothing, Nothing) — 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 MainWindow.Keyboard.vb:290— ' was a bare TODO stub that just swallowed the key - the real method to — 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 MainWindow.Keyboard.vb:690— ' TODO: Implement quick fix/show properties — 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 MainWindow.Keyboard.vb:782— ' TODO: Implement toggle breakpoint — 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 MainWindow.Keyboard.vb:789— ' TODO: Implement step over debugging — 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 MainWindow.Keyboard.vb:796— ' TODO: Implement step out debugging — 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 MainWindow.Menu.vb:367— ' Bottom Panel - single toggle for the whole dock (Output/Errors/Warnings, TODO, — 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.
FileTooLong: Syntax/CodeSenseEngine.vb Syntax/CodeSenseEngine.vb— FileTooLong — 1366 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 866 over it, 2.73× 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: Widgets/PreferencesTab.vb Widgets/PreferencesTab.vb— FileTooLong — 1363 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 863 over it, 2.73× 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: Widgets/CustomDrawProjectExplorer.AddNewItem.vb Widgets/CustomDrawProjectExplorer.AddNewItem.vb— FileTooLong — 1199 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 699 over it, 2.40× 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: Widgets/ThemeEditor.vb Widgets/ThemeEditor.vb— FileTooLong — 1187 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 687 over it, 2.37× 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: Models/DocumentModel.vb Models/DocumentModel.vb— FileTooLong — 1176 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 676 over it, 2.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: ./MainWindow.Editor.vb MainWindow.Editor.vb— FileTooLong — 1093 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 593 over it, 2.19× 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: Widgets/ReferenceManagerTab.vb Widgets/ReferenceManagerTab.vb— FileTooLong — 984 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 484 over it, 1.97× 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: Widgets/TODOPanel.vb Widgets/TODOPanel.vb— FileTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 452 over it, 1.90× 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: Parsers/RoslynConverter.vb Parsers/RoslynConverter.vb— FileTooLong — 936 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 436 over it, 1.87× 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: Widgets/FindReplacePanel.vb Widgets/FindReplacePanel.vb— FileTooLong — 917 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 417 over it, 1.83× 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: Widgets/AIAssistantPanel.vb Widgets/AIAssistantPanel.vb— FileTooLong — 900 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 400 over it, 1.80× 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: Widgets/CustomDrawNotebook.vb Widgets/CustomDrawNotebook.vb— FileTooLong — 879 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 379 over it, 1.76× 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: Managers/ProjectManager.vb Managers/ProjectManager.vb— FileTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 354 over it, 1.71× 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: Widgets/CustomDrawObjectExplorer.Toolbar.vb Widgets/CustomDrawObjectExplorer.Toolbar.vb— FileTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 354 over it, 1.71× 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: Managers/ProjectManager.Extension3.vb Managers/ProjectManager.Extension3.vb— FileTooLong — 788 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 288 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Managers/BottomPanelManager.vb Managers/BottomPanelManager.vb— FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 276 over it, 1.55× 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: Editors/CustomDrawingEditor.vb Editors/CustomDrawingEditor.vb— FileTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 228 over it, 1.46× 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: Widgets/CustomDrawObjectExplorer.TreeManagement.vb Widgets/CustomDrawObjectExplorer.TreeManagement.vb— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 218 over it, 1.44× 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: ./Program.vb Program.vb— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× 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: Widgets/GitPanel.vb Widgets/GitPanel.vb— FileTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 204 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Widgets/BuildOutputPanel.vb Widgets/BuildOutputPanel.vb— FileTooLong — 694 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 194 over it, 1.39× 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: ./MainWindow.ProjectManager.vb MainWindow.ProjectManager.vb— FileTooLong — 687 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 187 over it, 1.37× 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: ./MainWindow.Menu.vb MainWindow.Menu.vb— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 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: Editors/CustomDrawingEditor.Keyboard.vb Editors/CustomDrawingEditor.Keyboard.vb— FileTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 147 over it, 1.29× 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: Widgets/CustomDrawObjectExplorer.Drawing.vb Widgets/CustomDrawObjectExplorer.Drawing.vb— FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Hotspot: Editors/CustomDrawingEditor.Keyboard.vb Editors/CustomDrawingEditor.Keyboard.vb:20— Editors/CustomDrawingEditor.Keyboard.vb changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 119 in CustomDrawingEditor.OnKeyPress at line 20. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.Keyboard.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.Drawing.vb Editors/CustomDrawingEditor.Drawing.vb:107— Editors/CustomDrawingEditor.Drawing.vb changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in CustomDrawingEditor.DrawContent at line 107. 5 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.Drawing.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/ThemeEditor.vb Widgets/ThemeEditor.vb:511— Widgets/ThemeEditor.vb changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in ThemeEditor.UpdateThemeColor at line 511. 7 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/ThemeEditor.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: MainWindow.Keyboard.vb MainWindow.Keyboard.vb:131— MainWindow.Keyboard.vb changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in MainWindow.OnWindowKeyPress at line 131. 4 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.Keyboard.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: MainWindow.Editor.vb MainWindow.Editor.vb:1670— MainWindow.Editor.vb changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in MainWindow.OnCustomNotebookTabClosed at line 1670. 12 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.Editor.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Program.vb Program.vb:389— Program.vb changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in Program.Main at line 389. 5 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Program.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.CodeSenseTrigger.vb Editors/CustomDrawingEditor.CodeSenseTrigger.vb:490— Editors/CustomDrawingEditor.CodeSenseTrigger.vb changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in CustomDrawingEditor.SelectCodeSenseSuggestionBestMatch at line 490. 9 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.CodeSenseTrigger.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.CodeSensePopup.vb Editors/CustomDrawingEditor.CodeSensePopup.vb:549— Editors/CustomDrawingEditor.CodeSensePopup.vb changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in CustomDrawingEditor.HandleCodeSensePopupKeyPress at line 549. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.CodeSensePopup.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/PreferencesTab.vb Widgets/PreferencesTab.vb:1243— Widgets/PreferencesTab.vb changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in PreferencesTab.LoadSettings at line 1243. 4 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/PreferencesTab.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Utilities/AIChatClient.vb Utilities/AIChatClient.vb:446— Utilities/AIChatClient.vb changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in AIChatClient.ParseArtifact at line 446. 4 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Utilities/AIChatClient.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/FindReplacePanel.vb Widgets/FindReplacePanel.vb:929— Widgets/FindReplacePanel.vb changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in FindReplacePanel.CompleteReplaceAllInProject at line 929. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/FindReplacePanel.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Syntax/CodeSenseEngine.vb Syntax/CodeSenseEngine.vb:1243— Syntax/CodeSenseEngine.vb changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in CodeSenseEngine.AddTypeMemberSuggestions at line 1243. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Syntax/CodeSenseEngine.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: MainWindow.AI.vb MainWindow.AI.vb:89— MainWindow.AI.vb changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in MainWindow.ShowGenerateCodeDialog at line 89. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.AI.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Models/SourceFileInfo.AtomicOperations.vb Models/SourceFileInfo.AtomicOperations.vb:162— Models/SourceFileInfo.AtomicOperations.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in SourceFileInfo.DeleteCharacter at line 162. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Models/SourceFileInfo.AtomicOperations.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/CustomDrawProjectExplorer.ContextMenu.vb Widgets/CustomDrawProjectExplorer.ContextMenu.vb:628— Widgets/CustomDrawProjectExplorer.ContextMenu.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in CustomDrawProjectExplorer.OnContextMenuProperties at line 628. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/CustomDrawProjectExplorer.ContextMenu.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Models/SourceFileInfo.vb Models/SourceFileInfo.vb:188— Models/SourceFileInfo.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in SourceFileInfo.MakeNew at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Models/SourceFileInfo.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.AutoEndConstruct.vb Editors/CustomDrawingEditor.AutoEndConstruct.vb:37— Editors/CustomDrawingEditor.AutoEndConstruct.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in CustomDrawingEditor.TryAutoCompleteBlockStatement at line 37. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.AutoEndConstruct.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.Editing.vb Editors/CustomDrawingEditor.Editing.vb:115— Editors/CustomDrawingEditor.Editing.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CustomDrawingEditor.InsertNewLine at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.Editing.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Managers/ProjectManager.Parser.vb Managers/ProjectManager.Parser.vb:844— Managers/ProjectManager.Parser.vb changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ProjectManager.ParseFileContent at line 844. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Managers/ProjectManager.Parser.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.ContextMenu.vb Editors/CustomDrawingEditor.ContextMenu.vb:249— Editors/CustomDrawingEditor.ContextMenu.vb changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in CustomDrawingEditor.UpdateTextAreaContextMenuStates at line 249. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.ContextMenu.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/CustomDrawObjectExplorer.TreeManagement.vb Widgets/CustomDrawObjectExplorer.TreeManagement.vb:460— Widgets/CustomDrawObjectExplorer.TreeManagement.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in CustomDrawObjectExplorer.ShouldDisplayNode at line 460. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/CustomDrawObjectExplorer.TreeManagement.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Editors/CustomDrawingEditor.Mouse.vb Editors/CustomDrawingEditor.Mouse.vb:818— Editors/CustomDrawingEditor.Mouse.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in CustomDrawingEditor.OnMotionNotify at line 818. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Editors/CustomDrawingEditor.Mouse.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Widgets/LineNumberWidget.vb Widgets/LineNumberWidget.vb:219— Widgets/LineNumberWidget.vb changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in LineNumberWidget.DrawLineNumbers at line 219. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/LineNumberWidget.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Parsers/RoslynConverter.vb Parsers/RoslynConverter.vb:137— Parsers/RoslynConverter.vb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in RoslynConverter.ProcessMember at line 137. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Parsers/RoslynConverter.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Managers/ProjectManager.vb Managers/ProjectManager.vb:684— Managers/ProjectManager.vb changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in ProjectManager.RemoveFileFromProject at line 684. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Managers/ProjectManager.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyMethods: MainWindow MainWindow.AI.vb— TooManyMethods — 12441 significant lines (blank, comment-only and punctuation-only lines excluded), 665 methods. The bar is 30 methods; this is 635 over it, 22.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CustomDrawingEditor Editors/CustomDrawingEditor.AutoEndConstruct.vb— TooManyMethods — 11448 significant lines (blank, comment-only and punctuation-only lines excluded), 470 methods. The bar is 30 methods; this is 440 over it, 15.67× 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: CustomDrawProjectExplorer Widgets/CustomDrawProjectExplorer.AddNewItem.vb— TooManyMethods — 4104 significant lines (blank, comment-only and punctuation-only lines excluded), 180 methods. The bar is 30 methods; this is 150 over it, 6.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CustomDrawObjectExplorer Widgets/CustomDrawObjectExplorer.ContextMenu.vb— TooManyMethods — 3572 significant lines (blank, comment-only and punctuation-only lines excluded), 179 methods. The bar is 30 methods; this is 149 over it, 5.97× 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: ProjectManager Managers/ProjectManager.Extension.vb— TooManyMethods — 3312 significant lines (blank, comment-only and punctuation-only lines excluded), 141 methods. The bar is 30 methods; this is 111 over it, 4.70× 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: CustomDrawNotebook Widgets/CustomDrawNotebook.Animation.vb— TooManyMethods — 2149 significant lines (blank, comment-only and punctuation-only lines excluded), 84 methods. The bar is 30 methods; this is 54 over it, 2.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CustomDrawDataGrid Widgets/CustomDrawDataGrid.Drawing.vb— TooManyMethods — 1722 significant lines (blank, comment-only and punctuation-only lines excluded), 80 methods. The bar is 30 methods; this is 50 over it, 2.67× the bar. 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: FindReplacePanel Widgets/FindReplacePanel.Events.vb— TooManyMethods — 1726 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: CodeSenseEngine Syntax/CodeSenseEngine.vb— TooManyMethods — 1318 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× 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: AIAssistantPanel Widgets/AIAssistantPanel.vb— TooManyMethods — 885 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BuildOutputPanel Widgets/BuildOutputPanel.DataGrid.vb— TooManyMethods — 851 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BottomPanelManager Managers/BottomPanelManager.vb— TooManyMethods — 767 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SourceFileInfo Models/SourceFileInfo.AtomicOperations.vb— TooManyMethods — 1515 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: DocumentModel Models/DocumentModel.vb— TooManyMethods — 1102 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.73× 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: PreferencesTab Widgets/PreferencesTab.vb— TooManyMethods — 1353 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ThemeEditor Widgets/ThemeEditor.vb— TooManyMethods — 1175 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GitPanel Widgets/GitPanel.RefreshStatus.vb— TooManyMethods — 710 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ReferenceManagerTab Widgets/ReferenceManagerTab.vb— TooManyMethods — 974 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TodoPanel Widgets/TODOPanel.vb— TooManyMethods — 666 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ScratchpadPanel Widgets/ScratchpadPanel.vb— TooManyMethods — 618 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: RoslynConverter Parsers/RoslynConverter.vb— TooManyMethods — 924 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HelpBrowser Widgets/HelpBrowser.vb— TooManyMethods — 547 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UndoRedoManager Managers/UndoRedoManager.vb— TooManyMethods — 393 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
MethodTooLong: CustomDrawingEditor.OnKeyPress Editors/CustomDrawingEditor.Keyboard.vb:20— MethodTooLong — OnKeyPress runs 279 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 179 over it, 2.79× 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: KeyboardHelper.GetKeyString Utilities/KeyboardHelper.vb:20— MethodTooLong — GetKeyString runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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: CustomDrawingEditor.DrawContent Editors/CustomDrawingEditor.Drawing.vb:107— MethodTooLong — DrawContent runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainWindow.OnWindowKeyPress MainWindow.Keyboard.vb:131— MethodTooLong — OnWindowKeyPress runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: Program.Main Program.vb:389— MethodTooLong — Main runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: VBTokenizer.TokenizeLine Syntax/VBTokenizer.vb:38— MethodTooLong — TokenizeLine runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: PreferencesTab.CreateAITab Widgets/PreferencesTab.vb:839— MethodTooLong — CreateAITab runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: MainWindow.CreateStatusBar MainWindow.StatusBar.vb:28— MethodTooLong — CreateStatusBar runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: PreferencesTab.LoadSettings Widgets/PreferencesTab.vb:1243— MethodTooLong — LoadSettings runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: ProjectManager.ProcessNodeInContext Managers/ProjectManager.Extension.vb:89— MethodTooLong — ProcessNodeInContext runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ThemeEditor.BuildUI Widgets/ThemeEditor.vb:82— MethodTooLong — BuildUI runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: MainWindow.ShowGenerateCodeDialog MainWindow.AI.vb:89— MethodTooLong — ShowGenerateCodeDialog 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: CustomDrawingEditor.TryAutoCompleteBlockStatement Editors/CustomDrawingEditor.AutoEndConstruct.vb:37— MethodTooLong — TryAutoCompleteBlockStatement runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: FindReplacePanel.SearchInProjectOptimized Widgets/FindReplacePanel.InMemorySearch.vb:62— MethodTooLong — SearchInProjectOptimized runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainWindow.New(…) MainWindow.vb:75— MethodTooLong — New(…) runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NewProjectDialog.BuildUI Dialogs/NewProjectDialog.vb:115— MethodTooLong — BuildUI runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: PreferencesTab.SaveSettings Widgets/PreferencesTab.vb:1430— MethodTooLong — SaveSettings runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× 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: CustomDrawNotebook.UpdateNavigationButtons Widgets/CustomDrawNotebook.vb:1381— MethodTooLong — UpdateNavigationButtons runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: AssemblySettingsEditor.BuildUI Editors/AssemblySettingsEditor.vb:75— MethodTooLong — BuildUI runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: PreferencesTab.CreateGitTab Widgets/PreferencesTab.vb:637— MethodTooLong — CreateGitTab runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× 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: CustomDrawingEditor.OnMotionNotify Editors/CustomDrawingEditor.Mouse.vb:818— MethodTooLong — OnMotionNotify 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.
MethodTooLong: CustomDrawNotebook.ShowAll Widgets/CustomDrawNotebook.Compatibility.vb:84— MethodTooLong — ShowAll runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
Low cohesion: MainWindow (LCOM4 35) MainWindow.vb:19— MainWindow's methods fall into 35 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 35 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: ProjectManager (LCOM4 18) Managers/ProjectManager.vb:21— ProjectManager's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CustomDrawProjectExplorer (LCOM4 16) Widgets/CustomDrawProjectExplorer.vb:25— CustomDrawProjectExplorer's methods fall into 16 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 16 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: BuildOutputPanel (LCOM4 13) Widgets/BuildOutputPanel.vb:16— BuildOutputPanel's methods fall into 13 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 13 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: CustomDrawObjectExplorer (LCOM4 10) Widgets/CustomDrawObjectExplorer.vb:25— CustomDrawObjectExplorer's methods fall into 10 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 10 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: CustomDrawingEditor (LCOM4 7) Editors/CustomDrawingEditor.vb:22— CustomDrawingEditor'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: CustomDrawDataGrid (LCOM4 7) Widgets/CustomDrawDataGrid.vb:18— CustomDrawDataGrid'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: CodeSenseEngine (LCOM4 6) Syntax/CodeSenseEngine.vb:69— CodeSenseEngine's methods fall into 6 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 6 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: FileSystemWatcher (LCOM4 4) Utilities/FileSystemWatcher.vb:12— FileSystemWatcher'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: ThemeEditor (LCOM4 4) Widgets/ThemeEditor.vb:15— ThemeEditor'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.
Repeated repair: MainWindow.vb MainWindow.vb:636— MainWindow.vb changed 31 times in last 90 days and 16 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is MainWindow.OnMainNotebookPageSwitched at line 636), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix pOpenTabs desync on rename, duplicate event wiring, and a runaway theme-menu subscription found by a full-codebase bug-hunting pass”; “Wire up Mem0 memory, fix project scaffolding, finish AI assistant stubs”; “Fix AI assistant's file actions never firing; surface them when they do”; “Fix toolbar double-click-to-maximize; document remaining drag-to-move as a known KWin quirk”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: MainWindow.Events.vb MainWindow.Events.vb:286— MainWindow.Events.vb changed 15 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is MainWindow.OnRunProject at line 286), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Ctrl+D never wired, View-menu checkboxes desyncing (and inverting) from real state, and Build Configuration radio buttons ignoring the loaded configuration”; “Fix remaining silent-catch handlers to surface real error dialogs”; “Fix Ctrl+E and View menu using two divergent, out-of-sync panel toggles”; “Fix Save All always claiming success even when a file failed to save”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.Events.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: Widgets/HelpBrowser.vb Widgets/HelpBrowser.vb:298— Widgets/HelpBrowser.vb changed 15 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is HelpBrowser.SetThemeManager at line 298), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Attempt fix for WebKitGTK content going blank after Home/page cycling”; “Fix Home content and an embedded page both showing at once in Help tab”; “Fix embedded Help pages staying blank permanently after any Home visit”; “Fix Back/Forward re-fetching embedded pages over the network”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/HelpBrowser.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: MainWindow.Toolbar.vb MainWindow.Toolbar.vb:284— MainWindow.Toolbar.vb changed 11 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is MainWindow.OnShowFindPanel at line 284), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix remaining silent-catch handlers to surface real error dialogs”; “Fix Outdent/Indent/Comment toolbar buttons never disabled”; “Fix toolbar double-click-to-maximize; document remaining drag-to-move as a known KWin quirk”; “Convert main toolbar to bevel buttons, add icon auto-contrast, fix combo dropdown bugs”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.Toolbar.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: Managers/UndoRedoManager.vb Managers/UndoRedoManager.vb:425— Managers/UndoRedoManager.vb changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is UndoRedoManager.ApplyUndoAction at line 425), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix pSourceFiles key normalization gaps, UndoRedoManager.Clear() state leaks, and unescaped credential-tool arguments”; “Fix undo/redo stack-limit corruption and stale modified flag; make undo history size configurable”; “Fix undo/redo grouping: BeginUserAction/EndUserAction never actually grouped”; “Fix data-corrupting Undo() eReplace case - wrong range, wrong cursor”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Managers/UndoRedoManager.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: MainWindow.Help.vb MainWindow.Help.vb:129— MainWindow.Help.vb changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is MainWindow.GetCurrentWordAtCursor at line 129), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Run output/error panel tags being swapped, help tabs leaking on close, a stale Preferences tab index, a duplicate status bar separator, and a dead help-tab title update”; “Rebuild Help tab: fix invisible/broken content, replace dead WebKit control, curate Home page”; “Fix remaining icon names and case-sensitive comparisons mangled by old keyword-capitalization bug”; “Fix Object Explorer losing its tree when opening Scratchpad/Help tabs”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.Help.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: MainWindow.HelpTab.vb MainWindow.HelpTab.vb:25— MainWindow.HelpTab.vb changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is MainWindow.OpenHelpTab at line 25), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Run output/error panel tags being swapped, help tabs leaking on close, a stale Preferences tab index, a duplicate status bar separator, and a dead help-tab title update”; “Rebuild Help tab: fix invisible/broken content, replace dead WebKit control, curate Home page”; “Fix Object Explorer losing its tree when opening Scratchpad/Help tabs”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- MainWindow.HelpTab.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: Models/SourceFileInfo.CaseCorrection.vb Models/SourceFileInfo.CaseCorrection.vb:56— Models/SourceFileInfo.CaseCorrection.vb changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is SourceFileInfo.ApplyCaseCorrection at line 56), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix silent BOM/encoding corruption on save, a crash on a missing project file, and a case-correction string-tracking bug”; “Fix CodeSense wrong-suggestion-commit bug and Partial-modifier-order blind spot”; “Fix As-context CodeSense popup noise and restore live keyword auto-capitalization”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Models/SourceFileInfo.CaseCorrection.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: Widgets/CustomDrawObjectExplorer.ContextMenu.vb Widgets/CustomDrawObjectExplorer.ContextMenu.vb:34— Widgets/CustomDrawObjectExplorer.ContextMenu.vb changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is CustomDrawObjectExplorer.ShowTooltip at line 34), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix Object Explorer's right-click menu never actually working”; “Fix Object Explorer's "Navigate to Definition" context menu item doing nothing”; “Fix crash bugs and correctness issues in the Roslyn parser subsystem”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-05-13..2026-08-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-05-13 16:33:47 -05:00' --until='2026-08-11 16:33:47 -05:00' --full-history --no-merges -- Widgets/CustomDrawObjectExplorer.ContextMenu.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
ClassTooLong: Program Program.vb— ClassTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 304 over it, 1.76× 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: AssemblySettingsEditor Editors/AssemblySettingsEditor.vb— ClassTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 199 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ProjectParser Parsers/ProjectParser.vb— ClassTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 182 over it, 1.46× 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: SyntaxNode Syntax/SyntaxNode.vb— ClassTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 167 over it, 1.42× 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: NavigationDropdownPopup Widgets/NavigationDropdownPopup.vb— ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 113 over it, 1.28× 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: CredentialManager Managers/CredentialManager.vb— ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 49 over it, 1.12× 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: GitManager Managers/GitManager.vb— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 40 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AIChatClient Utilities/AIChatClient.vb— ClassTooLong — 432 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 32 over it, 1.08× 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: NavigationDropdowns Widgets/NavigationDropdowns.vb— ClassTooLong — 410 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 10 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.
Duplicated block (12 lines × 2) Managers/GitManager.vb:471— Managers/GitManager.vb:471-482 | Managers/GitManager.vb:494-505 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) Widgets/CustomDrawObjectExplorer.Drawing.vb:181— Widgets/CustomDrawObjectExplorer.Drawing.vb:181-192 | Widgets/CustomDrawProjectExplorer.Drawing.vb:408-419 — 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 (12 lines × 2) Widgets/FindReplacePanel.SortableResults.vb:411— Widgets/FindReplacePanel.SortableResults.vb:411-422 | Widgets/FindReplacePanel.SortableResults.vb:435-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) Widgets/CustomDrawObjectExplorer.Toolbar.vb:869— Widgets/CustomDrawObjectExplorer.Toolbar.vb:869-880 | Widgets/CustomDrawProjectExplorer.Settings.vb:61-72 — 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 (12 lines × 2) Widgets/ReferenceManagerTab.vb:1485— Widgets/ReferenceManagerTab.vb:1485-1496 | Widgets/ResxEditor.vb:374-385 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) Managers/ReferenceManager.vb:489— Managers/ReferenceManager.vb:489-496 | Widgets/ReferenceManagerTab.vb:1466-1472 — 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 (7 lines × 2) Widgets/ScratchpadPanel.vb:603— Widgets/ScratchpadPanel.vb:603-609 | Widgets/ScratchpadPanel.vb:620-626 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Dialogs/DefinitionPickerDialog.vb:99— Dialogs/DefinitionPickerDialog.vb:99-105 | Dialogs/GitBranchDialog.vb:116-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) Widgets/CustomDrawObjectExplorer.Events.vb:416— Widgets/CustomDrawObjectExplorer.Events.vb:416-422 | Widgets/CustomDrawProjectExplorer.Events.vb:327-333 — before extracting anything, compare `Widgets/CustomDrawObjectExplorer.Events.vb` and `Widgets/CustomDrawProjectExplorer.Events.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (7 lines × 2) Widgets/CustomDrawObjectExplorer.Events.vb:429— Widgets/CustomDrawObjectExplorer.Events.vb:429-435 | Widgets/CustomDrawProjectExplorer.Events.vb:340-346 — before extracting anything, compare `Widgets/CustomDrawObjectExplorer.Events.vb` and `Widgets/CustomDrawProjectExplorer.Events.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (9 lines × 2) MainWindow.Toolbar.vb:238— MainWindow.Toolbar.vb:238-246 | Widgets/BuildOutputPanel.vb:237-245 — 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 (9 lines × 2) AI/OpenAICompatibleProvider.vb:169— AI/OpenAICompatibleProvider.vb:169-177 | AI/OpenAICompatibleProvider.vb:197-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) Widgets/CustomDrawObjectExplorer.Events.vb:55— Widgets/CustomDrawObjectExplorer.Events.vb:55-63 | Widgets/CustomDrawProjectExplorer.Events.vb:23-31 — before extracting anything, compare `Widgets/CustomDrawObjectExplorer.Events.vb` and `Widgets/CustomDrawProjectExplorer.Events.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (9 lines × 2) Widgets/ReferenceManagerTab.vb:1514— Widgets/ReferenceManagerTab.vb:1514-1522 | Widgets/ResxEditor.vb:389-397 — 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) Managers/ProjectManager.Parser.vb:944— Managers/ProjectManager.Parser.vb:944-963 | Models/SourceFileInfo.Parsing.vb:605-625 — 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 (20 lines × 2) Widgets/CustomDrawObjectExplorer.vb:737— Widgets/CustomDrawObjectExplorer.vb:737-756 | Widgets/CustomDrawProjectExplorer.Navigation.vb:447-466 — 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) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1454— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1454-1473 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1497-1516 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1519` calls `AppendLine` and `Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1476` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) Editors/CustomDrawingEditor.Search.vb:182— Editors/CustomDrawingEditor.Search.vb:182-199 | Editors/CustomDrawingEditor.Search.vb:224-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) Managers/ProjectManager.Parser.vb:974— Managers/ProjectManager.Parser.vb:974-991 | Models/SourceFileInfo.Parsing.vb:507-524 — 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 (18 lines × 2) Dialogs/BuildConfigurationDialog.vb:52— Dialogs/BuildConfigurationDialog.vb:52-69 | Widgets/TODOPanel.vb:1081-1098 — 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 (15 lines × 2) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1355— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1355-1369 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1430-1444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) Widgets/CustomDrawNotebook.Events.vb:281— Widgets/CustomDrawNotebook.Events.vb:281-295 | Widgets/CustomDrawNotebook.Events.vb:324-338 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) Syntax/SyntaxNode.vb:684— Syntax/SyntaxNode.vb:684-698 | Syntax/SyntaxNode.vb:709-723 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Syntax/SyntaxNode.vb:725` calls `IsNullOrEmpty` and `Syntax/SyntaxNode.vb:699` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1337— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1337-1347 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1413-1423 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1334` calls `AppendLine` and `Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1410` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) Widgets/ReferenceManagerTab.vb:1006— Widgets/ReferenceManagerTab.vb:1006-1018 | Widgets/ReferenceManagerTab.vb:1049-1059 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) AI/AnthropicProvider.vb:92— AI/AnthropicProvider.vb:92-102 | AI/OpenAICompatibleProvider.vb:102-112 — 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 (10 lines × 2) MainWindow.Help.vb:217— MainWindow.Help.vb:217-226 | MainWindow.HelpTab.vb:64-73 — 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 (10 lines × 2) Widgets/ScratchpadPanel.vb:788— Widgets/ScratchpadPanel.vb:788-797 | Widgets/ScratchpadPanel.vb:810-819 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) AI/AIFileSystemBridge.vb:43— AI/AIFileSystemBridge.vb:43-52 | AI/AIFileSystemBridge.vb:74-83 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) Parsers/RoslynConverter.vb:1228— Parsers/RoslynConverter.vb:1228-1250 | Parsers/RoslynConverter.vb:1252-1274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) Widgets/CustomDrawObjectExplorer.Events.vb:245— Widgets/CustomDrawObjectExplorer.Events.vb:245-267 | Widgets/CustomDrawProjectExplorer.Events.vb:178-200 — before extracting anything, compare `Widgets/CustomDrawObjectExplorer.Events.vb` and `Widgets/CustomDrawProjectExplorer.Events.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (17 lines × 2) MainWindow.Menu.vb:907— MainWindow.Menu.vb:907-923 | MainWindow.Menu.vb:928-944 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1308— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1308-1324 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1379-1395 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) Editors/CustomDrawingEditor.vb:899— Editors/CustomDrawingEditor.vb:899-914 | Editors/CustomDrawingEditor.vb:920-935 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) Widgets/CustomDrawObjectExplorer.Toolbar.vb:141— Widgets/CustomDrawObjectExplorer.Toolbar.vb:141-156 | Widgets/CustomDrawProjectExplorer.Toolbar.vb:101-116 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) Managers/ProjectInfo.vb:130— Managers/ProjectInfo.vb:130-143 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:695-708 — 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 (14 lines × 2) AI/Mem0Client.vb:46— AI/Mem0Client.vb:46-60 | AI/Mem0Client.vb:139-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.
Appears unstructured (no recognised architecture) — ~102.8k production LoC (422 types) across 1 project(s) / 13 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
CustomDrawingEditor.OnKeyPress (cyclomatic 119) Editors/CustomDrawingEditor.Keyboard.vb:20— CustomDrawingEditor.OnKeyPress has cyclomatic complexity 119 (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.
KeyboardHelper.GetKeyString (cyclomatic 118) Utilities/KeyboardHelper.vb:20— KeyboardHelper.GetKeyString has cyclomatic complexity 118 (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.
VBTokenizer.TokenizeLine (cyclomatic 90) Syntax/VBTokenizer.vb:38— VBTokenizer.TokenizeLine has cyclomatic complexity 90 (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.
CustomDrawingEditor.DrawContent (cyclomatic 72) Editors/CustomDrawingEditor.Drawing.vb:107— CustomDrawingEditor.DrawContent has cyclomatic complexity 72 (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.
CustomDrawingEditor.TryAutoCompleteBlockStatement (cyclomatic 55) Editors/CustomDrawingEditor.AutoEndConstruct.vb:37— CustomDrawingEditor.TryAutoCompleteBlockStatement has cyclomatic complexity 55 (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.
Program.Main (cyclomatic 52) Program.vb:389— Program.Main has cyclomatic complexity 52 (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.
SourceFileInfo.DeleteCharacter (cyclomatic 51) Models/SourceFileInfo.AtomicOperations.vb:162— SourceFileInfo.DeleteCharacter has cyclomatic complexity 51 (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.
MainWindow.OnWindowKeyPress (cyclomatic 49) MainWindow.Keyboard.vb:131— MainWindow.OnWindowKeyPress has cyclomatic complexity 49 (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.
CustomDrawingEditor.HandleCodeSensePopupKeyPress (cyclomatic 46) Editors/CustomDrawingEditor.CodeSensePopup.vb:549— CustomDrawingEditor.HandleCodeSensePopupKeyPress has cyclomatic complexity 46 (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.
SourceFileInfo.InsertCharacter (cyclomatic 46) Models/SourceFileInfo.AtomicOperations.vb:29— SourceFileInfo.InsertCharacter has cyclomatic complexity 46 (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.
ThemeEditor.UpdateThemeColor (cyclomatic 40) Widgets/ThemeEditor.vb:511— ThemeEditor.UpdateThemeColor has cyclomatic complexity 40 (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.
CustomDrawObjectExplorer.ShouldDisplayNode (cyclomatic 39) Widgets/CustomDrawObjectExplorer.TreeManagement.vb:460— CustomDrawObjectExplorer.ShouldDisplayNode has cyclomatic complexity 39 (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.
SourceFileInfo.SetLineMetadataAndCharacterTokens (cyclomatic 39) Models/SourceFileInfo.AtomicOperations.vb:420— SourceFileInfo.SetLineMetadataAndCharacterTokens has cyclomatic complexity 39 (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.
CustomDrawingEditor.OnMotionNotify (cyclomatic 37) Editors/CustomDrawingEditor.Mouse.vb:818— CustomDrawingEditor.OnMotionNotify has cyclomatic complexity 37 (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.
CustomDrawingEditor.FindMissingDocTags (cyclomatic 37) Editors/CustomDrawingEditor.XmlDocStub.vb:243— CustomDrawingEditor.FindMissingDocTags has cyclomatic complexity 37 (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.
ManifestEditor.ApplySyntaxHighlighting (cyclomatic 36) Editors/ManifestEditor.vb:407— ManifestEditor.ApplySyntaxHighlighting has cyclomatic complexity 36 (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.
ProjectManager.ProcessNodeInContext (cyclomatic 36) Managers/ProjectManager.Extension.vb:89— ProjectManager.ProcessNodeInContext has cyclomatic complexity 36 (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.
RoslynConverter.ParseXmlDocumentation (cyclomatic 33) Parsers/RoslynConverter.vb:1195— RoslynConverter.ParseXmlDocumentation has cyclomatic complexity 33 (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.
CustomDrawNotebook.FocusFirstFocusableChild (cyclomatic 32) Widgets/CustomDrawNotebook.vb:790— CustomDrawNotebook.FocusFirstFocusableChild has cyclomatic complexity 32 (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.
ProjectManager.DumpNodeRecursive (cyclomatic 31) Managers/ProjectManager.Extension3.vb:676— ProjectManager.DumpNodeRecursive has cyclomatic complexity 31 (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.
SourceFileInfo.MakeNew (cyclomatic 30) Models/SourceFileInfo.vb:188— SourceFileInfo.MakeNew has cyclomatic complexity 30 (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.
MainWindow.OnCustomNotebookTabClosed (cyclomatic 29) MainWindow.Editor.vb:1670— MainWindow.OnCustomNotebookTabClosed has cyclomatic complexity 29 (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.
CustomDrawDataGrid.FormatCellValue (cyclomatic 29) Widgets/CustomDrawDataGrid.Methods.vb:689— CustomDrawDataGrid.FormatCellValue has cyclomatic complexity 29 (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.
Program.ProcessNonGuiArguments (cyclomatic 28) Program.vb:780— Program.ProcessNonGuiArguments 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.
CustomDrawingEditor.HandleKeypadCharacter (cyclomatic 28) Editors/CustomDrawingEditor.Keyboard.vb:919— CustomDrawingEditor.HandleKeypadCharacter 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.
CustomDrawProjectExplorer.OnDrawingAreaKeyPress (cyclomatic 28) Widgets/CustomDrawProjectExplorer.Events.vb:227— CustomDrawProjectExplorer.OnDrawingAreaKeyPress 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.
CustomDrawingEditor.ToggleCommentBlock (cyclomatic 27) Editors/CustomDrawingEditor.Comment.vb:26— CustomDrawingEditor.ToggleCommentBlock has cyclomatic complexity 27 (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.
ProjectManager.MergeNodeIntoNamespace (cyclomatic 27) Managers/ProjectManager.Extension3.vb:333— ProjectManager.MergeNodeIntoNamespace has cyclomatic complexity 27 (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.
CustomDrawingEditor.SelectCodeSenseSuggestionBestMatch (cyclomatic 26) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:490— CustomDrawingEditor.SelectCodeSenseSuggestionBestMatch has cyclomatic complexity 26 (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.
CustomDrawingEditor.OutdentSelection (cyclomatic 26) Editors/CustomDrawingEditor.TextManipulation.vb:662— CustomDrawingEditor.OutdentSelection has cyclomatic complexity 26 (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.
ProjectManager.MergeNodeIntoProjectFixed (cyclomatic 26) Managers/ProjectManager.vb:1183— ProjectManager.MergeNodeIntoProjectFixed has cyclomatic complexity 26 (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.
CustomDrawNotebook.UpdateNavigationButtons (cyclomatic 26) Widgets/CustomDrawNotebook.vb:1381— CustomDrawNotebook.UpdateNavigationButtons has cyclomatic complexity 26 (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.
CodeSenseEngine.AddTypeMemberSuggestions (cyclomatic 26) Syntax/CodeSenseEngine.vb:1243— CodeSenseEngine.AddTypeMemberSuggestions has cyclomatic complexity 26 (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.
CustomDrawingEditor.GetWordAt (cyclomatic 25) Editors/CustomDrawingEditor.HoverTooltip.vb:303— CustomDrawingEditor.GetWordAt 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.
AIChatClient.ParseArtifact (cyclomatic 25) Utilities/AIChatClient.vb:446— AIChatClient.ParseArtifact 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.
CustomDrawDataGrid.DrawCell (cyclomatic 24) Widgets/CustomDrawDataGrid.Drawing.vb:299— CustomDrawDataGrid.DrawCell has cyclomatic complexity 24 (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.
CustomDrawObjectExplorer.GetNodeFullyQualifiedName (cyclomatic 24) Widgets/CustomDrawObjectExplorer.Toolbar.vb:1412— CustomDrawObjectExplorer.GetNodeFullyQualifiedName has cyclomatic complexity 24 (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.
CustomDrawProjectExplorer.ScanDirectoryRecursive (cyclomatic 24) Widgets/CustomDrawProjectExplorer.Project.vb:647— CustomDrawProjectExplorer.ScanDirectoryRecursive has cyclomatic complexity 24 (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.
CustomDrawNotebook.ShowAll (cyclomatic 24) Widgets/CustomDrawNotebook.Compatibility.vb:84— CustomDrawNotebook.ShowAll has cyclomatic complexity 24 (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.
CustomDrawNotebook.CalculateButtonsWidth (cyclomatic 24) Widgets/CustomDrawNotebook.vb:1528— CustomDrawNotebook.CalculateButtonsWidth has cyclomatic complexity 24 (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.
CustomDrawingEditor.GetCodeSenseKindColor (cyclomatic 23) Editors/CustomDrawingEditor.CodeSensePopup.vb:372— CustomDrawingEditor.GetCodeSenseKindColor 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.
CustomDrawingEditor.GetParameterNamesFromSignature (cyclomatic 23) Editors/CustomDrawingEditor.XmlDocStub.vb:153— CustomDrawingEditor.GetParameterNamesFromSignature 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.
CustomDrawObjectExplorer.OnDrawingAreaKeyPress (cyclomatic 23) Widgets/CustomDrawObjectExplorer.Events.vb:307— CustomDrawObjectExplorer.OnDrawingAreaKeyPress 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.
CustomDrawProjectExplorer.BuildTreeFromFileList (cyclomatic 23) Widgets/CustomDrawProjectExplorer.vb:612— CustomDrawProjectExplorer.BuildTreeFromFileList 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.
PreferencesTab.LoadSettings (cyclomatic 23) Widgets/PreferencesTab.vb:1243— PreferencesTab.LoadSettings 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.
CustomDrawingEditor.CheckCodeSenseTrigger (cyclomatic 22) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:375— CustomDrawingEditor.CheckCodeSenseTrigger 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.
CustomDrawingEditor.FindIdentifierDeclarationText (cyclomatic 22) Editors/CustomDrawingEditor.HoverTooltip.vb:156— CustomDrawingEditor.FindIdentifierDeclarationText 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.
CustomDrawingEditor.OnScrollEvent (cyclomatic 22) Editors/CustomDrawingEditor.ScrollManual.vb:350— CustomDrawingEditor.OnScrollEvent 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.
CustomDrawDataGrid.DrawRow (cyclomatic 22) Widgets/CustomDrawDataGrid.Drawing.vb:214— CustomDrawDataGrid.DrawRow 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.
PreferencesTab.SaveSettings (cyclomatic 22) Widgets/PreferencesTab.vb:1430— PreferencesTab.SaveSettings 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.
CustomDrawNotebook.OnKeyPress (cyclomatic 22) Widgets/CustomDrawNotebook.Keyboard.vb:29— CustomDrawNotebook.OnKeyPress 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.
SourceFileInfo.ForceImmediateParsing (cyclomatic 22) Models/SourceFileInfo.Parsing.vb:375— SourceFileInfo.ForceImmediateParsing 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.
MainWindow.ShowGenerateCodeDialog (cyclomatic 21) MainWindow.AI.vb:89— MainWindow.ShowGenerateCodeDialog 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.
CustomDrawingEditor.IsDeclarationParameterListOpenParen (cyclomatic 21) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:287— CustomDrawingEditor.IsDeclarationParameterListOpenParen 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.
CustomDrawingEditor.IndentSelection (cyclomatic 21) Editors/CustomDrawingEditor.TextManipulation.vb:493— CustomDrawingEditor.IndentSelection 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.
CustomDrawingEditor.BuildXmlDocBodyLines (cyclomatic 21) Editors/CustomDrawingEditor.XmlDocStub.vb:92— CustomDrawingEditor.BuildXmlDocBodyLines 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.
DocumentModel.TokenizeLine (cyclomatic 21) Models/DocumentModel.vb:1144— DocumentModel.TokenizeLine 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.
ProjectManager.DiagnoseRootClasses (cyclomatic 21) Managers/ProjectManager.Extension3.vb:868— ProjectManager.DiagnoseRootClasses 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.
SourceFileInfo.InsertLineInternal (cyclomatic 21) Models/SourceFileInfo.InternalOperations.vb:144— SourceFileInfo.InsertLineInternal 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.
ProjectManager.ProcessFileStructure (cyclomatic 20) Managers/ProjectManager.Extension3.vb:204— ProjectManager.ProcessFileStructure 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.
SolutionManager.BuildDependencyOrder (cyclomatic 20) Managers/SolutionManager.vb:222— SolutionManager.BuildDependencyOrder 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.
NuGetClient.SearchPackagesAsync (cyclomatic 20) Utilities/SimpleNuGetClient.vb:109— NuGetClient.SearchPackagesAsync 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.
CustomDrawObjectExplorer.DrawFallbackIcon (cyclomatic 19) Widgets/CustomDrawObjectExplorer.Drawing.vb:611— CustomDrawObjectExplorer.DrawFallbackIcon 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.
CustomDrawObjectExplorer.GetNodeTooltip (cyclomatic 19) Widgets/CustomDrawObjectExplorer.Toolbar.vb:970— CustomDrawObjectExplorer.GetNodeTooltip 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.
CustomDrawProjectExplorer.OnContextMenuProperties (cyclomatic 19) Widgets/CustomDrawProjectExplorer.ContextMenu.vb:628— CustomDrawProjectExplorer.OnContextMenuProperties 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.
FindReplacePanel.CompleteReplaceAllInProject (cyclomatic 19) Widgets/FindReplacePanel.vb:929— FindReplacePanel.CompleteReplaceAllInProject 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.
LineNumberWidget.DrawLineNumbers (cyclomatic 19) Widgets/LineNumberWidget.vb:219— LineNumberWidget.DrawLineNumbers 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.
CodeSenseEngine.PopulateScopeContext (cyclomatic 19) Syntax/CodeSenseEngine.vb:1807— CodeSenseEngine.PopulateScopeContext 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.
CodeSenseEngine.ResolveVariableType (cyclomatic 19) Syntax/CodeSenseEngine.vb:1884— CodeSenseEngine.ResolveVariableType 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.
SourceFileInfo.DeleteText (cyclomatic 19) Models/SourceFileInfo.AtomicOperations.vb:330— SourceFileInfo.DeleteText 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.
SourceFileInfo.DeleteLine (cyclomatic 19) Models/SourceFileInfo.AtomicOperations.vb:557— SourceFileInfo.DeleteLine 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.
SourceFileInfo.DetectEncoding (cyclomatic 19) Models/SourceFileInfo.IO.vb:182— SourceFileInfo.DetectEncoding 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.
CustomDrawingEditor.GetObjectBeforePeriod (cyclomatic 18) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:785— CustomDrawingEditor.GetObjectBeforePeriod 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.
CustomDrawingEditor.GetMemberAccessTargetBeforeCurrentWord (cyclomatic 18) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:843— CustomDrawingEditor.GetMemberAccessTargetBeforeCurrentWord 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.
CustomDrawingEditor.UpdateTextAreaContextMenuStates (cyclomatic 18) Editors/CustomDrawingEditor.ContextMenu.vb:249— CustomDrawingEditor.UpdateTextAreaContextMenuStates 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.
CustomDrawingEditor.FindContainingBlockNode (cyclomatic 18) Editors/CustomDrawingEditor.ContextMenu.vb:718— CustomDrawingEditor.FindContainingBlockNode 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.
CustomDrawingEditor.UpdateFontMetrics (cyclomatic 18) Editors/CustomDrawingEditor.Helpers.vb:345— CustomDrawingEditor.UpdateFontMetrics 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.
CustomDrawingEditor.OutdentLine (cyclomatic 18) Editors/CustomDrawingEditor.TextManipulation.vb:398— CustomDrawingEditor.OutdentLine 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.
ProjectManager.FindDefinition (cyclomatic 18) Managers/ProjectManager.Extension3.vb:1224— ProjectManager.FindDefinition 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.
ProjectManager.ParseFileContent (cyclomatic 18) Managers/ProjectManager.Parser.vb:844— ProjectManager.ParseFileContent 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.
CustomDrawProjectExplorer.ShowAddNewItemSelector (cyclomatic 18) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:471— CustomDrawProjectExplorer.ShowAddNewItemSelector 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.
CodeSenseEngine.AddNamespaceMemberSuggestions (cyclomatic 18) Syntax/CodeSenseEngine.vb:1171— CodeSenseEngine.AddNamespaceMemberSuggestions 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.
SyntaxNode.GetDisplayText (cyclomatic 18) Syntax/SyntaxNode.vb:153— SyntaxNode.GetDisplayText 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.
MainWindow.CloseTab (cyclomatic 17) MainWindow.Editor.vb:720— MainWindow.CloseTab has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MainWindow.UpdateMenuStates (cyclomatic 17) MainWindow.Menu.vb:324— MainWindow.UpdateMenuStates has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CustomDrawingEditor.RebuildVisualLineMap (cyclomatic 17) Editors/CustomDrawingEditor.Folding.vb:22— CustomDrawingEditor.RebuildVisualLineMap has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CustomDrawingEditor.ClassifyControlFlowLine (cyclomatic 17) Editors/CustomDrawingEditor.KeywordPairHighlight.vb:255— CustomDrawingEditor.ClassifyControlFlowLine has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CustomDrawingEditor.OnSettingsZoomChanged (cyclomatic 17) Editors/CustomDrawingEditor.Settings.vb:459— CustomDrawingEditor.OnSettingsZoomChanged has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ProjectManager.GetImportsDerivedCandidates (cyclomatic 17) Managers/ProjectManager.SymbolIndex.vb:112— ProjectManager.GetImportsDerivedCandidates has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ProjectSyntaxTree.MergeNodeIntoProject (cyclomatic 17) Parsers/ProjectSyntaxTree.vb:392— ProjectSyntaxTree.MergeNodeIntoProject has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CustomDrawObjectExplorer.HandleProgressiveFQNSearch (cyclomatic 17) Widgets/CustomDrawObjectExplorer.Toolbar.vb:1126— CustomDrawObjectExplorer.HandleProgressiveFQNSearch has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CustomDrawObjectExplorer.BuildVisualNodes (cyclomatic 17) Widgets/CustomDrawObjectExplorer.TreeManagement.vb:706— CustomDrawObjectExplorer.BuildVisualNodes has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FindReplacePanel.FindMatchesInLineOptimized (cyclomatic 17) Widgets/FindReplacePanel.InMemorySearch.vb:294— FindReplacePanel.FindMatchesInLineOptimized has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MainWindow.OnNotebookTabClosing (cyclomatic 16) MainWindow.Editor.vb:618— MainWindow.OnNotebookTabClosing 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.
CustomDrawingEditor.ResolveIdentifierTypeName (cyclomatic 16) Editors/CustomDrawingEditor.AutoEndConstruct.vb:561— CustomDrawingEditor.ResolveIdentifierTypeName 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.
CustomDrawingEditor.OnClipboardTextReceived (cyclomatic 16) Editors/CustomDrawingEditor.Clipboard.vb:124— CustomDrawingEditor.OnClipboardTextReceived 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. This is NOT this file's highest cyclomatic complexity: CustomDrawingEditor.CalculateNodeIndentation (cyclomatic 17) 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.
CustomDrawingEditor.DrawCodeSensePopup (cyclomatic 16) Editors/CustomDrawingEditor.CodeSensePopup.vb:227— CustomDrawingEditor.DrawCodeSensePopup 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.
CustomDrawingEditor.CommitCodeSenseSelection (cyclomatic 16) Editors/CustomDrawingEditor.CodeSensePopup.vb:505— CustomDrawingEditor.CommitCodeSenseSelection 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.
CustomDrawingEditor.HandleCodeSensePopupMotion (cyclomatic 16) Editors/CustomDrawingEditor.CodeSensePopup.vb:727— CustomDrawingEditor.HandleCodeSensePopupMotion 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.
CustomDrawingEditor.IsTypingParameterName (cyclomatic 16) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:237— CustomDrawingEditor.IsTypingParameterName 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. This is NOT this file's highest cyclomatic complexity: CustomDrawingEditor.CheckKeywordTrigger (cyclomatic 18) 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.
CustomDrawingEditor.GetWordAtCursor (cyclomatic 16) Editors/CustomDrawingEditor.Cursor.vb:319— CustomDrawingEditor.GetWordAtCursor 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.
CustomDrawingEditor.InsertNewLine (cyclomatic 16) Editors/CustomDrawingEditor.Editing.vb:115— CustomDrawingEditor.InsertNewLine 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.
CustomDrawingEditor.CutLine (cyclomatic 16) Editors/CustomDrawingEditor.Editing.vb:455— CustomDrawingEditor.CutLine 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.
CustomDrawingEditor.GetUnimplementedInterfaceMembers (cyclomatic 16) Editors/CustomDrawingEditor.ImplementInterface.vb:25— CustomDrawingEditor.GetUnimplementedInterfaceMembers 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.
CustomDrawingEditor.FindContainingMemberScope (cyclomatic 16) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:336— CustomDrawingEditor.FindContainingMemberScope 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.
CustomDrawingEditor.CorrectKeywordEndingAt (cyclomatic 16) Editors/CustomDrawingEditor.LineTracking.vb:42— CustomDrawingEditor.CorrectKeywordEndingAt 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.
GitManager.GetFileStatus (cyclomatic 16) Managers/GitManager.vb:187— GitManager.GetFileStatus 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.
ProjectManager.DiagnoseNamespaceStructure (cyclomatic 16) Managers/ProjectManager.Extension2.vb:674— ProjectManager.DiagnoseNamespaceStructure 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.
ProjectManager.FindDefinitionInFileContent (cyclomatic 16) Managers/ProjectManager.Extension3.vb:1333— ProjectManager.FindDefinitionInFileContent 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.
ProjectParser.MergeNamespaceContents (cyclomatic 16) Parsers/ProjectParser.vb:990— ProjectParser.MergeNamespaceContents 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. This is NOT this file's highest cyclomatic complexity: ProjectParser.ConvertTokenType (cyclomatic 99) 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.
CustomDrawDataGrid.PerformSort (cyclomatic 16) Widgets/CustomDrawDataGrid.Methods.vb:236— CustomDrawDataGrid.PerformSort 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.
NavigationDropdownPopup.DrawItemIcon (cyclomatic 16) Widgets/NavigationDropdownPopup.vb:568— NavigationDropdownPopup.DrawItemIcon 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.
ResxEditor.OnCellDoubleClicked (cyclomatic 16) Widgets/ResxEditor.vb:316— ResxEditor.OnCellDoubleClicked 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.
CodeSenseEngine.ProcessProjectNode (cyclomatic 16) Syntax/CodeSenseEngine.vb:547— CodeSenseEngine.ProcessProjectNode 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 2 projects that do not exist · ×1
Solution references 2 projects that do not exist SimpleIDE.sln— `SimpleIDE.sln` declares 2 project file(s) that are missing from the tree (`SimpleIDE.WebKitGtk.vbproj`, `SimpleIDE.Widgets.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.
VBTokenizer.TokenizeLine (cognitive 161) Syntax/VBTokenizer.vb:38— VBTokenizer.TokenizeLine has cognitive complexity 161 (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.
ProjectManager.ProcessNodeInContext (cognitive 119) Managers/ProjectManager.Extension.vb:89— ProjectManager.ProcessNodeInContext has cognitive complexity 119 (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.
RoslynConverter.ParseXmlDocumentation (cognitive 114) Parsers/RoslynConverter.vb:1195— RoslynConverter.ParseXmlDocumentation has cognitive complexity 114 (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.
CustomDrawingEditor.OnKeyPress (cognitive 109) Editors/CustomDrawingEditor.Keyboard.vb:20— CustomDrawingEditor.OnKeyPress has cognitive complexity 109 (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.
CustomDrawingEditor.DrawContent (cognitive 107) Editors/CustomDrawingEditor.Drawing.vb:107— CustomDrawingEditor.DrawContent has cognitive complexity 107 (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.
ManifestEditor.ApplySyntaxHighlighting (cognitive 98) Editors/ManifestEditor.vb:407— ManifestEditor.ApplySyntaxHighlighting has cognitive complexity 98 (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.
CodeSenseEngine.AddTypeMemberSuggestions (cognitive 96) Syntax/CodeSenseEngine.vb:1243— CodeSenseEngine.AddTypeMemberSuggestions has cognitive complexity 96 (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.
Program.Main (cognitive 95) Program.vb:389— Program.Main has cognitive complexity 95 (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.
CustomDrawingEditor.TryAutoCompleteBlockStatement (cognitive 71) Editors/CustomDrawingEditor.AutoEndConstruct.vb:37— CustomDrawingEditor.TryAutoCompleteBlockStatement has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProjectManager.MergeNodeIntoProjectFixed (cognitive 71) Managers/ProjectManager.vb:1183— ProjectManager.MergeNodeIntoProjectFixed has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.OnMotionNotify (cognitive 63) Editors/CustomDrawingEditor.Mouse.vb:818— CustomDrawingEditor.OnMotionNotify has cognitive complexity 63 (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.
ProjectManager.ProcessFileStructure (cognitive 62) Managers/ProjectManager.Extension3.vb:204— ProjectManager.ProcessFileStructure has cognitive complexity 62 (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.
CustomDrawingEditor.ToggleCommentBlock (cognitive 59) Editors/CustomDrawingEditor.Comment.vb:26— CustomDrawingEditor.ToggleCommentBlock has cognitive complexity 59 (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.
CustomDrawingEditor.FindIdentifierDeclarationText (cognitive 58) Editors/CustomDrawingEditor.HoverTooltip.vb:156— CustomDrawingEditor.FindIdentifierDeclarationText has cognitive complexity 58 (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.
ProjectManager.DiagnoseProjectStructure (cognitive 57) Managers/ProjectManager.Extension2.vb:738— ProjectManager.DiagnoseProjectStructure 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.
SourceFileInfo.SetLineMetadataAndCharacterTokens (cognitive 56) Models/SourceFileInfo.AtomicOperations.vb:420— SourceFileInfo.SetLineMetadataAndCharacterTokens has cognitive complexity 56 (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.
ProjectManager.BuildNamespaceHierarchy (cognitive 50) Managers/ProjectManager.Extension.vb:379— ProjectManager.BuildNamespaceHierarchy has cognitive complexity 50 (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.
ProjectManager.MergeNodeIntoNamespace (cognitive 50) Managers/ProjectManager.Extension3.vb:333— ProjectManager.MergeNodeIntoNamespace has cognitive complexity 50 (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.
MainWindow.OnCustomNotebookTabClosed (cognitive 48) MainWindow.Editor.vb:1670— MainWindow.OnCustomNotebookTabClosed has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FindReplacePanel.FindMatchesInLineOptimized (cognitive 48) Widgets/FindReplacePanel.InMemorySearch.vb:294— FindReplacePanel.FindMatchesInLineOptimized has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawNotebook.FocusFirstFocusableChild (cognitive 48) Widgets/CustomDrawNotebook.vb:790— CustomDrawNotebook.FocusFirstFocusableChild has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawNotebook.UpdateNavigationButtons (cognitive 48) Widgets/CustomDrawNotebook.vb:1381— CustomDrawNotebook.UpdateNavigationButtons has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.OutdentSelection (cognitive 44) Editors/CustomDrawingEditor.TextManipulation.vb:662— CustomDrawingEditor.OutdentSelection has cognitive complexity 44 (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.
NuGetClient.SearchPackagesAsync (cognitive 44) Utilities/SimpleNuGetClient.vb:109— NuGetClient.SearchPackagesAsync has cognitive complexity 44 (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.
CustomDrawingEditor.SelectCodeSenseSuggestionBestMatch (cognitive 42) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:490— CustomDrawingEditor.SelectCodeSenseSuggestionBestMatch 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.
SourceFileInfo.DeleteCharacter (cognitive 42) Models/SourceFileInfo.AtomicOperations.vb:162— SourceFileInfo.DeleteCharacter 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.
DocumentModel.TokenizeLine (cognitive 41) Models/DocumentModel.vb:1144— DocumentModel.TokenizeLine 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.
CustomDrawingEditor.FindMissingDocTags (cognitive 40) Editors/CustomDrawingEditor.XmlDocStub.vb:243— CustomDrawingEditor.FindMissingDocTags has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SolutionManager.BuildDependencyOrder (cognitive 40) Managers/SolutionManager.vb:222— SolutionManager.BuildDependencyOrder has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CodeSenseEngine.PopulateScopeContext (cognitive 40) Syntax/CodeSenseEngine.vb:1807— CodeSenseEngine.PopulateScopeContext has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SourceFileInfo.ForceImmediateParsing (cognitive 40) Models/SourceFileInfo.Parsing.vb:375— SourceFileInfo.ForceImmediateParsing has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DocumentModel.ParseDocument (cognitive 39) Models/DocumentModel.vb:910— DocumentModel.ParseDocument 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.
CustomDrawProjectExplorer.OnContextMenuDelete (cognitive 39) Widgets/CustomDrawProjectExplorer.ContextMenu.vb:442— CustomDrawProjectExplorer.OnContextMenuDelete 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.
MainWindow.OnWindowKeyPress (cognitive 38) MainWindow.Keyboard.vb:131— MainWindow.OnWindowKeyPress 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.
MainWindow.UpdateWelcomeTabRecentFiles (cognitive 38) MainWindow.WelcomeTab.vb:231— MainWindow.UpdateWelcomeTabRecentFiles 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.
CustomDrawDataGrid.FormatCellValue (cognitive 38) Widgets/CustomDrawDataGrid.Methods.vb:689— CustomDrawDataGrid.FormatCellValue 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.
CustomDrawProjectExplorer.BuildTreeFromFileList (cognitive 38) Widgets/CustomDrawProjectExplorer.vb:612— CustomDrawProjectExplorer.BuildTreeFromFileList 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.
SourceFileInfo.InsertLineInternal (cognitive 38) Models/SourceFileInfo.InternalOperations.vb:144— SourceFileInfo.InsertLineInternal 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.
FindReplacePanel.CompleteReplaceAllInProject (cognitive 37) Widgets/FindReplacePanel.vb:929— FindReplacePanel.CompleteReplaceAllInProject 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.
PreferencesTab.OnGitStorageMethodChanged (cognitive 37) Widgets/PreferencesTab.vb:1840— PreferencesTab.OnGitStorageMethodChanged 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.
CustomDrawingEditor.OnScrollEvent (cognitive 36) Editors/CustomDrawingEditor.ScrollManual.vb:350— CustomDrawingEditor.OnScrollEvent 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.
CustomDrawNotebook.ShowAll (cognitive 36) Widgets/CustomDrawNotebook.Compatibility.vb:84— CustomDrawNotebook.ShowAll 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.
CodeSenseEngine.ResolveVariableType (cognitive 36) Syntax/CodeSenseEngine.vb:1884— CodeSenseEngine.ResolveVariableType 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.
MainWindow.UpdateCodeSenseReferences (cognitive 35) MainWindow.CodeSense.vb:66— MainWindow.UpdateCodeSenseReferences 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.
SourceFileInfo.InsertCharacter (cognitive 35) Models/SourceFileInfo.AtomicOperations.vb:29— SourceFileInfo.InsertCharacter 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.
SourceFileInfo.MakeNew (cognitive 34) Models/SourceFileInfo.vb:188— SourceFileInfo.MakeNew 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.
CustomDrawDataGrid.PerformSort (cognitive 34) Widgets/CustomDrawDataGrid.Methods.vb:236— CustomDrawDataGrid.PerformSort 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.
CustomDrawProjectExplorer.OnContextMenuProperties (cognitive 34) Widgets/CustomDrawProjectExplorer.ContextMenu.vb:628— CustomDrawProjectExplorer.OnContextMenuProperties 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.
CustomDrawingEditor.ResolveIdentifierTypeName (cognitive 33) Editors/CustomDrawingEditor.AutoEndConstruct.vb:561— CustomDrawingEditor.ResolveIdentifierTypeName 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.
AIChatClient.ParseArtifact (cognitive 33) Utilities/AIChatClient.vb:446— AIChatClient.ParseArtifact 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.
CustomDrawDataGrid.DrawCell (cognitive 33) Widgets/CustomDrawDataGrid.Drawing.vb:299— CustomDrawDataGrid.DrawCell 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.
CustomDrawDataGrid.DrawRow (cognitive 32) Widgets/CustomDrawDataGrid.Drawing.vb:214— CustomDrawDataGrid.DrawRow 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.
MainWindow.ShowGenerateCodeDialog (cognitive 31) MainWindow.AI.vb:89— MainWindow.ShowGenerateCodeDialog has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.GetCurrentTabInfo (cognitive 31) MainWindow.Editor.vb:249— MainWindow.GetCurrentTabInfo has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.IndentSelection (cognitive 31) Editors/CustomDrawingEditor.TextManipulation.vb:493— CustomDrawingEditor.IndentSelection has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawNotebook.OnKeyPress (cognitive 31) Widgets/CustomDrawNotebook.Keyboard.vb:29— CustomDrawNotebook.OnKeyPress has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProjectSyntaxTree.MergeNodeIntoProject (cognitive 30) Parsers/ProjectSyntaxTree.vb:392— ProjectSyntaxTree.MergeNodeIntoProject 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.
CustomDrawObjectExplorer.SearchVisualNodesByFQN (cognitive 30) Widgets/CustomDrawObjectExplorer.Toolbar.vb:890— CustomDrawObjectExplorer.SearchVisualNodesByFQN 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.
CustomDrawObjectExplorer.HandleProgressiveFQNSearch (cognitive 30) Widgets/CustomDrawObjectExplorer.Toolbar.vb:1126— CustomDrawObjectExplorer.HandleProgressiveFQNSearch 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.
CustomDrawProjectExplorer.OnContextMenuRename (cognitive 30) Widgets/CustomDrawProjectExplorer.ContextMenu.vb:788— CustomDrawProjectExplorer.OnContextMenuRename 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.
CodeSenseEngine.AddNamespaceMemberSuggestions (cognitive 30) Syntax/CodeSenseEngine.vb:1171— CodeSenseEngine.AddNamespaceMemberSuggestions 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.
CustomDrawingEditor.CheckCodeSenseTrigger (cognitive 29) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:375— CustomDrawingEditor.CheckCodeSenseTrigger 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.
CustomDrawingEditor.CutLine (cognitive 29) Editors/CustomDrawingEditor.Editing.vb:455— CustomDrawingEditor.CutLine 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.
ProjectParser.ProcessNodeForTokens (cognitive 29) Parsers/ProjectParser.vb:701— ProjectParser.ProcessNodeForTokens 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.
CustomDrawProjectExplorer.ScanDirectoryRecursive (cognitive 29) Widgets/CustomDrawProjectExplorer.Project.vb:647— CustomDrawProjectExplorer.ScanDirectoryRecursive 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.
CodeSenseEngine.FindContainingClass (cognitive 29) Syntax/CodeSenseEngine.vb:1715— CodeSenseEngine.FindContainingClass 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.
SourceFileInfo.UpdateFromParseResult (cognitive 29) Models/SourceFileInfo.Parsing.vb:164— SourceFileInfo.UpdateFromParseResult 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.
CustomDrawingEditor.GetSelectedText (cognitive 28) Editors/CustomDrawingEditor.Cursor.vb:549— CustomDrawingEditor.GetSelectedText 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.
ProjectManager.VerifyNodeChildren (cognitive 28) Managers/ProjectManager.Extension3.vb:800— ProjectManager.VerifyNodeChildren 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.
CustomDrawingEditor.GetWordAt (cognitive 27) Editors/CustomDrawingEditor.HoverTooltip.vb:303— CustomDrawingEditor.GetWordAt has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawDataGrid.OnContentButtonPress (cognitive 27) Widgets/CustomDrawDataGrid.Events.vb:158— CustomDrawDataGrid.OnContentButtonPress has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.DiagnoseAllNotebooks (cognitive 27) MainWindow.Diagnose.vb:16— MainWindow.DiagnoseAllNotebooks has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.OnRevertToSaved (cognitive 26) MainWindow.Menu.vb:972— MainWindow.OnRevertToSaved 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.
MainWindow.ShowWelcomeTab (cognitive 26) MainWindow.WelcomeTab.vb:24— MainWindow.ShowWelcomeTab 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.
CustomDrawingEditor.FindEnclosingCallOpenParen (cognitive 26) Editors/CustomDrawingEditor.ParameterHint.vb:136— CustomDrawingEditor.FindEnclosingCallOpenParen 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.
ProjectManager.DumpNodeRecursive (cognitive 26) Managers/ProjectManager.Extension3.vb:676— ProjectManager.DumpNodeRecursive 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.
Program.ProcessNonGuiArguments (cognitive 25) Program.vb:780— Program.ProcessNonGuiArguments 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.
CustomDrawingEditor.Dispose (cognitive 25) Editors/CustomDrawingEditor.Dispose.vb:75— CustomDrawingEditor.Dispose 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.
CustomDrawingEditor.GetParameterNamesFromSignature (cognitive 25) Editors/CustomDrawingEditor.XmlDocStub.vb:153— CustomDrawingEditor.GetParameterNamesFromSignature 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.
ProjectManager.FindDefinition (cognitive 25) Managers/ProjectManager.Extension3.vb:1224— ProjectManager.FindDefinition 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.
ProjectManager.FindDefinitionInFileContent (cognitive 25) Managers/ProjectManager.Extension3.vb:1333— ProjectManager.FindDefinitionInFileContent 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.
ProjectParser.ParseProject (cognitive 25) Parsers/ProjectParser.vb:253— ProjectParser.ParseProject 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.
CustomDrawObjectExplorer.UpdateVisibleNodes (cognitive 25) Widgets/CustomDrawObjectExplorer.TreeManagement.vb:1216— CustomDrawObjectExplorer.UpdateVisibleNodes 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.
CustomDrawProjectExplorer.OnDrawingAreaKeyPress (cognitive 25) Widgets/CustomDrawProjectExplorer.Events.vb:227— CustomDrawProjectExplorer.OnDrawingAreaKeyPress 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.
FindReplacePanel.ApplyReplaceAll (cognitive 25) Widgets/FindReplacePanel.vb:1093— FindReplacePanel.ApplyReplaceAll 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.
PreferencesTab.SaveSettings (cognitive 25) Widgets/PreferencesTab.vb:1430— PreferencesTab.SaveSettings 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.
MainWindow.EnsureNotebooksReady (cognitive 24) MainWindow.Events.vb:781— MainWindow.EnsureNotebooksReady has cognitive complexity 24 (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.
CustomDrawingEditor.GetObjectBeforePeriod (cognitive 24) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:785— CustomDrawingEditor.GetObjectBeforePeriod has cognitive complexity 24 (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.
CustomDrawingEditor.TryShowEnumParameterSuggestions (cognitive 24) Editors/CustomDrawingEditor.EnumParameterHint.vb:52— CustomDrawingEditor.TryShowEnumParameterSuggestions has cognitive complexity 24 (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.
ProjectManager.DiagnoseRootClasses (cognitive 24) Managers/ProjectManager.Extension3.vb:868— ProjectManager.DiagnoseRootClasses has cognitive complexity 24 (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.
ProjectManager.UpdateCharacterTokens (cognitive 24) Managers/ProjectManager.Parser.vb:1003— ProjectManager.UpdateCharacterTokens has cognitive complexity 24 (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.
FindReplacePanel.SearchInProjectOptimized (cognitive 24) Widgets/FindReplacePanel.InMemorySearch.vb:62— FindReplacePanel.SearchInProjectOptimized has cognitive complexity 24 (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.
LineNumberWidget.DrawLineNumbers (cognitive 24) Widgets/LineNumberWidget.vb:219— LineNumberWidget.DrawLineNumbers has cognitive complexity 24 (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.
NavigationDropdowns.UpdatePosition (cognitive 24) Widgets/NavigationDropdowns.vb:482— NavigationDropdowns.UpdatePosition has cognitive complexity 24 (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.
CustomDrawNotebook.CalculateButtonsWidth (cognitive 24) Widgets/CustomDrawNotebook.vb:1528— CustomDrawNotebook.CalculateButtonsWidth has cognitive complexity 24 (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.
MainWindow.UpdateTabLabel (cognitive 23) MainWindow.Editor.vb:1110— MainWindow.UpdateTabLabel 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.
MainWindow.ReloadModifiedFiles (cognitive 23) MainWindow.Git.vb:552— MainWindow.ReloadModifiedFiles 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.
CustomDrawingEditor.GetCodeSenseKindColor (cognitive 23) Editors/CustomDrawingEditor.CodeSensePopup.vb:372— CustomDrawingEditor.GetCodeSenseKindColor 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.
CustomDrawingEditor.RebuildVisualLineMap (cognitive 23) Editors/CustomDrawingEditor.Folding.vb:22— CustomDrawingEditor.RebuildVisualLineMap 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.
LineMetadata.GetEncodedTokens (cognitive 23) Models/LineMetadata.vb:83— LineMetadata.GetEncodedTokens 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.
ProjectManager.MergeNodeIntoProjectTree (cognitive 23) Managers/ProjectManager.Extension2.vb:260— ProjectManager.MergeNodeIntoProjectTree 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.
ProjectManager.DiagnoseNamespaceStructure (cognitive 23) Managers/ProjectManager.Extension2.vb:674— ProjectManager.DiagnoseNamespaceStructure 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.
ProjectManager.ParseFileContent (cognitive 23) Managers/ProjectManager.Parser.vb:844— ProjectManager.ParseFileContent 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.
CustomDrawProjectExplorer.ShowAddNewFolderDialog (cognitive 23) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:305— CustomDrawProjectExplorer.ShowAddNewFolderDialog 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.
MainWindow.SaveWindowStateEnhanced (cognitive 23) MainWindow.WindowState.vb:160— MainWindow.SaveWindowStateEnhanced 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.
MainWindow.OnMainNotebookPageSwitched (cognitive 22) MainWindow.vb:636— MainWindow.OnMainNotebookPageSwitched 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.
MainWindow.HasBuildOutput (cognitive 22) MainWindow.Build.vb:1088— MainWindow.HasBuildOutput 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.
MainWindow.OnRequestGotoDefinition (cognitive 22) MainWindow.Editor.vb:1885— MainWindow.OnRequestGotoDefinition 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.
CustomDrawingEditor.FindAllPlainText (cognitive 22) Editors/CustomDrawingEditor.Search.vb:492— CustomDrawingEditor.FindAllPlainText 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.
SourceFileInfo.DeleteLine (cognitive 22) Models/SourceFileInfo.AtomicOperations.vb:557— SourceFileInfo.DeleteLine 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.
MainWindow.CloseTab (cognitive 21) MainWindow.Editor.vb:720— MainWindow.CloseTab has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.UpdateTabModifiedState (cognitive 21) MainWindow.ManifestIntegration.vb:257— MainWindow.UpdateTabModifiedState has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.OnClipboardTextReceived (cognitive 21) Editors/CustomDrawingEditor.Clipboard.vb:124— CustomDrawingEditor.OnClipboardTextReceived has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.HandleCodeSensePopupMotion (cognitive 21) Editors/CustomDrawingEditor.CodeSensePopup.vb:727— CustomDrawingEditor.HandleCodeSensePopupMotion has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.PerformDragDropMove (cognitive 21) Editors/CustomDrawingEditor.DragDrop.vb:357— CustomDrawingEditor.PerformDragDropMove has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.SeedIdentifierCaseMapsFromCurrentContent (cognitive 21) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:50— CustomDrawingEditor.SeedIdentifierCaseMapsFromCurrentContent has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.CorrectUsageCasingOnLine (cognitive 21) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:126— CustomDrawingEditor.CorrectUsageCasingOnLine has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawingEditor.HandleHomeKey (cognitive 21) Editors/CustomDrawingEditor.Keyboard.vb:740— CustomDrawingEditor.HandleHomeKey has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (CustomDrawingEditor.HandleEndKey) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CustomDrawingEditor.HandleEndKey (cognitive 21) Editors/CustomDrawingEditor.Keyboard.vb:791— CustomDrawingEditor.HandleEndKey has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (CustomDrawingEditor.HandleHomeKey) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
CustomDrawingEditor.OutdentLine (cognitive 21) Editors/CustomDrawingEditor.TextManipulation.vb:398— CustomDrawingEditor.OutdentLine has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProjectManager.RemoveFileFromProject (cognitive 21) Managers/ProjectManager.vb:684— ProjectManager.RemoveFileFromProject has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProjectManager.FindOrCreateNamespace (cognitive 21) Managers/ProjectManager.Extension2.vb:198— ProjectManager.FindOrCreateNamespace has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProjectManager.GetImportsDerivedCandidates (cognitive 21) Managers/ProjectManager.SymbolIndex.vb:112— ProjectManager.GetImportsDerivedCandidates has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CustomDrawDataGrid.ApplyFilter (cognitive 21) Widgets/CustomDrawDataGrid.Methods.vb:414— CustomDrawDataGrid.ApplyFilter has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemeEditor.UpdateThemeColor (cognitive 21) Widgets/ThemeEditor.vb:511— ThemeEditor.UpdateThemeColor has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SyntaxNode.GetDisplayText (cognitive 21) Syntax/SyntaxNode.vb:153— SyntaxNode.GetDisplayText has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SourceFileInfo.DeleteText (cognitive 21) Models/SourceFileInfo.AtomicOperations.vb:330— SourceFileInfo.DeleteText has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.OnCodeSenseRequested (cognitive 20) MainWindow.CodeSense.vb:180— MainWindow.OnCodeSenseRequested 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.
MainWindow.OnNotebookTabClosing (cognitive 20) MainWindow.Editor.vb:618— MainWindow.OnNotebookTabClosing 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.
CustomDrawingEditor.DeleteLine (cognitive 20) Editors/CustomDrawingEditor.Helpers.vb:85— CustomDrawingEditor.DeleteLine 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.
CustomDrawingEditor.FindContainingClassOrModuleNode (cognitive 20) Editors/CustomDrawingEditor.ImplementInterface.vb:189— CustomDrawingEditor.FindContainingClassOrModuleNode 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.
CustomDrawingEditor.FindCallableMemberNode (cognitive 20) Editors/CustomDrawingEditor.ParameterHint.vb:225— CustomDrawingEditor.FindCallableMemberNode 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.
CustomDrawingEditor.AutoScrollIfNearEdge (cognitive 20) Editors/CustomDrawingEditor.ScrollManual.vb:680— CustomDrawingEditor.AutoScrollIfNearEdge 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.
DocumentModel.CollectVariablesInScope (cognitive 20) Models/DocumentModel.vb:1557— DocumentModel.CollectVariablesInScope 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.
ProjectParser.ParseSourceFile (cognitive 20) Parsers/ProjectParser.vb:365— ProjectParser.ParseSourceFile 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.
ProjectParser.MergeNamespaceContents (cognitive 20) Parsers/ProjectParser.vb:990— ProjectParser.MergeNamespaceContents 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.
CustomDrawObjectExplorer.OnDrawingAreaDraw (cognitive 20) Widgets/CustomDrawObjectExplorer.Drawing.vb:931— CustomDrawObjectExplorer.OnDrawingAreaDraw 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.
CustomDrawObjectExplorer.ShouldDisplayNode (cognitive 20) Widgets/CustomDrawObjectExplorer.TreeManagement.vb:460— CustomDrawObjectExplorer.ShouldDisplayNode 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.
CustomDrawObjectExplorer.BuildVisualNodes (cognitive 20) Widgets/CustomDrawObjectExplorer.TreeManagement.vb:706— CustomDrawObjectExplorer.BuildVisualNodes 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.
ReferenceManagerTab.OnBrowseAssembly (cognitive 20) Widgets/ReferenceManagerTab.vb:741— ReferenceManagerTab.OnBrowseAssembly 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.
MainWindow.CreateNewTab (cognitive 19) MainWindow.Editor.vb:343— MainWindow.CreateNewTab 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.
MainWindow.OnLeftPanelNotebookSwitchPage (cognitive 19) MainWindow.Editor.vb:1328— MainWindow.OnLeftPanelNotebookSwitchPage 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.
CustomDrawingEditor.ProcessTextForSmartPaste (cognitive 19) Editors/CustomDrawingEditor.Clipboard.vb:433— CustomDrawingEditor.ProcessTextForSmartPaste 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.
CustomDrawingEditor.EnsurePasteColoring (cognitive 19) Editors/CustomDrawingEditor.Clipboard.vb:688— CustomDrawingEditor.EnsurePasteColoring 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.
CustomDrawingEditor.IsDeclarationParameterListOpenParen (cognitive 19) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:287— CustomDrawingEditor.IsDeclarationParameterListOpenParen 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.
CustomDrawingEditor.GetMemberAccessTargetBeforeCurrentWord (cognitive 19) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:843— CustomDrawingEditor.GetMemberAccessTargetBeforeCurrentWord 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.
CustomDrawingEditor.ReplaceSelection (cognitive 19) Editors/CustomDrawingEditor.Editing.vb:649— CustomDrawingEditor.ReplaceSelection 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.
CustomDrawingEditor.ExpandCollapsedAncestorsRecursive (cognitive 19) Editors/CustomDrawingEditor.Folding.vb:181— CustomDrawingEditor.ExpandCollapsedAncestorsRecursive 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.
CustomDrawingEditor.UpdateFontMetrics (cognitive 19) Editors/CustomDrawingEditor.Helpers.vb:345— CustomDrawingEditor.UpdateFontMetrics 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.
CustomDrawingEditor.FindContainingMemberScope (cognitive 19) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:336— CustomDrawingEditor.FindContainingMemberScope 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.
CustomDrawingEditor.Replace (cognitive 19) Editors/CustomDrawingEditor.Search.vb:253— CustomDrawingEditor.Replace 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.
ProjectManager.LoadAllSourceFiles (cognitive 19) Managers/ProjectManager.Parser.vb:516— ProjectManager.LoadAllSourceFiles 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.
ProjectManager.ReindexFile (cognitive 19) Managers/ProjectManager.SymbolIndex.vb:39— ProjectManager.ReindexFile 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.
CustomDrawObjectExplorer.GetNodeTooltip (cognitive 19) Widgets/CustomDrawObjectExplorer.Toolbar.vb:970— CustomDrawObjectExplorer.GetNodeTooltip 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.
CustomDrawProjectExplorer.ShowAddNewItemDialog (cognitive 19) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:166— CustomDrawProjectExplorer.ShowAddNewItemDialog 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.
CustomDrawProjectExplorer.OnContextMenuPaste (cognitive 19) Widgets/CustomDrawProjectExplorer.ContextMenu.vb:322— CustomDrawProjectExplorer.OnContextMenuPaste 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.
FindReplacePanel.FindMatchesInLine (cognitive 19) Widgets/FindReplacePanel.vb:794— FindReplacePanel.FindMatchesInLine 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.
CodeSenseEngine.BuildTopLevelNamespaceCache (cognitive 19) Syntax/CodeSenseEngine.vb:1490— CodeSenseEngine.BuildTopLevelNamespaceCache 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.
SourceFileInfo.GetLineMetadata (cognitive 19) Models/SourceFileInfo.Parsing.vb:318— SourceFileInfo.GetLineMetadata 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.
SourceFileInfo.UpdateCharacterTokens (cognitive 19) Models/SourceFileInfo.Parsing.vb:461— SourceFileInfo.UpdateCharacterTokens 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.
MainWindow.OnRunProject (cognitive 18) MainWindow.Events.vb:286— MainWindow.OnRunProject 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.
CustomDrawingEditor.DrawCodeSensePopup (cognitive 18) Editors/CustomDrawingEditor.CodeSensePopup.vb:227— CustomDrawingEditor.DrawCodeSensePopup 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.
CustomDrawingEditor.GetWordAtCursor (cognitive 18) Editors/CustomDrawingEditor.Cursor.vb:319— CustomDrawingEditor.GetWordAtCursor 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.
CustomDrawingEditor.GetUnimplementedInterfaceMembers (cognitive 18) Editors/CustomDrawingEditor.ImplementInterface.vb:25— CustomDrawingEditor.GetUnimplementedInterfaceMembers 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.
CustomDrawingEditor.BuildInterfaceStub (cognitive 18) Editors/CustomDrawingEditor.ImplementInterface.vb:98— CustomDrawingEditor.BuildInterfaceStub 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.
CustomDrawingEditor.ExtractDeclarations (cognitive 18) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:177— CustomDrawingEditor.ExtractDeclarations 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.
CustomDrawingEditor.FindAllWithRegex (cognitive 18) Editors/CustomDrawingEditor.Search.vb:534— CustomDrawingEditor.FindAllWithRegex 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.
DocumentModel.ConvertToDocumentNode (cognitive 18) Models/DocumentModel.vb:1039— DocumentModel.ConvertToDocumentNode 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.
DocumentModel.OnProjectManagerParseCompleted (cognitive 18) Models/DocumentModel.vb:1677— DocumentModel.OnProjectManagerParseCompleted 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.
RoslynConverter.ProcessRegions (cognitive 18) Parsers/RoslynConverter.vb:1412— RoslynConverter.ProcessRegions 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.
AIAssistantPanel.ParseAIResponse (cognitive 18) Widgets/AIAssistantPanel.vb:766— AIAssistantPanel.ParseAIResponse 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.
BuildOutputPanel.UpdateTabLabels (cognitive 18) Widgets/BuildOutputPanel.vb:719— BuildOutputPanel.UpdateTabLabels 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.
BuildOutputPanel.ShowBuildResultDataGrid (cognitive 18) Widgets/BuildOutputPanel.DataGrid.vb:111— BuildOutputPanel.ShowBuildResultDataGrid 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.
CustomDrawDataGrid.OnHeaderMotionNotify (cognitive 18) Widgets/CustomDrawDataGrid.Events.vb:82— CustomDrawDataGrid.OnHeaderMotionNotify 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.
CustomDrawObjectExplorer.OnDrawingAreaKeyPress (cognitive 18) Widgets/CustomDrawObjectExplorer.Events.vb:307— CustomDrawObjectExplorer.OnDrawingAreaKeyPress 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.
ReferenceManagerTab.OnAddAssemblies (cognitive 18) Widgets/ReferenceManagerTab.vb:803— ReferenceManagerTab.OnAddAssemblies 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.
CodeSenseEngine.GetFrameworkTypeSuggestions (cognitive 18) Syntax/CodeSenseEngine.vb:300— CodeSenseEngine.GetFrameworkTypeSuggestions 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.
CodeSenseEngine.AddProjectTypeSuggestionForNode (cognitive 18) Syntax/CodeSenseEngine.vb:1573— CodeSenseEngine.AddProjectTypeSuggestionForNode 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.
SourceFileInfo.InsertMultiLineTextInternal (cognitive 18) Models/SourceFileInfo.InternalOperations.vb:249— SourceFileInfo.InsertMultiLineTextInternal 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.
MainWindow.ShowQuickOpen (cognitive 17) MainWindow.Keyboard.vb:591— MainWindow.ShowQuickOpen 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.
MainWindow.UpdateMenuStates (cognitive 17) MainWindow.Menu.vb:324— MainWindow.UpdateMenuStates 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.
MainWindow.UpdateWindowTitle (cognitive 17) MainWindow.Project.vb:297— MainWindow.UpdateWindowTitle 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.
CustomDrawingEditor.InsertNewLine (cognitive 17) Editors/CustomDrawingEditor.Editing.vb:115— CustomDrawingEditor.InsertNewLine 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.
CustomDrawingEditor.HandleKeypadCharacter (cognitive 17) Editors/CustomDrawingEditor.Keyboard.vb:919— CustomDrawingEditor.HandleKeypadCharacter 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.
CustomDrawingEditor.ReplaceAll (cognitive 17) Editors/CustomDrawingEditor.Search.vb:320— CustomDrawingEditor.ReplaceAll 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.
CustomDrawingEditor.SurroundSelectionWith (cognitive 17) Editors/CustomDrawingEditor.SurroundWith.vb:34— CustomDrawingEditor.SurroundSelectionWith 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.
ProjectManager.EnsureAllFilesLoaded (cognitive 17) Managers/ProjectManager.Extension3.vb:507— ProjectManager.EnsureAllFilesLoaded 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.
CustomDrawObjectExplorer.PerformSearch (cognitive 17) Widgets/CustomDrawObjectExplorer.Toolbar.vb:705— CustomDrawObjectExplorer.PerformSearch 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.
CustomDrawProjectExplorer.ShowAddEmptyVBFileDialog (cognitive 17) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1679— CustomDrawProjectExplorer.ShowAddEmptyVBFileDialog 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.
FindReplacePanel.SearchInMemoryFile (cognitive 17) Widgets/FindReplacePanel.InMemorySearch.vb:234— FindReplacePanel.SearchInMemoryFile 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.
NewProjectDialog.OnResponse (cognitive 17) Dialogs/NewProjectDialog.vb:338— NewProjectDialog.OnResponse 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.
MemoryManifest.SearchMemories (cognitive 17) AI/MemoryManifest.vb:185— MemoryManifest.SearchMemories 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.
MainWindow.ShowFindPanel (cognitive 16) MainWindow.Find.vb:65— MainWindow.ShowFindPanel 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.
MainWindow.RenameSymbol (cognitive 16) MainWindow.Keyboard.vb:735— MainWindow.RenameSymbol 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.
MainWindow.UpdateObjectExplorerForActiveTab (cognitive 16) MainWindow.ObjectExplorerIntegration.vb:115— MainWindow.UpdateObjectExplorerForActiveTab 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.
CustomDrawingEditor.IsTypingParameterName (cognitive 16) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:237— CustomDrawingEditor.IsTypingParameterName 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.
CustomDrawingEditor.SearchForMatchingBracketBackward (cognitive 16) Editors/CustomDrawingEditor.Colors.vb:146— CustomDrawingEditor.SearchForMatchingBracketBackward 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.
CustomDrawingEditor.FindSystemEnumType (cognitive 16) Editors/CustomDrawingEditor.EnumParameterHint.vb:117— CustomDrawingEditor.FindSystemEnumType 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.
CustomDrawingEditor.DetectAndApplyDeclarationCaseChange (cognitive 16) Editors/CustomDrawingEditor.IdentifierCaseSync.vb:265— CustomDrawingEditor.DetectAndApplyDeclarationCaseChange 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.
CustomDrawingEditor.SelectWord (cognitive 16) Editors/CustomDrawingEditor.Mouse.vb:568— CustomDrawingEditor.SelectWord 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.
CustomDrawingEditor.OutdentLinePrivate (cognitive 16) Editors/CustomDrawingEditor.TextManipulation.vb:274— CustomDrawingEditor.OutdentLinePrivate 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.
CustomDrawingEditor.CheckXmlDocTrigger (cognitive 16) Editors/CustomDrawingEditor.XmlDocStub.vb:24— CustomDrawingEditor.CheckXmlDocTrigger 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.
ProjectManager.CheckSourceFile (cognitive 16) Managers/ProjectManager.Extension3.vb:992— ProjectManager.CheckSourceFile 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.
ProjectManager.ParseProjectStructure (cognitive 16) Managers/ProjectManager.Parser.vb:255— ProjectManager.ParseProjectStructure 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.
ReferenceManager.GetAllReferences (cognitive 16) Managers/ReferenceManager.vb:240— ReferenceManager.GetAllReferences 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.
RoslynConverter.ExtractLocalVariables (cognitive 16) Parsers/RoslynConverter.vb:1108— RoslynConverter.ExtractLocalVariables 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.
ProjectParser.ParseContent (cognitive 16) Parsers/ProjectParser.vb:508— ProjectParser.ParseContent 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.
CustomDrawDataGrid.UpdateColumnWidths (cognitive 16) Widgets/CustomDrawDataGrid.Methods.vb:768— CustomDrawDataGrid.UpdateColumnWidths 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.
CustomDrawObjectExplorer.ShowImmediateChildren (cognitive 16) Widgets/CustomDrawObjectExplorer.Toolbar.vb:1274— CustomDrawObjectExplorer.ShowImmediateChildren 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.
LineNumberWidget.OnButtonPress (cognitive 16) Widgets/LineNumberWidget.vb:375— LineNumberWidget.OnButtonPress 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.
ScratchpadPanel.OnNewScratchpad (cognitive 16) Widgets/ScratchpadPanel.vb:482— ScratchpadPanel.OnNewScratchpad 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.
CustomDrawNotebook.RemovePage (cognitive 16) Widgets/CustomDrawNotebook.vb:485— CustomDrawNotebook.RemovePage 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.
CodeSenseEngine.AddNodeMemberSuggestions (cognitive 16) Syntax/CodeSenseEngine.vb:1108— CodeSenseEngine.AddNodeMemberSuggestions 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.
SourceFileInfo.EnsureCharacterTokens (cognitive 16) Models/SourceFileInfo.Parsing.vb:248— SourceFileInfo.EnsureCharacterTokens 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.
Near-duplicate member pair (43 shared lines) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1308— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1308-1369 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1379-1444 — These two members are variants of one another: 43 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Editors/CustomDrawingEditor.Drawing.vb:501— Editors/CustomDrawingEditor.Drawing.vb:501-517 | Models/CharacterColorInfo.vb:115-123 | Widgets/CustomDrawObjectExplorer.Drawing.vb:348-364 | Widgets/CustomDrawProjectExplorer.Drawing.vb:366-381 | Widgets/NavigationDropdownPopup.vb:648-658 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (49–50 lines × 2) Editors/CustomDrawingEditor.TextManipulation.vb:494— Editors/CustomDrawingEditor.TextManipulation.vb:494-543 | Editors/CustomDrawingEditor.TextManipulation.vb:663-711 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (32–49 lines × 2) Editors/CustomDrawingEditor.ContextMenu.vb:477— Editors/CustomDrawingEditor.ContextMenu.vb:477-525 | Editors/CustomDrawingEditor.ContextMenu.vb:543-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (41–42 lines × 2) Editors/CustomDrawingEditor.TextManipulation.vb:599— Editors/CustomDrawingEditor.TextManipulation.vb:599-640 | Editors/CustomDrawingEditor.TextManipulation.vb:786-826 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (35–36 lines × 2) Models/DocumentModel.vb:953— Models/DocumentModel.vb:953-988 | Models/DocumentModel.vb:1689-1723 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (33 lines × 2) MainWindow.Navigation.vb:379— MainWindow.Navigation.vb:379-411 | MainWindow.Navigation.vb:437-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (32 lines × 2) MainWindow.Help.vb:303— MainWindow.Help.vb:303-334 | MainWindow.Keyboard.vb:961-992 — 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 (29–30 lines × 2) Parsers/RoslynConverter.vb:159— Parsers/RoslynConverter.vb:159-188 | Parsers/RoslynConverter.vb:211-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2) MainWindow.Build.vb:567— MainWindow.Build.vb:567-595 | Widgets/PreferencesTab.vb:1909-1937 — 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 (21–29 lines × 2) Editors/CustomDrawingEditor.Editing.vb:359— Editors/CustomDrawingEditor.Editing.vb:359-379 | Editors/CustomDrawingEditor.TextManipulation.vb:57-85 — 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 (27 lines × 2) Widgets/CustomDrawObjectExplorer.Navigation.vb:22— Widgets/CustomDrawObjectExplorer.Navigation.vb:22-48 | Widgets/CustomDrawProjectExplorer.Navigation.vb:477-503 — 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 (25 lines × 2) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:750— Editors/CustomDrawingEditor.CodeSenseTrigger.vb:750-774 | Editors/CustomDrawingEditor.CodeSenseTrigger.vb:900-924 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Editors/CustomDrawingEditor.CodeSenseTrigger.vb:900` calls `lLine` and `Editors/CustomDrawingEditor.CodeSenseTrigger.vb:750` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–24 lines × 2) Managers/BuildManager.vb:338— Managers/BuildManager.vb:338-352 | Managers/BuildManager.vb:376-399 — 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 `Managers/BuildManager.vb:376` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (18–23 lines × 3) MainWindow.Navigation.vb:300— MainWindow.Navigation.vb:300-322 | MainWindow.Resources.vb:221-238 | MainWindow.Resources.vb:274-291 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19–22 lines × 2) Models/DocumentModel.vb:1640— Models/DocumentModel.vb:1640-1661 | Models/DocumentModel.vb:1792-1810 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Models/DocumentModel.vb:1662` calls `AddEventHandler` and `Models/DocumentModel.vb:1813` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) Managers/BuildManager.vb:72— Managers/BuildManager.vb:72-102 | Managers/BuildManager.vb:259-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) Widgets/TODOPanel.vb:681— Widgets/TODOPanel.vb:681-701 | Widgets/TODOPanel.vb:993-1013 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (19 lines × 3) Widgets/ThemeEditor.vb:650— Widgets/ThemeEditor.vb:650-668 | Widgets/ThemeEditor.vb:1151-1169 | Widgets/ThemeEditor.vb:1238-1256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Widgets/ThemeEditor.vb:1170` calls `SelectRegion` and `Widgets/ThemeEditor.vb:670` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) Utilities/StrongNameHelper.vb:41— Utilities/StrongNameHelper.vb:41-59 | Utilities/StrongNameHelper.vb:70-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–18 lines × 2) Widgets/CustomDrawObjectExplorer.Events.vb:282— Widgets/CustomDrawObjectExplorer.Events.vb:282-299 | Widgets/CustomDrawProjectExplorer.Events.vb:206-219 — before extracting anything, compare `Widgets/CustomDrawObjectExplorer.Events.vb` and `Widgets/CustomDrawProjectExplorer.Events.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 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 (16–18 lines × 2) Widgets/HelpBrowser.vb:343— Widgets/HelpBrowser.vb:343-360 | Widgets/HelpBrowser.vb:392-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 3) Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1175— Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1175-1191 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1221-1237 | Widgets/CustomDrawProjectExplorer.AddNewItem.vb:1269-1285 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13–16 lines × 3) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:753— Editors/CustomDrawingEditor.CodeSenseTrigger.vb:753-767 | Editors/CustomDrawingEditor.CodeSenseTrigger.vb:860-872 | Editors/CustomDrawingEditor.CodeSenseTrigger.vb:902-917 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 2) Editors/AssemblySettingsEditor.vb:347— Editors/AssemblySettingsEditor.vb:347-360 | Editors/AssemblySettingsEditor.vb:679-690 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) Editors/CustomDrawingEditor.Clipboard.vb:38— Editors/CustomDrawingEditor.Clipboard.vb:38-50 | Editors/CustomDrawingEditor.Clipboard.vb:292-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Editors/CustomDrawingEditor.Clipboard.vb:34` calls `Get`, `Intern` and `Editors/CustomDrawingEditor.Clipboard.vb:291` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–12 lines × 5) Editors/CustomDrawingEditor.Drawing.vb:506— Editors/CustomDrawingEditor.Drawing.vb:506-517 | Models/CharacterColorInfo.vb:115-120 | Widgets/CustomDrawObjectExplorer.Drawing.vb:353-364 | Widgets/CustomDrawProjectExplorer.Drawing.vb:372-381 | Widgets/NavigationDropdownPopup.vb:650-658 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Models/CharacterColorInfo.vb:120` calls `ToByte`, `Substring`, `Color` and `Editors/CustomDrawingEditor.Drawing.vb:517` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–12 lines × 3) Editors/CustomDrawingEditor.CodeSenseTrigger.vb:115— Editors/CustomDrawingEditor.CodeSenseTrigger.vb:115-125 | Editors/CustomDrawingEditor.CodeSenseTrigger.vb:159-170 | Editors/CustomDrawingEditor.CodeSenseTrigger.vb:199-210 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) Editors/CustomDrawingEditor.Cursor.vb:555— Editors/CustomDrawingEditor.Cursor.vb:555-565 | Editors/CustomDrawingEditor.vb:900-910 | Editors/CustomDrawingEditor.vb:921-931 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) Syntax/SyntaxNode.vb:687— Syntax/SyntaxNode.vb:687-695 | Syntax/SyntaxNode.vb:712-720 | Syntax/SyntaxNode.vb:799-807 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–8 lines × 2) Editors/CustomDrawingEditor.Editing.vb:685— Editors/CustomDrawingEditor.Editing.vb:685-691 | Editors/CustomDrawingEditor.TextManipulation.vb:127-134 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Editors/CustomDrawingEditor.TextManipulation.vb:125` calls `IsNullOrEmpty` and `Editors/CustomDrawingEditor.Editing.vb:684` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 4) MainWindow.Resources.vb:229— MainWindow.Resources.vb:229-235 | MainWindow.Resources.vb:282-288 | Widgets/ThemeEditor.vb:656-662 | Widgets/ThemeEditor.vb:1157-1163 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 2) Editors/AssemblySettingsEditor.vb:653— Editors/AssemblySettingsEditor.vb:653-657 | Editors/ManifestEditor.vb:547-551 — 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.
No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
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.
Fat interface: IEditor (112 members) Interfaces/IEditor.vb:20— `IEditor` declares 112 members: `FilePath`, `IsModified`, `IsReadOnly`, `CanUndo`, `CanRedo`, `CanCut`, `CanCopy`, `CanPaste`, `Text`, `TextLines`, `LineCount`, `CharCount`, `CurrentLine`, `CurrentColumn`, `HasSelection`, `SelectionStart`, `SelectionEnd`, `SelectedText`, `Widget`, `SupportsLineNumbers`, `SupportsSyntaxHighlighting`, `SupportsNavigation`, `RootNode`, `SourceFileInfo`, `Modified`, `CursorPositionChanged`, `SelectionChanged`, `TextChanged`, `UndoRedoStateChanged`, `DocumentParsed`, `LineExited`, `ProjectManagerRequested`, `RequestGotoDefinition`, `RequestFindAllReferences`, `CodeSenseRequested`, `CodeSenseCancelled`, `FindRequested`, `ReplaceRequested`, `SetThemeManager`, `Undo`, and 72 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 112 declarations carry 111 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 111 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IObjectExplorer (20 members) Interfaces/IObjectExplorer.vb:20— `IObjectExplorer` declares 20 members: `NodeSelected`, `NodeDoubleClicked`, `NodeActivated`, `NavigateToFile`, `CloseRequested`, `UpdateStructure`, `LoadProjectStructure`, `SetProjectStructure`, `ClearStructure`, `RefreshStructure`, `SetCurrentEditor`, `InitializeWithProjectManager`, `NavigateToNode`, `SetRefreshEnabled`, `OnPageActivated`, `DiagnoseTreeViewStatus`, `TestTreeViewVisibility`, `TestWithSimpleContent`, `DiagnoseWithLabel`, `CheckTreeViewContent`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: ICustomNotebook (21 members) Interfaces/ICustomNotebook.vb:11— `ICustomNotebook` declares 21 members: `CurrentPage`, `NPages`, `AppendPage`, `RemovePage`, `GetNthPage`, `GetTabLabel`, `SetTabLabel`, `SetTabLabelText`, `PageNum`, `SetTabModified`, `SetTabIcon`, `ShowTabContextMenu`, `SwitchToNextTab`, `SwitchToPreviousTab`, `TabClosing`, `CurrentTabChanged`, `TabClosed`, `TabReordered`, `TabContextMenuRequested`, `TabModifiedChanged`, `HidePanelRequested`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Single-project monolith — The whole codebase lives in one project — at this size, splitting along clear seams (domain / infrastructure / hosting) would make boundaries explicit and builds faster.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `SimpleIDE` (102785 LoC, 389 public types across 11 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
README/code drift — README advertises Docker containerisation, but no Dockerfile/compose file exists — searched for: `dockerfile`, `docker-compose`, `compose.yaml`, `compose.yml`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest files (package.json, *.csproj, *.props, *.slnx, *.yml, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a0f7bb-7497-758f-82a8-e782a011d300 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 41 · Warnings: 614 · Recommendations: 12 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 01-10-2026 @ 13:50 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.