Public report — MahApps.Metro, published 16 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
167findings with an exact file:lineof 181 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
53/107dimensions across the health lenses43953 LoC · 13 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.
MahApps/MahApps.Metro is sound in substance but carries real gaps (54%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (96%) — the structure is clean and changes stay contained.
The area that most needs attention is Readiness (49%) — 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 (54%) 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: SAST step to CI running what this repository's stack ships (Security & performance tooling); Nothing pauses a release for a human (Deployment & Rollback); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene).
For scale: Medium (~43,953 production lines); rebuilding it from scratch would take roughly ~0.6 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (96%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
X3 · Swallowed exception (caught, then discarded) src/MahApps.Metro/Controls/MultiSelectionComboBox/DefaultStringToObjectParser.cs
X3 · Swallowed exception (caught, then discarded) src/MahApps.Metro/Converters/MarkupConverter.cs
X3 · Swallowed exception (caught, then discarded) src/MahApps.Metro/Converters/MarkupConverter.cs
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.
This codebase represents roughly ~0.6 person-years of build effort (about ~€81,000 to rebuild). Its weakest lens is Readiness at 49% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.1) — desktop/game × a 0.8× 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 ADRs found finding(s) in ADR Quality.
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Value concentrated against a weak lens · Medium · Value at risk
This is a Medium asset (~0.6 person-years to rebuild), and its weakest lens is Readiness at 49%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
Architecture — module dependency matrix
16 modules, 7 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 56% · Adequate · gated by X1
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
11
High / Critical
A04:2021 — Insecure Design
1
Medium
Roadmap
First, add a security scanning step to the build so risky changes fail before they land, using the repository's existing analyzer options or a language-agnostic security analyzer. Next, pause releases for a human approval or draft-release gate so a bad build can be stopped before users can download it. Then keep a changelog for each release, extend structured logging in the service projects and give library projects a diagnostics seam instead of imposing a logging dependency, and record significant architecture decisions in dated, discoverable decision documents.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
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. 50 of 53 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 53 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 167 of 181 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D21 Naming Consistency — 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.
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 (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
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.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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").
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D20, D24, 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.
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.
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MultiSelectionComboBox.KeyDownHandler at 54. A further 3 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DataGridNumericUpDownColumn.RefreshCellContent at 25 — they are counted neither in the figure above nor in this dimension's score.
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Utils.IsValid (cyclomatic 21) finding(s) in Cyclomatic Complexity — start with ClipBorder.Utils.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 MultiSelectionComboBox.KeyDownHandler (cyclomatic 54) finding(s) in Cyclomatic Complexity — start with MultiSelectionComboBox.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Utils.IsEqualTo (cyclomatic 42) finding(s) in Cyclomatic Complexity — start with ClipBorder.Utils.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Utils.IsValid (cognitive 16) finding(s) in Cognitive Complexity — start with ClipBorder.Utils.cs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 RangeSlider.ReCalculateRangeSelected (cognitive 86) finding(s) in Cognitive Complexity — start with RangeSlider.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 RangeSlider.CentralThumbMouseDown (cognitive 72) finding(s) in Cognitive Complexity — start with RangeSlider.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.8 / 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.
Resolve the 12 TooManyMethods finding(s) in God Classes — start with CheckBoxHelper.cs, RadioButtonHelper.cs, TextBoxHelper.cs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with RangeSlider.cs, CheckBoxHelper.cs, MultiSelectionComboBox.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 ClassTooLong finding(s) in God Classes — start with HamburgerMenu.Properties.cs, FlipView.cs, Flyout.cs. — One of this dimension's main actionable groups (5 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ 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.
520 test methods: 520 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/MahApps.Metro/Controls/MetroWindow.cs.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
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.
13 projects, 643 source files, 47222 hand-written lines of code (43953 production / 3269 test), plus 118 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 12 inter-project edges (build status unknown — did not finish).
Build status unknown
✓ On the Gold path — maintain.
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
MahApps.Metro's documentation is strong in the README and a few other files but thin on comprehensive architecture and usage guides. The README gives an excellent overview of what MahApps.Metro does (WPF toolkit for .NET Framework 4.6.2 through .NET 6 on Windows), its NuGet badges, release status, and links to samples, but it is the single file in a set that only mentions 'Let's get started' as the starting point without any real guidance beyond the banner. The architecture/Docs markdown files are zero, so no deeper structure or design docs exist, leaving usage and migration content unaddressed. XML coverage (2027 of 2867) is high for a single project but not enough to flag gaps in completeness.
The README gives only a banner with links and no real 'Let's get started' content; the body begins with an unshown heading outline marker, so the actual guidance is clipped before it can be assessed.README.md
Resolve the 1 The README gives only a banner with links and no real 'Let's get… 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.
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.
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.
Do you agree with this assessment?
D24 · Comment Value / 10Adequate◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
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.
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).
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 3 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep could NOT parse 2 file(s) — `src/Mahapps.Metro.Tests/Tests/HeaderedControlHelperTests.cs`, `src/Mahapps.Metro.Tests/Tests/TextBoxHelperTests.cs` — so nothing in them was analysed and no absence of findings there is evidence of anything. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
High: github-actions-mutable-action-tag · ×11.github/workflows/ci.yml:18detected by semgrep finding
What to do
Resolve the 11 High finding(s) in Static Analysis (SAST) — start with ci.yml (11). — One of this dimension's main actionable groups (11 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Exemplary✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
3 of 129 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/MahApps.Metro/Controls/Dialogs/ProgressDialog.cs.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Workflow token permissions not restricted finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×7) — ColorChannelMinMaxConverter.cs:71, ColorChannelMinMaxConverter.cs:135, HSVColorChannelMinMaxConverter.cs:63, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
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.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×15) — Flyout3ViewModel.cs:21, Flyout3ViewModel.cs:22, MainWindow.xaml.cs:494, …
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 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 4 of 4 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
Only 5/13 projects share a common root namespace — the code's module identity is inconsistent.
What to do
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.
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.
Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
X1 · Async correctness2.9 / 10Weak✓ Tool-verified
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×25) — MetroWindow.cs:1190, NumericUpDown.cs:1500, HamburgerMenuDefault.xaml.cs:36, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 0/40 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — DialogManager.cs:26, DialogManager.cs:74, DialogManager.cs:124, …
1 further occurrence(s) are not listed individually; the score already reflects all 41.
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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. — FlipView.cs:1095
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — DefaultStringToObjectParser.cs:49, MarkupConverter.cs:31, MarkupConverter.cs:43
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 54 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
D11 Test Reliability — Test reliability not measured — no test run produced results
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
D21 Naming Consistency — LLM evaluation failed
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
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.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into 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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X5 Nullable reference types — no NRT-eligible projects
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X9 Subsumed condition operand — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
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.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:18— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v1`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:20— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-dotnet@<40-character SHA>`. This step references `actions/setup-dotnet@v1`; resolve the SHA it points at today with `gh api repos/actions/setup-dotnet/commits/v1 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/ci.yml:29— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: cake-build/cake-action@<40-character SHA>`. This step references `cake-build/cake-action@v1`; resolve the SHA it points at today with `gh api repos/cake-build/cake-action/commits/v1 --jq .sha`.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:36— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:37— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:38— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:39— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:40— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:41— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:42— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
High: watchdog-secret-into-unpinned-action .github/workflows/ci.yml:43— This step hands a repository secret to a third-party action that is NOT pinned to an immutable reference. A tag - `@v1`, `@v1.2.2`, `@main` - is a pointer the action's owner can repoint at any moment, so the code that receives this secret is whatever that owner publishes next, and it can change without a single commit to this repository or any review by you. An action runs in the job's own process: it can read every secret bound to the step, everything in the workspace, and the runner's network. Pin the action to a full 40-character commit SHA, which names one immutable tree - `uses: owner/repo@<40-character SHA>`, resolved with `gh api repos/<owner>/<repo>/commits/<ref> --jq .sha` - and review the diff before you move it. Where the secret is a long-lived personal access token, scope it down or replace it with the per-run `GITHUB_TOKEN` as well: pinning bounds WHICH code runs, not what the credential can do.
NoWarnInCsproj src/MahApps.Metro.Samples/MahApps.Metro.Demo/MahApps.Metro.Demo.csproj:11— SA1652 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/MahApps.Metro.Samples/MahApps.Metro.Caliburn.Demo/MahApps.Metro.Caliburn.Demo.csproj:11— SA1652 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/MahApps.Metro.Samples/MahApps.Metro.Demo/MahApps.Metro.Demo.csproj:11— WPF0041 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
WriteOnlyPrivateField src/MahApps.Metro.Samples/MahApps.Metro.Caliburn.Demo/Controls/ViewLocator.cs:17— private IThemeManager themeManager — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
EmptyCatchBlock src/MahApps.Metro/Controls/FlipView.cs:1095— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
async void method: OnClosing src/MahApps.Metro/Controls/MetroWindow.cs:1190— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SimulateDecimalPointKeyPress src/MahApps.Metro/Controls/NumericUpDown.cs:1500— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: HamburgerMenuControl_OnOptionsItemClick src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleViews/HamburgerMenuDefault.xaml.cs:36— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Execute src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleViews/HamburgerMenuDefault.xaml.cs:71— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Mscb_Example_AddedItem src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleViews/MultiSelectionComboBoxExample.xaml.cs:28— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: TextBoxSearchOnExecuted src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleViews/TextExamples.xaml.cs:36— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: CleanWindowClosing src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleWindows/CleanWindowDemo.xaml.cs:31— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Button_Click_1 src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleWindows/CleanWindowDemo.xaml.cs:99— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ClickMeOnClick src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleWindows/FlyoutDemo.xaml.cs:95— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: InitializeAsync src/MahApps.Metro.Samples/MahApps.Metro.Demo/ExampleWindows/InteropDemo.xaml.cs:22— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowMessageDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:218— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowLimitedMessageDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:238— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowCustomDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:256— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowAwaitCustomDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:275— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowSecondCustomDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:286— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowLoginDialogPasswordPreview src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:298— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowLoginDialogOnlyPassword src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:311— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowLoginDialogWithRememberCheckBox src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:324— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowProgressDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:337— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowInputDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:383— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowInputDialogCustomButtonSizes src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:395— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: ShowLoginDialog src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:412— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RunProgressFromVm src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindowViewModel.cs:460— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RunCustomFromVm src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindowViewModel.cs:484— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: OnStartup src/MahApps.Metro.Samples/MahApps.Metro.Caliburn.Demo/AppBootstrapper.cs:70— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
TooManyMethods: CheckBoxHelper src/MahApps.Metro/Controls/Helper/CheckBoxHelper.cs:0— TooManyMethods — 1137 significant lines (blank, comment-only and punctuation-only lines excluded), 162 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: RadioButtonHelper src/MahApps.Metro/Controls/Helper/RadioButtonHelper.cs:0— TooManyMethods — 505 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: TextBoxHelper src/MahApps.Metro/Controls/Helper/TextBoxHelper.cs:0— TooManyMethods — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: RangeSlider src/MahApps.Metro/Controls/RangeSlider.cs:0— TooManyMethods — 1257 significant lines (blank, comment-only and punctuation-only lines excluded), 66 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ItemHelper src/MahApps.Metro/Controls/Helper/ItemHelper.cs:0— TooManyMethods — 499 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: TimePickerBase src/MahApps.Metro/Controls/TimePicker/TimePickerBase.cs:0— TooManyMethods — 516 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NumericUpDown src/MahApps.Metro/Controls/NumericUpDown.cs:0— TooManyMethods — 814 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MultiSelectionComboBox src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:0— TooManyMethods — 926 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MetroWindow src/MahApps.Metro/Controls/MetroWindow.cs:0— TooManyMethods — 809 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindow src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:0— TooManyMethods — 293 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SliderHelper src/MahApps.Metro/Controls/Helper/SliderHelper.cs:0— TooManyMethods — 265 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ToggleSwitch src/MahApps.Metro/Controls/ToggleSwitch.cs:0— TooManyMethods — 358 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: Controls/RangeSlider.cs src/MahApps.Metro/Controls/RangeSlider.cs:0— FileTooLong — 1270 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Helper/CheckBoxHelper.cs src/MahApps.Metro/Controls/Helper/CheckBoxHelper.cs:0— FileTooLong — 1142 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: MultiSelectionComboBox/MultiSelectionComboBox.cs src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:0— FileTooLong — 945 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controls/MetroWindow.cs src/MahApps.Metro/Controls/MetroWindow.cs:0— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controls/NumericUpDown.cs src/MahApps.Metro/Controls/NumericUpDown.cs:0— FileTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Helper/TextBoxHelper.cs src/MahApps.Metro/Controls/Helper/TextBoxHelper.cs:0— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controls/FlipView.cs src/MahApps.Metro/Controls/FlipView.cs:0— FileTooLong — 590 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TimePicker/TimePickerBase.cs src/MahApps.Metro/Controls/TimePicker/TimePickerBase.cs:0— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controls/Flyout.cs src/MahApps.Metro/Controls/Flyout.cs:0— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Helper/RadioButtonHelper.cs src/MahApps.Metro/Controls/Helper/RadioButtonHelper.cs:0— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Helper/ItemHelper.cs src/MahApps.Metro/Controls/Helper/ItemHelper.cs:0— FileTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
BareSuppressMessage src/MahApps.Metro/Controls/ToggleSwitch.cs:22— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/Mahapps.Metro.Tests/Tests/HeaderedControlHelperTests.cs:19— System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:16— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:38— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:39— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:40— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:41— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/MahApps.Metro/Properties/AssemblyInfo.cs:42— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/ColorChannelMinMaxConverter.cs:71— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/ColorChannelMinMaxConverter.cs:135— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/HSVColorChannelMinMaxConverter.cs:63— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/HSVColorChannelMinMaxConverter.cs:91— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/HSVColorChannelMinMaxConverter.cs:147— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/PercentageToGridLengthConverter.cs:38— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/MahApps.Metro/Converters/StringIsNullOrEmptyConverter.cs:24— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
ClassTooLong: HamburgerMenu src/MahApps.Metro/Controls/HamburgerMenu/HamburgerMenu.Properties.cs:0— ClassTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods, declared across 5 files: HamburgerMenu/HamburgerMenu.Properties.cs (10), HamburgerMenu/HamburgerMenu.Events.cs (9), HamburgerMenu/HamburgerMenu.cs (3), HamburgerMenu/HamburgerMenu.HamburgerButton.cs (1), +1 more file(s). To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FlipView src/MahApps.Metro/Controls/FlipView.cs:0— ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Flyout src/MahApps.Metro/Controls/Flyout.cs:0— ClassTooLong — 504 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ColorPicker src/MahApps.Metro/Controls/ColorPicker/ColorPicker.cs:0— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SampleData src/MahApps.Metro.Samples/MahApps.Metro.Demo/Models/Album.cs:0— ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (9 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1116— src/MahApps.Metro/Controls/RangeSlider.cs:1116-1124 | src/MahApps.Metro/Controls/RangeSlider.cs:1157-1165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1116` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1129— src/MahApps.Metro/Controls/RangeSlider.cs:1129-1137 | src/MahApps.Metro/Controls/RangeSlider.cs:1144-1152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1457— src/MahApps.Metro/Controls/RangeSlider.cs:1457-1465 | src/MahApps.Metro/Controls/RangeSlider.cs:1556-1564 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1457` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1505— src/MahApps.Metro/Controls/RangeSlider.cs:1505-1513 | src/MahApps.Metro/Controls/RangeSlider.cs:1601-1609 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1505` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/MahApps.Metro/Controls/MetroThumb.cs:38— src/MahApps.Metro/Controls/MetroThumb.cs:38-46 | src/MahApps.Metro/Controls/MetroThumbContentControl.cs:235-243 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
BarePragmaDisable src/MahApps.Metro/Controls/MetroWindow.cs:1544— #pragma warning disable 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair.
BarePragmaDisable src/MahApps.Metro/Controls/MetroWindow.cs:1650— #pragma warning disable 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair.
BarePragmaDisable src/MahApps.Metro/Controls/MetroWindow.cs:1673— #pragma warning disable 618 — the disable is closed again below, so its scope is not the problem; what it records is no reason. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair.
BarePragmaDisable src/MahApps.Metro/Controls/NumericUpDown.cs:524— #pragma warning disable WPF0024 — the disable is closed again below, so its scope is not the problem; what it records is no reason. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair.
MethodTooLong: SampleData.Seed src/MahApps.Metro.Samples/MahApps.Metro.Demo/Models/Album.cs:92— MethodTooLong — Seed runs 418 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Animals.GenerateDate src/MahApps.Metro.Samples/MahApps.Metro.Demo/Models/Animals.cs:15— MethodTooLong — GenerateDate runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainWindowViewModel.MainWindowViewModel(…) src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindowViewModel.cs:73— MethodTooLong — MainWindowViewModel(…) runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HamburgerMenuListBox.PrepareContainerForItemOverride src/MahApps.Metro/Controls/HamburgerMenu/HamburgerMenuListBox.cs:22— MethodTooLong — PrepareContainerForItemOverride runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
TodoComment src/MahApps.Metro/Actions/CloseTabItemAction.cs:55— // TODO Raise a closing event to cancel this action — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MahApps.Metro/Controls/MetroTabControl.cs:111— // Todo Rename this to TabItemClosing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/MahApps.Metro/Controls/MetroWindow.cs:223— // TODO Find a way to reset the zIndex of any open Flyout if <see cref="ShowFlyoutsOverDialogs"/> is changed by the user — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (16 lines × 2) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:482— src/MahApps.Metro/Controls/ClipBorder.Utils.cs:482-497 | src/MahApps.Metro/Controls/ClipBorder.Utils.cs:516-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/ClipBorder.Utils.cs:482` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:181— src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:181-196 | src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs:375-390 — before extracting anything, compare `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs` and `src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:181` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/MahApps.Metro/Controls/HotKeyBox.cs:113— src/MahApps.Metro/Controls/HotKeyBox.cs:113-128 | src/MahApps.Metro/Controls/NumericUpDown.cs:973-988 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/HotKeyBox.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: MainWindow (LCOM4 19) src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:17— MainWindow's methods form 19 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: MetroWindow (LCOM4 6) src/MahApps.Metro/Controls/MetroWindow.cs:38— MetroWindow'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: FlipView (LCOM4 4) src/MahApps.Metro/Controls/FlipView.cs:23— FlipView'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.
Swallowed exception (caught, then discarded) src/MahApps.Metro/Controls/MultiSelectionComboBox/DefaultStringToObjectParser.cs:49— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/MahApps.Metro/Converters/MarkupConverter.cs:31— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/MahApps.Metro/Converters/MarkupConverter.cs:43— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Utils.IsValid (cyclomatic 21) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:235— Utils.IsValid has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (Utils.IsValid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Utils.IsValid (cyclomatic 21) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:324— Utils.IsValid has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (Utils.IsValid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Utils.IsValid (cognitive 16) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:235— Utils.IsValid has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Utils.IsValid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Utils.IsValid (cognitive 16) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:324— Utils.IsValid has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Utils.IsValid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Duplicated block (18 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:947— src/MahApps.Metro/Controls/RangeSlider.cs:947-964 | src/MahApps.Metro/Controls/RangeSlider.cs:973-990 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:947` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1006— src/MahApps.Metro/Controls/RangeSlider.cs:1006-1023 | src/MahApps.Metro/Controls/RangeSlider.cs:1032-1049 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1006` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/MahApps.Metro/Controls/ClipBorder.cs:401— src/MahApps.Metro/Controls/ClipBorder.cs:401-412 | src/MahApps.Metro/Controls/ClipBorder.cs:419-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/ClipBorder.cs:401` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1488— src/MahApps.Metro/Controls/RangeSlider.cs:1488-1499 | src/MahApps.Metro/Controls/RangeSlider.cs:1539-1550 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1488` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
MultiSelectionComboBox.KeyDownHandler (cyclomatic 54) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1538— MultiSelectionComboBox.KeyDownHandler has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Utils.IsEqualTo (cyclomatic 42) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:443— Utils.IsEqualTo has cyclomatic complexity 42 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RangeSlider.CentralThumbMouseDown (cyclomatic 34) src/MahApps.Metro/Controls/RangeSlider.cs:1522— RangeSlider.CentralThumbMouseDown has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MultiSelectionComboBox.UpdateSelectedItemsFromTextTimer_Tick (cyclomatic 31) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:895— MultiSelectionComboBox.UpdateSelectedItemsFromTextTimer_Tick has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Flyout.ApplyAnimation (cyclomatic 28) src/MahApps.Metro/Controls/Flyout.cs:894— Flyout.ApplyAnimation has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RangeSlider.ReCalculateRangeSelected (cyclomatic 26) src/MahApps.Metro/Controls/RangeSlider.cs:1111— RangeSlider.ReCalculateRangeSelected has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MultiSelectionComboBox.OnPreviewMouseWheel (cyclomatic 24) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1442— MultiSelectionComboBox.OnPreviewMouseWheel has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TiltBehavior.CompositionTargetRendering (cyclomatic 23) src/MahApps.Metro/Behaviors/TiltBehavior.cs:138— TiltBehavior.CompositionTargetRendering has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MultiSelectionComboBox.SyncSelectedItems (cyclomatic 23) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1892— MultiSelectionComboBox.SyncSelectedItems has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RangeSlider.MoveToNextValue (cyclomatic 23) src/MahApps.Metro/Controls/RangeSlider.cs:1916— RangeSlider.MoveToNextValue has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ColorPicker.OnIsDropDownOpenChanged (cyclomatic 19) src/MahApps.Metro/Controls/ColorPicker/ColorPicker.cs:803— ColorPicker.OnIsDropDownOpenChanged has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 814). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
DropDownButton.OnItemsChanged (cyclomatic 19) src/MahApps.Metro/Controls/DropDownButton.cs:511— DropDownButton.OnItemsChanged has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MahAppsCommands.ClearControl (cyclomatic 19) src/MahApps.Metro/Controls/Helper/MahAppsCommands.cs:55— MahAppsCommands.ClearControl has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
RangeSlider.UpdateEndPoint (cyclomatic 19) src/MahApps.Metro/Controls/RangeSlider.cs:1874— RangeSlider.UpdateEndPoint has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClipBorder.OnRender (cyclomatic 18) src/MahApps.Metro/Controls/ClipBorder.cs:358— ClipBorder.OnRender has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NumericUpDown.ValidateText (cyclomatic 18) src/MahApps.Metro/Controls/NumericUpDown.cs:1635— NumericUpDown.ValidateText has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RangeSlider.JumpToNextTick (cyclomatic 18) src/MahApps.Metro/Controls/RangeSlider.cs:2162— RangeSlider.JumpToNextTick has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CustomValidationPopup.CustomValidationPopup_Loaded (cyclomatic 17) src/MahApps.Metro/Controls/CustomValidationPopup.cs:142— CustomValidationPopup.CustomValidationPopup_Loaded has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MetroWindow.FlyoutsPreviewMouseDown (cyclomatic 17) src/MahApps.Metro/Controls/MetroWindow.cs:1309— MetroWindow.FlyoutsPreviewMouseDown has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Flyout.OnRenderSizeChanged (cyclomatic 16) src/MahApps.Metro/Controls/Flyout.cs:970— Flyout.OnRenderSizeChanged has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RangeSlider.CenterThumbDragDelta (cyclomatic 16) src/MahApps.Metro/Controls/RangeSlider.cs:1797— RangeSlider.CenterThumbDragDelta has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
No assertions: MetroWindowSmokeTest src/Mahapps.Metro.Tests/Tests/MetroWindowTest.cs:21— Test method exercises code but verifies nothing — add an assertion.
D11 · Test Reliability· Test reliability not measured · ×1
Test reliability not measured — no test run produced results — Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
RangeSlider.ReCalculateRangeSelected (cognitive 86) src/MahApps.Metro/Controls/RangeSlider.cs:1111— RangeSlider.ReCalculateRangeSelected has cognitive complexity 86 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RangeSlider.CentralThumbMouseDown (cognitive 72) src/MahApps.Metro/Controls/RangeSlider.cs:1522— RangeSlider.CentralThumbMouseDown has cognitive complexity 72 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectionComboBox.UpdateSelectedItemsFromTextTimer_Tick (cognitive 70) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:895— MultiSelectionComboBox.UpdateSelectedItemsFromTextTimer_Tick has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectionComboBox.KeyDownHandler (cognitive 69) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1538— MultiSelectionComboBox.KeyDownHandler has cognitive complexity 69 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.CenterThumbDragDelta (cognitive 47) src/MahApps.Metro/Controls/RangeSlider.cs:1797— RangeSlider.CenterThumbDragDelta has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TiltBehavior.CompositionTargetRendering (cognitive 46) src/MahApps.Metro/Behaviors/TiltBehavior.cs:138— TiltBehavior.CompositionTargetRendering has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Flyout.OnIsOpenPropertyChanged (cognitive 44) src/MahApps.Metro/Controls/Flyout.cs:131— Flyout.OnIsOpenPropertyChanged has cognitive complexity 44 (threshold 15). Most of this is not in the body itself: 0 of the 44 points are its own statements and the rest belongs to one function literal inside it that branches (line 135). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
MultiSelectionComboBox.SyncSelectedItems (cognitive 40) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1892— MultiSelectionComboBox.SyncSelectedItems has cognitive complexity 40 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Flyout.ApplyAnimation (cognitive 39) src/MahApps.Metro/Controls/Flyout.cs:894— Flyout.ApplyAnimation has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.JumpToNextTick (cognitive 38) src/MahApps.Metro/Controls/RangeSlider.cs:2162— RangeSlider.JumpToNextTick has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectionComboBox.OnPreviewMouseWheel (cognitive 37) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1442— MultiSelectionComboBox.OnPreviewMouseWheel has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.MoveToNextValue (cognitive 37) src/MahApps.Metro/Controls/RangeSlider.cs:1916— RangeSlider.MoveToNextValue has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.MoveThumbHorizontal (cognitive 33) src/MahApps.Metro/Controls/RangeSlider.cs:936— RangeSlider.MoveThumbHorizontal has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (RangeSlider.MoveThumbVertical) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RangeSlider.MoveThumbVertical (cognitive 33) src/MahApps.Metro/Controls/RangeSlider.cs:995— RangeSlider.MoveThumbVertical has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (RangeSlider.MoveThumbHorizontal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Utils.IsEqualTo (cognitive 30) src/MahApps.Metro/Controls/ClipBorder.Utils.cs:443— Utils.IsEqualTo has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DropDownButton.OnItemsChanged (cognitive 28) src/MahApps.Metro/Controls/DropDownButton.cs:511— DropDownButton.OnItemsChanged has cognitive complexity 28 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TextBoxHelper.OnIsMonitoringChanged (cognitive 28) src/MahApps.Metro/Controls/Helper/TextBoxHelper.cs:821— TextBoxHelper.OnIsMonitoringChanged has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.UpdateEndPoint (cognitive 28) src/MahApps.Metro/Controls/RangeSlider.cs:1874— RangeSlider.UpdateEndPoint has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColorPicker.OnIsDropDownOpenChanged (cognitive 27) src/MahApps.Metro/Controls/ColorPicker/ColorPicker.cs:803— ColorPicker.OnIsDropDownOpenChanged has cognitive complexity 27 (threshold 15). Most of this is not in the body itself: 8 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 814). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
RangeSlider.LeftButtonMouseDown (cognitive 26) src/MahApps.Metro/Controls/RangeSlider.cs:1426— RangeSlider.LeftButtonMouseDown has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (RangeSlider.RightButtonMouseDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RangeSlider.RightButtonMouseDown (cognitive 26) src/MahApps.Metro/Controls/RangeSlider.cs:1474— RangeSlider.RightButtonMouseDown has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (RangeSlider.LeftButtonMouseDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RangeSlider.SnapToTickHandle (cognitive 25) src/MahApps.Metro/Controls/RangeSlider.cs:2031— RangeSlider.SnapToTickHandle has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClipBorder.OnRender (cognitive 24) src/MahApps.Metro/Controls/ClipBorder.cs:358— ClipBorder.OnRender has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColorHelper.ColorHelper.ctor (cognitive 24) src/MahApps.Metro/Controls/ColorPicker/ColorHelper.cs:57— ColorHelper.ColorHelper.ctor has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HamburgerMenuItemStyleSelector.SelectStyle (cognitive 24) src/MahApps.Metro/Controls/HamburgerMenu/MenuItems/HamburgerMenuItemStyleSelector.cs:18— HamburgerMenuItemStyleSelector.SelectStyle has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RangeSlider.LeftThumbDragDelta (cognitive 24) src/MahApps.Metro/Controls/RangeSlider.cs:1641— RangeSlider.LeftThumbDragDelta has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (RangeSlider.RightThumbDragDelta) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RangeSlider.RightThumbDragDelta (cognitive 24) src/MahApps.Metro/Controls/RangeSlider.cs:1714— RangeSlider.RightThumbDragDelta has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (RangeSlider.LeftThumbDragDelta) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RangeSlider.ReCalculateSize (cognitive 23) src/MahApps.Metro/Controls/RangeSlider.cs:1055— RangeSlider.ReCalculateSize has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NumericUpDown.OnValueChanged (cognitive 22) src/MahApps.Metro/Controls/NumericUpDown.cs:1188— NumericUpDown.OnValueChanged has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CloseTabItemAction.Invoke (cognitive 21) src/MahApps.Metro/Actions/CloseTabItemAction.cs:19— CloseTabItemAction.Invoke has cognitive complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.ReCalculateRangeSelected (cognitive 20) src/MahApps.Metro/Controls/RangeSlider.cs:1178— RangeSlider.ReCalculateRangeSelected has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TimePickerBase.SetHourPartValues (cognitive 20) src/MahApps.Metro/Controls/TimePicker/TimePickerBase.cs:1059— TimePickerBase.SetHourPartValues has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScrollViewerHelper.EndOfVerticalScrollReachedCommandPropertyChanged (cognitive 19) src/MahApps.Metro/Controls/Helper/ScrollViewerHelper.cs:157— ScrollViewerHelper.EndOfVerticalScrollReachedCommandPropertyChanged has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ScrollViewerHelper.EndOfHorizontalScrollReachedCommandPropertyChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ScrollViewerHelper.EndOfHorizontalScrollReachedCommandPropertyChanged (cognitive 19) src/MahApps.Metro/Controls/Helper/ScrollViewerHelper.cs:238— ScrollViewerHelper.EndOfHorizontalScrollReachedCommandPropertyChanged has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ScrollViewerHelper.EndOfVerticalScrollReachedCommandPropertyChanged) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ResizeModeMinMaxButtonVisibilityConverter.Convert (cognitive 19) src/MahApps.Metro/Converters/ResizeModeMinMaxButtonVisibilityConverter.cs:20— ResizeModeMinMaxButtonVisibilityConverter.Convert has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowsSettingBehavior.SaveWindowState (cognitive 18) src/MahApps.Metro/Behaviors/WindowsSettingBehavior.cs:150— WindowsSettingBehavior.SaveWindowState has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MahAppsCommands.ClearControl (cognitive 18) src/MahApps.Metro/Controls/Helper/MahAppsCommands.cs:55— MahAppsCommands.ClearControl has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ColorPicker.OnLostMouseCapture (cognitive 17) src/MahApps.Metro/Controls/ColorPicker/ColorPicker.cs:872— ColorPicker.OnLostMouseCapture has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MultiSelectorBinding.OnCollectionChanged (cognitive 17) src/MahApps.Metro/Controls/Helper/MultiSelectorHelper.cs:197— MultiSelectorBinding.OnCollectionChanged has cognitive complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BaseMetroTabControl.CloseThisTabItem (cognitive 17) src/MahApps.Metro/Controls/MetroTabControl.cs:149— BaseMetroTabControl.CloseThisTabItem has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RangeSlider.CalculateNextTick (cognitive 17) src/MahApps.Metro/Controls/RangeSlider.cs:2105— RangeSlider.CalculateNextTick has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeHelper.GetChildObjects (cognitive 17) src/MahApps.Metro/Controls/TreeHelper.cs:211— TreeHelper.GetChildObjects has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CustomValidationPopup.CustomValidationPopup_Loaded (cognitive 16) src/MahApps.Metro/Controls/CustomValidationPopup.cs:142— CustomValidationPopup.CustomValidationPopup_Loaded has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FlyoutsControl.PrepareContainerForItemOverride (cognitive 16) src/MahApps.Metro/Controls/FlyoutsControl.cs:69— FlyoutsControl.PrepareContainerForItemOverride has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiSelectionComboBox.OnItemsChanged (cognitive 16) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1297— MultiSelectionComboBox.OnItemsChanged has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
RangeSlider.ReCalculateRangeSelected (cognitive 16) src/MahApps.Metro/Controls/RangeSlider.cs:1229— RangeSlider.ReCalculateRangeSelected has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeHelper.FindChild (cognitive 16) src/MahApps.Metro/Controls/TreeHelper.cs:114— TreeHelper.FindChild has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Medium: watchdog-personal-data-in-log src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindowViewModel.cs:491— Personal data appears to be written to a log or console sink. Under GDPR Article 5(1)(c) logs should carry the minimum needed to operate the system; prefer a pseudonymous identifier over the personal value itself.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 3 floating ref(s) across 1 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
Workflow token permissions not restricted — No workflow declares a `permissions:` block, so every job runs with the repository's default GITHUB_TOKEN scope (1 workflow file(s) checked). On a repository whose default is read/write, a compromised action or a malicious pull request inherits write access to code, issues, releases and packages. Declare a least-privilege `permissions:` block — `permissions: {contents: read}` at the top of each workflow, widened per job only where a job genuinely writes.
Duplicated block (28 lines × 2) src/MahApps.Metro/Controls/HamburgerMenu/HamburgerMenu.Properties.cs:43— src/MahApps.Metro/Controls/HamburgerMenu/HamburgerMenu.Properties.cs:43-70 | src/MahApps.Metro/Controls/SplitView/SplitView.cs:170-197 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/HamburgerMenu/HamburgerMenu.Properties.cs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) src/MahApps.Metro/Controls/Helper/ExpanderHelper.cs:201— src/MahApps.Metro/Controls/Helper/ExpanderHelper.cs:201-217 | src/MahApps.Metro/Controls/Helper/ExpanderHelper.cs:296-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/Helper/ExpanderHelper.cs:201` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1554— src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1554-1568 | src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1576-1590 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1554` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:200— src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:200-212 | src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs:394-406 | src/MahApps.Metro/Controls/Dialogs/MessageDialog.cs:347-359 — before extracting anything, compare `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs` and `src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) src/MahApps.Metro/Controls/DropDownButton.cs:429— src/MahApps.Metro/Controls/DropDownButton.cs:429-441 | src/MahApps.Metro/Controls/SplitButton.cs:323-335 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/DropDownButton.cs:429` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) src/MahApps.Metro/Controls/ClipBorder.cs:542— src/MahApps.Metro/Controls/ClipBorder.cs:542-552 | src/MahApps.Metro/Controls/ClipBorder.cs:553-563 | src/MahApps.Metro/Controls/ClipBorder.cs:564-574 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) src/MahApps.Metro/Controls/RangeSlider.cs:1440— src/MahApps.Metro/Controls/RangeSlider.cs:1440-1450 | src/MahApps.Metro/Controls/RangeSlider.cs:1584-1594 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/RangeSlider.cs:1440` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:137— src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:137-146 | src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs:305-314 — before extracting anything, compare `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs` and `src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:31— src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:31-36 | src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs:32-37 — before extracting anything, compare `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs` and `src/MahApps.Metro/Controls/Dialogs/LoginDialog.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/MahApps.Metro/Controls/Dialogs/InputDialog.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 4) src/MahApps.Metro/Controls/DropDownButton.cs:361— src/MahApps.Metro/Controls/DropDownButton.cs:361-371 | src/MahApps.Metro/Controls/HamburgerMenu/MenuItems/HamburgerMenuItem.cs:175-185 | src/MahApps.Metro/Controls/SplitButton.cs:245-255 | src/MahApps.Metro/Controls/ToggleSwitch.cs:665-675 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Coverage not measured — analyzer environment — Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read.
Swallowed exception (empty catch) src/MahApps.Metro/Controls/FlipView.cs:1095— 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.
Commented-out code src/MahApps.Metro.Samples/MahApps.Metro.Caliburn.Demo/ViewModels/Flyouts/Flyout3ViewModel.cs:21— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro.Samples/MahApps.Metro.Caliburn.Demo/ViewModels/Flyouts/Flyout3ViewModel.cs:22— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:494— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro.Samples/MahApps.Metro.Demo/MainWindow.xaml.cs:495— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/CustomValidationPopup.cs:445— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1361— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1362— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1366— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1367— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1629— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MetroWindow.cs:1630— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1137— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1215— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1216— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/MahApps.Metro/Controls/MultiSelectionComboBox/MultiSelectionComboBox.cs:1217— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: src/MahApps.Metro/Controls/MetroWindow.cs. Pair on, review, or document these before any departure.
D19 · Documentation Quality· The README gives only a banner with links and no real 'Let's get started' content; the body begins with an unshown heading outline marker, so the actual guidance is clipped before it can be assessed. · ×1
The README gives only a banner with links and no real 'Let's get started' content; the body begins with an unshown heading outline marker, so the actual guidance is clipped before it can be assessed. README.md— Add a short Getting Started section covering installation, first controls, and a minimal app to run.
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 44k LoC across 13 projects the codebase is large and multi-module, so explicit bounded contexts are needed. Name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
Split MahApps.Metro — A large UI toolkit whose namespaces are all facets of the Metro theme and controls, so it is a grab-bag. Suggested: by namespace: Themes, Controls, Layout
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 3 of 129 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 100 lines or more, excluding tests, vendored, generated and example/demo trees, largest first). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — largest first: src/MahApps.Metro/Controls/Dialogs/ProgressDialog.cs, src/MahApps.Metro/Controls/ColorPicker/ColorCanvas.cs, src/MahApps.Metro/Controls/MultiSelectionComboBox/ICompareObjectToString.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (`sbom-tool generate` (install it with `dotnet tool install --global Microsoft.Sbom.DotNetTool`) or `dotnet CycloneDX` over the solution, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Ship it with the artifact you distribute — for a package registry that means packing the document (`*.spdx.json` / `*.cdx.json`) into the package itself, so it cannot drift from what a consumer installs.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
Logging is not universal — Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 0/40 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Build status unknown — The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 solution
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 01a00a9e-9f2f-775a-8cea-5b3f5a1e4e68 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 4 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by name with a deliberately specific classifier (the same one the GDPR dimensions use, so CardDefinition or FileName don't trip); informational — it feeds no score.
Issues: 16 · Warnings: 188 · Recommendations: 31 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 16-08-2026 @ 12:49 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.