Executive summary
ElektroStudios/Easy-Link-File-Viewer has a provisional result, because the code didn't build. Its score is held back in part because we found no recorded design decisions and no architecture document or diagram. It scores 66 out of 100, and the ratings may change once the code builds. None of its nine critical findings concern security.
Maturity, at 52, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 14 points. Fixing the 13 comments that repeat the code, or contradict it comes next, worth about 13 points. Raising Maturity to 70 would lift the score to about 75.
Nine errors are caught and ignored, so failures can go unnoticed. Handling or logging the ignored errors would close this risk.
The product code is 17,663 lines, about €26,000 to rebuild. The check for malicious packages couldn't finish, so that result is missing, not a clean pass.
If Maturity rose from 52 to 70, the lowest score rated Strong, the score would rise from 66 to about 75.
New since the last survey: 1 finding
- Cohesion (LCOM4) · Low cohesion: Form1 (LCOM4 6) Source/GUI/UI/Form1.vb
Fixed since the last survey: 3 findings
- Cohesion (LCOM4) · Low cohesion: Form1 (LCOM4 5) Source/GUI/UI/Form1.vb
- Code Coverage · No automated tests
- Churn × Complexity Hotspots · Hotspot: Source/Shared/DevCase/ShortcutFileInfo.vb Source/Shared/DevCase/ShortcutFileInfo.vb
Rebuild cost: about €26,000 · Estimate
| Cost to rebuild | €8,700 to €44,000, for 145 to 462 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, 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.9 at a score of 66. 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. |
| Size | Small: 17,663 lines of product code |
| What it is not | Not 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 DevCase.Core.Application.Console | 2 DevCase.Core.Application.Forms | 3 DevCase.Core.Application.Tools | 4 DevCase.Core.Application.UserInterface | 5 DevCase.Core.Design | 6 DevCase.Core.IO.Tools | 7 DevCase.Core.Imaging.Tools | 8 DevCase.Extensions.ContainerControlExtensions | 9 DevCase.Extensions.MenuStripExtensions | 10 DevCase.Extensions.ToolStripExtensions | 11 DevCase.Runtime.TypeConverters | 12 DevCase.UserControls.Controls | 13 DevCase.Win32.Delegates | 14 DevCase.Win32.Enums | 15 DevCase.Win32.Structures | 16 Microsoft.VisualBasic | 17 My | 18 DevCase.Core.Extensions | 19 DevCase.Core.IO | 20 DevCase.Extensions.ControlExtensions | 21 DevCase.UI.Dialogs | 22 DevCase.Win32.Interfaces | 23 (global) | 24 DevCase.Win32 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 DevCase.Core.Application.Console | ||||||||||||||||||||||||
| 2 DevCase.Core.Application.Forms | ||||||||||||||||||||||||
| 3 DevCase.Core.Application.Tools | ||||||||||||||||||||||||
| 4 DevCase.Core.Application.UserInterface | ||||||||||||||||||||||||
| 5 DevCase.Core.Design | ||||||||||||||||||||||||
| 6 DevCase.Core.IO.Tools | ||||||||||||||||||||||||
| 7 DevCase.Core.Imaging.Tools | ||||||||||||||||||||||||
| 8 DevCase.Extensions.ContainerControlExtensions | ||||||||||||||||||||||||
| 9 DevCase.Extensions.MenuStripExtensions | ||||||||||||||||||||||||
| 10 DevCase.Extensions.ToolStripExtensions | ||||||||||||||||||||||||
| 11 DevCase.Runtime.TypeConverters | ||||||||||||||||||||||||
| 12 DevCase.UserControls.Controls | ||||||||||||||||||||||||
| 13 DevCase.Win32.Delegates | ||||||||||||||||||||||||
| 14 DevCase.Win32.Enums | ||||||||||||||||||||||||
| 15 DevCase.Win32.Structures | ||||||||||||||||||||||||
| 16 Microsoft.VisualBasic | ||||||||||||||||||||||||
| 17 My | ||||||||||||||||||||||||
| 18 DevCase.Core.Extensions | 1 | |||||||||||||||||||||||
| 19 DevCase.Core.IO | 1 | |||||||||||||||||||||||
| 20 DevCase.Extensions.ControlExtensions | 1 | |||||||||||||||||||||||
| 21 DevCase.UI.Dialogs | 1 | 1 | 1 | 1 | ||||||||||||||||||||
| 22 DevCase.Win32.Interfaces | 4 | 1 | ||||||||||||||||||||||
| 23 (global) | 1 | 4 | ||||||||||||||||||||||
| 24 DevCase.Win32 | 2 | 10 | 4 | 1 |
18→4 DevCase.Core.Extensions uses DevCase.Core.Application.UserInterface✕
- Connections
- 1 pair of types, where a type in DevCase.Core.Extensions uses a type in DevCase.Core.Application.UserInterface.
- The types involved
DevCase.Core.Extensions.FormExtensions→DevCase.Core.Application.UserInterface.VisualTheme
- Direction
- DevCase.Core.Extensions uses DevCase.Core.Application.UserInterface, so a change to DevCase.Core.Application.UserInterface can break DevCase.Core.Extensions, while a change to DevCase.Core.Extensions can't break DevCase.Core.Application.UserInterface.
- Position
- Below the diagonal: DevCase.Core.Extensions uses a module listed above it, which is the healthy direction.
19→14 DevCase.Core.IO uses DevCase.Win32.Enums✕
- Connections
- 1 pair of types, where a type in DevCase.Core.IO uses a type in DevCase.Win32.Enums.
- The types involved
DevCase.Core.IO.ShortcutFileInfo→DevCase.Win32.Enums.IShellLinkResolveFlags
- Direction
- DevCase.Core.IO uses DevCase.Win32.Enums, so a change to DevCase.Win32.Enums can break DevCase.Core.IO, while a change to DevCase.Core.IO can't break DevCase.Win32.Enums.
- Position
- Below the diagonal: DevCase.Core.IO uses a module listed above it, which is the healthy direction.
20→4 DevCase.Extensions.ControlExtensions uses DevCase.Core.Application.UserInterface✕
- Connections
- 1 pair of types, where a type in DevCase.Extensions.ControlExtensions uses a type in DevCase.Core.Application.UserInterface.
- The types involved
DevCase.Extensions.ControlExtensions.ControlExtensions→DevCase.Core.Application.UserInterface.VisualTheme
- Direction
- DevCase.Extensions.ControlExtensions uses DevCase.Core.Application.UserInterface, so a change to DevCase.Core.Application.UserInterface can break DevCase.Extensions.ControlExtensions, while a change to DevCase.Extensions.ControlExtensions can't break DevCase.Core.Application.UserInterface.
- Position
- Below the diagonal: DevCase.Extensions.ControlExtensions uses a module listed above it, which is the healthy direction.
21→1 DevCase.UI.Dialogs uses DevCase.Core.Application.Console✕
- Connections
- 1 pair of types, where a type in DevCase.UI.Dialogs uses a type in DevCase.Core.Application.Console.
- The types involved
DevCase.UI.Dialogs.DevMessageBox→DevCase.Core.Application.Console.ConsoleWindowWrapper
- Direction
- DevCase.UI.Dialogs uses DevCase.Core.Application.Console, so a change to DevCase.Core.Application.Console can break DevCase.UI.Dialogs, while a change to DevCase.UI.Dialogs can't break DevCase.Core.Application.Console.
- Position
- Below the diagonal: DevCase.UI.Dialogs uses a module listed above it, which is the healthy direction.
21→2 DevCase.UI.Dialogs uses DevCase.Core.Application.Forms✕
- Connections
- 1 pair of types, where a type in DevCase.UI.Dialogs uses a type in DevCase.Core.Application.Forms.
- The types involved
DevCase.UI.Dialogs.DevMessageBox→DevCase.Core.Application.Forms.TransparentControlsForm
- Direction
- DevCase.UI.Dialogs uses DevCase.Core.Application.Forms, so a change to DevCase.Core.Application.Forms can break DevCase.UI.Dialogs, while a change to DevCase.UI.Dialogs can't break DevCase.Core.Application.Forms.
- Position
- Below the diagonal: DevCase.UI.Dialogs uses a module listed above it, which is the healthy direction.
21→14 DevCase.UI.Dialogs uses DevCase.Win32.Enums✕
- Connections
- 1 pair of types, where a type in DevCase.UI.Dialogs uses a type in DevCase.Win32.Enums.
- The types involved
DevCase.UI.Dialogs.DevMessageBox→DevCase.Win32.Enums.WindowStylesEx
- Direction
- DevCase.UI.Dialogs uses DevCase.Win32.Enums, so a change to DevCase.Win32.Enums can break DevCase.UI.Dialogs, while a change to DevCase.UI.Dialogs can't break DevCase.Win32.Enums.
- Position
- Below the diagonal: DevCase.UI.Dialogs uses a module listed above it, which is the healthy direction.
21→15 DevCase.UI.Dialogs uses DevCase.Win32.Structures✕
- Connections
- 1 pair of types, where a type in DevCase.UI.Dialogs uses a type in DevCase.Win32.Structures.
- The types involved
DevCase.UI.Dialogs.DevMessageBox→DevCase.Win32.Structures.NativeRectangle
- Direction
- DevCase.UI.Dialogs uses DevCase.Win32.Structures, so a change to DevCase.Win32.Structures can break DevCase.UI.Dialogs, while a change to DevCase.UI.Dialogs can't break DevCase.Win32.Structures.
- Position
- Below the diagonal: DevCase.UI.Dialogs uses a module listed above it, which is the healthy direction.
22→14 DevCase.Win32.Interfaces uses DevCase.Win32.Enums✕
- Connections
- 4 pairs of types, where a type in DevCase.Win32.Interfaces uses a type in DevCase.Win32.Enums.
- The types involved
DevCase.Win32.Interfaces.IShellItem→DevCase.Win32.Enums.ShellItemGetDisplayNameDevCase.Win32.Interfaces.IShellLinkW→DevCase.Win32.Enums.IShellLinkGetPathFlagsDevCase.Win32.Interfaces.IShellLinkW→DevCase.Win32.Enums.IShellLinkResolveFlagsDevCase.Win32.Interfaces.IShellLinkW→DevCase.Win32.Enums.NativeWindowState
- Direction
- DevCase.Win32.Interfaces uses DevCase.Win32.Enums, so a change to DevCase.Win32.Enums can break DevCase.Win32.Interfaces, while a change to DevCase.Win32.Interfaces can't break DevCase.Win32.Enums.
- Position
- Below the diagonal: DevCase.Win32.Interfaces uses a module listed above it, which is the healthy direction.
22→15 DevCase.Win32.Interfaces uses DevCase.Win32.Structures✕
- Connections
- 1 pair of types, where a type in DevCase.Win32.Interfaces uses a type in DevCase.Win32.Structures.
- The types involved
DevCase.Win32.Interfaces.IShellLinkW→DevCase.Win32.Structures.Win32FindDataW
- Direction
- DevCase.Win32.Interfaces uses DevCase.Win32.Structures, so a change to DevCase.Win32.Structures can break DevCase.Win32.Interfaces, while a change to DevCase.Win32.Interfaces can't break DevCase.Win32.Structures.
- Position
- Below the diagonal: DevCase.Win32.Interfaces uses a module listed above it, which is the healthy direction.
23→4 (global) uses DevCase.Core.Application.UserInterface✕
- Connections
- 1 pair of types, where a type in (global) uses a type in DevCase.Core.Application.UserInterface.
- The types involved
Form1→DevCase.Core.Application.UserInterface.VisualTheme
- Direction
- (global) uses DevCase.Core.Application.UserInterface, so a change to DevCase.Core.Application.UserInterface can break (global), while a change to (global) can't break DevCase.Core.Application.UserInterface.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
23→19 (global) uses DevCase.Core.IO✕
- Connections
- 4 pairs of types, where a type in (global) uses a type in DevCase.Core.IO.
- The types involved
CommandLineOptions→DevCase.Core.IO.ShortcutWindowStateCommandLineParser→DevCase.Core.IO.ShortcutWindowStateCommandLineProcessor→DevCase.Core.IO.ShortcutFileInfoForm1→DevCase.Core.IO.ShortcutFileInfo
- Direction
- (global) uses DevCase.Core.IO, so a change to DevCase.Core.IO can break (global), while a change to (global) can't break DevCase.Core.IO.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
24→13 DevCase.Win32 uses DevCase.Win32.Delegates✕
- Connections
- 2 pairs of types, where a type in DevCase.Win32 uses a type in DevCase.Win32.Delegates.
- The types involved
DevCase.Win32.NativeMethods→DevCase.Win32.Delegates.EnumThreadWindowsProcDevCase.Win32.NativeMethods→DevCase.Win32.Delegates.WndProc
- Direction
- DevCase.Win32 uses DevCase.Win32.Delegates, so a change to DevCase.Win32.Delegates can break DevCase.Win32, while a change to DevCase.Win32 can't break DevCase.Win32.Delegates.
- Position
- Below the diagonal: DevCase.Win32 uses a module listed above it, which is the healthy direction.
24→14 DevCase.Win32 uses DevCase.Win32.Enums✕
- Connections
- 10 pairs of types, where a type in DevCase.Win32 uses a type in DevCase.Win32.Enums.
- The types involved
DevCase.Win32.NativeMethods→DevCase.Win32.Enums.BackgroundModeDevCase.Win32.NativeMethods→DevCase.Win32.Enums.GetDCExFlagsDevCase.Win32.NativeMethods→DevCase.Win32.Enums.HResultDevCase.Win32.NativeMethods→DevCase.Win32.Enums.MuiLanguageModeDevCase.Win32.NativeMethods→DevCase.Win32.Enums.SHGetFileInfoFlagsDevCase.Win32.NativeMethods→DevCase.Win32.Enums.SetWindowPosFlagsDevCase.Win32.NativeMethods→DevCase.Win32.Enums.ShellItemGetDisplayNameDevCase.Win32.NativeMethods→DevCase.Win32.Enums.WindowLongValuesDevCase.Win32.NativeMethods→DevCase.Win32.Enums.WindowStylesDevCase.Win32.NativeMethods→DevCase.Win32.Enums.WindowStylesEx
- Direction
- DevCase.Win32 uses DevCase.Win32.Enums, so a change to DevCase.Win32.Enums can break DevCase.Win32, while a change to DevCase.Win32 can't break DevCase.Win32.Enums.
- Position
- Below the diagonal: DevCase.Win32 uses a module listed above it, which is the healthy direction.
24→15 DevCase.Win32 uses DevCase.Win32.Structures✕
- Connections
- 4 pairs of types, where a type in DevCase.Win32 uses a type in DevCase.Win32.Structures.
- The types involved
DevCase.Win32.NativeMethods→DevCase.Win32.Structures.NativeColorDevCase.Win32.NativeMethods→DevCase.Win32.Structures.NativeRectangleDevCase.Win32.NativeMethods→DevCase.Win32.Structures.NativeSizeDevCase.Win32.NativeMethods→DevCase.Win32.Structures.ShellFileInfo
- Direction
- DevCase.Win32 uses DevCase.Win32.Structures, so a change to DevCase.Win32.Structures can break DevCase.Win32, while a change to DevCase.Win32 can't break DevCase.Win32.Structures.
- Position
- Below the diagonal: DevCase.Win32 uses a module listed above it, which is the healthy direction.
24→22 DevCase.Win32 uses DevCase.Win32.Interfaces✕
- Connections
- 1 pair of types, where a type in DevCase.Win32 uses a type in DevCase.Win32.Interfaces.
- The types involved
DevCase.Win32.NativeMethods→DevCase.Win32.Interfaces.IShellItem
- Direction
- DevCase.Win32 uses DevCase.Win32.Interfaces, so a change to DevCase.Win32.Interfaces can break DevCase.Win32, while a change to DevCase.Win32 can't break DevCase.Win32.Interfaces.
- Position
- Below the diagonal: DevCase.Win32 uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 13 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (12), TransparentControlsForm.vb; 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +13.6 pts | Low | ADR Quality |
| Resolve the 13 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (12), TransparentControlsForm.vb. | +13.4 pts | Medium | Comment Value |
| 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. | +11.7 pts | Medium | Architecture documentation |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +2.0 pts | Low | Bus Factor |
| Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with ShortcutFileInfoIconIndexEditor.vb (5), Form1.vb, ShortcutAppIdHelper.vb. | +1.5 pts | Low | Explicit Debt |
| 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. | +2.7 pts | Medium | Documentation (README) |
| Resolve the 1 Build failed finding(s) in Solution Shape. | +1.3 pts | Low | Solution Shape |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. | +1.0 pts | Low | Vulnerability-disclosure Policy |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb | 3.1 | Slop | Explicit Debt: EmptyCatchBlock |
| Source/GUI/UI/Form1.vb | 3.2 | Slop | Explicit Debt: EmptyCatchBlock |
| Source/Shared/DevCase/ShortcutFileInfo.vb | 4.7 | Mixed | Explicit Debt: EmptyCatchBlock |
| Source/Shared/AppId Support/ShortcutAppIdHelper.vb | 6.1 | Mixed | Explicit Debt: EmptyCatchBlock |
| Source/Shared/DevCase/Win32/NativeMethods.vb | 6.7 | Mixed | Explicit Debt: ObsoleteWithCallers |
| Source/Shared/DevCase/Extensions/ControlExtensions.vb | 7.0 | Mixed | Cyclomatic Complexity: ControlExtensions.Internal_SetThemeVisualStudioDark (cyclomatic 42) |
| Source/Shared/DevCase/DevMessageBox.vb | 7.1 | Mixed | Cyclomatic Complexity: DevMessageBox.CustomDlgWndProc (cyclomatic 29) |
| Source/Shared/DevCase/OpenFileOrFolderDialog.vb | 7.6 | Mixed | Explicit Debt: EmptyCatchBlock |
| Source/Shared/DevCase/EnumDescriptionConverter.vb | 7.8 | Mixed | Cognitive Complexity: EnumDescriptionConverter.ConvertTo (cognitive 48) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| Source/GUI/UI/AboutBox1.vb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| Source/CLI/CommandLineParser.vb | 8.5 | Near-clean | Cyclomatic Complexity: CommandLineParser.Parse (cyclomatic 22) |
| Source/Shared/DevCase/Extensions/ToolStripExtensions.vb | 8.5 | Near-clean | Cognitive Complexity: ToolStripExtensions.ForEachItem (cognitive 16) |
| Source/Shared/DevCase/ImageUtil.vb | 8.5 | Near-clean | Code Duplication: Duplicated block (14 lines × 2) |
| Source/CLI/My Project/AssemblyInfo.vb | 9.1 | Near-clean | Comment Value: redundant comment |
| Source/GUI/My Project/AssemblyInfo.vb | 9.1 | Near-clean | Comment Value: redundant comment |
| Source/Shared/My Project/AssemblyInfo.vb | 9.1 | Near-clean | Comment Value: redundant comment |
| REDACTED | 9.3 | Near-clean | Vulnerability-disclosure Policy: REDACTED |
| Source/Shared/DevCase/TransparentControlsForm.vb | 9.5 | Near-clean | Comment Value: redundant comment |
| Source/Shared/Shared.vbproj | 9.5 | Near-clean | Project Cohesion: Projects may be oversized for their cohesion |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
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 35 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 35 dimensions across the health lenses
- 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, 70 of 79 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- 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 analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry), so no test ever ran. This is OUR limitation, not a defect in the repo — it is excluded from the score. We track the analyzer-image gap so it can be closed.
- D12 Dependency Hygiene — 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its 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.
- D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
- D43 Malicious Dependencies — 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- IC1 Incompleteness & stubs — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- PF3 Async & latency hygiene — 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. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
- S1 Web-Security Posture — not measured this run — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X10 Duplicated predicate — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X20 Mistyped argument guard — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — 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. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — 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. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — 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. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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
- 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.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: 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.
- 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 Complexity
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ControlExtensions.Internal_SetThemeVisualStudioDark at 42. A further 1 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 ShortcutFileInfo.op_= at 16 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ControlExtensions.Internal_SetThemeVisualStudioDark (cyclomatic 42), ControlExtensions.Internal_SetThemeDefault (cyclomatic 40), DevMessageBox.CustomDlgWndProc (cyclomatic 29). — 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 6 together lifts Cyclomatic Complexity from 8.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was DevMessageBox.CustomDlgWndProc at 78.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with DevMessageBox.CustomDlgWndProc (cognitive 78). — Refactoring it lifts Cognitive Complexity from 7.3 to about 7.6/10.
D3 · God Classes
13 god class(es) detected.
What to do
- Resolve the 4 MethodTooLong finding(s) in God Classes — start with ControlExtensions.vb (2), DevMessageBox.vb, ShortcutFileInfo.vb. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 FileTooLong finding(s) in God Classes — start with ShortcutFileInfo.vb, Form1.vb, ControlExtensions.vb. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with Form1.vb, NativeMethods.vb, DevMessageBox.vb. — One of this dimension's main actionable groups (4 warning-level).
D4 · Code Duplication
6 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (17 lines × 3) finding(s) in Code Duplication — start with ControlExtensions.vb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (19–20 lines × 2) finding(s) in Code Duplication — start with Form1.vb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (12 lines × 3) finding(s) in Code Duplication — start with ControlExtensions.vb. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 7 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with Form1.vb. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 1 direct `PackageReference`(s), and 4 further package(s) were reached beyond them. No lockfile was read, so the graded set is as deep as the licence tool resolved and is not certified to be the complete transitive graph.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Source/Shared/DevCase/DevMessageBox.vb. Counted over 44 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
11 deducted debt markers + 0 dead symbols across 17663 LoC in the .NET projects (0.5/KLoC) → score 9.0.
What to do
- Resolve the 9 EmptyCatchBlock finding(s) in Explicit Debt — start with ShortcutFileInfoIconIndexEditor.vb (5), Form1.vb, ShortcutAppIdHelper.vb. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with AboutBox1.vb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ObsoleteWithCallers finding(s) in Explicit Debt — start with NativeMethods.vb. — One of this dimension's main actionable groups (1 warning-level).
D18 · Solution Shape
4 projects, 83 source files, 20804 hand-written lines of code (17663 production / 3141 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), plus 1400 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 4 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
13 of 142 judged comments only repeat the code they sit on (9.2 %). 14 comment(s) in another language or script were not judged.
What to do
- Resolve the 13 redundant comment finding(s) in Comment Value — start with AssemblyInfo.vb (12), TransparentControlsForm.vb. — One of this dimension's main actionable groups (13 recommendation-level).
D26 · Project Cohesion
1 of 4 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Shared.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
86 % of calls cross a namespace and 4 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues. semgrep hit a parse error in 2 file(s) — `REDACTED`, `appveyor.yml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
D34 · Knowledge Freshness
2 of 44 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/GUI/JotUtil.vb. Counted over 44 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but only routes reports to a public channel (no private reporting contact).
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 3 of 3 have no README of their own, in their folder or in their family's project (`Source/CLI`, `Source/GUI`, `Source/Shared`).
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Only 1/4 projects share a common root namespace — the code's module identity is inconsistent.
M4 · Documentation accuracy
- CONTRIBUTING.md links to `Images/Paypal_Donate.png`, but `Images/Paypal_Donate.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:14
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `Images/Paypal_Donate.png`, but `Images/Paypal_Donate.png` does not exist.
P1 · CI/CD gates
P2 · Observability
What to do
- For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
P3 · Security & performance tooling
- `Source/Tests/Tests.vbproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Source/Tests/Tests.vbproj:20
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 81% | Checked 6 of 13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 95% | Exemplary | Strongest area. |
| Maturity | 52% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 73% | Strong | Solid. |
| Security | 85% | Checked 5 of 11 | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX5 Architecture & structure — no elaborate style needed at this size (~17.7k production LoC (104 types) across 3 project(s) / 24 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help.)
- AX6 Interface segregation — no public interfaces
- 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 — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~3141 lines of test source are present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — analyzer environment
- D12 Dependency Hygiene — Dependency hygiene not measured
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Visual Basic not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (17,663 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — 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; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Scanner failed to run — not a clean result
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is present (.vb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — 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.
- PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
Critical — 9 finding(s)
- EmptyCatchBlock Source/GUI/UI/Form1.vb:1522
- EmptyCatchBlock Source/Shared/AppId Support/ShortcutAppIdHelper.vb:379
- EmptyCatchBlock Source/Shared/DevCase/OpenFileOrFolderDialog.vb:277
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfo.vb:1211
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:85
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:93
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:102
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:110
- EmptyCatchBlock Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:118
Serious — 41 finding(s)
- MethodTooLong: ControlExtensions.Internal_SetThemeDefault Source/Shared/DevCase/Extensions/ControlExtensions.vb:190
- MethodTooLong: ControlExtensions.Internal_SetThemeVisualStudioDark Source/Shared/DevCase/Extensions/ControlExtensions.vb:522
- MethodTooLong: DevMessageBox.CustomDlgWndProc Source/Shared/DevCase/DevMessageBox.vb:1793
- MethodTooLong: ShortcutFileInfo.WriteLink Source/Shared/DevCase/ShortcutFileInfo.vb:1308
- FileTooLong: DevCase/ShortcutFileInfo.vb Source/Shared/DevCase/ShortcutFileInfo.vb
- FileTooLong: UI/Form1.vb Source/GUI/UI/Form1.vb
- FileTooLong: Extensions/ControlExtensions.vb Source/Shared/DevCase/Extensions/ControlExtensions.vb
- FileTooLong: DevCase/DevMessageBox.vb Source/Shared/DevCase/DevMessageBox.vb
- TooManyMethods: Form1 Source/GUI/UI/Form1.vb
- TooManyMethods: NativeMethods Source/Shared/DevCase/Win32/NativeMethods.vb
- TooManyMethods: DevMessageBox Source/Shared/DevCase/DevMessageBox.vb
- TooManyMethods: ShortcutFileInfo Source/Shared/DevCase/ShortcutFileInfo.vb
- ControlExtensions.Internal_SetThemeVisualStudioDark (cyclomatic 42) Source/Shared/DevCase/Extensions/ControlExtensions.vb:522
- ControlExtensions.Internal_SetThemeDefault (cyclomatic 40) Source/Shared/DevCase/Extensions/ControlExtensions.vb:190
- DevMessageBox.CustomDlgWndProc (cyclomatic 29) Source/Shared/DevCase/DevMessageBox.vb:1793
- CommandLineParser.Parse (cyclomatic 22) Source/CLI/CommandLineParser.vb:85
- ShortcutFileInfo.WriteLink (cyclomatic 20) Source/Shared/DevCase/ShortcutFileInfo.vb:1308
- ShortcutFileInfoIconIndexEditor.PaintValue (cyclomatic 19) Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:70
- TodoComment Source/GUI/UI/AboutBox1.vb:50
- ObsoleteWithCallers Source/Shared/DevCase/Win32/NativeMethods.vb:2016
- Build failed
- DevMessageBox.CustomDlgWndProc (cognitive 78) Source/Shared/DevCase/DevMessageBox.vb:1793
- EnumDescriptionConverter.ConvertTo (cognitive 48) Source/Shared/DevCase/EnumDescriptionConverter.vb:211
- ControlExtensions.Internal_SetThemeVisualStudioDark (cognitive 43) Source/Shared/DevCase/Extensions/ControlExtensions.vb:522
- ControlExtensions.Internal_SetThemeDefault (cognitive 40) Source/Shared/DevCase/Extensions/ControlExtensions.vb:190
- EnumDescriptionConverter.ConvertFrom (cognitive 35) Source/Shared/DevCase/EnumDescriptionConverter.vb:300
- ShortcutFileInfo.WriteLink (cognitive 31) Source/Shared/DevCase/ShortcutFileInfo.vb:1308
- ShortcutFileInfoIconIndexEditor.PaintValue (cognitive 20) Source/Shared/DevCase/ShortcutFileInfoIconIndexEditor.vb:70
- ShortcutAppIdHelper.GetInstalledAppUserModelIds (cognitive 18) Source/Shared/AppId Support/ShortcutAppIdHelper.vb:496
- ShortcutFileInfo.ReadLink (cognitive 17) Source/Shared/DevCase/ShortcutFileInfo.vb:1180
- ToolStripExtensions.ForEachItem (cognitive 16) Source/Shared/DevCase/Extensions/ToolStripExtensions.vb:86
- ClassTooLong: ControlExtensions Source/Shared/DevCase/Extensions/ControlExtensions.vb
- REDACTED
- Duplicated block (17 lines × 3) Source/Shared/DevCase/Extensions/ControlExtensions.vb:646
- Duplicated block (19–20 lines × 2) Source/GUI/UI/Form1.vb:528
- Duplicated block (12 lines × 3) Source/Shared/DevCase/Extensions/ControlExtensions.vb:427
- Duplicated block (14 lines × 2) Source/Shared/DevCase/ImageUtil.vb:127
- Duplicated block (7 lines × 2) Source/GUI/UI/Form1.vb:303
- Duplicated block (6 lines × 2) Source/GUI/UI/Form1.vb:328
- Low cohesion: Form1 (LCOM4 6) Source/GUI/UI/Form1.vb:46
- NuGet dependencies are not locked
Minor — 26 finding(s)
- redundant comment Source/CLI/My Project/AssemblyInfo.vb:7
- redundant comment Source/CLI/My Project/AssemblyInfo.vb:11
- redundant comment Source/CLI/My Project/AssemblyInfo.vb:22
- redundant comment Source/CLI/My Project/AssemblyInfo.vb:25
- redundant comment Source/GUI/My Project/AssemblyInfo.vb:6
- redundant comment Source/GUI/My Project/AssemblyInfo.vb:10
- redundant comment Source/GUI/My Project/AssemblyInfo.vb:21
- redundant comment Source/GUI/My Project/AssemblyInfo.vb:24
- redundant comment Source/Shared/DevCase/TransparentControlsForm.vb:328
- redundant comment Source/Shared/My Project/AssemblyInfo.vb:7
- redundant comment Source/Shared/My Project/AssemblyInfo.vb:11
- redundant comment Source/Shared/My Project/AssemblyInfo.vb:22
- redundant comment Source/Shared/My Project/AssemblyInfo.vb:25
- Orphaned file Source/GUI/JotUtil.vb:1
- Orphaned file Source/Shared/DevCase/RegistryUtil.vb:1
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion Source/Shared/Shared.vbproj:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Inconsistent root namespaces
- README/code drift CONTRIBUTING.md:14
- No dependency-update automation Source/Tests/Tests.vbproj:20
Minor — 3 finding(s)
- doc comments repeat the names Source/Shared/DevCase/ShortcutFileInfo.vb:1458
- doc comments repeat the names Source/Tests/Helpers/TextAssert.vb:89
- Off the main sequence: Shared Source/Shared/Shared.vbproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e6373faca4ec43388ab70f2bd07eae9c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.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-e6373faca4ec43388ab70f2bd07eae9c/tree.json --exit-code 0 --source . | 0 | artifacts/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 . | 0 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | 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 scan; nuget packages.config: osv-scanner exited 127 with no findings — dependency CVEs were not measured | 0 | — |
| D31 · IaC & Container Security | trivy | — | 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. | 0 | — |
| D40 · Network Egress Confinement | runtime-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 Confinement | runtime-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 Enforcement | runtime-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 Dependencies | osv-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-83166b0ad8ad4f859fab17a0e29dcbd4 | 0 | artifacts/raw/osv-scanner.json |