display-drivers-uninstaller

Executive summary

Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.

Wagnard/display-drivers-uninstaller carries serious gaps (39%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.

It is strongest in Security (100%) — its security and compliance posture is in good shape.

The area that most needs attention is Readiness (17%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (51%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.

Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); ILogger (or Serilog) and log at meaningful points across… (Observability); 1 No automated tests finding(s) in Code Coverage (Code Coverage).

For scale: — (~0 production lines); rebuilding it from scratch would take roughly — (—). Approximate, ±~30%.

It builds on a genuinely strong Security foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.

Code Health 73% Adequate · gated by D1, D2, D18 Architecture 56% Adequate · gated by AX5 Maturity 51% Adequate · gated by M2 Readiness 17% ⚠ Critical · gated by D8, D9, P1, P2, P3 Security 100% ★ Exemplary

How the score is built — each lens's share of the headline Width 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.

Readiness 17% · 47% weightMaturity 51% · 26% weightArchitecture 56% · 14% weightCode Health 73% · 8% weightSecurity 100% · 4% weight

Raise Readiness 17 → 70 (the Healthy floor) ⇒ headline 39 → ~59.

Code composition — where the lines go

Generated 100%

New since the last scan (22+)

22 finding(s) are new versus the previous scan (2026-08-03) — surfaced by this scheduled scan itself, no pull request required.

D3 · FileTooLong: Win32/TaskScheduler.vb display-driver-uninstaller/Display Driver Uninstaller/Win32/TaskScheduler.vb
D4 · Duplicated block (226 lines × 3) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb
D4 · Duplicated block (15 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb
D4 · Duplicated block (15 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb
D4 · Duplicated block (13 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb
D4 · Duplicated block (11 lines × 6) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb
D4 · Duplicated block (10 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb
D4 · Duplicated block (9 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb
D4 · Duplicated block (8 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb
D4 · Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb
D4 · Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmLog.xaml.vb
D4 · Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb
D35 · Change coupling: GPUCleanup.vb ↔ ImpersonateLoggedOnUser.vb display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb
D35 · Change coupling: LogEntry.vb ↔ SetupAPI.vb display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb
D35 · Change coupling: AppSettings.vb ↔ ThreadSettings.vb display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb
D35 · Change coupling: LogEntry.vb ↔ WinAPI.vb display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb
D35 · Change coupling: AppPaths.vb ↔ Application.xaml.vb display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb
D35 · Change coupling: AppLaunchOptions.vb ↔ GPUCleanup.vb display-driver-uninstaller/Display Driver Uninstaller/AppLaunchOptions.vb
D35 · Change coupling: CheckUpdate.vb ↔ AssemblyInfo.vb display-driver-uninstaller/Display Driver Uninstaller/CheckUpdate.vb
D35 · Change coupling: DebugWindow.xaml.vb ↔ GPUCleanup.vb display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb
P2 · No structured logging
SC1 · NuGet dependencies are not locked

A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

Resolve the 1 No automated tests finding(s) in Code Coverage.

+19.1 pts · Low effort · Code Coverage

Resolve the 1 No tests found finding(s) in Test Distribution.

+19.1 pts · Low effort · Test Distribution

Add a CI workflow that builds and runs the test suite on every push/PR.

+22.1 pts · Medium effort · CI/CD gates

Diagnosis — what's actually going on

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.

At a glance — Code Health · 73% · Adequate · gated by D1, D2, D18

The Good

D3 · .NET / C# God Classes 8.1 D4 · .NET / C# Code Duplication 9.8 GD1 · Repo Unfinished & placeholder code 10.0 X1 · Repo Async correctness 10.0 X3 · Repo Exception handling 10.0 X4 · Repo Structured logging 10.0

The Bad

D17 · .NET / C# Explicit Debt 5.8

The Ugly

D1 · .NET / C# Cyclomatic Complexity 2.0 D2 · .NET / C# Cognitive Complexity 2.0 D18 · .NET / C# Solution Shape 2.0

At a glance — Architecture · 56% · Adequate · gated by AX5

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 8.8 D26 · .NET / C# Project Cohesion 10.0 D35 · .NET / C# Change Coupling 7.2

The Ugly

AX5 · Repo Architecture & structure 3.0

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

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 10.0 D19 · .NET / C# Documentation Quality 8.0 D21 · .NET / C# Naming Consistency 10.0 D34 · .NET / C# Knowledge Freshness 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M1 · Repo Documentation (README) 6.7 M3 · Repo Folder & project structure 6.0

The Ugly

M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 17% · Critical · gated by D8, D9, P1, P2, P3

The Good

D12 · .NET / C# Dependency Hygiene 10.0 D13 · .NET / C# Secret Scanning 10.0

The Ugly

D8 · .NET / C# Code Coverage 0.0 P1 · Repo CI/CD gates 0.0 P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 100% · Exemplary

The Good

D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 10.0 D30 · .NET / C# Dependency Vulnerabilities 10.0

Roadmap

First, establish a continuous integration workflow to automatically build and test every code change. Next, implement structured logging across all projects to improve observability and system monitoring. Then, address the lack of automated tests by resolving the identified coverage gaps and ensuring tests are properly distributed. Finally, begin documenting significant architectural decisions and their rationale to improve long-term maintainability.

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.	+19.1 pts	Low	Code Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.	+19.1 pts	Low	Test Distribution
Add a CI workflow that builds and runs the test suite on every push/PR.	+22.1 pts	Medium	CI/CD gates
Adopt ILogger (or Serilog) and log at meaningful points across the projects.	+22.1 pts	Medium	Observability
Start an ADR log (docs/adr/) recording significant decisions and their rationale.	+5.7 pts	Medium	Architecture documentation
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.	+5.1 pts	Medium	Folder & project structure
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.	+4.6 pts	Medium	Architecture & structure
Add a 'Testing' section to the root README — how to run the test suite.	+4.5 pts	Medium	Documentation (README)

File quality

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

File	Score	Band	Worst signal
display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb	1.0	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb	1.0	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb	1.3	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb	2.2	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb	2.8	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/Win32/ServiceInstaller.vb	3.2	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb	3.9	Slop	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb	4.8	Mixed	Cyclomatic Complexity: DebugWindow.CopyCommand (cyclomatic 48)
display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb	4.8	Mixed	Cyclomatic Complexity: AppSettings.Load (cyclomatic 62)
display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb	4.9	Mixed	Cyclomatic Complexity: LogEntry.AddDevices (cyclomatic 47)
display-driver-uninstaller/Display Driver Uninstaller/Win32/TaskScheduler.vb	5.4	Mixed	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/DDUSafeBootService.vb	5.5	Mixed	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb	6.1	Mixed	Explicit Debt: EmptyCatchBlock
display-driver-uninstaller/Display Driver Uninstaller/AppLaunchOptions.vb	6.7	Mixed	Explicit Debt: TodoComment
display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb	7.0	Mixed	Cyclomatic Complexity: SetupAPI.TEST_GetDevices (cyclomatic 52)
display-driver-uninstaller/Display Driver Uninstaller/Language.vb	7.0	Mixed	Cyclomatic Complexity: Languages.CheckLanguageFileForErrors (cyclomatic 52)
display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb	7.0	Mixed	Cyclomatic Complexity: FileIO.DeleteInternal (cyclomatic 40)
display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb	7.1	Mixed	Cyclomatic Complexity: Registry.FixRights (cyclomatic 30)
display-driver-uninstaller/Display Driver Uninstaller/Tools.vb	7.1	Mixed	Cyclomatic Complexity: Tools.PreferredUILanguages (cyclomatic 16)
display-driver-uninstaller/Display Driver Uninstaller/AppLog.vb	7.2	Mixed	Cyclomatic Complexity: AppLog.OpenLog (cyclomatic 52)

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. 32 of 34 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 34 dimensions across the health lenses

D1D2D3D4D5D6D8D9D12D13D15D16D17D18D19D21D26D28D29D30D34D35AX5GD1M1M2M3M4P1P2P3X1X3X4

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, 262 of 267 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
jscpd	Code duplication	—	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.301	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.301	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fdeb1-5e2c-7e39-9f34-e63753991291.

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

Run transparency — what happened this run

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

D31 IaC & Container Security — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D36 Supply-chain Provenance & Signing — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.

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 (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
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 suite (`dotnet test --collect`) 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").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (EF migrations, designer files, snapshots) 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.
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.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
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.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

65 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GPUCleanup.Start at 334.

GPUCleanup.Start (cyclomatic 334)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:20

CleanupEngine.Installer (cyclomatic 191)display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1385

GPUCleanup.CleanNvidiaFolders (cyclomatic 168)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:6281

GPUCleanup.CleanVulkan (cyclomatic 167)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8475

CleanupEngine.Clsidleftover (cyclomatic 123)display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2481

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

What to do

Resolve the 1 GPUCleanup.Start (cyclomatic 334) finding(s) in Cyclomatic Complexity — start with GPUCleanup.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CleanupEngine.Installer (cyclomatic 191) finding(s) in Cyclomatic Complexity — start with CleanupEngine.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 GPUCleanup.CleanNvidiaFolders (cyclomatic 168) finding(s) in Cyclomatic Complexity — start with GPUCleanup.vb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

83 method(s) exceeded the cognitive complexity threshold of 15; the worst was GPUCleanup.Start at 1157.

GPUCleanup.Start (cognitive 1157)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:20

CleanupEngine.Installer (cognitive 1131)display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1385

CleanupEngine.Clsidleftover (cognitive 552)display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2481

GPUCleanup.CleanVulkan (cognitive 499)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8475

Languages.CheckLanguageFileForErrors (cognitive 308)display-driver-uninstaller/Display Driver Uninstaller/Language.vb:734

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

What to do

Resolve the 1 GPUCleanup.Start (cognitive 1157) finding(s) in Cognitive Complexity — start with GPUCleanup.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CleanupEngine.Installer (cognitive 1131) finding(s) in Cognitive Complexity — start with CleanupEngine.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CleanupEngine.Clsidleftover (cognitive 552) finding(s) in Cognitive Complexity — start with CleanupEngine.vb. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes8.1 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

11 god class(es) detected.

FileTooLong: Display Driver Uninstaller/AppSettings.vb · ×11display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:0

TooManyMethods: Application · ×6display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:0

ClassTooLong: AppSettings · ×3display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:0

What to do

Resolve the 11 FileTooLong finding(s) in God Classes — start with ACL.vb, AppSettings.vb, Application.xaml.vb. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 6 TooManyMethods finding(s) in God Classes — start with Application.xaml.vb, CleanupEngine.vb, FileIO.vb. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with AppSettings.vb, DebugWindow.xaml.vb, Language.vb. — One of this dimension's main actionable groups (3 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.8 / 10Exemplary✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

14 duplicated block group(s) detected.

Duplicated block (6 lines × 2) · ×3display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb:20

Duplicated block (15 lines × 2) · ×2display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:549

Duplicated block (10 lines × 2) · ×2display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1733

Duplicated block (226 lines × 3)display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1196

Duplicated block (14 lines × 2)display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:435

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

✓ On the Gold path — maintain.

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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)8.8 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

3 of 31 classes have LCOM4 above 3.

Low cohesion: FrmMain (LCOM4 7) · ×3display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:31

What to do

Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with AppSettings.vb, DebugWindow.xaml.vb, FrmMain.xaml.vb. — One of this dimension's main actionable groups (3 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

No automated tests — the solution has no test code.

No automated tests

What to do

Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

No test projects found.

No tests found

What to do

Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

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.

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

0 outdated, 0 vulnerable, 0 deprecated packages.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

No source file's living knowledge is concentrated in a single author.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt5.8 / 10Adequate✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

67 deducted debt markers + 0 dead symbols across 27592 LoC (2.1/KLoC) → score 5.8.

EmptyCatchBlock · ×61display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:244

TodoComment · ×6display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:7

What to do

Resolve the 61 EmptyCatchBlock finding(s) in Explicit Debt — start with GPUCleanup.vb (33), CleanupEngine.vb (10), DDUSafeBootService.vb (4). — One of this dimension's main actionable groups (61 issue-level).
Resolve the 6 TodoComment finding(s) in Explicit Debt — start with AUDIOCleanup.vb (3), AppLaunchOptions.vb, FrmMain.xaml.vb. — One of this dimension's main actionable groups (6 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D18 · Solution Shape2.0 / 10Critical✓ Tool-verified

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

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

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

1 projects, 0 .cs files, 27592 hand-written lines of code (27592 production / 0 test), plus 196 generated (EF migrations / designer / snapshots, excluded from quality), 0 inter-project edges (build failed).

Shell project: Display Driver Uninstallerdisplay-driver-uninstaller/Display Driver Uninstaller/Display Driver Uninstaller.vbproj

Build did not complete in the analyzer

What to do

Resolve the 1 Shell project finding(s) in Solution Shape — start with Display Driver Uninstaller.vbproj. — 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.

Do you agree with this assessment?

D19 · Documentation Quality / 10Strong◐ Sampled · advisory

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.

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

The Display Driver Uninstaller project has two README files (one long with usage notes, one focused on requirements and recommended usage) plus an architecture/design doc that is clipped mid-sentence. The main content covers the tool's purpose, a strong safety note about backing up/restoring before use, and detailed recommended usage for Normal vs Safemode modes, internet/blocking-Windows-Update prerequisites, and where to find troubleshooting (Issues/solutions.txt). It also links out to an external driver-tutorial guide, which is excellent. The two READMEs are well written but the clipped architecture doc leaves some design elements unexplained.

XML-doc coverage: Display Driver Uninstallerdisplay-driver-uninstaller/Display Driver Uninstaller/Display Driver Uninstaller.vbproj

What to do

Improve Documentation Quality — currently 8.0/10. — The Display Driver Uninstaller project has two README files (one long with usage notes, one focused on requirements and recommended usage) plus an architecture/design doc that is clipped mid-sentence. The main content covers the tool's purpose, a strong safety note about backing up/restoring before use, and detailed recommended usage for Normal vs Safemode modes, internet/blocking-Windows-Update prerequisites, and where to find troubleshooting (Issues/solutions.txt). It also links out to an external driver-tutorial guide, which is excellent. The two READMEs are well written but the clipped architecture doc leaves some design elements unexplained.

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

Do you agree with this assessment?

D21 · Naming Consistency / 10Exemplary◐ Sampled · 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.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 1 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

Do you agree with this assessment?

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

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

Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

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

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.

Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.

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

No known-vulnerable NuGet packages (direct or transitive).

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

Do you agree with this assessment?

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

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

Every significant source file has living knowledge — recently and meaningfully worked.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling7.2 / 10Strong✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

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

Strongest change-coupling: GPUCleanup.vb↔ImpersonateLoggedOnUser.vb 65%; LogEntry.vb↔SetupAPI.vb 62%; AppSettings.vb↔ThreadSettings.vb 58%

Change coupling: GPUCleanup.vb ↔ ImpersonateLoggedOnUser.vb · ×8display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb

What to do

Resolve the 8 Change coupling finding(s) in Change Coupling — start with LogEntry.vb (2), AppLaunchOptions.vb, AppPaths.vb. — One of this dimension's main actionable groups (8 warning-level).

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX5 · Architecture & structure3.0 / 10Weak✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

~27.6k production LoC (219 types) across 1 project(s) / 9 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.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

Do you agree with this assessment?

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

What to do

Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

No Architecture Decision Records found — decisions aren't captured for future maintainers.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.

What to do

Start an ADR log (docs/adr/) recording significant decisions and their rationale.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.

Do you agree with this assessment?

M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

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.

Projects aren't grouped under a src/ folder — production and tooling code are mixed at the root.
Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.

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.
Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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.

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.

Do you agree with this assessment?

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

No ILogger/Serilog usage found — production issues will be hard to diagnose.

What to do

Adopt ILogger (or Serilog) and log at meaningful points across the projects.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.

No static application security testing (CodeQL / security analyzers / codehealth) detected.

What to do

Add a SAST step (e.g. CodeQL) or a security analyzer package.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

Do you agree with this assessment?

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.

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.

Lens	Score	Rating	Impact
Code Health	73%	Adequate — gated by D1, D2, D18	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	56%	Adequate — gated by AX5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	51%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	17%	Critical — gated by D8, D9, P1, P2, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	100%	Exemplary	Strongest area.

Not included — 57 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
AX10 Code composition — no source files detected — code composition not applicable
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — no csproj graph available
AX4 Dependency direction — no csproj graph available
AX6 Interface segregation — no public interfaces
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
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — No tests in the analyzed solution to assess for quality.
D11 Test Reliability — Test reliability not included
D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 27600 LoC in a single project there are no cross-project coupling risks to measure.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not run — 0/3 markers found
ED1 Event-Driven — not run — 0/3 markers found
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not run — 0/3 markers found
IC1 Incompleteness & stubs — no C# methods found
P12 CI test-gate honesty — no CI workflow found
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
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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 — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — no data
X2 Cancellation propagation — no async methods found
X5 Nullable reference types — no NRT-eligible projects

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.

Issue — 62 finding(s)

D17 · Explicit Debt · EmptyCatchBlock · ×61

EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:244 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:281 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:302 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb:184 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:1105 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:1125 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:1254 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1619 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1626 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1747 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1754 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1775 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1824 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1831 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1852 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3434 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3439 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/DDUSafeBootService.vb:23 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/DDUSafeBootService.vb:94 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/DDUSafeBootService.vb:156 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/DDUSafeBootService.vb:177 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:716 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb:118 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1654 — empty catch block
EmptyCatchBlock display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:2937 — empty catch block
+ 36 more in this group — see findings.md.

D8 · Code Coverage · No automated tests · ×1

No automated tests — No automated tests — the solution has no test code. Untested code is the largest single risk to changing it safely.

Warning — 199 finding(s)

D3 · God Classes · FileTooLong · ×11

FileTooLong: Display Driver Uninstaller/AppSettings.vb display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:0 — FileTooLong — 849 lines.
FileTooLong: Display Driver Uninstaller/Application.xaml.vb display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:0 — FileTooLong — 1057 lines.
FileTooLong: Display Driver Uninstaller/CleanupEngine.vb display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:0 — FileTooLong — 3017 lines.
FileTooLong: Display Driver Uninstaller/DebugWindow.xaml.vb display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:0 — FileTooLong — 542 lines.
FileTooLong: Display Driver Uninstaller/FileIO.vb display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:0 — FileTooLong — 643 lines.
FileTooLong: Display Driver Uninstaller/FrmMain.xaml.vb display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:0 — FileTooLong — 1227 lines.
FileTooLong: Display Driver Uninstaller/GPUCleanup.vb display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:0 — FileTooLong — 7827 lines.
FileTooLong: Display Driver Uninstaller/Language.vb display-driver-uninstaller/Display Driver Uninstaller/Language.vb:0 — FileTooLong — 749 lines.
FileTooLong: Win32/ACL.vb display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:0 — FileTooLong — 686 lines.
FileTooLong: Win32/SetupAPI.vb display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:0 — FileTooLong — 2965 lines.
FileTooLong: Win32/TaskScheduler.vb display-driver-uninstaller/Display Driver Uninstaller/Win32/TaskScheduler.vb:0 — FileTooLong — 1060 lines.

D35 · Change Coupling · Change coupling · ×8

Change coupling: GPUCleanup.vb ↔ ImpersonateLoggedOnUser.vb display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb — `display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb` and `display-driver-uninstaller/Display Driver Uninstaller/Win32/ImpersonateLoggedOnUser.vb` change together 65% of the time (13 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: LogEntry.vb ↔ SetupAPI.vb display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb — `display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb` and `display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb` change together 62% of the time (20 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AppSettings.vb ↔ ThreadSettings.vb display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb — `display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb` and `display-driver-uninstaller/Display Driver Uninstaller/ThreadSettings.vb` change together 58% of the time (11 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: LogEntry.vb ↔ WinAPI.vb display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb — `display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb` and `display-driver-uninstaller/Display Driver Uninstaller/Win32/WinAPI.vb` change together 55% of the time (6 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AppPaths.vb ↔ Application.xaml.vb display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb — `display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb` and `display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb` change together 53% of the time (10 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AppLaunchOptions.vb ↔ GPUCleanup.vb display-driver-uninstaller/Display Driver Uninstaller/AppLaunchOptions.vb — `display-driver-uninstaller/Display Driver Uninstaller/AppLaunchOptions.vb` and `display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb` change together 50% of the time (17 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: CheckUpdate.vb ↔ AssemblyInfo.vb display-driver-uninstaller/Display Driver Uninstaller/CheckUpdate.vb — `display-driver-uninstaller/Display Driver Uninstaller/CheckUpdate.vb` and `display-driver-uninstaller/Display Driver Uninstaller/My Project/AssemblyInfo.vb` change together 50% of the time (10 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: DebugWindow.xaml.vb ↔ GPUCleanup.vb display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb — `display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb` and `display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb` change together 50% of the time (7 shared commits) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.

D17 · Explicit Debt · TodoComment · ×6

TodoComment display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:7 — 'todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:112 — 'Todo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:233 — ' Todo: more precise. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment display-driver-uninstaller/Display Driver Uninstaller/AppLaunchOptions.vb:180 — ' TODO: Add cmdline args for those RemoveXXXX properties — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:939 — 'If System.Diagnostics.Debugger.IsAttached Then 'TODO: remove when tested — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:514 — 'TODO : Parent.ChildDevices.Length < 1 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: PROJ-123`), so the task is planned where tasks live and the ticket links back to the code.

D3 · God Classes · TooManyMethods · ×6

TooManyMethods: Application display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:0 — TooManyMethods — 1006 lines, 31 methods.
TooManyMethods: CleanupEngine display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:0 — TooManyMethods — 3006 lines, 44 methods.
TooManyMethods: FileIO display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:0 — TooManyMethods — 634 lines, 31 methods.
TooManyMethods: FrmMain display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:0 — TooManyMethods — 1214 lines, 65 methods.
TooManyMethods: GPUCleanup display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:0 — TooManyMethods — 7815 lines, 41 methods.
TooManyMethods: SetupAPI display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:0 — TooManyMethods — 3223 lines, 68 methods.

D3 · God Classes · ClassTooLong · ×3

ClassTooLong: AppSettings display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:0 — ClassTooLong — 797 lines, 8 methods.
ClassTooLong: DebugWindow display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:0 — ClassTooLong — 515 lines, 27 methods.
ClassTooLong: Languages display-driver-uninstaller/Display Driver Uninstaller/Language.vb:0 — ClassTooLong — 743 lines, 22 methods.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3

Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb:20 — display-driver-uninstaller/Display Driver Uninstaller/FrmSystemRestore.xaml.vb:20-25 | display-driver-uninstaller/Display Driver Uninstaller/FrmNotice.xaml.vb:15-20
Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmLog.xaml.vb:192 — display-driver-uninstaller/Display Driver Uninstaller/FrmLog.xaml.vb:192-197 | display-driver-uninstaller/Display Driver Uninstaller/FrmLog.xaml.vb:199-204
Duplicated block (6 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:611 — display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:611-616 | display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:637-642

D6 · Cohesion (LCOM4) · Low cohesion · ×3

Low cohesion: FrmMain (LCOM4 7) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:31 — FrmMain's methods form 7 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: DebugWindow (LCOM4 5) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:8 — DebugWindow's methods form 5 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: AppSettings (LCOM4 4) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:79 — AppSettings's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2

Duplicated block (15 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:549 — display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:549-563 | display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:572-585
Duplicated block (15 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1285 — display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1285-1298 | display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1302-1316

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2

Duplicated block (10 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1733 — display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1733-1742 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1810-1819
Duplicated block (10 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:166 — display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:166-175 | display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:243-252

D1 · Cyclomatic Complexity · GPUCleanup.Start (cyclomatic 334) · ×1

GPUCleanup.Start (cyclomatic 334) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:20 — GPUCleanup.Start has cyclomatic complexity 334 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.Installer (cyclomatic 191) · ×1

CleanupEngine.Installer (cyclomatic 191) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1385 — CleanupEngine.Installer has cyclomatic complexity 191 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanNvidiaFolders (cyclomatic 168) · ×1

GPUCleanup.CleanNvidiaFolders (cyclomatic 168) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:6281 — GPUCleanup.CleanNvidiaFolders has cyclomatic complexity 168 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanVulkan (cyclomatic 167) · ×1

GPUCleanup.CleanVulkan (cyclomatic 167) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8475 — GPUCleanup.CleanVulkan has cyclomatic complexity 167 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.Clsidleftover (cyclomatic 123) · ×1

CleanupEngine.Clsidleftover (cyclomatic 123) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2481 — CleanupEngine.Clsidleftover has cyclomatic complexity 123 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanNvidia (cyclomatic 103) · ×1

GPUCleanup.CleanNvidia (cyclomatic 103) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3813 — GPUCleanup.CleanNvidia has cyclomatic complexity 103 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanNvidiaCache (cyclomatic 77) · ×1

GPUCleanup.CleanNvidiaCache (cyclomatic 77) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:6067 — GPUCleanup.CleanNvidiaCache has cyclomatic complexity 77 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.Cleandriverstore (cyclomatic 66) · ×1

CleanupEngine.Cleandriverstore (cyclomatic 66) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3461 — CleanupEngine.Cleandriverstore has cyclomatic complexity 66 (threshold 15).

D1 · Cyclomatic Complexity · AppSettings.Load (cyclomatic 62) · ×1

AppSettings.Load (cyclomatic 62) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:845 — AppSettings.Load has cyclomatic complexity 62 (threshold 15).

D1 · Cyclomatic Complexity · AppLog.OpenLog (cyclomatic 52) · ×1

AppLog.OpenLog (cyclomatic 52) display-driver-uninstaller/Display Driver Uninstaller/AppLog.vb:225 — AppLog.OpenLog has cyclomatic complexity 52 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.TEST_GetDevices (cyclomatic 52) · ×1

SetupAPI.TEST_GetDevices (cyclomatic 52) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1590 — SetupAPI.TEST_GetDevices has cyclomatic complexity 52 (threshold 15).

D1 · Cyclomatic Complexity · Languages.CheckLanguageFileForErrors (cyclomatic 52) · ×1

Languages.CheckLanguageFileForErrors (cyclomatic 52) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:734 — Languages.CheckLanguageFileForErrors has cyclomatic complexity 52 (threshold 15).

D1 · Cyclomatic Complexity · DebugWindow.CopyCommand (cyclomatic 48) · ×1

DebugWindow.CopyCommand (cyclomatic 48) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:245 — DebugWindow.CopyCommand has cyclomatic complexity 48 (threshold 15).

D1 · Cyclomatic Complexity · Languages.ReadFile (cyclomatic 48) · ×1

Languages.ReadFile (cyclomatic 48) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:398 — Languages.ReadFile has cyclomatic complexity 48 (threshold 15).

D1 · Cyclomatic Complexity · LogEntry.AddDevices (cyclomatic 47) · ×1

LogEntry.AddDevices (cyclomatic 47) display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb:209 — LogEntry.AddDevices has cyclomatic complexity 47 (threshold 15).

D1 · Cyclomatic Complexity · Application.Application_Startup (cyclomatic 45) · ×1

Application.Application_Startup (cyclomatic 45) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:561 — Application.Application_Startup has cyclomatic complexity 45 (threshold 15).

D1 · Cyclomatic Complexity · FrmMain.GetGPUDetails (cyclomatic 43) · ×1

FrmMain.GetGPUDetails (cyclomatic 43) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:980 — FrmMain.GetGPUDetails has cyclomatic complexity 43 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanIntel (cyclomatic 41) · ×1

GPUCleanup.CleanIntel (cyclomatic 41) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:7279 — GPUCleanup.CleanIntel has cyclomatic complexity 41 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.TEST_EnableDevice (cyclomatic 41) · ×1

SetupAPI.TEST_EnableDevice (cyclomatic 41) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1779 — SetupAPI.TEST_EnableDevice has cyclomatic complexity 41 (threshold 15).

D1 · Cyclomatic Complexity · FileIO.DeleteInternal (cyclomatic 40) · ×1

FileIO.DeleteInternal (cyclomatic 40) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:402 — FileIO.DeleteInternal has cyclomatic complexity 40 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.EnableDevice (cyclomatic 35) · ×1

SetupAPI.EnableDevice (cyclomatic 35) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1992 — SetupAPI.EnableDevice has cyclomatic complexity 35 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.GetDevicesByHID (cyclomatic 35) · ×1

SetupAPI.GetDevicesByHID (cyclomatic 35) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2436 — SetupAPI.GetDevicesByHID has cyclomatic complexity 35 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.UninstallDevice (cyclomatic 35) · ×1

SetupAPI.UninstallDevice (cyclomatic 35) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2737 — SetupAPI.UninstallDevice has cyclomatic complexity 35 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.GetDevices (cyclomatic 34) · ×1

SetupAPI.GetDevices (cyclomatic 34) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2594 — SetupAPI.GetDevices has cyclomatic complexity 34 (threshold 15).

D1 · Cyclomatic Complexity · DebugWindow.Filter (cyclomatic 34) · ×1

DebugWindow.Filter (cyclomatic 34) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:167 — DebugWindow.Filter has cyclomatic complexity 34 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.RemoveCLSIDInstance (cyclomatic 32) · ×1

CleanupEngine.RemoveCLSIDInstance (cyclomatic 32) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3060 — CleanupEngine.RemoveCLSIDInstance has cyclomatic complexity 32 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.GetDevicesByCompatibleID (cyclomatic 31) · ×1

SetupAPI.GetDevicesByCompatibleID (cyclomatic 31) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2282 — SetupAPI.GetDevicesByCompatibleID has cyclomatic complexity 31 (threshold 15).

D1 · Cyclomatic Complexity · FrmMain.FrmMain_ContentRendered (cyclomatic 31) · ×1

FrmMain.FrmMain_ContentRendered (cyclomatic 31) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:565 — FrmMain.FrmMain_ContentRendered has cyclomatic complexity 31 (threshold 15).

D1 · Cyclomatic Complexity · Registry.FixRights (cyclomatic 30) · ×1

Registry.FixRights (cyclomatic 30) display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:1081 — Registry.FixRights has cyclomatic complexity 30 (threshold 15).

D1 · Cyclomatic Complexity · FrmMain.EnableDriverSearch (cyclomatic 30) · ×1

FrmMain.EnableDriverSearch (cyclomatic 30) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1217 — FrmMain.EnableDriverSearch has cyclomatic complexity 30 (threshold 15).

D1 · Cyclomatic Complexity · AUDIOCleanup.Start (cyclomatic 27) · ×1

AUDIOCleanup.Start (cyclomatic 27) display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:11 — AUDIOCleanup.Start has cyclomatic complexity 27 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.RemoveAppx1809Async (cyclomatic 27) · ×1

CleanupEngine.RemoveAppx1809Async (cyclomatic 27) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:131 — CleanupEngine.RemoveAppx1809Async has cyclomatic complexity 27 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.UpdateDeviceInf (cyclomatic 27) · ×1

SetupAPI.UpdateDeviceInf (cyclomatic 27) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3019 — SetupAPI.UpdateDeviceInf has cyclomatic complexity 27 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.Old_TemporaryNvidiaSpeedup (cyclomatic 26) · ×1

GPUCleanup.Old_TemporaryNvidiaSpeedup (cyclomatic 26) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3758 — GPUCleanup.Old_TemporaryNvidiaSpeedup has cyclomatic complexity 26 (threshold 15).

D1 · Cyclomatic Complexity · FrmMain.GPUIdentify (cyclomatic 26) · ×1

FrmMain.GPUIdentify (cyclomatic 26) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:171 — FrmMain.GPUIdentify has cyclomatic complexity 26 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.RemoveSharedDlls (cyclomatic 24) · ×1

CleanupEngine.RemoveSharedDlls (cyclomatic 24) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:85 — CleanupEngine.RemoveSharedDlls has cyclomatic complexity 24 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.RemoveAppxPre1809Async (cyclomatic 24) · ×1

CleanupEngine.RemoveAppxPre1809Async (cyclomatic 24) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:746 — CleanupEngine.RemoveAppxPre1809Async has cyclomatic complexity 24 (threshold 15).

D1 · Cyclomatic Complexity · FileIO.GetFilesToDeleteInternal (cyclomatic 24) · ×1

FileIO.GetFilesToDeleteInternal (cyclomatic 24) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:595 — FileIO.GetFilesToDeleteInternal has cyclomatic complexity 24 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.RemoveInf (cyclomatic 24) · ×1

SetupAPI.RemoveInf (cyclomatic 24) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2879 — SetupAPI.RemoveInf has cyclomatic complexity 24 (threshold 15).

D1 · Cyclomatic Complexity · FileIO.GetFileNames (cyclomatic 23) · ×1

FileIO.GetFileNames (cyclomatic 23) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:714 — FileIO.GetFileNames has cyclomatic complexity 23 (threshold 15).

D1 · Cyclomatic Complexity · AppSettings.UpdateWinText (cyclomatic 23) · ×1

AppSettings.UpdateWinText (cyclomatic 23) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:595 — AppSettings.UpdateWinText has cyclomatic complexity 23 (threshold 15).

D1 · Cyclomatic Complexity · SetupAPI.GetDriverDetails (cyclomatic 23) · ×1

SetupAPI.GetDriverDetails (cyclomatic 23) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3406 — SetupAPI.GetDriverDetails has cyclomatic complexity 23 (threshold 15).

D1 · Cyclomatic Complexity · ServiceInstaller.StopService (cyclomatic 22) · ×1

ServiceInstaller.StopService (cyclomatic 22) display-driver-uninstaller/Display Driver Uninstaller/Win32/ServiceInstaller.vb:50 — ServiceInstaller.StopService has cyclomatic complexity 22 (threshold 15).

D1 · Cyclomatic Complexity · FileIO.GetDirNames (cyclomatic 21) · ×1

FileIO.GetDirNames (cyclomatic 21) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:823 — FileIO.GetDirNames has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanAmdCache (cyclomatic 21) · ×1

GPUCleanup.CleanAmdCache (cyclomatic 21) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:2813 — GPUCleanup.CleanAmdCache has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · FileSystem.FixFileSecurity (cyclomatic 21) · ×1

FileSystem.FixFileSecurity (cyclomatic 21) display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:789 — FileSystem.FixFileSecurity has cyclomatic complexity 21 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.Deletesubregkey (cyclomatic 20) · ×1

CleanupEngine.Deletesubregkey (cyclomatic 20) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:24 — CleanupEngine.Deletesubregkey has cyclomatic complexity 20 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.InterfaceRemovalWithValue (cyclomatic 20) · ×1

CleanupEngine.InterfaceRemovalWithValue (cyclomatic 20) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1278 — CleanupEngine.InterfaceRemovalWithValue has cyclomatic complexity 20 (threshold 15).

D1 · Cyclomatic Complexity · AppLog.SaveLog (cyclomatic 20) · ×1

AppLog.SaveLog (cyclomatic 20) display-driver-uninstaller/Display Driver Uninstaller/AppLog.vb:123 — AppLog.SaveLog has cyclomatic complexity 20 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.RemoveStaleInstalledPfns (cyclomatic 18) · ×1

CleanupEngine.RemoveStaleInstalledPfns (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:525 — CleanupEngine.RemoveStaleInstalledPfns has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanAmd (cyclomatic 18) · ×1

GPUCleanup.CleanAmd (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1187 — GPUCleanup.CleanAmd has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanEnvironementPath (cyclomatic 18) · ×1

GPUCleanup.CleanEnvironementPath (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3566 — GPUCleanup.CleanEnvironementPath has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.Checkamdkmpfd (cyclomatic 18) · ×1

GPUCleanup.Checkamdkmpfd (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3634 — GPUCleanup.Checkamdkmpfd has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanIntelFolders (cyclomatic 18) · ×1

GPUCleanup.CleanIntelFolders (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8237 — GPUCleanup.CleanIntelFolders has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · AppPaths.New.ctor (cyclomatic 18) · ×1

AppPaths.New.ctor (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb:155 — AppPaths.New.ctor has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · LogEntry.AddException (cyclomatic 18) · ×1

LogEntry.AddException (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb:349 — LogEntry.AddException has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · Languages.TranslateControl (cyclomatic 18) · ×1

Languages.TranslateControl (cyclomatic 18) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:296 — Languages.TranslateControl has cyclomatic complexity 18 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.Cleanserviceprocess (cyclomatic 17) · ×1

CleanupEngine.Cleanserviceprocess (cyclomatic 17) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1890 — CleanupEngine.Cleanserviceprocess has cyclomatic complexity 17 (threshold 15).

D1 · Cyclomatic Complexity · CleanupEngine.PnpLockdownFiles (cyclomatic 17) · ×1

CleanupEngine.PnpLockdownFiles (cyclomatic 17) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2221 — CleanupEngine.PnpLockdownFiles has cyclomatic complexity 17 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanAmdFolders (cyclomatic 17) · ×1

GPUCleanup.CleanAmdFolders (cyclomatic 17) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:2874 — GPUCleanup.CleanAmdFolders has cyclomatic complexity 17 (threshold 15).

D1 · Cyclomatic Complexity · Application.HandleBootModeStartup (cyclomatic 17) · ×1

Application.HandleBootModeStartup (cyclomatic 17) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:928 — Application.HandleBootModeStartup has cyclomatic complexity 17 (threshold 15).

D1 · Cyclomatic Complexity · GPUCleanup.CleanIntelCache (cyclomatic 16) · ×1

GPUCleanup.CleanIntelCache (cyclomatic 16) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8190 — GPUCleanup.CleanIntelCache has cyclomatic complexity 16 (threshold 15).

D1 · Cyclomatic Complexity · Tools.PreferredUILanguages (cyclomatic 16) · ×1

Tools.PreferredUILanguages (cyclomatic 16) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:122 — Tools.PreferredUILanguages has cyclomatic complexity 16 (threshold 15).

D1 · Cyclomatic Complexity · Application.GetOSVersion (cyclomatic 16) · ×1

Application.GetOSVersion (cyclomatic 16) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:878 — Application.GetOSVersion has cyclomatic complexity 16 (threshold 15).

D1 · Cyclomatic Complexity · Languages.GetTranslation (cyclomatic 16) · ×1

Languages.GetTranslation (cyclomatic 16) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:122 — Languages.GetTranslation has cyclomatic complexity 16 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.Start (cognitive 1157) · ×1

GPUCleanup.Start (cognitive 1157) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:20 — GPUCleanup.Start has cognitive complexity 1157 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.Installer (cognitive 1131) · ×1

CleanupEngine.Installer (cognitive 1131) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1385 — CleanupEngine.Installer has cognitive complexity 1131 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.Clsidleftover (cognitive 552) · ×1

CleanupEngine.Clsidleftover (cognitive 552) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2481 — CleanupEngine.Clsidleftover has cognitive complexity 552 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanVulkan (cognitive 499) · ×1

GPUCleanup.CleanVulkan (cognitive 499) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8475 — GPUCleanup.CleanVulkan has cognitive complexity 499 (threshold 15).

D2 · Cognitive Complexity · Languages.CheckLanguageFileForErrors (cognitive 308) · ×1

Languages.CheckLanguageFileForErrors (cognitive 308) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:734 — Languages.CheckLanguageFileForErrors has cognitive complexity 308 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanNvidiaCache (cognitive 300) · ×1

GPUCleanup.CleanNvidiaCache (cognitive 300) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:6067 — GPUCleanup.CleanNvidiaCache has cognitive complexity 300 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.Cleandriverstore (cognitive 200) · ×1

CleanupEngine.Cleandriverstore (cognitive 200) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3461 — CleanupEngine.Cleandriverstore has cognitive complexity 200 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanNvidiaFolders (cognitive 166) · ×1

GPUCleanup.CleanNvidiaFolders (cognitive 166) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:6281 — GPUCleanup.CleanNvidiaFolders has cognitive complexity 166 (threshold 15).

D2 · Cognitive Complexity · AppLog.OpenLog (cognitive 165) · ×1

AppLog.OpenLog (cognitive 165) display-driver-uninstaller/Display Driver Uninstaller/AppLog.vb:225 — AppLog.OpenLog has cognitive complexity 165 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.TEST_GetDevices (cognitive 141) · ×1

SetupAPI.TEST_GetDevices (cognitive 141) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1590 — SetupAPI.TEST_GetDevices has cognitive complexity 141 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.RemoveCLSIDInstance (cognitive 140) · ×1

CleanupEngine.RemoveCLSIDInstance (cognitive 140) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:3060 — CleanupEngine.RemoveCLSIDInstance has cognitive complexity 140 (threshold 15).

D2 · Cognitive Complexity · LogEntry.AddDevices (cognitive 124) · ×1

LogEntry.AddDevices (cognitive 124) display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb:209 — LogEntry.AddDevices has cognitive complexity 124 (threshold 15).

D2 · Cognitive Complexity · Languages.ReadFile (cognitive 120) · ×1

Languages.ReadFile (cognitive 120) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:398 — Languages.ReadFile has cognitive complexity 120 (threshold 15).

D2 · Cognitive Complexity · FileIO.DeleteInternal (cognitive 111) · ×1

FileIO.DeleteInternal (cognitive 111) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:402 — FileIO.DeleteInternal has cognitive complexity 111 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanNvidia (cognitive 106) · ×1

GPUCleanup.CleanNvidia (cognitive 106) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3813 — GPUCleanup.CleanNvidia has cognitive complexity 106 (threshold 15).

D2 · Cognitive Complexity · FrmMain.GetGPUDetails (cognitive 94) · ×1

FrmMain.GetGPUDetails (cognitive 94) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:980 — FrmMain.GetGPUDetails has cognitive complexity 94 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanEnvironementPath (cognitive 87) · ×1

GPUCleanup.CleanEnvironementPath (cognitive 87) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3566 — GPUCleanup.CleanEnvironementPath has cognitive complexity 87 (threshold 15).

D2 · Cognitive Complexity · DebugWindow.Filter (cognitive 87) · ×1

DebugWindow.Filter (cognitive 87) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:167 — DebugWindow.Filter has cognitive complexity 87 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetDevicesByHID (cognitive 86) · ×1

SetupAPI.GetDevicesByHID (cognitive 86) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2436 — SetupAPI.GetDevicesByHID has cognitive complexity 86 (threshold 15).

D2 · Cognitive Complexity · FrmMain.GPUIdentify (cognitive 76) · ×1

FrmMain.GPUIdentify (cognitive 76) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:171 — FrmMain.GPUIdentify has cognitive complexity 76 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetDevicesByCompatibleID (cognitive 75) · ×1

SetupAPI.GetDevicesByCompatibleID (cognitive 75) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2282 — SetupAPI.GetDevicesByCompatibleID has cognitive complexity 75 (threshold 15).

D2 · Cognitive Complexity · DebugWindow.CopyCommand (cognitive 74) · ×1

DebugWindow.CopyCommand (cognitive 74) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:245 — DebugWindow.CopyCommand has cognitive complexity 74 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.PnpLockdownFiles (cognitive 70) · ×1

CleanupEngine.PnpLockdownFiles (cognitive 70) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2221 — CleanupEngine.PnpLockdownFiles has cognitive complexity 70 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetDevices (cognitive 70) · ×1

SetupAPI.GetDevices (cognitive 70) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2594 — SetupAPI.GetDevices has cognitive complexity 70 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.Checkamdkmpfd (cognitive 69) · ×1

GPUCleanup.Checkamdkmpfd (cognitive 69) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3634 — GPUCleanup.Checkamdkmpfd has cognitive complexity 69 (threshold 15).

D2 · Cognitive Complexity · FrmMain.EnableDriverSearch (cognitive 67) · ×1

FrmMain.EnableDriverSearch (cognitive 67) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1217 — FrmMain.EnableDriverSearch has cognitive complexity 67 (threshold 15).

D2 · Cognitive Complexity · Application.Application_Startup (cognitive 63) · ×1

Application.Application_Startup (cognitive 63) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:561 — Application.Application_Startup has cognitive complexity 63 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.RemoveAppx1809Async (cognitive 62) · ×1

CleanupEngine.RemoveAppx1809Async (cognitive 62) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:131 — CleanupEngine.RemoveAppx1809Async has cognitive complexity 62 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanAmdCache (cognitive 61) · ×1

GPUCleanup.CleanAmdCache (cognitive 61) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:2813 — GPUCleanup.CleanAmdCache has cognitive complexity 61 (threshold 15).

D2 · Cognitive Complexity · FrmMain.FrmMain_ContentRendered (cognitive 61) · ×1

FrmMain.FrmMain_ContentRendered (cognitive 61) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:565 — FrmMain.FrmMain_ContentRendered has cognitive complexity 61 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.TEST_EnableDevice (cognitive 60) · ×1

SetupAPI.TEST_EnableDevice (cognitive 60) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1779 — SetupAPI.TEST_EnableDevice has cognitive complexity 60 (threshold 15).

D2 · Cognitive Complexity · FileIO.GetFileNames (cognitive 58) · ×1

FileIO.GetFileNames (cognitive 58) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:714 — FileIO.GetFileNames has cognitive complexity 58 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.RemoveAppxPre1809Async (cognitive 57) · ×1

CleanupEngine.RemoveAppxPre1809Async (cognitive 57) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:746 — CleanupEngine.RemoveAppxPre1809Async has cognitive complexity 57 (threshold 15).

D2 · Cognitive Complexity · FileIO.GetDirNames (cognitive 54) · ×1

FileIO.GetDirNames (cognitive 54) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:823 — FileIO.GetDirNames has cognitive complexity 54 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.UninstallDevice (cognitive 54) · ×1

SetupAPI.UninstallDevice (cognitive 54) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2737 — SetupAPI.UninstallDevice has cognitive complexity 54 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.RemoveSharedDlls (cognitive 53) · ×1

CleanupEngine.RemoveSharedDlls (cognitive 53) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:85 — CleanupEngine.RemoveSharedDlls has cognitive complexity 53 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.EnableDevice (cognitive 53) · ×1

SetupAPI.EnableDevice (cognitive 53) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:1992 — SetupAPI.EnableDevice has cognitive complexity 53 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.Old_TemporaryNvidiaSpeedup (cognitive 52) · ×1

GPUCleanup.Old_TemporaryNvidiaSpeedup (cognitive 52) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3758 — GPUCleanup.Old_TemporaryNvidiaSpeedup has cognitive complexity 52 (threshold 15).

D2 · Cognitive Complexity · Registry.FixRights (cognitive 49) · ×1

Registry.FixRights (cognitive 49) display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:1081 — Registry.FixRights has cognitive complexity 49 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetDriverDetails (cognitive 47) · ×1

SetupAPI.GetDriverDetails (cognitive 47) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3406 — SetupAPI.GetDriverDetails has cognitive complexity 47 (threshold 15).

D2 · Cognitive Complexity · FileIO.GetFilesToDeleteInternal (cognitive 46) · ×1

FileIO.GetFilesToDeleteInternal (cognitive 46) display-driver-uninstaller/Display Driver Uninstaller/FileIO.vb:595 — FileIO.GetFilesToDeleteInternal has cognitive complexity 46 (threshold 15).

D2 · Cognitive Complexity · AppSettings.Load (cognitive 46) · ×1

AppSettings.Load (cognitive 46) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:845 — AppSettings.Load has cognitive complexity 46 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanIntelCache (cognitive 44) · ×1

GPUCleanup.CleanIntelCache (cognitive 44) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8190 — GPUCleanup.CleanIntelCache has cognitive complexity 44 (threshold 15).

D2 · Cognitive Complexity · AUDIOCleanup.Start (cognitive 43) · ×1

AUDIOCleanup.Start (cognitive 43) display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:11 — AUDIOCleanup.Start has cognitive complexity 43 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetSiblings (cognitive 42) · ×1

SetupAPI.GetSiblings (cognitive 42) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3626 — SetupAPI.GetSiblings has cognitive complexity 42 (threshold 15).

D2 · Cognitive Complexity · AppLog.SaveLog (cognitive 40) · ×1

AppLog.SaveLog (cognitive 40) display-driver-uninstaller/Display Driver Uninstaller/AppLog.vb:123 — AppLog.SaveLog has cognitive complexity 40 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.UpdateDeviceInf (cognitive 39) · ×1

SetupAPI.UpdateDeviceInf (cognitive 39) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3019 — SetupAPI.UpdateDeviceInf has cognitive complexity 39 (threshold 15).

D2 · Cognitive Complexity · TaskSchedulerControl.GetAllTasks (cognitive 39) · ×1

TaskSchedulerControl.GetAllTasks (cognitive 39) display-driver-uninstaller/Display Driver Uninstaller/Win32/TaskScheduler.vb:60 — TaskSchedulerControl.GetAllTasks has cognitive complexity 39 (threshold 15).

D2 · Cognitive Complexity · Languages.GetChildren (cognitive 37) · ×1

Languages.GetChildren (cognitive 37) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:246 — Languages.GetChildren has cognitive complexity 37 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.Checkpcieroot (cognitive 35) · ×1

GPUCleanup.Checkpcieroot (cognitive 35) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3675 — GPUCleanup.Checkpcieroot has cognitive complexity 35 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.Deletesubregkey (cognitive 34) · ×1

CleanupEngine.Deletesubregkey (cognitive 34) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:24 — CleanupEngine.Deletesubregkey has cognitive complexity 34 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.RemoveInf (cognitive 34) · ×1

SetupAPI.RemoveInf (cognitive 34) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2879 — SetupAPI.RemoveInf has cognitive complexity 34 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanIntel (cognitive 33) · ×1

GPUCleanup.CleanIntel (cognitive 33) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:7279 — GPUCleanup.CleanIntel has cognitive complexity 33 (threshold 15).

D2 · Cognitive Complexity · AppPaths.New.ctor (cognitive 33) · ×1

AppPaths.New.ctor (cognitive 33) display-driver-uninstaller/Display Driver Uninstaller/AppPaths.vb:155 — AppPaths.New.ctor has cognitive complexity 33 (threshold 15).

D2 · Cognitive Complexity · LogEntry.AddException (cognitive 32) · ×1

LogEntry.AddException (cognitive 32) display-driver-uninstaller/Display Driver Uninstaller/LogEntry.vb:349 — LogEntry.AddException has cognitive complexity 32 (threshold 15).

D2 · Cognitive Complexity · Languages.TranslateControl (cognitive 31) · ×1

Languages.TranslateControl (cognitive 31) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:296 — Languages.TranslateControl has cognitive complexity 31 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.RemoveStaleInstalledPfns (cognitive 29) · ×1

CleanupEngine.RemoveStaleInstalledPfns (cognitive 29) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:525 — CleanupEngine.RemoveStaleInstalledPfns has cognitive complexity 29 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.PrePnplockdownfiles (cognitive 29) · ×1

CleanupEngine.PrePnplockdownfiles (cognitive 29) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2187 — CleanupEngine.PrePnplockdownfiles has cognitive complexity 29 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetChild (cognitive 29) · ×1

SetupAPI.GetChild (cognitive 29) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3765 — SetupAPI.GetChild has cognitive complexity 29 (threshold 15).

D2 · Cognitive Complexity · Application.HandleBootModeStartup (cognitive 28) · ×1

Application.HandleBootModeStartup (cognitive 28) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:928 — Application.HandleBootModeStartup has cognitive complexity 28 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.Cleanserviceprocess (cognitive 26) · ×1

CleanupEngine.Cleanserviceprocess (cognitive 26) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1890 — CleanupEngine.Cleanserviceprocess has cognitive complexity 26 (threshold 15).

D2 · Cognitive Complexity · AppSettings.UpdateWinText (cognitive 26) · ×1

AppSettings.UpdateWinText (cognitive 26) display-driver-uninstaller/Display Driver Uninstaller/AppSettings.vb:595 — AppSettings.UpdateWinText has cognitive complexity 26 (threshold 15).

D2 · Cognitive Complexity · ServiceInstaller.StopService (cognitive 26) · ×1

ServiceInstaller.StopService (cognitive 26) display-driver-uninstaller/Display Driver Uninstaller/Win32/ServiceInstaller.vb:50 — ServiceInstaller.StopService has cognitive complexity 26 (threshold 15).

D2 · Cognitive Complexity · FrmLog.CopyValues (cognitive 25) · ×1

FrmLog.CopyValues (cognitive 25) display-driver-uninstaller/Display Driver Uninstaller/FrmLog.xaml.vb:281 — FrmLog.CopyValues has cognitive complexity 25 (threshold 15).

D2 · Cognitive Complexity · Languages.GetParentTranslation (cognitive 25) · ×1

Languages.GetParentTranslation (cognitive 25) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:76 — Languages.GetParentTranslation has cognitive complexity 25 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.UpdateDevicesByID (cognitive 24) · ×1

SetupAPI.UpdateDevicesByID (cognitive 24) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:3173 — SetupAPI.UpdateDevicesByID has cognitive complexity 24 (threshold 15).

D2 · Cognitive Complexity · FrmMain.Testing2MenuItem_Click (cognitive 23) · ×1

FrmMain.Testing2MenuItem_Click (cognitive 23) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1396 — FrmMain.Testing2MenuItem_Click has cognitive complexity 23 (threshold 15).

D2 · Cognitive Complexity · CleanupEngine.InterfaceRemovalWithValue (cognitive 22) · ×1

CleanupEngine.InterfaceRemovalWithValue (cognitive 22) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1278 — CleanupEngine.InterfaceRemovalWithValue has cognitive complexity 22 (threshold 15).

D2 · Cognitive Complexity · FileSystem.FixFileSecurity (cognitive 22) · ×1

FileSystem.FixFileSecurity (cognitive 22) display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:789 — FileSystem.FixFileSecurity has cognitive complexity 22 (threshold 15).

D2 · Cognitive Complexity · Tools.StrRemoveAny (cognitive 21) · ×1

Tools.StrRemoveAny (cognitive 21) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:192 — Tools.StrRemoveAny has cognitive complexity 21 (threshold 15).

D2 · Cognitive Complexity · SetupAPI.GetAllDeviceParent (cognitive 20) · ×1

SetupAPI.GetAllDeviceParent (cognitive 20) display-driver-uninstaller/Display Driver Uninstaller/Win32/SetupAPI.vb:2174 — SetupAPI.GetAllDeviceParent has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · Tools.FixBrokenPathIfNeeded (cognitive 20) · ×1

Tools.FixBrokenPathIfNeeded (cognitive 20) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:307 — Tools.FixBrokenPathIfNeeded has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · Languages.GetTranslation (cognitive 20) · ×1

Languages.GetTranslation (cognitive 20) display-driver-uninstaller/Display Driver Uninstaller/Language.vb:122 — Languages.GetTranslation has cognitive complexity 20 (threshold 15).

D2 · Cognitive Complexity · ImpersonateUser.TakeTokenInternal (cognitive 19) · ×1

ImpersonateUser.TakeTokenInternal (cognitive 19) display-driver-uninstaller/Display Driver Uninstaller/Win32/ImpersonateLoggedOnUser.vb:25 — ImpersonateUser.TakeTokenInternal has cognitive complexity 19 (threshold 15).

D2 · Cognitive Complexity · FrmMain.InfoDriverSearch (cognitive 19) · ×1

FrmMain.InfoDriverSearch (cognitive 19) display-driver-uninstaller/Display Driver Uninstaller/FrmMain.xaml.vb:1281 — FrmMain.InfoDriverSearch has cognitive complexity 19 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanEmptyTaskDirectories (cognitive 18) · ×1

GPUCleanup.CleanEmptyTaskDirectories (cognitive 18) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:5991 — GPUCleanup.CleanEmptyTaskDirectories has cognitive complexity 18 (threshold 15).

D2 · Cognitive Complexity · GPUCleanup.CleanAmd (cognitive 17) · ×1

GPUCleanup.CleanAmd (cognitive 17) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1187 — GPUCleanup.CleanAmd has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · Tools.PreferredUILanguages (cognitive 17) · ×1

Tools.PreferredUILanguages (cognitive 17) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:122 — Tools.PreferredUILanguages has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · Tools.StateChanged (cognitive 17) · ×1

Tools.StateChanged (cognitive 17) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:424 — Tools.StateChanged has cognitive complexity 17 (threshold 15).

D2 · Cognitive Complexity · Inf.New.ctor (cognitive 16) · ×1

Inf.New.ctor (cognitive 16) display-driver-uninstaller/Display Driver Uninstaller/Inf.vb:59 — Inf.New.ctor has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · Priviliges.AdjustToken (cognitive 16) · ×1

Priviliges.AdjustToken (cognitive 16) display-driver-uninstaller/Display Driver Uninstaller/Win32/ACL.vb:425 — Priviliges.AdjustToken has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · ServiceInstaller.GetServiceStatus (cognitive 16) · ×1

ServiceInstaller.GetServiceStatus (cognitive 16) display-driver-uninstaller/Display Driver Uninstaller/Win32/ServiceInstaller.vb:170 — ServiceInstaller.GetServiceStatus has cognitive complexity 16 (threshold 15).

D2 · Cognitive Complexity · Application.GetOSVersion (cognitive 16) · ×1

Application.GetOSVersion (cognitive 16) display-driver-uninstaller/Display Driver Uninstaller/Application.xaml.vb:878 — Application.GetOSVersion has cognitive complexity 16 (threshold 15).

D4 · Code Duplication · Duplicated block (226 lines × 3) · ×1

Duplicated block (226 lines × 3) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1196 — display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1196-1421 | display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:3828-3931 | display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8141-8170

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1

Duplicated block (14 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:435 — display-driver-uninstaller/Display Driver Uninstaller/AUDIOCleanup.vb:435-448 | display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:1125-1138

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1

Duplicated block (13 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8802 — display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8802-8814 | display-driver-uninstaller/Display Driver Uninstaller/GPUCleanup.vb:8824-8835

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1

Duplicated block (12 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:50 — display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:50-61 | display-driver-uninstaller/Display Driver Uninstaller/DebugWindow.xaml.vb:65-76

D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1

Duplicated block (11 lines × 6) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2397 — display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2397-2407 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2409-2419 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2421-2431 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2441-2451 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2453-2463 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:2465-2475

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1

Duplicated block (9 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1802 — display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1802-1810 | display-driver-uninstaller/Display Driver Uninstaller/CleanupEngine.vb:1836-1843

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1

Duplicated block (8 lines × 2) display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:124 — display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:124-131 | display-driver-uninstaller/Display Driver Uninstaller/Tools.vb:137-144

Recommendation — 3 finding(s)

D11 · Test Reliability · Test reliability not included · ×1

Test reliability not included — No test projects found, so reliability couldn't be assessed.

D18 · Solution Shape · Shell project · ×1

Shell project: Display Driver Uninstaller display-driver-uninstaller/Display Driver Uninstaller/Display Driver Uninstaller.vbproj — `Display Driver Uninstaller` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.

D9 · Test Distribution · No tests found · ×1

No tests found — No test projects found in the repository.

Info — 3 finding(s)

D18 · Solution Shape · Build did not complete in the analyzer · ×1

Build did not complete in the analyzer — `dotnet build` reported 1 error(s) but no C# compiler diagnostic — an SDK / target-framework / restore mismatch in the analyzer environment, not a code defect (common for an older codebase whose target framework the analyzer's SDK can't build). Solution Shape is scored on structure and is NOT capped; the C# semantic analysis loads independently and is unaffected.

D19 · Documentation Quality · XML-doc coverage · ×1

XML-doc coverage: Display Driver Uninstaller display-driver-uninstaller/Display Driver Uninstaller/Display Driver Uninstaller.vbproj — Display Driver Uninstaller: 100 % XML-doc coverage (0/0).

D22 · Internal API Consistency · No exposed public API · ×1

No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.

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.

Dimension	Tool	Version	Command	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .	artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	dotnet	—	dotnet list "display-driver-uninstaller/Display Driver Uninstaller.sln" package --vulnerable --include-transitive --format json	artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.	—
D33 · JS/npm Dependency Vulnerabilities	trivy	—	trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	—
D38 · OSV Dependency Vulnerabilities	osv-scanner	—	osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.	—

Run 019fdeb1-5e2c-7e39-9f34-e63753991291 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Wagnard/display-Drivers-Uninstaller

Executive summary

Top priorities

Diagnosis — what's actually going on

At a glance — Code Health · 73% · Adequate · gated by D1, D2, D18

At a glance — Architecture · 56% · Adequate · gated by AX5

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

At a glance — Readiness · 17% · Critical · gated by D8, D9, P1, P2, P3

At a glance — Security · 100% · Exemplary

Roadmap

File quality

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts