Public report of dalyIsaac/Whim, published 17 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 17 November 2026, 20:17 UTC · Survey ID cd_7fb8b7510d4e4eb697b57059bf981b83

dalyIsaac/Whim

Measured 17 November 2026, 20:16 UTC, at code version 1e86b57

Code coverage is not measured: Suite not runnable in-image.

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

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

CAI score 59.1out of 100 At risk

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 25,416 lines of product code in 27 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Code Health, 55.2

Findings by how serious they are

33 critical 76 serious 222 minor

2 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 20:16 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

60of 60 dimensions measured by tools.
294of 331 findings point to an exact file and line, so you can open each one in the code. The other 37 concern the repository as a whole, such as missing documentation.
60dimensions across 6 lenses, read from 25,416 lines of product code in 27 projects.
Chapters

Executive summary

dalyIsaac/Whim is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back because it has analysis rules switched off in the settings. It scores 59.1 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Code Health, at 55.2, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 3.6 points. Handling the discarded errors would lift Code Health itself, worth about 3.2 points. Raising Code Health to 67 would lift the score to about 61.8.

Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two known security holes in the packages the code depends on can be used by attackers, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks. The pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The four analysis rules switched off in the settings need switching back on in the settings file.

The product code is 25,416 lines, about €77,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Code Health 55.2 · counts for 46%Maturity 55.6 · counts for 25%Production Readiness 63.2 · counts for 14%Security and Compliance 67.7 · counts for 8%Architecture 71.9 · counts for 4%Performance 100.0 · counts for 2%

If Code Health rose from 55.2 to 67, the lowest score rated Strong, the score would rise from 59.1 to about 61.8.

Code composition: what the lines of code are
Business logic 15%Supporting code 18%Tests 66%
Rebuild cost: about €77,000 · Estimate
Cost to rebuild€25,000 to €130,000, for 421 to 1,346 hours of work, about 0.5 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 59. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 25,416 lines of product code
Comment linesThe estimate prices 17,575 lines. Comment lines count towards the size of 25,416 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Whim.Runner.csproj.
Raises the score by about 3.6 points · Low effort · ADR Quality
2
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with CoreSavedStateManager.cs.
Raises the score by about 3.2 points · Low effort · Explicit Debt
3
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props.
Raises the score by about 3.2 points · Low effort · Explicit Debt

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €77,000 to build again, about 0.5 person-years of work. Its weakest lens is Code Health, at 55.2 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3.6 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch Whim Whim Whim.Bar Bar Whim.Bar->Whim Whim.CommandPalette CommandPalette Whim.CommandPalette->Whim Whim.FloatingWindow FloatingWindow Whim.FloatingWindow->Whim Whim.FocusIndicator FocusIndicator Whim.FocusIndicator->Whim Whim.Gaps Gaps Whim.Gaps->Whim Whim.Gaps->Whim.FloatingWindow Whim.LayoutPreview LayoutPreview Whim.LayoutPreview->Whim Whim.LayoutPreview->Whim.FloatingWindow Whim.Runner Runner Whim.Runner->Whim Whim.Runner->Whim.Bar Whim.Runner->Whim.CommandPalette Whim.Runner->Whim.FloatingWindow Whim.Runner->Whim.FocusIndicator Whim.Runner->Whim.Gaps Whim.Runner->Whim.LayoutPreview Whim.SliceLayout SliceLayout Whim.Runner->Whim.SliceLayout Whim.TreeLayout TreeLayout Whim.Runner->Whim.TreeLayout Whim.TreeLayout.Bar Bar Whim.Runner->Whim.TreeLayout.Bar Whim.TreeLayout.CommandPalette CommandPalette Whim.Runner->Whim.TreeLayout.CommandPalette Whim.Updater Updater Whim.Runner->Whim.Updater Whim.Yaml Yaml Whim.Runner->Whim.Yaml Whim.SliceLayout->Whim Whim.TreeLayout->Whim Whim.TreeLayout.Bar->Whim Whim.TreeLayout.Bar->Whim.Bar Whim.TreeLayout.Bar->Whim.TreeLayout Whim.TreeLayout.CommandPalette->Whim Whim.TreeLayout.CommandPalette->Whim.CommandPalette Whim.TreeLayout.CommandPalette->Whim.TreeLayout Whim.Updater->Whim Whim.Yaml->Whim Whim.Yaml->Whim.Bar Whim.Yaml->Whim.CommandPalette Whim.Yaml->Whim.FloatingWindow Whim.Yaml->Whim.FocusIndicator Whim.Yaml->Whim.Gaps Whim.Yaml->Whim.LayoutPreview Whim.Yaml->Whim.SliceLayout Whim.Yaml->Whim.TreeLayout Whim.Yaml->Whim.TreeLayout.Bar Whim.Yaml->Whim.TreeLayout.CommandPalette Whim.Yaml->Whim.Updater

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

21 modules, with 28 dependencies between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Windows.Win32.Foundation2 Windows.Win32.Graphics.Dwm3 Windows.Win32.Graphics.Gdi4 Windows.Win32.UI.Input.KeyboardAndMouse5 Windows.Win32.UI.WindowsAndMessaging6 app_rules.generate_app_rules7 Whim8 Windows.Win329 Whim.Bar10 Whim.CommandPalette11 Whim.FloatingWindow12 Whim.FocusIndicator13 Whim.Gaps14 Whim.LayoutPreview15 Whim.Runner16 Whim.SliceLayout17 Whim.TreeLayout18 Whim.Updater19 Whim.TreeLayout.Bar20 Whim.TreeLayout.CommandPalette21 Whim.Yaml
1 Windows.Win32.Foundation
2 Windows.Win32.Graphics.Dwm
3 Windows.Win32.Graphics.Gdi
4 Windows.Win32.UI.Input.KeyboardAndMouse
5 Windows.Win32.UI.WindowsAndMessaging
6 app_rules.generate_app_rules
7 Whim4621884
8 Windows.Win32111
9 Whim.Bar62
10 Whim.CommandPalette26
11 Whim.FloatingWindow230
12 Whim.FocusIndicator113
13 Whim.Gaps13
14 Whim.LayoutPreview21
15 Whim.Runner4
16 Whim.SliceLayout22
17 Whim.TreeLayout34
18 Whim.Updater5
19 Whim.TreeLayout.Bar1025
20 Whim.TreeLayout.CommandPalette822
21 Whim.Yaml91
Uses a module listed above itPart of a loopThe module itself
1 Windows.Win32.Foundation2 Windows.Win32.Graphics.Dwm3 Windows.Win32.Graphics.Gdi4 Windows.Win32.UI.Input.KeyboardAndMouse5 Windows.Win32.UI.WindowsAndMessaging6 app_rules.generate_app_rules7 Whim8 Windows.Win329 Whim.Bar10 Whim.CommandPalette11 Whim.FloatingWindow12 Whim.FocusIndicator13 Whim.Gaps14 Whim.LayoutPreview15 Whim.Runner16 Whim.SliceLayout17 Whim.TreeLayout18 Whim.Updater19 Whim.TreeLayout.Bar20 Whim.TreeLayout.CommandPalette21 Whim.YamlWindows.Win32.Foundation1Windows.Win32.Graphics.Dwm2Windows.Win32.Graphics.Gdi3Windows.Win32.UI.Input.KeyboardAndMouse4Windows.Win32.UI.WindowsAndMessaging5app_rules.generate_app_rules6Whim7Windows.Win328Whim.Bar9Whim.CommandPalette10Whim.FloatingWindow11Whim.FocusIndicator12Whim.Gaps13Whim.LayoutPreview14Whim.Runner15Whim.SliceLayout16Whim.TreeLayout17Whim.Updater18Whim.TreeLayout.Bar19Whim.TreeLayout.CommandPalette20Whim.Yaml21462188411162262301131321422345102582291

At a glance — Code Health · 55.2 · Adequate · gated by X1 ·

At a glance — Architecture · 71.9 · Adequate · gated by AX2 ·

At a glance — Maturity · 55.6 · Adequate · gated by D34, M2 ·

At a glance — Readiness · 63.2 · Adequate · gated by P3 ·

At a glance — Security · 67.7 · Adequate · gated by D36 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection24High / Critical
A03:2025 — Software Supply Chain Failures15High / Critical

Roadmap

Top priorities: Resolve the 101 Orphaned file finding(s) in Knowledge Freshness — start with TreeHelpers.cs, SliceLayouts.cs, CoreCommands.cs; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Whim.Runner.csproj; Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with CoreSavedStateManager.cs.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Whim.Runner.csproj.+3.6 ptsLowADR Quality
Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with CoreSavedStateManager.cs.+3.2 ptsLowExplicit Debt
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props.+3.2 ptsLowExplicit Debt
Resolve the 4 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (4).+3.2 ptsLowExplicit Debt
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+2.9 ptsLowDocumentation Quality
Sync-over-async (deadlock risk) through `.Result`+3.1 ptsMediumAsync correctness
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+3.0 ptsMediumArchitecture documentation
Resolve the 49 redundant comment finding(s) in Comment Value — start with MonitorEventListenerTests.cs (4), MutableRootSectorTests.cs (4), ProxyFloatingLayoutEngine.cs (3).+2.7 ptsMediumComment Value

File quality

Per-file score 0–10 — a quality signature. Of 76 files carrying findings, judged against the Preview bar: 5% slop · 11% mixed · 84% near-clean.

FileScoreBandWorst signal
REDACTED2.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopDependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
.editorconfig5.5MixedExplicit Debt: AnalyzerSeverityNone
src/Whim/Native/CoreNativeManager.cs6.3MixedGod Classes: TooManyMethods: CoreNativeManager
src/Whim/Store/MonitorSector/Transforms/MonitorsChangedTransform.cs6.7MixedExplicit Debt: HackComment
src/Whim/Commands/CoreCommands.cs6.9MixedGod Classes: MethodTooLong: CoreCommands.CoreCommands(…)
src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs6.9MixedCode Duplication: Edited copy of a member (23 corresponding lines)
REDACTED7.2Near-cleanStatic Analysis (SAST): High: REDACTED
src/Whim/Context/CoreSavedStateManager.cs7.6Near-cleanExplicit Debt: EmptyCatchBlock
src/Directory.Build.props7.6Near-cleanExplicit Debt: NoWarnInCsproj
src/Whim.Bar.Tests/Directory.Build.props7.6Near-cleanExplicit Debt: NoWarnInCsproj repeated across 13 files
src/Whim.TreeLayout/Tree/TreeHelpers.cs7.6Near-cleanCognitive Complexity: TreeHelpers.GetNodeContainingPoint (cognitive 26)
src/Whim.SliceLayout/AreaHelpers.cs7.8Near-cleanCognitive Complexity: AreaHelpers.Prune (cognitive 21)
src/Whim.TreeLayout/TreeLayoutEngine.cs7.8Near-cleanGod Classes: ClassTooLong: TreeLayoutEngine
src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs7.8Near-cleanCode Duplication: Edited copy of a member (34 corresponding lines)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 33

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 76

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 222

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

Could not be resolved — 2

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 60 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 60 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D18D19D20D24D26D27D28D29D30D34D35D36D43D44AX10AX2AX3AX4AX5AX6AX8GD1IC1M1M2M3M4P1P2P3P4P6PF3X1X12X13X16X18X21X22X23X25X27X28X29X3X30X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1eb27-d191-7405-867f-fc4618e9ab1a.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`dotnet test Whim.sln --collect:"XPlat Code Coverage`), uploaded by `codecov/codecov-action` shows that coverage is collected and tracked in your own CI. The suite could not be built/run in-image, so the number could not be read here — it is excluded from the score rather than treated as unmeasured-by-the-team. To have it measured, make the suite runnable without services we do not provision (a database, a broker). For context only, test code is ≈ 100% of production LoC (33,798 test / 25,188 production) — a rough proxy, NOT a coverage measurement. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 631 commit(s) sampled, automation and bot accounts excluded). One of them holds 94% of the history; the other 10 hold 0.6% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'src/Whim.Runner/Whim.Runner.csproj' with message: WindowsAppSDKSelfContained requires a supported Windows architecture.
  • D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 4 error(s), and the diagnostics it printed were: MSB3073: The command ""/tmp/nuget-packages/microsoft.windowsappsdk/1.7.250401001/buildTransitive/../tools/net6.0/../net472/XamlCompiler.exe" "obj/Debug/net8.0-windows10.0.19041.0/input.json" "obj/Debug/net8.0-windows10.0.19041.0/output.json"" exited with code 126.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (25,188 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/Whim.Bar/BarConfig.cs`, `src/Whim.Bar/BarPlugin.cs`, `src/Whim.CommandPalette/CommandPaletteCommands.cs`, `src/Whim.CommandPalette/ExecuteCommand.cs`, `src/Whim.CommandPalette/Variants/FreeText/FreeTextVariantViewModel.cs`, … (+38 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (src/Whim.Yaml/ErrorWindow.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • 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").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 method(s) exceeded the cyclomatic complexity threshold of 15. 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 BatteryWidgetIcons.GetBatteryIcon at 41 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Whim.Bar/Battery/BatteryWidgetIcons.cs (BatteryWidgetIcons.GetBatteryIcon at 41), src/Whim/Keybind/VirtualKeyExtensions.cs (VirtualKeyExtensions.TryParseKeyModifier at 17), src/Whim/Store/WindowSector/WindowEventListener.cs (WindowEventListener.WinEventProc at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity9.1 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 method(s) exceeded the cognitive complexity threshold of 15; the worst was TreeHelpers.GetNodeContainingPoint at 26.

TreeHelpers.GetNodeContainingPoint (cognitive 26)src/Whim.TreeLayout/Tree/TreeHelpers.cs:165
AreaHelpers.Prune (cognitive 21)src/Whim.SliceLayout/AreaHelpers.cs:15
MonitorsChangedTransform.UpdateMapSector (cognitive 18)src/Whim/Store/MonitorSector/Transforms/MonitorsChangedTransform.cs:97
GapsLayoutEngine.DoLayout (cognitive 16)src/Whim.Gaps/GapsLayoutEngine.cs:44

What to do

  1. Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with TreeHelpers.GetNodeContainingPoint (cognitive 26), AreaHelpers.Prune (cognitive 21), MonitorsChangedTransform.UpdateMapSector (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.3 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 god class(es) detected.

TooManyMethods: CoreNativeManager · ×2src/Whim/Native/CoreNativeManager.cs
MethodTooLong: CoreCommands.CoreCommands(…)src/Whim/Commands/CoreCommands.cs:14
ClassTooLong: TreeLayoutEnginesrc/Whim.TreeLayout/TreeLayoutEngine.cs

What to do

  1. Resolve the 2 TooManyMethods finding(s) in God Classes — start with CoreNativeManager.cs, WorkspacePickers.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 MethodTooLong finding(s) in God Classes — start with CoreCommands.cs. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with TreeLayoutEngine.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication8.7 / 10Strong✓ Tool-verified

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

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

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

4 duplicated block group(s) detected. 3.3 % of the production lines (836 of 25,188) are in a reported copy. A further 23 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (10 corresponding lines) · ×3src/Whim/Store/MapSector/Transforms/MoveWindowToAdjacentMonitorTransform.cs:15
Edited copy of a member (34 corresponding lines) · ×2src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:251
Edited copy of a member (22 corresponding lines) · ×2src/Whim/Keybind/KeyModifiers.cs:76
Edited copy of a member (21 corresponding lines) · ×2src/Whim/Layout/FocusLayoutEngine.cs:188
Edited copy of a member (18 corresponding lines) · ×2src/Whim.FloatingWindow/FloatingWindowPlugin.cs:46

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

What to do

  1. Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with MoveWindowToAdjacentMonitorTransform.cs, CamelCase.cs, CoreNativeManager.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Edited copy of a member (34 corresponding lines) finding(s) in Code Duplication — start with MenuVariantViewModel.cs, CamelCase.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with KeyModifiers.cs, WindowMovedTransform.cs. — One of this dimension's main actionable groups (2 warning-level).

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

D5 · Coupling9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

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

Off the main sequence: Whimsrc/Whim/Whim.csproj:1

What to do

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

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

D6 · Cohesion (LCOM4)9.8 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 74 classes have LCOM4 above 3.

Low cohesion: CoreNativeManager (LCOM4 13)src/Whim/Native/CoreNativeManager.cs:15

What to do

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

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

D10 · Test Quality10.0 / 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.

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

0 skipped, 0 zero-assertion, 10 mock references across 1346 tests.

Mock framework: NSubstitute · ×10

✓ On the Gold path — maintain.

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

D12 · Dependency Hygiene8.7 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

17 outdated, 0 vulnerable, 1 deprecated packages.

Deprecated: xunitDirectory.Packages.props:32
Outdated: coverlet.collectorDirectory.Packages.props:27
Outdated: Microsoft.CodeAnalysis.Scripting · ×16

What to do

  1. Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Directory.Packages.props. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 160 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 26 direct `PackageReference`(s), and 134 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt4.8 / 10Weak✓ Tool-verified

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

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

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

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

AnalyzerSeverityNone · ×4.editorconfig:237
EmptyCatchBlocksrc/Whim/Context/CoreSavedStateManager.cs:63
NoWarnInCsprojsrc/Directory.Build.props:6
NoWarnInCsproj repeated across 13 filessrc/Whim.Bar.Tests/Directory.Build.props:4
BareSuppressMessage repeated across 18 filessrc/Whim.Bar.Tests/GlobalSuppressions.cs:11

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

What to do

  1. Resolve the 4 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (4). — One of this dimension's main actionable groups (4 issue-level).
  2. Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with CoreSavedStateManager.cs. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props. — One of this dimension's main actionable groups (1 issue-level).

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

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

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

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

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

27 projects, 578 source files, 58986 hand-written lines of code (25188 production / 33798 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 71 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

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

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

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

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

What to do

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

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundsrc/Whim.Runner/Whim.Runner.csproj:25

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Whim.Runner.csproj. — 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.

D24 · Comment Value5.7 5.6 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 5.6 / 10 · rule-coverage 99% · ceiling Documented

53 of 1222 judged comments only repeat the code they sit on (4.3 %). 13 comment(s) in another language or script were not judged.

redundant comment · ×49src/Whim.Bar.Tests/ActiveLayout/ActiveLayoutWidgetViewModelTests.cs:224
doc comments repeat the names · ×17src/Whim/Commands/CommandManager.cs:11

What to do

  1. Resolve the 49 redundant comment finding(s) in Comment Value — start with MonitorEventListenerTests.cs (4), MutableRootSectorTests.cs (4), ProxyFloatingLayoutEngine.cs (3). — One of this dimension's main actionable groups (49 recommendation-level).

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

D26 · Project Cohesion9.3 / 10Exemplary✓ Tool-verified

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

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

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

1 of 27 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionsrc/Whim/Whim.csproj:1

✓ On the Gold path — maintain.

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

D27 · Navigability7.7 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

58 % of calls cross a namespace and 16 % go through an interface, but 88 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)7.1 / 10Adequategated by 24 critical findings✓ Tool-verified

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

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

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

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

24 finding(s): 0 critical, 24 high, 0 medium, 0 low. 22 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 hit a parse error in 82 file(s) — `src/Whim.Bar.Tests/Workspace/WorkspaceModelTests.cs` (line 41), `src/Whim.Bar/BarConfig.cs` (line 46, line 47, line 48, …), `src/Whim.Bar/BarPlugin.cs` (line 14), `src/Whim.CommandPalette.Tests/Variants/Menu/MenuVariantViewModelTests.cs` (line 146, line 249, line 332), `src/Whim.CommandPalette/CommandPaletteCommands.cs` (line 193, line 227), … (+77 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 37 of those file(s) — `src/Whim.Bar/BarConfig.cs`, `src/Whim.Bar/BarPlugin.cs`, `src/Whim.CommandPalette/ExecuteCommand.cs`, `src/Whim.CommandPalette/Variants/FreeText/FreeTextVariantViewModel.cs`, `src/Whim.CommandPalette/Variants/Menu/MenuVariantRowViewModel.cs`, … (+32 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 4 of those file(s) — `src/Whim.Tests/Keybind/KeyModifiersTests.cs`, `src/Whim.Tests/Store/WorkspaceSector/Transforms/LayoutEngineCustomActionTransformTests.cs`, `src/Whim.Tests/Utils/ResultTests.cs`, `src/Whim.TreeLayout.Tests/Utils/TestTreeWindowStates.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 22 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (22 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities7.8 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

4 finding(s): 1 critical, 1 high, 2 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

103 of 103 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Whim/Native/ICoreNativeManager.cs. Counted over 103 of the 328 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×101src/Whim.TreeLayout/Tree/TreeHelpers.cs:1
Most significant orphaned file · ×2src/Whim/Native/ICoreNativeManager.cs:1
Dormant codebase

What to do

  1. Resolve the 101 Orphaned file finding(s) in Knowledge Freshness — start with TreeHelpers.cs, SliceLayouts.cs, CoreCommands.cs. — One of this dimension's main actionable groups (101 recommendation-level).
  2. Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with ICoreNativeManager.cs, TreeLayoutEngine.cs. — One of this dimension's main actionable groups (2 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: BaseProxyLayoutEngine.cs↔Workspace.cs 82%; ICoreNativeManager.cs↔Workspace.cs 62%; CoreNativeManager.cs↔Workspace.cs 57%

Change-coupling hub: Workspace.cs → BaseProxyLayoutEngine.cs, CoreNativeManager.cs, ICoreNativeManager.cssrc/Whim/Workspace/Workspace.cs
Change coupling: BaseProxyLayoutEngine.cs ↔ IWorkspace.cssrc/Whim/Layout/BaseProxyLayoutEngine.cs:1

What to do

  1. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Workspace.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Change coupling finding(s) in Change Coupling — start with BaseProxyLayoutEngine.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 27 platform declaration(s) and 6 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

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

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

AX2 · Stateful singletons1.0 / 10Critical✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `ErrorWindow` is not registered, but `YamlLoader` creates it and keeps it in the static `_errorWindow`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_message; e.g. `_message` at line 26). — src/Whim.Yaml/ErrorWindow.xaml.cs:10
  • `Logger` is not registered, but the singleton `Context` creates it and keeps it in `Logger`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_loggerConfiguration, _logger; e.g. `_loggerConfiguration` at line 49). — src/Whim/Logging/Logger.cs:10
  • `FilterManager` is not registered, but the singleton `Context` creates it and keeps it in `FilterManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_filters, _ignoreWindowClasses, _ignoreProcessFileNames, _ignoreTitles; e.g. `_filters` at line 21). — src/Whim/Filter/FilterManager.cs:6
  • `PluginManager` is not registered, but the singleton `Context` creates it and keeps it in `PluginManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_plugins; e.g. `_plugins` at line 107). — src/Whim/Plugin/PluginManager.cs:7
  • `KeybindManager` is not registered, but the singleton `Context` creates it and keeps it in `KeybindManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_uniqueKeyModifiers, _commandsKeybindsMap, _keybindsCommandsMap; e.g. `_uniqueKeyModifiers` at line 19). — src/Whim/Keybind/KeybindManager.cs:5
  • `NotificationManager` is not registered, but the singleton `Context` creates it and keeps it in `NotificationManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_initialized, _notificationHandlers; e.g. `_initialized` at line 21). — src/Whim/Notification/NotificationManager.cs:5
  • `CoreSavedStateManager` is not registered, but the singleton `InternalContext` creates it and keeps it in `CoreSavedStateManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (SavedState; e.g. `SavedState` at line 34). — src/Whim/Context/CoreSavedStateManager.cs:6
  • `KeybindHook` is not registered, but the singleton `InternalContext` creates it and keeps it in `KeybindHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_unhookKeyboardHook; e.g. `_unhookKeyboardHook` at line 29). — src/Whim/Keybind/KeybindHook.cs:11
  • `MouseHook` is not registered, but the singleton `InternalContext` creates it and keeps it in `MouseHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_unhookMouseHook; e.g. `_unhookMouseHook` at line 29). — src/Whim/Native/MouseHook.cs:9
  • `MutableRootSector` is not registered, but the singleton `RootSector` creates it and keeps it in `MutableRootSector`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_dispatchEventsScheduled; e.g. `_dispatchEventsScheduled` at line 54). — src/Whim/Store/RootSector/MutableRootSector.cs:3
  • `WorkspaceSector` is not registered, but the singleton `MutableRootSector` creates it and keeps it in `WorkspaceSector`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (WindowHandleToFocus; e.g. `WindowHandleToFocus` at line 155). — src/Whim/Store/WorkspaceSector/WorkspaceSector.cs:17
  • `Engine` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_context; e.g. `_context` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Whim/Engine.cs:6
  • `YamlLoader` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_errorWindow; e.g. `_errorWindow` at line 115). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Whim.Yaml/YamlLoader.cs:13

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

AX6 · Interface segregation9.7 / 10Exemplary✓ Tool-verified

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

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IContext` declares 19 members: `Logger`, `UncaughtExceptionHandling`, `ResourceManager`, `RouterManager`, `FilterManager`, `CommandManager`, `KeybindManager`, `PluginManager`, `NativeManager`, `FileManager`, `NotificationManager`, `Store`, `WindowProcessorManager`, `Initialize`, `HandleUncaughtException`, `CreateWindow`, `Exiting`, `Exited`, `Exit`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Whim/Context/IContext.cs:28
  • `ILayoutEngine` declares 17 members: `Name`, `Count`, `Identity`, `AddWindow`, `MoveWindowToPoint`, `RemoveWindow`, `MinimizeWindowStart`, `MinimizeWindowEnd`, `ContainsWindow`, `DoLayout`, `GetFirstWindow`, `FocusWindowInDirection`, `SwapWindowInDirection`, `MoveWindowEdgesInDirection`, `PerformCustomAction`, `GetLayoutEngine`, `ContainsEqual`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Whim/Layout/ILayoutEngine.cs:22
  • `INativeManager` declares 24 members: `QuitWindow`, `ForceForegroundWindow`, `HideWindow`, `ShowWindowMaximized`, `ShowWindowMinimized`, `MinimizeWindow`, `ShowWindowNoActivate`, `RestoreWindow`, `GetClassName`, `HideCaptionButtons`, `PreventWindowActivation`, `GetWindowOffset`, `DwmGetWindowRectangle`, `SetWindowCorners`, `DeferWindowPos`, `DeferWindowPos`, `GetUwpAppProcessPath`, `Compositor`, `ShouldSystemUseDarkMode`, `CreateTransparentWindowController`, `SetWindowExTransparent`, `RemoveWindowExTransparent`, `TryEnqueue`, `GetWhimVersion`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Whim/Native/INativeManager.cs:11
  • `IWindow` declares 20 members: `Handle`, `Title`, `WindowClass`, `IsUwp`, `Rectangle`, `ProcessId`, `ProcessFileName`, `ProcessFilePath`, `IsFocused`, `IsMinimized`, `IsMaximized`, `Focus`, `Hide`, `ShowNormal`, `ShowMaximized`, `ShowMinimized`, `Restore`, `BringToTop`, `Close`, `GetIcon`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Whim/Window/IWindow.cs:8

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

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

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

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — src/Whim.LayoutPreview/NonNegativeValueConverter.cs:19

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

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

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). — src/Whim.Runner/App.xaml.cs:26

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.
M1 · Documentation (README)6.8 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P2 · Observability7.8 / 10Strong✓ Tool-verified

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

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

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:19

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

  • Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

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

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness1.8 / 10Critical✓ 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.

  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×4) — src/Whim/ConfigLoader/ConfigLoader.cs:105, src/Whim/Store/Store.cs:60, src/Whim/Store/Store.cs:98, …
  • `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. — src/Whim.Updater/UpdaterPlugin.cs:94

What to do

  • Sync-over-async (deadlock risk) through `.Result`
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness6.1 / 10Adequate✓ Tool-verified

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. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `NotificationManager` declares a finalizer (line 83), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Whim/Notification/NotificationManager.cs:83
  • `Store` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_lock` itself (line 18), which makes that instance its own. But `_lock` is named in none of the methods the disposal search covered: `Dispose` (line 144), `Dispose` (line 162), `Dispose` (line 144), `Dispose` (line 162) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_lock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Whim/Store/Store.cs:18
  • `WindowMessageMonitor` declares a finalizer (line 146), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — src/Whim/WindowMessage/WindowMessageMonitor.cs:146

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

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

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — src/Whim/Context/CoreSavedStateManager.cs:63

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types9.6 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • ~0.5 `!` suppressions per 1k syntax nodes — 45 suppression(s) across the 81932 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

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

LensScoreRatingImpact
Code Health55.2Adequate — gated by X1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture71.9Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity55.6Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness63.2Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security67.7Adequate — gated by D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 53 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • 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
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — 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
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 5 candidate(s) found and not reported.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 43 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (32 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 33 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · AnalyzerSeverityNone · ×4
  • AnalyzerSeverityNone .editorconfig:237 — CA1014 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:240 — IDE0130 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:264 — IDE0055 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
  • AnalyzerSeverityNone .editorconfig:267 — IDE0060 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
D17 · Explicit Debt · EmptyCatchBlock · ×1
  • EmptyCatchBlock src/Whim/Context/CoreSavedStateManager.cs:63 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D17 · Explicit Debt · NoWarnInCsproj · ×1
  • NoWarnInCsproj src/Directory.Build.props:6 — EnableGenerateDocumentationFile — 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.
D17 · Explicit Debt · NoWarnInCsproj repeated across 13 files · ×1
  • NoWarnInCsproj repeated across 13 files src/Whim.Bar.Tests/Directory.Build.props:4 — The identical NoWarnInCsproj (`CS1591`) appears in 13 files (13 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 13 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 76 finding(s)
AX2 · Stateful singletons · Stateful shared instance · ×11
  • Stateful shared instance: ErrorWindow src/Whim.Yaml/ErrorWindow.xaml.cs:10 — `ErrorWindow` is not registered, but `YamlLoader` creates it and keeps it in the static `_errorWindow`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_message; e.g. `_message` at line 26).
  • Stateful shared instance: Logger src/Whim/Logging/Logger.cs:10 — `Logger` is not registered, but the singleton `Context` creates it and keeps it in `Logger`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_loggerConfiguration, _logger; e.g. `_loggerConfiguration` at line 49).
  • Stateful shared instance: FilterManager src/Whim/Filter/FilterManager.cs:6 — `FilterManager` is not registered, but the singleton `Context` creates it and keeps it in `FilterManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_filters, _ignoreWindowClasses, _ignoreProcessFileNames, _ignoreTitles; e.g. `_filters` at line 21).
  • Stateful shared instance: PluginManager src/Whim/Plugin/PluginManager.cs:7 — `PluginManager` is not registered, but the singleton `Context` creates it and keeps it in `PluginManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_plugins; e.g. `_plugins` at line 107).
  • Stateful shared instance: KeybindManager src/Whim/Keybind/KeybindManager.cs:5 — `KeybindManager` is not registered, but the singleton `Context` creates it and keeps it in `KeybindManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_uniqueKeyModifiers, _commandsKeybindsMap, _keybindsCommandsMap; e.g. `_uniqueKeyModifiers` at line 19).
  • Stateful shared instance: NotificationManager src/Whim/Notification/NotificationManager.cs:5 — `NotificationManager` is not registered, but the singleton `Context` creates it and keeps it in `NotificationManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_initialized, _notificationHandlers; e.g. `_initialized` at line 21).
  • Stateful shared instance: CoreSavedStateManager src/Whim/Context/CoreSavedStateManager.cs:6 — `CoreSavedStateManager` is not registered, but the singleton `InternalContext` creates it and keeps it in `CoreSavedStateManager`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (SavedState; e.g. `SavedState` at line 34).
  • Stateful shared instance: KeybindHook src/Whim/Keybind/KeybindHook.cs:11 — `KeybindHook` is not registered, but the singleton `InternalContext` creates it and keeps it in `KeybindHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_unhookKeyboardHook; e.g. `_unhookKeyboardHook` at line 29).
  • Stateful shared instance: MouseHook src/Whim/Native/MouseHook.cs:9 — `MouseHook` is not registered, but the singleton `InternalContext` creates it and keeps it in `MouseHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_unhookMouseHook; e.g. `_unhookMouseHook` at line 29).
  • Stateful shared instance: MutableRootSector src/Whim/Store/RootSector/MutableRootSector.cs:3 — `MutableRootSector` is not registered, but the singleton `RootSector` creates it and keeps it in `MutableRootSector`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_dispatchEventsScheduled; e.g. `_dispatchEventsScheduled` at line 54).
  • Stateful shared instance: WorkspaceSector src/Whim/Store/WorkspaceSector/WorkspaceSector.cs:17 — `WorkspaceSector` is not registered, but the singleton `MutableRootSector` creates it and keeps it in `WorkspaceSector`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (WindowHandleToFocus; e.g. `WindowHandleToFocus` at line 155).
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×4
  • Sync-over-async (deadlock risk) through `.Result` src/Whim/ConfigLoader/ConfigLoader.cs:105 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Whim/Store/Store.cs:60 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Whim/Store/Store.cs:98 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` src/Whim/Store/Store.cs:124 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) src/Whim/Store/MapSector/Transforms/MoveWindowToAdjacentMonitorTransform.cs:15 — src/Whim/Store/MapSector/Transforms/MoveWindowToAdjacentMonitorTransform.cs:15-25 | src/Whim/Store/MapSector/Transforms/MoveWindowToMonitorIndexTransform.cs:15-24 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Whim.CommandPalette/Filters/CamelCase.cs:185 — src/Whim.CommandPalette/Filters/CamelCase.cs:185-196 | src/Whim.CommandPalette/Filters/Words.cs:97-106 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) src/Whim/Native/CoreNativeManager.cs:88 — src/Whim/Native/CoreNativeManager.cs:88-97 | src/Whim/Native/NativeManager.cs:88-97 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AX2 · Stateful singletons · Process-global static state · ×2
  • Process-global static state: Engine src/Whim/Engine.cs:6 — `Engine` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_context; e.g. `_context` at line 16). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
  • Process-global static state: YamlLoader src/Whim.Yaml/YamlLoader.cs:13 — `YamlLoader` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_errorWindow; e.g. `_errorWindow` at line 115). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: CoreNativeManager src/Whim/Native/CoreNativeManager.cs — TooManyMethods — 174 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Pickers src/Whim/Store/WorkspaceSector/WorkspacePickers.cs — TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods, declared across 4 files: WorkspaceSector/WorkspacePickers.cs (19), MapSector/MapPickers.cs (11), MonitorSector/MonitorPickers.cs (8), WindowSector/WindowPickers.cs (3). The bar is 30 methods; this is 11 over it, 1.37× the bar. 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:251 — src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:251-284 | src/Whim.CommandPalette/Variants/Select/SelectVariantViewModel.cs:224-260 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) src/Whim.CommandPalette/Filters/CamelCase.cs:60 — src/Whim.CommandPalette/Filters/CamelCase.cs:60-93 | src/Whim.CommandPalette/Filters/Words.cs:53-94 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) src/Whim/Keybind/KeyModifiers.cs:76 — src/Whim/Keybind/KeyModifiers.cs:76-97 | src/Whim/Keybind/KeyModifiers.cs:100-137 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) src/Whim/Store/WindowSector/Transforms/WindowMovedTransform.cs:10 — src/Whim/Store/WindowSector/Transforms/WindowMovedTransform.cs:10-34 | src/Whim/Store/WindowSector/Transforms/WindowMoveStartedTransform.cs:10-31 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) src/Whim/Layout/FocusLayoutEngine.cs:188 — src/Whim/Layout/FocusLayoutEngine.cs:188-208 | src/Whim/Layout/FocusLayoutEngine.cs:212-235 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) src/Whim/Store/Store.cs:95 — src/Whim/Store/Store.cs:95-116 | src/Whim/Store/Store.cs:121-141 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) src/Whim.FloatingWindow/FloatingWindowPlugin.cs:46 — src/Whim.FloatingWindow/FloatingWindowPlugin.cs:46-63 | src/Whim.FloatingWindow/FloatingWindowPlugin.cs:67-86 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:277 — src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:277-294 | src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:298-315 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×2
  • Edited copy of a member (13 corresponding lines) src/Whim/Store/WindowSector/Transforms/WindowMinimizeEndedTransform.cs:10 — src/Whim/Store/WindowSector/Transforms/WindowMinimizeEndedTransform.cs:10-23 | src/Whim/Store/WindowSector/Transforms/WindowMinimizeStartedTransform.cs:10-22 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) src/Whim/Router/RouterManager.cs:70 — src/Whim/Router/RouterManager.cs:70-82 | src/Whim/Router/RouterManager.cs:147-159 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
X18 · Disposal-pattern correctness · Finalizer on a type that owns no unmanaged resource · ×2
  • Finalizer on a type that owns no unmanaged resource src/Whim/Notification/NotificationManager.cs:83 — `NotificationManager` declares a finalizer (line 83), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
  • Finalizer on a type that owns no unmanaged resource src/Whim/WindowMessage/WindowMessageMonitor.cs:146 — `WindowMessageMonitor` declares a finalizer (line 146), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
D12 · Dependency Hygiene · Deprecated · ×1
  • Deprecated: xunit Directory.Packages.props:32 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
D17 · Explicit Debt · BareSuppressMessage repeated across 18 files · ×1
  • BareSuppressMessage repeated across 18 files src/Whim.Bar.Tests/GlobalSuppressions.cs:11 — The identical BareSuppressMessage (`SuppressMessage`) appears in 18 files (129 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 129 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D17 · Explicit Debt · ObsoleteWithCallers · ×1
  • ObsoleteWithCallers src/Whim/Keybind/IKeybind.cs:38 — [Obsolete] Modifiers
D17 · Explicit Debt · BareSuppressMessage · ×1
  • BareSuppressMessage src/Whim/Monitor/MonitorEnumCallback.cs:7 — 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment src/Whim/Store/MonitorSector/Transforms/MonitorsChangedTransform.cs:166 — // Hack to only accept window events after Windows has been given a chance to stop moving — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · TreeHelpers.GetNodeContainingPoint (cognitive 26) · ×1
  • TreeHelpers.GetNodeContainingPoint (cognitive 26) src/Whim.TreeLayout/Tree/TreeHelpers.cs:165 — TreeHelpers.GetNodeContainingPoint 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.
D2 · Cognitive Complexity · AreaHelpers.Prune (cognitive 21) · ×1
  • AreaHelpers.Prune (cognitive 21) src/Whim.SliceLayout/AreaHelpers.cs:15 — AreaHelpers.Prune has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MonitorsChangedTransform.UpdateMapSector (cognitive 18) · ×1
  • MonitorsChangedTransform.UpdateMapSector (cognitive 18) src/Whim/Store/MonitorSector/Transforms/MonitorsChangedTransform.cs:97 — MonitorsChangedTransform.UpdateMapSector has cognitive complexity 18 (threshold 15). Of this number, 17 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.
D2 · Cognitive Complexity · GapsLayoutEngine.DoLayout (cognitive 16) · ×1
  • GapsLayoutEngine.DoLayout (cognitive 16) src/Whim.Gaps/GapsLayoutEngine.cs:44 — GapsLayoutEngine.DoLayout 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.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: CoreCommands.CoreCommands(…) src/Whim/Commands/CoreCommands.cs:14 — MethodTooLong — CoreCommands(…) runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: TreeLayoutEngine src/Whim.TreeLayout/TreeLayoutEngine.cs — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 2 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: Workspace.cs → BaseProxyLayoutEngine.cs, CoreNativeManager.cs, ICoreNativeManager.cs src/Whim/Workspace/Workspace.cs — `src/Whim/Workspace/Workspace.cs` changes together with 3 other files — `src/Whim/Layout/BaseProxyLayoutEngine.cs`, `src/Whim/Native/CoreNativeManager.cs`, `src/Whim/Native/ICoreNativeManager.cs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: BaseProxyLayoutEngine.cs ↔ IWorkspace.cs src/Whim/Layout/BaseProxyLayoutEngine.cs:1 — `src/Whim/Layout/BaseProxyLayoutEngine.cs` and `src/Whim/Workspace/IWorkspace.cs` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `18bbcb1f` Let `ILayoutEngine`s perform custom actions (#736); `85afb4a4` `MoveWindowEdgesInDirection` now takes in coordinates in the unit squ…; `4da0f87a` Refactor Workspace to remove accidental overloading (#308) (at that commit the file was still `src/Whim/Layout/ProxyLayoutEngine.cs`) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) src/Whim/Commands/CoreCommands.cs:352 — src/Whim/Commands/CoreCommands.cs:352-376 | src/Whim/Commands/CoreCommands.cs:379-408 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:147 — src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:147-176 | src/Whim.CommandPalette/Variants/Select/SelectVariantViewModel.cs:137-171 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:88 — src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:88-116 | src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:124-146 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) src/Whim.TreeLayout/Tree/SplitNode.cs:112 — src/Whim.TreeLayout/Tree/SplitNode.cs:112-152 | src/Whim.TreeLayout/Tree/SplitNode.cs:155-166 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) src/Whim.SliceLayout/SliceLayoutEngine.cs:162 — src/Whim.SliceLayout/SliceLayoutEngine.cs:162-185 | src/Whim.SliceLayout/SliceLayoutEngine.cs:188-207 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×1
  • Edited copy of a member (17 corresponding lines) src/Whim.TreeLayout/TreeLayoutPlugin.cs:48 — src/Whim.TreeLayout/TreeLayoutPlugin.cs:48-64 | src/Whim.TreeLayout/TreeLayoutPlugin.cs:80-96 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) src/Whim/Router/RouterManager.cs:25 — src/Whim/Router/RouterManager.cs:25-37 | src/Whim/Router/RouterManager.cs:55-67 | src/Whim/Router/RouterManager.cs:85-97 | src/Whim/Router/RouterManager.cs:132-144 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) src/Whim/Store/MapSector/MapSector.cs:27 — src/Whim/Store/MapSector/MapSector.cs:27-48 | src/Whim/Store/MonitorSector/MonitorSector.cs:30-44 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) src/Whim/Keybind/KeybindHook.cs:38 — src/Whim/Keybind/KeybindHook.cs:38-48 | src/Whim/Native/MouseHook.cs:38-48 | src/Whim/WindowMessage/WindowMessageMonitor.cs:55-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) src/Whim.CommandPalette/Variants/Menu/MenuVariantRowViewModel.cs:15 — src/Whim.CommandPalette/Variants/Menu/MenuVariantRowViewModel.cs:15-19 | src/Whim.CommandPalette/Variants/Select/SelectVariantRowViewModel.cs:40-44 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/Whim/Commands/CoreCommands.cs:354 — src/Whim/Commands/CoreCommands.cs:354-372 | src/Whim/Commands/CoreCommands.cs:386-404 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) src/Whim/Layout/FocusLayoutEngine.cs:191 — src/Whim/Layout/FocusLayoutEngine.cs:191-204 | src/Whim/Layout/FocusLayoutEngine.cs:215-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) src/Whim/Store/MapSector/Transforms/MoveWindowEdgesInDirectionTransform.cs:38 — src/Whim/Store/MapSector/Transforms/MoveWindowEdgesInDirectionTransform.cs:38-49 | src/Whim/Store/MapSector/Transforms/MoveWindowToMonitorTransform.cs:26-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) src/Whim/Store/MapSector/Transforms/MoveWindowEdgesInDirectionTransform.cs:25 — src/Whim/Store/MapSector/Transforms/MoveWindowEdgesInDirectionTransform.cs:25-35 | src/Whim/Store/MapSector/Transforms/MoveWindowToAdjacentWorkspaceTransform.cs:23-33 | src/Whim/Store/MapSector/Transforms/MoveWindowToWorkspaceTransform.cs:24-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Whim/Store/MapSector/Transforms/MoveWindowToWorkspaceTransform.cs:36` calls `Debug` and `src/Whim/Store/MapSector/Transforms/MoveWindowEdgesInDirectionTransform.cs:38` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: Whim src/Whim/Whim.csproj:1 — Whim: abstractness 0.23, instability 0.00, distance 0.77 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: CoreNativeManager (LCOM4 13) src/Whim/Native/CoreNativeManager.cs:15 — CoreNativeManager's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
GD1 · Unfinished & placeholder code · Unfinished stub · ×1
  • Unfinished stub — throws NotImplementedException src/Whim.LayoutPreview/NonNegativeValueConverter.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
X1 · Async correctness · async void method · ×1
  • async void method: Timer_Elapsed src/Whim.Updater/UpdaterPlugin.cs:94 — `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.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1
  • Owned disposable field is never released src/Whim/Store/Store.cs:18 — `Store` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_lock` itself (line 18), which makes that instance its own. But `_lock` is named in none of the methods the disposal search covered: `Dispose` (line 144), `Dispose` (line 162), `Dispose` (line 144), `Dispose` (line 162) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_lock?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) src/Whim/Context/CoreSavedStateManager.cs:63 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Minor — 179 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×101
  • Orphaned file src/Whim.TreeLayout/Tree/TreeHelpers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.SliceLayout/SliceLayouts.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Commands/CoreCommands.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Store/MapSector/MapPickers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Store/WorkspaceSector/WorkspacePickers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Native/CoreNativeManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.SliceLayout/SliceLayoutEngine.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Native/NativeManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.SliceLayout/AreaHelpers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.Yaml/YamlPluginLoader.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.CommandPalette/CommandPaletteCommands.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.CommandPalette/Variants/Menu/MenuVariantViewModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.Yaml/YamlLoader.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Layout/FocusLayoutEngine.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Store/WindowSector/WindowEventListener.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.CommandPalette/Variants/Select/SelectVariantViewModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Layout/ILayoutEngine.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Logging/Logger.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim.TreeLayout/Tree/SplitNode.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Native/WindowBackdropController.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Native/DeferWindowPosHandle.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Utils/Result.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Store/MonitorSector/MonitorPickers.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/Whim/Store/WorkspaceSector/WorkspaceSector.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 76 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×49
  • redundant comment src/Whim.Bar.Tests/ActiveLayout/ActiveLayoutWidgetViewModelTests.cs:224 — "WHEN attempting to set a new layout engine" repeats the code it sits on: 4 of its 5 words (set, new, layout, engine) are already in `sut.ActiveLayoutEngine = "NewLayout";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.CommandPalette/CommandPalettePlugin.cs:118 — "Get the activation config from the state." repeats the code it sits on: 4 of its 4 words (get, activation, config, state) are already in `if (state.TryGetProperty("activationConfig", out JsonElement activationConfig))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.CommandPalette/CommandPaletteWindow.xaml.cs:44 — "Focus the text box." repeats the code it sits on: 3 of its 3 words (focus, text, box) are already in `TextEntry.Focus(FocusState.Programmatic);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.FloatingWindow.Tests/ProxyFloatingLayoutEngineTests.cs:104 — "GIVEN a floating window which we add to the engine" repeats the code it sits on: 4 of its 5 words (floating, window, add, engine) are already in `IWindow window = ProxyFloatingLayoutEngineUtils.SetupUpdateInner(ctx, root);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.FloatingWindow/FloatingUtils.cs:38 — "Try get the old rectangle." repeats the code it sits on: 4 of its 4 words (try, get, old, rectangle) are already in `IRectangle<double>? oldRectangle = dict.TryGetValue(window, out IRectangle<double>? rectangle)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:107 — "If the window is floating, update the rectangle and return." repeats the code it sits on: 4 of its 5 words (window, floating, update, rectangle) are already in `(ProxyFloatingLayoutEngine newEngine, bool error) = UpdateWindowRectangle(window);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:137 — "If the window is floating, update the rectangle and return." repeats the code it sits on: 4 of its 5 words (window, floating, update, rectangle) are already in `(ProxyFloatingLayoutEngine newEngine, bool error) = UpdateWindowRectangle(window);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.FloatingWindow/ProxyFloatingLayoutEngine.cs:227 — "Iterate over all windows in the inner layout engine." repeats the code it sits on: 5 of its 5 words (iterate, windows, inner, layout, engine) are already in `foreach (IWindowState windowState in InnerLayoutEngine.DoLayout(rectangle, monitor))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.SliceLayout.Tests/AreaHelpers/SetStartIndexesTests.cs:154 — "When the slice areas are set up" repeats the code it sits on: 3 of its 3 words (slice, areas, set) are already in `(ParentArea resultingParentArea, BaseSliceArea[] sliceAreas) = parentArea.SetStartIndexes();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.SliceLayout/AreaHelpers.cs:107 — "Replace the last slice area with an overflow area." repeats the code it sits on: 4 of its 5 words (last, slice, area, overflow) are already in `Logger.Error($"No overflow area found, replacing last slice area with overflow area");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.SliceLayout/AreaHelpers.cs:176 — "Sort the areas by order." repeats the code it sits on: 3 of its 3 words (sort, areas, order) are already in `sliceAreas.Sort((a, b) => a.Order.CompareTo(b.Order));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Filter/FilterManagerTests.cs:73 — "When the filter manager is cleared" repeats the code it sits on: 3 of its 3 words (filter, manager, cleared) are already in `filterManager.Clear();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Native/DeferWindowPosHandleTests.cs:42 — "Givenn GetWindowOffset returns null" repeats the code it sits on: 5 of its 6 words (get, window, offset, returns, null) are already in `ctx.NativeManager.GetWindowOffset(Arg.Any<HWND>()).ReturnsNull();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MapSector/MapPickersTests.cs:278 — "Given we have a monitor with an active layout engine" repeats the code it sits on: 4 of its 5 words (monitor, active, layout, engine) are already in `IMonitor monitor = CreateMonitor((HMONITOR)1);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MapSector/MapPickersTests.cs:404 — "Given we have a workspace and target monitor that is valid for it" repeats the code it sits on: 4 of its 5 words (workspace, target, monitor, valid) are already in `var workspace = CreateWorkspace();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MapSector/Transforms/ActivateWorkspaceTransformTests.cs:75 — "Given the workspace is already activated on the monitor" repeats the code it sits on: 4 of its 5 words (workspace, already, activated, monitor) are already in `Workspace workspace = CreateWorkspace();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MapSector/Transforms/InitializeWorkspacesTransformTests.cs:259 — "- the WorkspaceSector has initialized" repeats the code it sits on: 3 of its 3 words (workspace, sector, initialized) are already in `Assert.True(rootSector.WorkspaceSector.HasInitialized);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorEventListenerTests.cs:49 — "When WindowMessageMonitor.DisplayChanged is triggered" repeats the code it sits on: 5 of its 6 words (window, message, monitor, display, changed) are already in `internalCtx.WindowMessageMonitor.DisplayChanged += Raise.Event<EventHandler<WindowMessageMonitorEventArgs>>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorEventListenerTests.cs:66 — "When WindowMessageMonitor.WorkAreaChanged is triggered" repeats the code it sits on: 6 of its 7 words (window, message, monitor, work, area, changed) are already in `internalCtx.WindowMessageMonitor.WorkAreaChanged += Raise.Event<EventHandler<WindowMessageMonitorEventArgs>>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorEventListenerTests.cs:83 — "When WindowMessageMonitor.DpiChanged is triggered" repeats the code it sits on: 5 of its 6 words (window, message, monitor, dpi, changed) are already in `internalCtx.WindowMessageMonitor.DpiChanged += Raise.Event<EventHandler<WindowMessageMonitorEventArgs>>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorEventListenerTests.cs:102 — "When WindowMessageMonitor.SessionChanged is triggered" repeats the code it sits on: 5 of its 6 words (window, message, monitor, session, changed) are already in `internalCtx.WindowMessageMonitor.SessionChanged += Raise.Event<EventHandler<WindowMessageMonitorEventArgs>>(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorUtilsTests.cs:63 — "When we get the current monitors" repeats the code it sits on: 3 of its 3 words (get, current, monitors) are already in `ImmutableArray<IMonitor> monitors = MonitorUtils.GetCurrentMonitors(internalCtx);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/MonitorSector/MonitorUtilsTests.cs:79 — "When we get the current monitors" repeats the code it sits on: 3 of its 3 words (get, current, monitors) are already in `ImmutableArray<IMonitor> monitors = MonitorUtils.GetCurrentMonitors(internalCtx);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/Root/MutableRootSectorTests.cs:53 — "Given queued events in the monitor sector" repeats the code it sits on: 4 of its 5 words (queued, events, monitor, sector) are already in `rootSector.MonitorSector.QueueEvent(new EventArgs());`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment src/Whim.Tests/Store/Root/MutableRootSectorTests.cs:66 — "Given queued events in the window sector" repeats the code it sits on: 4 of its 5 words (queued, events, window, sector) are already in `rootSector.WindowSector.QueueEvent(new EventArgs());`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • + 24 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×4
  • Fat interface: IContext (19 members) src/Whim/Context/IContext.cs:28 — `IContext` declares 19 members: `Logger`, `UncaughtExceptionHandling`, `ResourceManager`, `RouterManager`, `FilterManager`, `CommandManager`, `KeybindManager`, `PluginManager`, `NativeManager`, `FileManager`, `NotificationManager`, `Store`, `WindowProcessorManager`, `Initialize`, `HandleUncaughtException`, `CreateWindow`, `Exiting`, `Exited`, `Exit`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ILayoutEngine (17 members) src/Whim/Layout/ILayoutEngine.cs:22 — `ILayoutEngine` declares 17 members: `Name`, `Count`, `Identity`, `AddWindow`, `MoveWindowToPoint`, `RemoveWindow`, `MinimizeWindowStart`, `MinimizeWindowEnd`, `ContainsWindow`, `DoLayout`, `GetFirstWindow`, `FocusWindowInDirection`, `SwapWindowInDirection`, `MoveWindowEdgesInDirection`, `PerformCustomAction`, `GetLayoutEngine`, `ContainsEqual`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: INativeManager (24 members) src/Whim/Native/INativeManager.cs:11 — `INativeManager` declares 24 members: `QuitWindow`, `ForceForegroundWindow`, `HideWindow`, `ShowWindowMaximized`, `ShowWindowMinimized`, `MinimizeWindow`, `ShowWindowNoActivate`, `RestoreWindow`, `GetClassName`, `HideCaptionButtons`, `PreventWindowActivation`, `GetWindowOffset`, `DwmGetWindowRectangle`, `SetWindowCorners`, `DeferWindowPos`, `DeferWindowPos`, `GetUwpAppProcessPath`, `Compositor`, `ShouldSystemUseDarkMode`, `CreateTransparentWindowController`, `SetWindowExTransparent`, `RemoveWindowExTransparent`, `TryEnqueue`, `GetWhimVersion`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IWindow (20 members) src/Whim/Window/IWindow.cs:8 — `IWindow` declares 20 members: `Handle`, `Title`, `WindowClass`, `IsUwp`, `Rectangle`, `ProcessId`, `ProcessFileName`, `ProcessFilePath`, `IsFocused`, `IsMinimized`, `IsMaximized`, `Focus`, `Hide`, `ShowNormal`, `ShowMaximized`, `ShowMinimized`, `Restore`, `BringToTop`, `Close`, `GetIcon`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
X7 · Silent fallback defaults · Silent fallback default on unknown code · ×3
  • Silent fallback default on unknown code src/Whim.Updater/Version.cs:95 — `GetVersionFromMatch` maps every unrecognised code to `ReleaseChannel.Stable`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/Whim.Yaml/YamlLayoutEngineLoader.cs:160 — `CreateTreeLayoutEngineCreator` maps every unrecognised code to `Direction.Right`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
  • Silent fallback default on unknown code src/Whim.Yaml/YamlLoaderUtils.cs:34 — `ParseBackdropType` maps every unrecognised code to `BackdropType.None`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×2
  • ObsoleteWithoutCallers src/Whim.Tests/Keybind/KeyModifiersTests.cs:75 — [Obsolete] UnifyModifiers
  • ObsoleteWithoutCallers src/Whim.Tests/Keybind/KeybindTests.cs:110 — [Obsolete] Keybind_FromString
D34 · Knowledge Freshness · Most significant orphaned file · ×2
  • Most significant orphaned file src/Whim/Native/ICoreNativeManager.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file src/Whim.TreeLayout/TreeLayoutEngine.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
X10 · Duplicated predicate · Duplicated predicate · ×2
  • Duplicated predicate src/Whim/Window/Window.cs:176 — `obj == null || GetType() != obj.GetType()` appears character-identically in 2 files — src/Whim/Window/Window.cs, src/Whim/Window/WindowState.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/Whim/Store/WindowSector/Transforms/WindowMovedTransform.cs:19 — `windowSector.IsLeftMouseButtonDown && internalCtx.CoreNativeManager.GetCursorPos(out IPoint<int> point)` appears character-identically in 2 files — src/Whim/Store/WindowSector/Transforms/WindowMoveStartedTransform.cs, src/Whim/Store/WindowSector/Transforms/WindowMovedTransform.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: coverlet.collector Directory.Packages.props:27 — coverlet.collector 6.0.4 → 10.1.1 available (referenced by Whim.Tests).
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found src/Whim.Runner/Whim.Runner.csproj:25 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/Whim.Runner/Whim.Runner.csproj` makes this repository a deployable product (line 25).
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion src/Whim/Whim.csproj:1 — `Whim` overshoots its size bounds (14180 LoC, 165 public types across 6 namespaces). 1 of 27 project(s) overshoot their size bounds, lowering Project Cohesion to 9.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 103 of 103 significant files have no living knowledge — the codebase as a whole is dormant, not 103 separate risks. Counted over 103 of the 328 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
IC1 · Incompleteness & stubs · Commented-out code · ×1
  • Commented-out code src/Whim.Runner/App.xaml.cs:26 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
M2 · Architecture documentation · No ADRs · ×1
  • 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:19 — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~0.5 `!` suppressions per 1k syntax nodes — 45 suppression(s) across the 81932 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch src/Whim.Yaml/YamlLoaderUtils.cs:94 — `ParseHex` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Minor — 43 finding(s)
D24 · Comment Value · doc comments repeat the names · ×17
  • doc comments repeat the names src/Whim/Commands/CommandManager.cs:11 — 18 of 542 documented parameters and 45 of 888 summaries in `Whim` only repeat the member or parameter name (e.g. "Add a command from a plugin." for `AddPluginCommand`). 271 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.Bar/BarWindow.xaml.cs:15 — 0 of 48 documented parameters and 4 of 81 summaries in `Whim.Bar` only repeat the member or parameter name (e.g. "The current window state." for `WindowState`). 34 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.CommandPalette/CommandPaletteCommands.cs:237 — 2 of 46 documented parameters and 3 of 137 summaries in `Whim.CommandPalette` only repeat the member or parameter name (e.g. "Move window to workspace command creator." for `MoveWindowToWorkspaceCommandCreator`). 27 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.FloatingWindow/IFloatingWindowPlugin.cs:11 — 1 of 13 documented parameters and 3 of 16 summaries in `Whim.FloatingWindow` only repeat the member or parameter name (e.g. "The floating windows." for `FloatingWindows`). 9 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.FloatingWindow.Tests/ProxyFloatingLayoutEngineTests.cs:13 — 0 of 8 documented parameters and 0 of 2 summaries in `Whim.FloatingWindow.Tests` only repeat the member or parameter name (e.g. "" for `ctx`). 8 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Whim.FocusIndicator/FocusIndicatorPlugin.cs:35 — 0 of 5 documented parameters and 0 of 18 summaries in `Whim.FocusIndicator` only repeat the member or parameter name (e.g. "" for `context`). 2 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.Gaps/GapsLayoutEngine.cs:17 — 0 of 6 documented parameters and 0 of 16 summaries in `Whim.Gaps` only repeat the member or parameter name (e.g. "" for `gapsConfig`). 6 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.LayoutPreview/LayoutPreviewWindow.xaml.cs:14 — 0 of 8 documented parameters and 1 of 11 summaries in `Whim.LayoutPreview` only repeat the member or parameter name (e.g. "The default title of the window." for `WindowTitle`). 4 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.Runner/ExceptionWindow.xaml.cs:22 — 0 of 2 documented parameters and 0 of 6 summaries in `Whim.Runner` only repeat the member or parameter name (e.g. "" for `app`). 2 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.SliceLayout/ISliceLayoutPlugin.cs:51 — 0 of 49 documented parameters and 3 of 48 summaries in `Whim.SliceLayout` only repeat the member or parameter name (e.g. "Promotes the given window in the stack." for `PromoteWindowInStack`). 37 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.TestUtils/Assert.cs:189 — 3 of 36 documented parameters and 0 of 39 summaries in `Whim.TestUtils` only repeat the member or parameter name (e.g. "The root sector." for `rootSector`). 16 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Whim.Tests/Store/MonitorSector/MonitorPickersTests.cs:178 — 0 of 11 documented parameters and 0 of 5 summaries in `Whim.Tests` only repeat the member or parameter name (e.g. "" for `root`). 9 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names src/Whim.TreeLayout/Tree/TreeHelpers.cs:8 — 8 of 74 documented parameters and 6 of 56 summaries in `Whim.TreeLayout` only repeat the member or parameter name (e.g. "The state of a node." for `NodeState`). 31 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.TreeLayout.Bar/TreeLayoutBarPlugin.cs:13 — 0 of 4 documented parameters and 0 of 10 summaries in `Whim.TreeLayout.Bar` only repeat the member or parameter name (e.g. "" for `plugin`). 4 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.TreeLayout.CommandPalette/TreeLayoutCommandPaletteCommands.cs:19 — 0 of 7 documented parameters and 0 of 3 summaries in `Whim.TreeLayout.CommandPalette` only repeat the member or parameter name (e.g. "" for `context`). 7 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.Updater/ReleaseManager.cs:122 — 0 of 11 documented parameters and 2 of 41 summaries in `Whim.Updater` only repeat the member or parameter name (e.g. "Gets the releases in the current that have not been installed." for `GetNotInstalledReleases`). 6 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
  • doc comments repeat the names src/Whim.Yaml/YamlLoaderUtils.cs:103 — 0 of 6 documented parameters and 0 of 8 summaries in `Whim.Yaml` only repeat the member or parameter name (e.g. "" for `str`). 1 documentation tag(s) are empty. This build requires documentation, so say what the name does not: units, ranges, null handling, side effects.
D12 · Dependency Hygiene · Outdated · ×16
  • Outdated: Microsoft.CodeAnalysis.Scripting — Microsoft.CodeAnalysis.Scripting 4.14.0 → 5.12.0 available (referenced by Whim).
  • Outdated: Microsoft.Win32.SystemEvents — Microsoft.Win32.SystemEvents 9.0.5 → 11.0.0 available (referenced by Whim).
  • Outdated: Microsoft.Windows.CsWin32 — Microsoft.Windows.CsWin32 0.3.183 → 0.3.371 available (referenced by Whim).
  • Outdated: Microsoft.Windows.SDK.BuildTools — Microsoft.Windows.SDK.BuildTools 10.0.26100.3916 → 10.0.28000.2957 available (referenced by Whim).
  • Outdated: Microsoft.WindowsAppSDK — Microsoft.WindowsAppSDK 1.7.250401001 → 2.6.5 available (referenced by Whim).
  • Outdated: Serilog — Serilog 4.3.0 → 4.4.0 available (referenced by Whim).
  • Outdated: System.Drawing.Common — System.Drawing.Common 9.0.5 → 11.0.0 available (referenced by Whim).
  • Outdated: FluentAssertions — FluentAssertions 8.2.0 → 8.11.0 available (referenced by Whim.Tests).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.13.0 → 18.12.0 available (referenced by Whim.Tests).
  • Outdated: NSubstitute — NSubstitute 5.3.0 → 6.2.0 available (referenced by Whim.Tests).
  • Outdated: xunit.analyzers — xunit.analyzers 1.20.0 → 2.3.0 available (referenced by Whim.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.0.2 → 4.0.1 available (referenced by Whim.Tests).
  • Outdated: Corvus.Json.ExtendedTypes — Corvus.Json.ExtendedTypes 4.3.9 → 5.8.11 available (referenced by Whim.Yaml).
  • Outdated: Corvus.Json.SourceGenerator — Corvus.Json.SourceGenerator 4.3.9 → 5.8.11 available (referenced by Whim.Yaml).
  • Outdated: Yaml2JsonNode — Yaml2JsonNode 2.2.0 → 3.1.0 available (referenced by Whim.Yaml).
  • Outdated: YamlDotNet — YamlDotNet 16.3.0 → 18.1.0 available (referenced by Whim.Yaml).
D10 · Test Quality · Mock framework · ×10
  • Mock framework: NSubstitute — Whim.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.CommandPalette.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.FloatingWindow.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.Gaps.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.TreeLayout.Bar.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.TestUtils references NSubstitute.
  • Mock framework: NSubstitute — Whim.Bar.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.SliceLayout.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.Updater.Tests references NSubstitute.
  • Mock framework: NSubstitute — Whim.Yaml.Tests references NSubstitute.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e4a3feacbde34c5b8525c6255c1a86d4/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=433" --report-format json --report-path /tmp/watchdog-gitleaks-e4a3feacbde34c5b8525c6255c1a86d4/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e4a3feacbde34c5b8525c6255c1a86d4/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .24artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan0—
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d95cda2b18a64e5ea938e75a6049daaf4artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 43 file(s) — `src/Whim.Bar/BarConfig.cs`, `src/Whim.Bar/BarPlugin.cs`, `src/Whim.CommandPalette/CommandPaletteCommands.cs`, `src/Whim.CommandPalette/ExecuteCommand.cs`, `src/Whim.CommandPalette/Variants/FreeText/FreeTextVariantViewModel.cs`, … (+38 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d95cda2b18a64e5ea938e75a6049daaf0artifacts/raw/osv-scanner.json

Run 01a1eb27-d191-7405-867f-fc4618e9ab1a · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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