Public report — SuperPVZTrainner, published 8 Aug 2026. Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version; ask the repo owner for the full report.
Watchdogby Canine Development 08-08-2026 @ 00:29 UTC Public
Code Health Audit

Lazuplis-Mei/SuperPVZTrainner

no automated testssingle-maintainerbounded contexts not declared
41% Weak
CriticalWeakAdequateStrongExemplary
middle
Security 100% Exemplary Architecture 95% Exemplary Code Health 82% Strong Maturity 36% Weak Readiness 17% Critical

Small · 4,557 LoC · 9 projects · rebuild ~0.1 person-years · weakest lens: Readiness (17%)

Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸

35/37dimensions tool-verifieddeterministic · confidence 1.0 · 2 LLM-assisted, advisory
117findings with an exact file:lineof 132 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
37/92dimensions across the health lenses4557 LoC · 9 projects — wide & deep

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.

Lazuplis-Mei/SuperPVZTrainner carries serious gaps (41%). 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. Architecture (95%) is solid too.

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 (36%) 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: Small (~4,557 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.

Code Health 82% Strong Architecture 95% ★ Exemplary Maturity 36% Weak · gated by M1, 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 36% · 26% weightCode Health 82% · 14% weightArchitecture 95% · 8% weightSecurity 100% · 4% weight

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

Code composition — where the lines go
Business logic 43%Plumbing 48%Generated 9%
New since the last scan (8+)

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

  • D3 · TooManyMethods: Memory PVZClass/PVZClass/PVZClass.vb
  • D3 · ClassTooLong: Zombie PVZClass/PVZClass/PVZClass.vb
  • D4 · Duplicated block (9 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb
  • D4 · Duplicated block (8 lines × 2) PVZTools/PVZTools.cs
  • D8 · No automated tests
  • D18 · Monorepo: only 1 of 4 solutions was scored
  • D24 · LLM evaluation failed
  • 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.

Rebuild cost & value ~ Modeled — €4,200–€22,000
Cost to rebuild€4,200–€22,000 (0.1 person-years (70–227 h), ~1 engineer)
Domain complexityStandard — harder problems cost more per line
Quality factor0.7× (at 41% quality) — the last 20% of quality is most of the work
Size & shapeSmall · 33% boilerplate · 20% straight-line · 47% branching logic

This codebase represents roughly ~0.1 person-years of build effort (about ~€13,000 to rebuild). Its weakest lens is Readiness at 17% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — desktop/game, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).

Top priorities

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

1
Resolve the 1 No automated tests finding(s) in Code Coverage.
+17.2 pts · Low effort · Code Coverage
2
Resolve the 1 No tests found finding(s) in Test Distribution.
+17.2 pts · Low effort · Test Distribution
3
Add a CI workflow that builds and runs the test suite on every push/PR.
+23.4 pts · Medium effort · CI/CD gates

Diagnosis — what's actually going on

Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.1 person-years to rebuild), and its weakest lens is Readiness at 17%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Evidence: valuation: Small, ~0.1 person-years rebuild (4,557 LoC) · weakest lens: Readiness 17%
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 7.3/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 2–5% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2 complexity, D4 duplication, D6 cohesion: averaging 7.3/10 across the code-quality signals
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch DarkStyle DarkStyle ITrainerExtension ITrainerExtension IZFormatSetter IZFormatSetter IZFormatSetter->DarkStyle IZFormatSetter->ITrainerExtension LightCheatEngine LightCheatEngine LightCheatEngine->DarkStyle LightCheatEngine->ITrainerExtension PVZScript PVZScript PVZTools PVZTools PVZTools->DarkStyle PVZTools->ITrainerExtension PakTool PakTool PakTool->DarkStyle PakTool->ITrainerExtension

At a glance — Code Health · 82% · Strong

The Good
D1 · .NET / C# Cyclomatic Complexity 7.8 D3 · .NET / C# God Classes 8.7 D4 · .NET / C# Code Duplication 9.4 D17 · .NET / C# Explicit Debt 8.8 D18 · .NET / C# Solution Shape 8.2 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 10.0 X1 · Repo Async correctness 10.0 X4 · Repo Structured logging 10.0
The Bad
D2 · .NET / C# Cognitive Complexity 5.4 X3 · Repo Exception handling 6.3

At a glance — Architecture · 95% · Exemplary

The Good
D5 · .NET / C# Coupling 8.2 D26 · .NET / C# Project Cohesion 10.0 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0
The Bad
D6 · .NET / C# Cohesion (LCOM4) 6.7

At a glance — Maturity · 36% · Weak · gated by M1, M2

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D21 · .NET / C# Naming Consistency 10.0 M4 · Repo Documentation accuracy 10.0
The Ugly
D19 · .NET / C# Documentation Quality 2.0 D20 · .NET / C# ADR Quality 0.0 M1 · Repo Documentation (README) 2.0 M2 · Repo Architecture documentation 0.0 M3 · Repo Folder & project structure 4.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

Roadmap

First, establish a continuous integration workflow to automatically build and test the codebase on every push or pull request. Next, implement structured logging and health checks across all services to improve observability and reliability. Then, address the single gap in automated testing to ensure code coverage is complete. After that, identify and add missing tests to improve test distribution. Finally, expand the README with a getting-started guide, architecture overview, and project map to improve documentation.

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

Do thisHelpsEffortDimension
Resolve the 1 No automated tests finding(s) in Code Coverage.+17.2 ptsLowCode Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.+17.2 ptsLowTest Distribution
Add a CI workflow that builds and runs the test suite on every push/PR.+23.4 ptsMediumCI/CD gates
Adopt ILogger (or Serilog) and log at meaningful points across the projects.+23.4 ptsMediumObservability
Resolve the 1 No ADRs found finding(s) in ADR Quality.+8.7 ptsLowADR Quality
Expand the README with getting-started, architecture overview and a project map.+14.1 ptsMediumDocumentation (README)
Start an ADR log (docs/adr/) recording significant decisions and their rationale.+14.1 ptsMediumArchitecture documentation
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.+13.8 ptsMediumFolder & project structure

File quality

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

FileScoreBandWorst signal
WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb1.0SlopExplicit Debt: EmptyCatchBlock
WPFTrainner/WPFTrainner/MainWindow.xaml.vb2.3SlopExplicit Debt: EmptyCatchBlock
PVZClass/PVZClass/PVZModifyClass.vb4.6MixedExplicit Debt: EmptyCatchBlock
WPFTrainner/ITrainerExtension/ITrainerExtension.cs5.4MixedExplicit Debt: EmptyCatchBlock
WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb5.5MixedCyclomatic Complexity: ModifyWindow.BtnSetZombieSeed_Click (cyclomatic 25)
WPFTrainner/WPFTrainner/ExpendWindow.xaml.vb6.7MixedExplicit Debt: ObsoleteWithCallers
WPFTrainner/WPFTrainner/OperationWindow.xaml.vb7.0MixedCode Duplication: Duplicated block (11 lines × 8)
LightCheatEngine/LightCEDisasmControl.xaml.cs7.0MixedCyclomatic Complexity: LightCEDisasmControl.MenuItem_Click_1 (cyclomatic 17)
PVZClass/PVZClass/PVZClass.vb7.2MixedGod Classes: FileTooLong: PVZClass/PVZClass.vb
PVZScript/PVZScript/Program.cs7.4MixedCyclomatic Complexity: Program.Mainloop (cyclomatic 27)
PVZTools/LawnStringsManager.xaml.cs7.4MixedCyclomatic Complexity: LawnStringsManager.FindItem (cyclomatic 26)
IZFormatSetter/IZFormatSetter/UserControl1.xaml.cs7.8MixedCyclomatic Complexity: UserControl1.ImageBackground_MouseDown (cyclomatic 37)
LightCheatEngine/ExpressionEval.cs7.8MixedCyclomatic Complexity: ExpressionEval.InfixToPostfix (cyclomatic 18)
PakTool/UserControl1.xaml.cs8.5Near-cleanCognitive Complexity: UserControl1.BtnExecute_Click (cognitive 42)
WPFTrainner/WPFTrainner/HpTrackWindow.xaml.vb8.5Near-cleanCognitive Complexity: HpTrackWindow.TimerTick (cognitive 35)
PVZScript/PVZScript/InterpreterClass.cs8.5Near-cleanCognitive Complexity: Interpreter.CallEx (cognitive 21)
PVZTools/GlobalKeyboardHook.cs8.5Near-cleanCognitive Complexity: GlobalKeyboardHook.KeyboardHookProc (cognitive 17)
PVZTools/PVZTools.cs8.5Near-cleanCode Duplication: Duplicated block (8 lines × 2)
WPFTrainner/WPFTrainner/WaveManageDialog.xaml.vb8.5Near-cleanCohesion (LCOM4): Low cohesion: WaveManageDialog (LCOM4 8)
WPFTrainner/WPFTrainner/ProcessSelector.xaml.vb8.5Near-cleanCohesion (LCOM4): Low cohesion: ProcessSelector (LCOM4 6)

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. 35 of 37 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.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 37 dimensions across the health lenses
D1D2D3D4D5D6D8D9D12D13D15D17D18D19D20D21D26D28D29D35AX10AX3AX4AX5AX6GD1IC1M1M2M3M4P1P2P3X1X3X4

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 117 of 132 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
jscpdCode duplication—✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.301✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.301✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fdec6-24aa-7713-9318-d31f1445c243.

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.

  • D24 Comment Value — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • D30 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.
  • 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.
  • 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.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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").
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.

The LLM boundary

LLM-set scores this run (4): D19, D20, 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 Complexity7.8 / 10Strong✓ Tool-verified

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

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

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

16 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UserControl1.ImageBackground_MouseDown at 37.

UserControl1.ImageBackground_MouseDown (cyclomatic 37)IZFormatSetter/IZFormatSetter/UserControl1.xaml.cs:89
Program.Mainloop (cyclomatic 27)PVZScript/PVZScript/Program.cs:84
LawnStringsManager.FindItem (cyclomatic 26)PVZTools/LawnStringsManager.xaml.cs:190
ModifyWindow.BtnSetZombieSeed_Click (cyclomatic 25)WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:628
ModifyWindow.CBZombieTimeProp_SelectionChanged (cyclomatic 24)WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:445

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

What to do

  1. Resolve the 1 UserControl1.ImageBackground_MouseDown (cyclomatic 37) finding(s) in Cyclomatic Complexity — start with UserControl1.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Program.Mainloop (cyclomatic 27) finding(s) in Cyclomatic Complexity — start with Program.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 LawnStringsManager.FindItem (cyclomatic 26) finding(s) in Cyclomatic Complexity — start with LawnStringsManager.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.

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

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

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

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

31 method(s) exceeded the cognitive complexity threshold of 15; the worst was LawnStringsManager.FindItem at 82.

LawnStringsManager.FindItem (cognitive 82)PVZTools/LawnStringsManager.xaml.cs:190
ModifyWindow.BtnSetZombieSeed_Click (cognitive 70)WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:628
UserControl1.ImageBackground_MouseDown (cognitive 65)IZFormatSetter/IZFormatSetter/UserControl1.xaml.cs:89
LightCEDisasmControl.MenuItem_Click_1 (cognitive 47)LightCheatEngine/LightCEDisasmControl.xaml.cs:199
MonitorWindow.Timer2Tick (cognitive 45)WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:138

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

What to do

  1. Resolve the 1 LawnStringsManager.FindItem (cognitive 82) finding(s) in Cognitive Complexity — start with LawnStringsManager.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 ModifyWindow.BtnSetZombieSeed_Click (cognitive 70) finding(s) in Cognitive Complexity — start with ModifyWindow.xaml.vb. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 UserControl1.ImageBackground_MouseDown (cognitive 65) finding(s) in Cognitive Complexity — start with UserControl1.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.

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

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

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

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

5 god class(es) detected.

FileTooLong: PVZClass/PVZClass.vb · ×5PVZClass/PVZClass/PVZClass.vb:0
TooManyMethods: PVZ · ×5PVZClass/PVZClass/PVZClass.vb:0
ClassTooLong: ZombiePVZClass/PVZClass/PVZClass.vb:0

What to do

  1. Resolve the 5 FileTooLong finding(s) in God Classes — start with MainWindow.xaml.vb, ModifyWindow.xaml.vb, MonitorWindow.xaml.vb. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 5 TooManyMethods finding(s) in God Classes — start with PVZClass.vb (2), MainWindow.xaml.vb, ModifyWindow.xaml.vb. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with PVZClass.vb. — One of this dimension's main actionable groups (1 warning-level).
  4. 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.

D4 · Code Duplication9.4 / 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.4 / 10 · rule-coverage 100% · ceiling Verified

24 duplicated block group(s) detected.

Duplicated block (8 lines × 2) · ×4WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:101
Duplicated block (8 lines × 5) · ×3WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:447
Duplicated block (8 lines × 4) · ×2WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:197
Duplicated block (6 lines × 2) · ×2WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:155
Duplicated block (5 lines × 2) · ×2PVZClass/PVZClass/PVZModifyClass.vb:463

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

D5 · Coupling8.2 / 10Strong✓ 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 8.2 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: PVZClass · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

8 of 29 classes have LCOM4 above 3.

Low cohesion: ModifyWindow (LCOM4 64) · ×8WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:4

What to do

  1. Resolve the 8 Low cohesion finding(s) in Cohesion (LCOM4) — start with InputDialog.xaml.vb, MainWindow.xaml.vb, ModifyWindow.xaml.vb. — One of this dimension's main actionable groups (8 warning-level).
  2. 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.

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

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
  2. 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.

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

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

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.

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.

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.

git history depth insufficient

✓ On the Gold path — maintain.

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

D17 · Explicit Debt8.8 / 10Strong✓ 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 8.8 / 10 · rule-coverage 100% · ceiling Prevented

14 deducted debt markers + 0 dead symbols across 16752 LoC (0.6/KLoC) → score 8.8.

EmptyCatchBlock · ×10PVZClass/PVZClass/PVZModifyClass.vb:10
ObsoleteWithCallers · ×2WPFTrainner/WPFTrainner/ExpendWindow.xaml.vb:40
ObsoleteWithoutCallers · ×2WPFTrainner/WPFTrainner/Application.xaml.vb:32

What to do

  1. Resolve the 10 EmptyCatchBlock finding(s) in Explicit Debt — start with MonitorWindow.xaml.vb (6), MainWindow.xaml.vb (2), ITrainerExtension.cs. — One of this dimension's main actionable groups (10 issue-level).
  2. Resolve the 2 ObsoleteWithCallers finding(s) in Explicit Debt — start with ExpendWindow.xaml.vb (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 ObsoleteWithoutCallers finding(s) in Explicit Debt — start with Application.xaml.vb, ExpendWindow.xaml.vb. — One of this dimension's main actionable groups (2 recommendation-level).
  4. 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.

D18 · Solution Shape8.2 / 10Strong✓ Tool-verified

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

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

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

9 projects, 30 .cs files, 16752 hand-written lines of code (16752 production / 0 test), plus 462 generated (EF migrations / designer / snapshots, excluded from quality), 15 inter-project edges (build failed).

Monorepo: only 1 of 4 solutions was scored
Shell project: WPFTrainner · ×2WPFTrainner/WPFTrainner/WPFTrainner.vbproj
Build did not complete in the analyzer

What to do

  1. Resolve the 2 Shell project finding(s) in Solution Shape — start with PVZClass.vbproj, WPFTrainner.vbproj. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 Monorepo finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality / 10Critical◐ 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 Critical / 10 · rule-coverage 100% · ceiling Documented

The only visible document is a single README for the SuperPVZTrainner project that describes itself as 'Super PlantsVsZombies Trainner' and contains no installation, usage, or architecture information. No architecture/design docs exist in the directory tree, and XML documentation coverage across all referenced assemblies is zero (0/10) to 53% (WPFTrainner), with only IZFormatSetter at 10%, indicating comprehensive code doc coverage is missing.

No installation, prerequisites, or usage instructions for the trainer.README.md
No architecture or component-design description of what the trainer does.README.md
XML-doc coverage: WPFTrainner · ×9WPFTrainner/WPFTrainner/WPFTrainner.vbproj

What to do

  1. Resolve the 1 No installation, prerequisites, or usage instructions for the trainer. finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 No architecture or component-design description of what the trainer… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

D20 · ADR Quality / 10Critical◐ Sampled · advisory

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

D21 · Naming 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 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

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 9 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

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

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

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

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.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

git history depth insufficient

✓ On the Gold path — maintain.

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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

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

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

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

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.

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.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)2.0 / 10Critical✓ 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.

  • The root README is 5 words — likely missing build/run/architecture context.

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • 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 9 of 9 project(s) that lack one — worth up to 2 pts.
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.
M3 · Folder & project structure4.0 / 10Weak✓ 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.
  • Only 1/9 projects share a common root namespace — the code's module identity is inconsistent.

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.
  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
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.

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

X3 · Exception handling6.3 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — ITrainerExtension.cs:53

What to do

  • Swallowed exception (empty catch)
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.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health82%StrongSolid.
Architecture95%ExemplarySolid.
Maturity36%Weak — gated by M1, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness17%Critical — gated by D8, D9, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100%ExemplaryStrongest area.
Not included — 56 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • 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
  • D16 Bus Factor — single-maintainer — knowledge-concentration (bus factor) risk
  • D22 Internal API Consistency — No exposed public API
  • D23 Boundary Type-Coupling — Bounded contexts not declared
  • D24 Comment Value — LLM evaluation failed
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D30 Dependency Vulnerabilities — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
  • 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.
  • D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
  • 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
  • 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
  • X6 Hand-rolled structured-format parsing — no data
  • X7 Silent fallback defaults — no data

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 — 11 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×10
  • EmptyCatchBlock PVZClass/PVZClass/PVZModifyClass.vb:10 — empty catch block
  • EmptyCatchBlock WPFTrainner/ITrainerExtension/ITrainerExtension.cs:53 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MainWindow.xaml.vb:462 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MainWindow.xaml.vb:476 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:88 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:533 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:682 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:807 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:856 — empty catch block
  • EmptyCatchBlock WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:923 — empty catch block
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 — 97 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×8
  • Low cohesion: ModifyWindow (LCOM4 64) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:4 — ModifyWindow's methods form 64 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: MonitorWindow (LCOM4 17) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:5 — MonitorWindow's methods form 17 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: MainWindow (LCOM4 17) WPFTrainner/WPFTrainner/MainWindow.xaml.vb:10 — MainWindow's methods form 17 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: OperationWindow (LCOM4 9) WPFTrainner/WPFTrainner/OperationWindow.xaml.vb:4 — OperationWindow's methods form 9 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: WaveManageDialog (LCOM4 8) WPFTrainner/WPFTrainner/WaveManageDialog.xaml.vb:4 — WaveManageDialog's methods form 8 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: ProcessSelector (LCOM4 6) WPFTrainner/WPFTrainner/ProcessSelector.xaml.vb:6 — ProcessSelector's methods form 6 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: ZombieListDialog (LCOM4 4) WPFTrainner/WPFTrainner/ZombieListDialog.xaml.vb:3 — ZombieListDialog'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.
  • Low cohesion: InputDialog (LCOM4 4) WPFTrainner/WPFTrainner/InputDialog.xaml.vb:1 — InputDialog'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.
D3 · God Classes · FileTooLong · ×5
  • FileTooLong: PVZClass/PVZClass.vb PVZClass/PVZClass/PVZClass.vb:0 — FileTooLong — 4484 lines.
  • FileTooLong: PVZClass/PVZModifyClass.vb PVZClass/PVZClass/PVZModifyClass.vb:0 — FileTooLong — 1304 lines.
  • FileTooLong: WPFTrainner/MainWindow.xaml.vb WPFTrainner/WPFTrainner/MainWindow.xaml.vb:0 — FileTooLong — 532 lines.
  • FileTooLong: WPFTrainner/ModifyWindow.xaml.vb WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:0 — FileTooLong — 1500 lines.
  • FileTooLong: WPFTrainner/MonitorWindow.xaml.vb WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:0 — FileTooLong — 1041 lines.
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: PVZ PVZClass/PVZClass/PVZClass.vb:0 — TooManyMethods — 5769 lines, 159 methods.
  • TooManyMethods: Memory PVZClass/PVZClass/PVZClass.vb:0 — TooManyMethods — 209 lines, 35 methods.
  • TooManyMethods: MainWindow WPFTrainner/WPFTrainner/MainWindow.xaml.vb:0 — TooManyMethods — 524 lines, 49 methods.
  • TooManyMethods: ModifyWindow WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:0 — TooManyMethods — 1498 lines, 124 methods.
  • TooManyMethods: MonitorWindow WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:0 — TooManyMethods — 1037 lines, 107 methods.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×4
  • Duplicated block (8 lines × 2) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:101 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:101-108 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:111-118
  • Duplicated block (8 lines × 2) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:416 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:416-423 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:431-438
  • Duplicated block (8 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb:499 — PVZClass/PVZClass/PVZModifyClass.vb:499-506 | PVZClass/PVZClass/PVZModifyClass.vb:1517-1524
  • Duplicated block (8 lines × 2) PVZTools/PVZTools.cs:26 — PVZTools/PVZTools.cs:26-33 | PVZTools/PVZTools.cs:36-43
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×3
  • Duplicated block (8 lines × 5) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:447 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:447-454 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:455-462 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:463-470 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:471-478 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:479-486
  • Duplicated block (8 lines × 5) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:496 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:496-503 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:504-511 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:512-519 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:520-527 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:528-535
  • Duplicated block (8 lines × 5) PVZClass/PVZClass/PVZModifyClass.vb:893 — PVZClass/PVZClass/PVZModifyClass.vb:893-900 | PVZClass/PVZClass/PVZModifyClass.vb:1270-1277 | PVZClass/PVZClass/PVZModifyClass.vb:1317-1324 | PVZClass/PVZClass/PVZModifyClass.vb:1471-1478 | PVZClass/PVZClass/PVZModifyClass.vb:1496-1503
D17 · Explicit Debt · ObsoleteWithCallers · ×2
  • ObsoleteWithCallers WPFTrainner/WPFTrainner/ExpendWindow.xaml.vb:40 — <Obsolete> GetTextDisplayWidth
  • ObsoleteWithCallers WPFTrainner/WPFTrainner/ExpendWindow.xaml.vb:46 — <Obsolete> GetTextDisplayWidth
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×2
  • Duplicated block (8 lines × 4) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:197 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:197-204 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:205-212 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:213-220 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:221-228
  • Duplicated block (8 lines × 4) PVZClass/PVZClass/PVZModifyClass.vb:422 — PVZClass/PVZClass/PVZModifyClass.vb:422-429 | PVZClass/PVZClass/PVZModifyClass.vb:1275-1282 | PVZClass/PVZClass/PVZModifyClass.vb:1476-1483 | PVZClass/PVZClass/PVZModifyClass.vb:1501-1508
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:155 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:155-160 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:161-166
  • Duplicated block (6 lines × 2) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1422 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1422-1427 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1428-1433
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2
  • Duplicated block (5 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb:463 — PVZClass/PVZClass/PVZModifyClass.vb:463-467 | PVZClass/PVZClass/PVZModifyClass.vb:469-473
  • Duplicated block (5 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb:929 — PVZClass/PVZClass/PVZModifyClass.vb:929-933 | PVZClass/PVZClass/PVZModifyClass.vb:936-940
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: PVZClass — PVZClass: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
  • Off the main sequence: DarkStyle — DarkStyle: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and heavily depended-on, so it's rigid to change.
D1 · Cyclomatic Complexity · UserControl1.ImageBackground_MouseDown (cyclomatic 37) · ×1
  • UserControl1.ImageBackground_MouseDown (cyclomatic 37) IZFormatSetter/IZFormatSetter/UserControl1.xaml.cs:89 — UserControl1.ImageBackground_MouseDown has cyclomatic complexity 37 (threshold 15).
D1 · Cyclomatic Complexity · Program.Mainloop (cyclomatic 27) · ×1
  • Program.Mainloop (cyclomatic 27) PVZScript/PVZScript/Program.cs:84 — Program.Mainloop has cyclomatic complexity 27 (threshold 15).
D1 · Cyclomatic Complexity · LawnStringsManager.FindItem (cyclomatic 26) · ×1
  • LawnStringsManager.FindItem (cyclomatic 26) PVZTools/LawnStringsManager.xaml.cs:190 — LawnStringsManager.FindItem has cyclomatic complexity 26 (threshold 15).
D1 · Cyclomatic Complexity · ModifyWindow.BtnSetZombieSeed_Click (cyclomatic 25) · ×1
  • ModifyWindow.BtnSetZombieSeed_Click (cyclomatic 25) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:628 — ModifyWindow.BtnSetZombieSeed_Click has cyclomatic complexity 25 (threshold 15).
D1 · Cyclomatic Complexity · ModifyWindow.CBZombieTimeProp_SelectionChanged (cyclomatic 24) · ×1
  • ModifyWindow.CBZombieTimeProp_SelectionChanged (cyclomatic 24) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:445 — ModifyWindow.CBZombieTimeProp_SelectionChanged has cyclomatic complexity 24 (threshold 15).
D1 · Cyclomatic Complexity · ModifyWindow.TBZombieTimeProp_PreviewKeyDown (cyclomatic 24) · ×1
  • ModifyWindow.TBZombieTimeProp_PreviewKeyDown (cyclomatic 24) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:494 — ModifyWindow.TBZombieTimeProp_PreviewKeyDown has cyclomatic complexity 24 (threshold 15).
D1 · Cyclomatic Complexity · MonitorWindow.Timer2Tick (cyclomatic 24) · ×1
  • MonitorWindow.Timer2Tick (cyclomatic 24) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:138 — MonitorWindow.Timer2Tick has cyclomatic complexity 24 (threshold 15).
D1 · Cyclomatic Complexity · MonitorWindow.Timer3Tick (cyclomatic 23) · ×1
  • MonitorWindow.Timer3Tick (cyclomatic 23) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:218 — MonitorWindow.Timer3Tick has cyclomatic complexity 23 (threshold 15).
D1 · Cyclomatic Complexity · Lang.ChangeLanguage (cyclomatic 23) · ×1
  • Lang.ChangeLanguage (cyclomatic 23) WPFTrainner/ITrainerExtension/ITrainerExtension.cs:17 — Lang.ChangeLanguage has cyclomatic complexity 23 (threshold 15).
D1 · Cyclomatic Complexity · ModifyWindow.CBPlantTimeProp_SelectionChanged (cyclomatic 21) · ×1
  • ModifyWindow.CBPlantTimeProp_SelectionChanged (cyclomatic 21) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:195 — ModifyWindow.CBPlantTimeProp_SelectionChanged has cyclomatic complexity 21 (threshold 15).
D1 · Cyclomatic Complexity · ModifyWindow.TBPlantTimeProp_PreviewKeyDown (cyclomatic 21) · ×1
  • ModifyWindow.TBPlantTimeProp_PreviewKeyDown (cyclomatic 21) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:238 — ModifyWindow.TBPlantTimeProp_PreviewKeyDown has cyclomatic complexity 21 (threshold 15).
D1 · Cyclomatic Complexity · MonitorWindow.Timer6Tick (cyclomatic 19) · ×1
  • MonitorWindow.Timer6Tick (cyclomatic 19) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:407 — MonitorWindow.Timer6Tick has cyclomatic complexity 19 (threshold 15).
D1 · Cyclomatic Complexity · MonitorWindow.Timer5Tick (cyclomatic 18) · ×1
  • MonitorWindow.Timer5Tick (cyclomatic 18) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:345 — MonitorWindow.Timer5Tick has cyclomatic complexity 18 (threshold 15).
D1 · Cyclomatic Complexity · ExpressionEval.InfixToPostfix (cyclomatic 18) · ×1
  • ExpressionEval.InfixToPostfix (cyclomatic 18) LightCheatEngine/ExpressionEval.cs:17 — ExpressionEval.InfixToPostfix has cyclomatic complexity 18 (threshold 15).
D1 · Cyclomatic Complexity · LightCEDisasmControl.MenuItem_Click_1 (cyclomatic 17) · ×1
  • LightCEDisasmControl.MenuItem_Click_1 (cyclomatic 17) LightCheatEngine/LightCEDisasmControl.xaml.cs:199 — LightCEDisasmControl.MenuItem_Click_1 has cyclomatic complexity 17 (threshold 15).
D1 · Cyclomatic Complexity · LightCEDisasmControl.LVMain_KeyDown (cyclomatic 16) · ×1
  • LightCEDisasmControl.LVMain_KeyDown (cyclomatic 16) LightCheatEngine/LightCEDisasmControl.xaml.cs:48 — LightCEDisasmControl.LVMain_KeyDown has cyclomatic complexity 16 (threshold 15).
D16 · Bus Factor · single-maintainer · ×1
  • single-maintainer — knowledge-concentration (bus factor) risk — single-maintainer — knowledge-concentration (bus factor) risk (1 author(s) across 10 commit(s) sampled).
D18 · Solution Shape · Monorepo · ×1
  • Monorepo: only 1 of 4 solutions was scored — This repository contains 4 .NET solutions, but a scan analyzes ONE. Every score, lens, and finding here reflects only `WPFTrainner/WPFTrainner.sln` — the other 3 (`IZFormatSetter/IZFormatSetter.sln`, `PVZClass/PVZClass.sln`, `PVZScript/PVZScript.sln`) were not analyzed and are not represented in the headline. To cover them, scan each solution as its own target and group them in a Solution or Product for a portfolio roll-up. If a secondary solution is an archived or vendored tree, declare it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — to exclude it from discovery the same way generated code is.
D2 · Cognitive Complexity · LawnStringsManager.FindItem (cognitive 82) · ×1
  • LawnStringsManager.FindItem (cognitive 82) PVZTools/LawnStringsManager.xaml.cs:190 — LawnStringsManager.FindItem has cognitive complexity 82 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.BtnSetZombieSeed_Click (cognitive 70) · ×1
  • ModifyWindow.BtnSetZombieSeed_Click (cognitive 70) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:628 — ModifyWindow.BtnSetZombieSeed_Click has cognitive complexity 70 (threshold 15).
D2 · Cognitive Complexity · UserControl1.ImageBackground_MouseDown (cognitive 65) · ×1
  • UserControl1.ImageBackground_MouseDown (cognitive 65) IZFormatSetter/IZFormatSetter/UserControl1.xaml.cs:89 — UserControl1.ImageBackground_MouseDown has cognitive complexity 65 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.MenuItem_Click_1 (cognitive 47) · ×1
  • LightCEDisasmControl.MenuItem_Click_1 (cognitive 47) LightCheatEngine/LightCEDisasmControl.xaml.cs:199 — LightCEDisasmControl.MenuItem_Click_1 has cognitive complexity 47 (threshold 15).
D2 · Cognitive Complexity · MonitorWindow.Timer2Tick (cognitive 45) · ×1
  • MonitorWindow.Timer2Tick (cognitive 45) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:138 — MonitorWindow.Timer2Tick has cognitive complexity 45 (threshold 15).
D2 · Cognitive Complexity · MonitorWindow.Timer3Tick (cognitive 43) · ×1
  • MonitorWindow.Timer3Tick (cognitive 43) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:218 — MonitorWindow.Timer3Tick has cognitive complexity 43 (threshold 15).
D2 · Cognitive Complexity · Lang.ChangeLanguage (cognitive 43) · ×1
  • Lang.ChangeLanguage (cognitive 43) WPFTrainner/ITrainerExtension/ITrainerExtension.cs:17 — Lang.ChangeLanguage has cognitive complexity 43 (threshold 15).
D2 · Cognitive Complexity · Program.Main (cognitive 43) · ×1
  • Program.Main (cognitive 43) PVZScript/PVZScript/Program.cs:15 — Program.Main has cognitive complexity 43 (threshold 15).
D2 · Cognitive Complexity · UserControl1.BtnExecute_Click (cognitive 42) · ×1
  • UserControl1.BtnExecute_Click (cognitive 42) PakTool/UserControl1.xaml.cs:84 — UserControl1.BtnExecute_Click has cognitive complexity 42 (threshold 15).
D2 · Cognitive Complexity · ExpressionEval.InfixToPostfix (cognitive 37) · ×1
  • ExpressionEval.InfixToPostfix (cognitive 37) LightCheatEngine/ExpressionEval.cs:17 — ExpressionEval.InfixToPostfix has cognitive complexity 37 (threshold 15).
D2 · Cognitive Complexity · HpTrackWindow.TimerTick (cognitive 35) · ×1
  • HpTrackWindow.TimerTick (cognitive 35) WPFTrainner/WPFTrainner/HpTrackWindow.xaml.vb:37 — HpTrackWindow.TimerTick has cognitive complexity 35 (threshold 15).
D2 · Cognitive Complexity · MonitorWindow.Timer5Tick (cognitive 33) · ×1
  • MonitorWindow.Timer5Tick (cognitive 33) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:345 — MonitorWindow.Timer5Tick has cognitive complexity 33 (threshold 15).
D2 · Cognitive Complexity · MonitorWindow.Timer6Tick (cognitive 33) · ×1
  • MonitorWindow.Timer6Tick (cognitive 33) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:407 — MonitorWindow.Timer6Tick has cognitive complexity 33 (threshold 15).
D2 · Cognitive Complexity · Program.Mainloop (cognitive 32) · ×1
  • Program.Mainloop (cognitive 32) PVZScript/PVZScript/Program.cs:84 — Program.Mainloop has cognitive complexity 32 (threshold 15).
D2 · Cognitive Complexity · PVZ.Plantf (cognitive 29) · ×1
  • PVZ.Plantf (cognitive 29) PVZClass/PVZClass/PVZModifyClass.vb:1551 — PVZ.Plantf has cognitive complexity 29 (threshold 15).
D2 · Cognitive Complexity · PVZ.Zombief (cognitive 29) · ×1
  • PVZ.Zombief (cognitive 29) PVZClass/PVZClass/PVZModifyClass.vb:1582 — PVZ.Zombief has cognitive complexity 29 (threshold 15).
D2 · Cognitive Complexity · MonitorWindow.Timer4Tick (cognitive 27) · ×1
  • MonitorWindow.Timer4Tick (cognitive 27) WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:293 — MonitorWindow.Timer4Tick has cognitive complexity 27 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.CBZombieTimeProp_SelectionChanged (cognitive 24) · ×1
  • ModifyWindow.CBZombieTimeProp_SelectionChanged (cognitive 24) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:445 — ModifyWindow.CBZombieTimeProp_SelectionChanged has cognitive complexity 24 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.TBZombieTimeProp_PreviewKeyDown (cognitive 24) · ×1
  • ModifyWindow.TBZombieTimeProp_PreviewKeyDown (cognitive 24) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:494 — ModifyWindow.TBZombieTimeProp_PreviewKeyDown has cognitive complexity 24 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.MenuItem_Click (cognitive 23) · ×1
  • LightCEDisasmControl.MenuItem_Click (cognitive 23) LightCheatEngine/LightCEDisasmControl.xaml.cs:158 — LightCEDisasmControl.MenuItem_Click has cognitive complexity 23 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.CBZombieInvincible_Click (cognitive 22) · ×1
  • ModifyWindow.CBZombieInvincible_Click (cognitive 22) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:557 — ModifyWindow.CBZombieInvincible_Click has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.MenuItem_Click_8 (cognitive 22) · ×1
  • LightCEDisasmControl.MenuItem_Click_8 (cognitive 22) LightCheatEngine/LightCEDisasmControl.xaml.cs:353 — LightCEDisasmControl.MenuItem_Click_8 has cognitive complexity 22 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.CBPlantTimeProp_SelectionChanged (cognitive 21) · ×1
  • ModifyWindow.CBPlantTimeProp_SelectionChanged (cognitive 21) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:195 — ModifyWindow.CBPlantTimeProp_SelectionChanged has cognitive complexity 21 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.TBPlantTimeProp_PreviewKeyDown (cognitive 21) · ×1
  • ModifyWindow.TBPlantTimeProp_PreviewKeyDown (cognitive 21) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:238 — ModifyWindow.TBPlantTimeProp_PreviewKeyDown has cognitive complexity 21 (threshold 15).
D2 · Cognitive Complexity · Interpreter.CallEx (cognitive 21) · ×1
  • Interpreter.CallEx (cognitive 21) PVZScript/PVZScript/InterpreterClass.cs:186 — Interpreter.CallEx has cognitive complexity 21 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.LVMain_KeyDown (cognitive 20) · ×1
  • LightCEDisasmControl.LVMain_KeyDown (cognitive 20) LightCheatEngine/LightCEDisasmControl.xaml.cs:48 — LightCEDisasmControl.LVMain_KeyDown has cognitive complexity 20 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.ContextMenu_Opened (cognitive 19) · ×1
  • LightCEDisasmControl.ContextMenu_Opened (cognitive 19) LightCheatEngine/LightCEDisasmControl.xaml.cs:411 — LightCEDisasmControl.ContextMenu_Opened has cognitive complexity 19 (threshold 15).
D2 · Cognitive Complexity · MainWindow.BtnFindGame_MouseDoubleClick (cognitive 18) · ×1
  • MainWindow.BtnFindGame_MouseDoubleClick (cognitive 18) WPFTrainner/WPFTrainner/MainWindow.xaml.vb:500 — MainWindow.BtnFindGame_MouseDoubleClick has cognitive complexity 18 (threshold 15).
D2 · Cognitive Complexity · GlobalKeyboardHook.KeyboardHookProc (cognitive 17) · ×1
  • GlobalKeyboardHook.KeyboardHookProc (cognitive 17) PVZTools/GlobalKeyboardHook.cs:125 — GlobalKeyboardHook.KeyboardHookProc has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · LightCEDisasmControl.MenuItem_Click_6 (cognitive 17) · ×1
  • LightCEDisasmControl.MenuItem_Click_6 (cognitive 17) LightCheatEngine/LightCEDisasmControl.xaml.cs:308 — LightCEDisasmControl.MenuItem_Click_6 has cognitive complexity 17 (threshold 15).
D2 · Cognitive Complexity · ModifyWindow.GetLevel (cognitive 16) · ×1
  • ModifyWindow.GetLevel (cognitive 16) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:48 — ModifyWindow.GetLevel has cognitive complexity 16 (threshold 15).
D24 · Comment Value · LLM evaluation failed · ×1
  • LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.notable[5].comment | LineNumber: 0 | BytePositionInLine: 971.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: Zombie PVZClass/PVZClass/PVZClass.vb:0 — ClassTooLong — 414 lines, 5 methods.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) PVZTools/LawnStringsManager.xaml.cs:200 — PVZTools/LawnStringsManager.xaml.cs:200-211 | PVZTools/LawnStringsManager.xaml.cs:247-258
D4 · Code Duplication · Duplicated block (11 lines × 8) · ×1
  • Duplicated block (11 lines × 8) WPFTrainner/WPFTrainner/OperationWindow.xaml.vb:12 — WPFTrainner/WPFTrainner/OperationWindow.xaml.vb:12-22 | WPFTrainner/WPFTrainner/SeparateWindow.xaml.vb:15-25 | WPFTrainner/WPFTrainner/WaveManageDialog.xaml.vb:77-87 | WPFTrainner/WPFTrainner/ZombieListDialog.xaml.vb:94-104 | WPFTrainner/WPFTrainner/InputDialog.xaml.vb:40-50 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:878-888 | WPFTrainner/WPFTrainner/MonitorWindow.xaml.vb:1054-1064 | WPFTrainner/WPFTrainner/ProcessSelector.xaml.vb:99-109
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1389 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1389-1399 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1401-1411
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb:356 — PVZClass/PVZClass/PVZModifyClass.vb:356-364 | PVZClass/PVZClass/PVZModifyClass.vb:538-545
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:240 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:240-247 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:260-267 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:268-275
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×1
  • Duplicated block (7 lines × 5) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1439 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1439-1445 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1451-1457 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1463-1469 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1475-1481 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1487-1493
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) PVZClass/PVZClass/PVZModifyClass.vb:561 — PVZClass/PVZClass/PVZModifyClass.vb:561-567 | PVZClass/PVZClass/PVZModifyClass.vb:1269-1275 | PVZClass/PVZClass/PVZModifyClass.vb:1469-1475 | PVZClass/PVZClass/PVZModifyClass.vb:1493-1499
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) PVZClass/PVZClass/PVZModifyClass.vb:294 — PVZClass/PVZClass/PVZModifyClass.vb:294-300 | PVZClass/PVZClass/PVZModifyClass.vb:308-314
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:992 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:992-997 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1001-1006 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1010-1015 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1019-1024
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) PVZClass/PVZClass/PVZModifyClass.vb:609 — PVZClass/PVZClass/PVZModifyClass.vb:609-614 | PVZClass/PVZClass/PVZModifyClass.vb:660-665 | PVZClass/PVZClass/PVZModifyClass.vb:667-672
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1279 — WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1279-1283 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1289-1293 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1301-1305 | WPFTrainner/WPFTrainner/ModifyWindow.xaml.vb:1315-1319
Recommendation — 11 finding(s)
D17 · Explicit Debt · ObsoleteWithoutCallers · ×2
  • ObsoleteWithoutCallers WPFTrainner/WPFTrainner/Application.xaml.vb:32 — <Obsolete> Main
  • ObsoleteWithoutCallers WPFTrainner/WPFTrainner/ExpendWindow.xaml.vb:29 — <Obsolete> Window_SizeChanged
D18 · Solution Shape · Shell project · ×2
  • Shell project: WPFTrainner WPFTrainner/WPFTrainner/WPFTrainner.vbproj — `WPFTrainner` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
  • Shell project: PVZClass PVZClass/PVZClass/PVZClass.vbproj — `PVZClass` contributes only 0 significant line(s) — an empty/placeholder project is structural noise. Remove it or fold its contents into a real project.
D11 · Test Reliability · Test reliability not included · ×1
  • Test reliability not included — No test projects found, so reliability couldn't be assessed.
D19 · Documentation Quality · No installation, prerequisites, or usage instructions for the trainer. · ×1
  • No installation, prerequisites, or usage instructions for the trainer. README.md — Add a short 'Getting Started' section covering how to install and run the trainer.
D19 · Documentation Quality · No architecture or component-design description of what the trainer does. · ×1
  • No architecture or component-design description of what the trainer does. README.md — Describe the trainer's purpose, its role in the SuperPVZ modding pipeline, and any external dependencies it requires.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found at common paths; consider documenting architectural decisions in Docs/ADL/ or similar.
D23 · Boundary Type-Coupling · Bounded contexts not declared · ×1
  • Bounded contexts not declared — At 16752 LoC across 9 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Declare architecture.contexts (≥2) in config to assess cross-boundary type coupling.
D34 · Knowledge Freshness · early-stage repository · ×1
  • early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (10 commit(s) sampled).
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test projects found in the repository.
Info — 13 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×9
  • XML-doc coverage: WPFTrainner WPFTrainner/WPFTrainner/WPFTrainner.vbproj — WPFTrainner: 100 % XML-doc coverage (0/0).
  • XML-doc coverage: ITrainerExtension WPFTrainner/ITrainerExtension/ITrainerExtension.csproj — ITrainerExtension: 0 % XML-doc coverage (0/10).
  • XML-doc coverage: PVZScript PVZScript/PVZScript/PVZScript.csproj — PVZScript: 0 % XML-doc coverage (0/56).
  • XML-doc coverage: PVZClass PVZClass/PVZClass/PVZClass.vbproj — PVZClass: 100 % XML-doc coverage (0/0).
  • XML-doc coverage: IZFormatSetter IZFormatSetter/IZFormatSetter/IZFormatSetter.csproj — IZFormatSetter: 10 % XML-doc coverage (1/10).
  • XML-doc coverage: PakTool PakTool/PakTool.csproj — PakTool: 53 % XML-doc coverage (16/30).
  • XML-doc coverage: PVZTools PVZTools/PVZTools.csproj — PVZTools: 15 % XML-doc coverage (10/65).
  • XML-doc coverage: LightCheatEngine LightCheatEngine/LightCheatEngine.csproj — LightCheatEngine: 9 % XML-doc coverage (6/64).
  • XML-doc coverage: DarkStyle DarkStyle/DarkStyle.csproj — DarkStyle: 6 % XML-doc coverage (2/35).
D15 · Churn × Complexity Hotspots · git history depth insufficient · ×1
  • git history depth insufficient — git history depth insufficient — install a full clone for reliable trend signal.
D18 · Solution Shape · Build did not complete in the analyzer · ×1
  • Build did not complete in the analyzer — `dotnet build` reported 9 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.
D22 · Internal API Consistency · No exposed public API · ×1
  • No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
D35 · Change Coupling · git history depth insufficient · ×1
  • git history depth insufficient — git history depth insufficient — a full clone gives reliable change-coupling.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .0artifacts/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 .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet: not applicable — the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.0—
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.0—
D33 · JS/npm Dependency Vulnerabilitiestrivy—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.0—
D36 · Supply-chain Provenance & Signingprovenance—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.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D38 · OSV Dependency Vulnerabilitiesosv-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.0—

Run 019fdec6-24aa-7713-9318-d31f1445c243 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 11 · Warnings: 97 · Recommendations: 11 · Info: 13 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 08-08-2026 @ 00:29 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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