Public report of SerZhyAle/FastMediaSorter_Lite, published 21 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 21 October 2026, 16:46 UTC · Survey ID cd_4a83feff4375442680db5b6f2d99d155
SerZhyAle/FastMediaSorter_Lite
Measured 21 October 2026, 16:35 UTC, at code version ca51d6f
Code coverage is not measured: No coverage collector is wired up.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 155,051 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 1.6 person-years · Weakest lens: Production Readiness, 46
Findings by how serious they are
524 critical935 serious56 minor
35 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 16:35 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
39of 43 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
1501of 1515 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
43dimensions across 6 lenses, read from 155,051 lines of product code in 3 projects.
SerZhyAle/FastMediaSorter_Lite scores 50 out of 100 and is rated Weak, while three of its six lenses score higher still: Architecture at 72, Performance at 61 and Security and Compliance at 60, all rated Adequate.
The score is lower than those three because the weakest lens counts most, and here that is Production Readiness, which scores 46 and is rated Weak. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in REDACTED Scanning and to resolve the 1 No ADRs found finding(s) in ADR Quality. The weakest lenses score close to each other, so improving any of them moves the score.
524 findings are critical: 507 in Explicit Debt, nine in Static Analysis (SAST), five in Secrets (history), two in REDACTED Scanning and one in Dependency Vulnerabilities.
Watchdog couldn't measure 35 dimensions in this code, among them Test Reliability, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 155,051 lines, which would take an estimated 1.6 person-years, around €240,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 64%Tests 36%
New since the last survey: 1052 findings
These 1052 critical or serious findings weren't in the previous survey, on 6 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 80 findings
These 80 critical or serious findings were in the previous survey, on 6 October 2026, and are gone from this one.
€78,000 to €390,000, for 1,305 to 4,139 hours of work, about 1.6 person-years for 1 to 4 engineers
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.7 at a score of 50. 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
Large: 155,051 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
3
Add a SAST step to CI running what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — so a security regression fails the build instead of landing.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €240,000 to build again, about 1.6 person-years of work. Its weakest lens is Production Readiness, at 46 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 2 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 6% on every change. The history of the code shows how much it changes: about 722,868 lines over the last 90 days, which is about 2,931,631 lines a year. At that pace, the extra work comes to an estimated 179.9 to 1079.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
43 modules, with 33 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 3 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
fms/exchange-server/internal/accounts uses fms/exchange-server/internal/password, so a change to fms/exchange-server/internal/password can break fms/exchange-server/internal/accounts, while a change to fms/exchange-server/internal/accounts can't break fms/exchange-server/internal/password.
Position
Below the diagonal: fms/exchange-server/internal/accounts uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/directory uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/internal/directory, while a change to fms/exchange-server/internal/directory can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/internal/directory uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/relay uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/internal/relay, while a change to fms/exchange-server/internal/relay can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/internal/relay uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/admin uses fms/exchange-server/internal/logx, so a change to fms/exchange-server/internal/logx can break fms/exchange-server/internal/admin, while a change to fms/exchange-server/internal/admin can't break fms/exchange-server/internal/logx.
Position
Below the diagonal: fms/exchange-server/internal/admin uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/admin uses fms/exchange-server/internal/accounts, so a change to fms/exchange-server/internal/accounts can break fms/exchange-server/internal/admin, while a change to fms/exchange-server/internal/admin can't break fms/exchange-server/internal/accounts.
Position
Below the diagonal: fms/exchange-server/internal/admin uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/admin uses fms/exchange-server/internal/directory, so a change to fms/exchange-server/internal/directory can break fms/exchange-server/internal/admin, while a change to fms/exchange-server/internal/admin can't break fms/exchange-server/internal/directory.
Position
Below the diagonal: fms/exchange-server/internal/admin uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/fms-exchange-server uses fms/exchange-server/internal/config, so a change to fms/exchange-server/internal/config can break fms/exchange-server/cmd/fms-exchange-server, while a change to fms/exchange-server/cmd/fms-exchange-server can't break fms/exchange-server/internal/config.
Position
Below the diagonal: fms/exchange-server/cmd/fms-exchange-server uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/fms-exchange-server uses fms/exchange-server/internal/admin, so a change to fms/exchange-server/internal/admin can break fms/exchange-server/cmd/fms-exchange-server, while a change to fms/exchange-server/cmd/fms-exchange-server can't break fms/exchange-server/internal/admin.
Position
Below the diagonal: fms/exchange-server/cmd/fms-exchange-server uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/cast, so a change to fms/exchange-server/internal/cast can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/cast.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/limits, so a change to fms/exchange-server/internal/limits can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/limits.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/logx, so a change to fms/exchange-server/internal/logx can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/logx.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/ports, so a change to fms/exchange-server/internal/ports can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/ports.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/tunnel, so a change to fms/exchange-server/internal/tunnel can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/tunnel.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/accounts, so a change to fms/exchange-server/internal/accounts can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/accounts.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/directory, so a change to fms/exchange-server/internal/directory can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/directory.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/relay, so a change to fms/exchange-server/internal/relay can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/relay.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/rendezvous uses fms/exchange-server/internal/admin, so a change to fms/exchange-server/internal/admin can break fms/exchange-server/internal/rendezvous, while a change to fms/exchange-server/internal/rendezvous can't break fms/exchange-server/internal/admin.
Position
Below the diagonal: fms/exchange-server/internal/rendezvous uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/limits, so a change to fms/exchange-server/internal/limits can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/limits.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/logx, so a change to fms/exchange-server/internal/logx can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/logx.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/password, so a change to fms/exchange-server/internal/password can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/password.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/ports, so a change to fms/exchange-server/internal/ports can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/ports.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/accounts, so a change to fms/exchange-server/internal/accounts can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/accounts.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/directory, so a change to fms/exchange-server/internal/directory can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/directory.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/admin, so a change to fms/exchange-server/internal/admin can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/admin.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/internal/testkit uses fms/exchange-server/internal/rendezvous, so a change to fms/exchange-server/internal/rendezvous can break fms/exchange-server/internal/testkit, while a change to fms/exchange-server/internal/testkit can't break fms/exchange-server/internal/rendezvous.
Position
Below the diagonal: fms/exchange-server/internal/testkit uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/exchange-probe uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/cmd/exchange-probe, while a change to fms/exchange-server/cmd/exchange-probe can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/cmd/exchange-probe uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/exchange-probe uses fms/exchange-server/internal/testkit, so a change to fms/exchange-server/internal/testkit can break fms/exchange-server/cmd/exchange-probe, while a change to fms/exchange-server/cmd/exchange-probe can't break fms/exchange-server/internal/testkit.
Position
Below the diagonal: fms/exchange-server/cmd/exchange-probe uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/exchange-vectors uses fms/exchange-server/internal/logx, so a change to fms/exchange-server/internal/logx can break fms/exchange-server/cmd/exchange-vectors, while a change to fms/exchange-server/cmd/exchange-vectors can't break fms/exchange-server/internal/logx.
Position
Below the diagonal: fms/exchange-server/cmd/exchange-vectors uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/exchange-vectors uses fms/exchange-server/internal/wire, so a change to fms/exchange-server/internal/wire can break fms/exchange-server/cmd/exchange-vectors, while a change to fms/exchange-server/cmd/exchange-vectors can't break fms/exchange-server/internal/wire.
Position
Below the diagonal: fms/exchange-server/cmd/exchange-vectors uses a module listed above it, which is the healthy direction.
fms/exchange-server/cmd/exchange-vectors uses fms/exchange-server/internal/testkit, so a change to fms/exchange-server/internal/testkit can break fms/exchange-server/cmd/exchange-vectors, while a change to fms/exchange-server/cmd/exchange-vectors can't break fms/exchange-server/internal/testkit.
Position
Below the diagonal: fms/exchange-server/cmd/exchange-vectors uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 50% · Weak · gated by D2, D17 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
17
High / Critical
A07:2025 — Authentication Failures
8
High / Critical
A03:2025 — Software Supply Chain Failures
7
High / Critical
Roadmap
Immediately resolve the two leaked secrets in REDACTED and REDACTED, and integrate a Roslyn-based SAST step with gitleaks into the CI pipeline to prevent security regressions. Address the 507 empty catch blocks, prioritizing fixes in TrayContext.vb, AppFileLogger.vb, and Share_Settings_Form.vb, while also creating the missing Architecture Decision Records. Finally, update the README and documentation contracts to accurately reflect the current repository structure and remove references to non-existent files.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED.
Add a SAST step to CI running what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — so a security regression fails the build instead of landing.
Reconcile the README with reality: exchange-server/README.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists; docs/contracts/ANYWHERE-ACCESS.md names `vectors/descriptor-v2.json`, but no file or folder `vectors/descriptor-v2.json` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-10-exchange-connection-string.md`, but no file or folder `PROPOSAL-2026-10-10-exchange-connection-string.md` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-12-access-and-connection-experience.md`, but no file or folder `PROPOSAL-2026-10-12-access-and-connection-experience.md` exists.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 524
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 935
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 56
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 35
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 39 of 43 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 43 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1501 of 1515 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog 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 source is present (.go, .vb) and it is .NET, which this analyzer re-runs through `dotnet test` — but the .NET workspace loaded none of this repository's test projects, so there was no suite to re-run and flakiness couldn't be assessed. The repository commits a project or solution file, so the load had something to read and still produced nothing: the remedy is the restore, the SDK band or the target resolution, not a new runner. Not scored — this is a gap on our side, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog 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.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 227 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (155,051 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D28 Secrets (history) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `packages/VideoLAN.LibVLC.Windows.3.0.21/build/x86/lua/http/requests/status.json`, `packages/VideoLAN.LibVLC.Windows.3.0.21/build/x86/lua/http/requests/playlist.json`, `packages/VideoLAN.LibVLC.Windows.3.0.21/build/x86/lua/http/requests/browse.json`, `packages/VideoLAN.LibVLC.Windows.3.0.21/build/x64/lua/http/requests/status.json`, `packages/VideoLAN.LibVLC.Windows.3.0.21/build/x64/lua/http/requests/playlist.json` and 1 more did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D39 IL Efficiency — not measured this run — Watchdog 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 build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 43 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
S1 Web-Security Posture — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
244 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Main_Form.KeybUse at 146. A further 27 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 Table_Form.ModernSettingTitle at 149 — they are counted neither in the figure above nor in this dimension's score. 10 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/OcrTranslateSettings.vb (OcrTranslateSettings.TessSingleLanguage at 71), src/Theming/ThemePalette.vb (ThemePalette.RoleForSystemColor at 37), src/Translate/TranslationQuality.vb (TranslationQuality.HasLettersForeignToTarget at 28), src/AudioMetadata.vb (AudioMetadata.CodecName at 27), src/CustomHotkeys.vb (CustomHotkeys.KeyFromName at 23), and 5 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 237 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with Main_Form.KeybUse (cyclomatic 146). — Refactoring it lifts Cyclomatic Complexity from 5.2 to about 5.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 332 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 120 down to 120 or less in Cognitive Complexity — start with StreamCatalogValidator.ValidateArchive (cognitive 203), prober.run (cognitive 155), Main_Form.UpdateCurrentFileAndDisplay (cognitive 136). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 3.6 to about 4.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.0 / 10Adequate✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 80 MethodTooLong finding(s) in God Classes — start with Table_Form.ModernLayout.vb (3), Localization.AppUx.vb (2), Main_Form.MediaLoading.vb (2). — One of this dimension's main actionable groups (80 warning-level).
Resolve the 45 FileTooLong finding(s) in God Classes — start with Table_Form.ModernLayout.vb, Main_Form.Chrome.vb, Localization.Resources.vb. — One of this dimension's main actionable groups (45 warning-level).
Resolve the 35 TooManyMethods finding(s) in God Classes — start with Main_Form.Archive.vb, Share_Settings_Form.Contract.vb, MainWindow.Access.vb. — One of this dimension's main actionable groups (35 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
101 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ExchangeDevices.vb, TransferPlan.vb, DocHtmlTranslateLauncher.vb. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ProtectedConfigWriter.vb (2), Main_Form.ShareLauncher.vb, SftpProvider.vb. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with ProtectedConfigWriter.vb (2), Localization.Activation.vb, NetworkInfo.vb. — One of this dimension's main actionable groups (11 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with Image_Panel_Form.Details.vb, Main_Form.Archive.vb, LocalProvider.vb. — One of this dimension's main actionable groups (9 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
393 test methods: 393 unit, 0 integration, 0 BDD, 0 e2e. The Go suite contributes 393 test case(s) across 48 `_test.go` file(s) declaring at least one — every `func Test…(t *testing.T)` that `go test` would collect, plus the suite methods a testify-style runner reaches; a table-driven case list counts once, so this is a floor. Its tier split is INFERRED from file names, paths and build constraints, not declared: 10 of those file(s) use Go's external test package (`package x_test`), which is a visibility boundary rather than a pyramid tier and was not read as one.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 209 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 14 direct `PackageReference`(s), and 178 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 58 Hotspot finding(s) in Churn × Complexity Hotspots — start with Table_Form.ModernLayout.vb, Main_Form.KeyboardInput.vb, Main_Form.MediaLoading.vb. — One of this dimension's main actionable groups (58 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D17 · Explicit Debt3.5 / 10Weak✓ Tool-verified
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
507 deducted debt markers + 0 dead symbols across 155051 LoC in the .NET projects (3.2/KLoC) → score 3.5.
EmptyCatchBlock · ×507src/AppFileLogger.vb:57
What to do
Resolve the 507 EmptyCatchBlock finding(s) in Explicit Debt — start with TrayContext.vb (30), AppFileLogger.vb (28), Share_Settings_Form.vb (13). — One of this dimension's main actionable groups (507 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
3 projects, 1001 source files, 155270 hand-written lines of code (155051 production / 219 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 1270 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
This repository is well documented: the root README describes the product (Fast Media Sorter & Sharing for Windows) with a name-history note and an overview table of viewer/server/share roles plus links to SFTP publishing, server pages, and companion apps; it also documents the docs/ directory as an internal index that users never reach. The exchange-server README is long but focused on its own directory (exchange-server package), describing the wire contract, layout, and a build/test plan with tickets 141-144. All visible documents are complete per their scope: the docs/README is an internal index; each exchange-server/README.md and contracts/README.md is a directory README documenting its own tier; no repository-wide overview, installation, or contribution guidance appears in any of these files. This is a deeply documented contracts catalog for FastMediaSorter, covering the ANYWHERE-ACCESS, APP-ACTIVATION, and desktop-UX pointers with precise versioning, ownership, and cross-references to local specifications. The documents are well structured: each one begins with an Id/version line, a Home reference, and a Role here section that explains what the repository holds while the contract is [PROPOSED], followed by a What this repository must do to stay conformant rationale (rules 4-7). The outline is complete for every document shown; there are no clipped sections. All four core documentation elements (overview, installation/usage, contribution guidance, licence) are absent from the visible documents and fall outside the scope of any one pointer. (11 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
2 of 3 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
47 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
19 finding(s): 0 critical, 9 high, 3 medium, 7 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `index.html` (line 431, line 432, line 433, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
3 finding(s): 0 critical, 1 high, 2 medium, 0 low. Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 534 of the 580 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 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.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, 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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
~155.1k production LoC (2456 types) across 3 project(s) / 43 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
What to do
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
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.
Add a README to the 3 of 3 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
exchange-server/README.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists. 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. — exchange-server/README.md:160
docs/contracts/ANYWHERE-ACCESS.md names `vectors/descriptor-v2.json`, but no file or folder `vectors/descriptor-v2.json` exists. 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. — docs/contracts/ANYWHERE-ACCESS.md:12
docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists. 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. — docs/contracts/DEVICE-EXCHANGE.md:33
docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-10-exchange-connection-string.md`, but no file or folder `PROPOSAL-2026-10-10-exchange-connection-string.md` exists. 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. — docs/contracts/DEVICE-EXCHANGE.md:41
docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-12-access-and-connection-experience.md`, but no file or folder `PROPOSAL-2026-10-12-access-and-connection-experience.md` exists. 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. — docs/contracts/DEVICE-EXCHANGE.md:62
docs/contracts/FDSEC.md names `FDSEC-FORMAT.md`, but no file or folder `FDSEC-FORMAT.md` exists. 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. — docs/contracts/FDSEC.md:7
docs/contracts/FDSEC.md names `FD-SEC-CONTRACT.md`, but no file or folder `FD-SEC-CONTRACT.md` exists. 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. — docs/contracts/FDSEC.md:7
docs/contracts/FDSEC.md names `PROPOSAL-2026-09-22-streaming-reader.md`, but no file or folder `PROPOSAL-2026-09-22-streaming-reader.md` exists. 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. — docs/contracts/FDSEC.md:64
docs/contracts/FDSEC.md names `PROPOSAL-2026-09-30-sealed-name-parity.md`, but no file or folder `PROPOSAL-2026-09-30-sealed-name-parity.md` exists. 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. — docs/contracts/FDSEC.md:74
docs/contracts/FMSCFG.md names `CONFIG_FORMAT.md`, but no file or folder `CONFIG_FORMAT.md` exists. 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. — docs/contracts/FMSCFG.md:7
docs/contracts/FMSCFG.md names `PROPOSAL-2026-09-25-fms-windows-producer.md`, but no file or folder `PROPOSAL-2026-09-25-fms-windows-producer.md` exists. 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. — docs/contracts/FMSCFG.md:31
docs/contracts/FMSCFG.md names `PROPOSAL-2026-09-22-canonical-vectors-per-producer.md`, but no file or folder `PROPOSAL-2026-09-22-canonical-vectors-per-producer.md` exists. 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. — docs/contracts/FMSCFG.md:94
docs/contracts/INSTALL-TRUST.md names `TRUST_GUIDE.md`, but no file or folder `TRUST_GUIDE.md` exists. 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. — docs/contracts/INSTALL-TRUST.md:7
docs/contracts/LETTERBOX-FILL.md names `vectors/letterbox-fill-vectors.json`, but no file or folder `vectors/letterbox-fill-vectors.json` exists. 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. — docs/contracts/LETTERBOX-FILL.md:7
docs/contracts/LIVE-BROADCAST.md names `11_live_broadcast_contract.md`, but no file or folder `11_live_broadcast_contract.md` exists. 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. — docs/contracts/LIVE-BROADCAST.md:7
docs/contracts/LIVE-BROADCAST.md names `13_contract_amendment_2026-10-07.md`, but no file or folder `13_contract_amendment_2026-10-07.md` exists. 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. — docs/contracts/LIVE-BROADCAST.md:7
docs/contracts/RULE-ADOPTION.md documents the environment variable `RELEASE_AND_DISTRIBUTION`, but no code, script or configuration file names it. 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. — docs/contracts/RULE-ADOPTION.md:31
docs/contracts/SHARE-SESSION.md names `share-session-reconnect.md`, but no file or folder `share-session-reconnect.md` exists. 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. — docs/contracts/SHARE-SESSION.md:7
docs/contracts/STREAM-BANK.md names `streams.csv`, but no file or folder `streams.csv` exists. 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. — docs/contracts/STREAM-BANK.md:18
docs/contracts/WAVE-PARTICLES.md documents the environment variable `SPI_GETCLIENTAREAANIMATION`, but no code, script or configuration file names it. 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. — docs/contracts/WAVE-PARTICLES.md:30
docs/contracts/WAVE-PARTICLES.md documents the environment variable `DWMWA_CLOAKED`, but no code, script or configuration file names it. 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. — docs/contracts/WAVE-PARTICLES.md:38
docs/contracts/WORKER-IPC.md names `SPECIFICATION_ANDROID_FOLDER_SHARE.md`, but no file or folder `SPECIFICATION_ANDROID_FOLDER_SHARE.md` exists. 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. — docs/contracts/WORKER-IPC.md:11
docs/contracts/WORKER-IPC.md names `PROPOSAL-2026-10-07-broadcast-supported.md`, but no file or folder `PROPOSAL-2026-10-07-broadcast-supported.md` exists. 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. — docs/contracts/WORKER-IPC.md:65
docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md names `project.assets.json`, but no file or folder `project.assets.json` exists. 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. — docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md:129
docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md documents the environment variable `ATTACH_VIRTUAL_DISK_FLAG_READ_ONLY`, but no code, script or configuration file names it. 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. — docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md:175
docs/guides/RESEARCH_COMPETITOR_FEATURES.md documents the environment variable `FOF_ALLOWUNDO`, but no code, script or configuration file names it. 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. — docs/guides/RESEARCH_COMPETITOR_FEATURES.md:69
docs/guides/SERVER_EDITION_BUILD_AND_TEST.md names `internal/service/scm.go`, but no file or folder `internal/service/scm.go` exists. 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. — docs/guides/SERVER_EDITION_BUILD_AND_TEST.md:81
docs/guides/SETTINGS_WINDOW_INVENTORY_DOTNET10.md names `SPECIFICATION_COPY_ACTIONS_REWORK.md`, but no file or folder `SPECIFICATION_COPY_ACTIONS_REWORK.md` exists. 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. — docs/guides/SETTINGS_WINDOW_INVENTORY_DOTNET10.md:167
docs/guides/SETTINGS_WINDOW_INVENTORY_DOTNET10.md names `169_SPECIFICATION_SETTINGS_RESET_ALL_ON_ABOUT_PAGE.md`, but no file or folder `169_SPECIFICATION_SETTINGS_RESET_ALL_ON_ABOUT_PAGE.md` exists. 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. — docs/guides/SETTINGS_WINDOW_INVENTORY_DOTNET10.md:258
docs/guides/TESTING.md names `internal/ipc`, but no file or folder `internal/ipc` exists. 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. — docs/guides/TESTING.md:174
docs/guides/TESTING.md names `internal/netaccess`, but no file or folder `internal/netaccess` exists. 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. — docs/guides/TESTING.md:175
docs/guides/TESTING.md names `internal/sftpserver`, but no file or folder `internal/sftpserver` exists. 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. — docs/guides/TESTING.md:175
docs/guides/TESTING.md names `internal/app`, but no file or folder `internal/app` exists. 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. — docs/guides/TESTING.md:177
docs/guides/TESTING.md names `internal/service`, but no file or folder `internal/service` exists. 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. — docs/guides/TESTING.md:177
docs/guides/TESTING.md names `cmd/worker`, but no file or folder `cmd/worker` exists. 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. — docs/guides/TESTING.md:178
docs/guides/TESTING.md names `cmd/devserve`, but no file or folder `cmd/devserve` exists. 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. — docs/guides/TESTING.md:178
docs/guides/TESTING.md names `granted-roots.json`, but no file or folder `granted-roots.json` exists. 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. — docs/guides/TESTING.md:211
docs/guides/WINDOWS_UI_AUDIT.md names `answer-row-widths.csv`, but no file or folder `answer-row-widths.csv` exists. 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. — docs/guides/WINDOWS_UI_AUDIT.md:280
packages/LibVLCSharp.3.9.3/README.md links to `../LibVLCSharp.Forms/README.md`, but `packages/LibVLCSharp.Forms/README.md` 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. — packages/LibVLCSharp.3.9.3/README.md:29
packages/LibVLCSharp.WinForms.3.9.3/README.md links to `../LibVLCSharp/README.md`, but `packages/LibVLCSharp/README.md` 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. — packages/LibVLCSharp.WinForms.3.9.3/README.md:8
What to do
Reconcile the README with reality: exchange-server/README.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists; docs/contracts/ANYWHERE-ACCESS.md names `vectors/descriptor-v2.json`, but no file or folder `vectors/descriptor-v2.json` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-10-exchange-connection-string.md`, but no file or folder `PROPOSAL-2026-10-10-exchange-connection-string.md` exists; docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-12-access-and-connection-experience.md`, but no file or folder `PROPOSAL-2026-10-12-access-and-connection-experience.md` exists.
For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean as a CI step. What was searched, so you can tell an absence from a miss: the 22606 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 36 use(s) across 167,373 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Go: on hot paths, reuse buffers and objects through sync.Pool, preallocate slices and maps with make([]T, 0, n) / make(map[K]V, n), size builders with Grow, append with strconv.Append*, and reslice with buf[:0] instead of allocating anew.
Visual Basic: on hot paths, work through Span(Of T)/Memory(Of T) (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool(Of T), return ValueTask from completions that are usually synchronous, write through IBufferWriter(Of T), and presize List/StringBuilder/Dictionary.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
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.
Not included — 71 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC7 A11y enforcement — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — 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 — ~86125 lines of test source are present (.go, .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 included — the .NET workspace loaded no .vb test project
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — 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.
DM1 Domain Modelling — not scored — this repository shows none of the 2 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
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.
PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
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
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.
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 — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock src/AppFileLogger.vb:57— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:58— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:59— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:60— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:70— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:72— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:76— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:183— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:196— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:199— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:202— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:204— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:214— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:218— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:221— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:223— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:239— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:310— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:336— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:343— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:393— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:450— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:459— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:464— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/AppFileLogger.vb:469— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
MethodTooLong: Localization.AddResourceStrings src/Localization/Localization.Resources.vb:26— MethodTooLong — AddResourceStrings runs 1096 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 996 over it, 10.96× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddManagerStrings src/FastMediaSorterCompanion/Localization/Localization.Manager.vb:10— MethodTooLong — AddManagerStrings runs 807 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 707 over it, 8.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddShareStrings src/FastMediaSorterCompanion/Localization/Localization.Share.vb:13— MethodTooLong — AddShareStrings runs 782 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 682 over it, 7.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddFileStrings src/Localization/Localization.Files.vb:9— MethodTooLong — AddFileStrings runs 756 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 656 over it, 7.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddSettingsExpansionStrings src/Localization/Localization.SettingsExpansion.vb:19— MethodTooLong — AddSettingsExpansionStrings runs 601 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 501 over it, 6.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddHostingStrings src/FastMediaSorterCompanion/Localization/Localization.Hosting.vb:11— MethodTooLong — AddHostingStrings runs 588 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 488 over it, 5.88× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddMenuStrings src/Localization/Localization.Menus.vb:16— MethodTooLong — AddMenuStrings runs 573 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 473 over it, 5.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddMediaStrings src/Localization/Localization.Media.vb:10— MethodTooLong — AddMediaStrings runs 427 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 327 over it, 4.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddVideoStrings src/Localization/Localization.Video.vb:22— MethodTooLong — AddVideoStrings runs 420 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 320 over it, 4.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddWizardStrings src/FastMediaSorterCompanion/Localization/Localization.Wizard.vb:9— MethodTooLong — AddWizardStrings runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddAppUxStrings src/Localization/Localization.AppUx.vb:16— MethodTooLong — AddAppUxStrings runs 389 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 289 over it, 3.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddRuntimeStrings src/Localization/Localization.Runtime.vb:15— MethodTooLong — AddRuntimeStrings runs 385 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 285 over it, 3.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddMainStrings src/Localization/Localization.Main.vb:16— MethodTooLong — AddMainStrings runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddBroadcastStrings src/FastMediaSorterCompanion/Localization/Localization.Broadcast.vb:8— MethodTooLong — AddBroadcastStrings runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddSettingsStrings src/Localization/Localization.Settings.vb:10— MethodTooLong — AddSettingsStrings runs 352 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 252 over it, 3.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddEditorStrings src/Localization/Localization.Editor.vb:16— MethodTooLong — AddEditorStrings runs 325 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 225 over it, 3.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddOcrTabStrings src/Localization/Localization.OcrTab.vb:15— MethodTooLong — AddOcrTabStrings runs 319 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 219 over it, 3.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddSecureStrings src/Localization/Localization.Secure.vb:21— MethodTooLong — AddSecureStrings runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddWelcomeStrings src/Localization/Localization.Welcome.vb:17— MethodTooLong — AddWelcomeStrings runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddChromeStrings src/Localization/Localization.Chrome.vb:9— MethodTooLong — AddChromeStrings runs 312 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 212 over it, 3.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Main_Form.KeybUse src/Main_Form.KeyboardInput.vb:104— MethodTooLong — KeybUse runs 298 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 198 over it, 2.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: prober.run REDACTED:132— MethodTooLong — run runs 286 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 186 over it, 2.86× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddExchangeAdminStrings src/FastMediaSorterCompanion/Localization/Localization.ExchangeAdmin.vb:19— MethodTooLong — AddExchangeAdminStrings runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddAppUxStrings src/FastMediaSorterCompanion/Localization/Localization.AppUx.vb:15— MethodTooLong — AddAppUxStrings runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Localization.AddLiveBroadcastStrings src/Localization/Localization.LiveBroadcast.vb:8— MethodTooLong — AddLiveBroadcastStrings runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: src/Table_Form.ModernLayout.vb src/Table_Form.ModernLayout.vb:920— src/Table_Form.ModernLayout.vb changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 149 in Table_Form.ModernSettingTitle at line 920. 1 of those changes was a fix/bug commit, and the other 21 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Table_Form.ModernLayout.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.KeyboardInput.vb src/Main_Form.KeyboardInput.vb:104— src/Main_Form.KeyboardInput.vb changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 146 in Main_Form.KeybUse at line 104. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.KeyboardInput.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.MediaLoading.vb src/Main_Form.MediaLoading.vb:1460— src/Main_Form.MediaLoading.vb changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in Main_Form.UpdateCurrentFileAndDisplay at line 1460. 3 of those changes were fix/bug commits, and the other 15 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.MediaLoading.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.FileOperations.vb src/Main_Form.FileOperations.vb:1649— src/Main_Form.FileOperations.vb changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in Main_Form.FinishFileOp at line 1649. 1 of those changes was a fix/bug commit, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.FileOperations.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.RecipientsOverlay.vb src/Main_Form.RecipientsOverlay.vb:526— src/Main_Form.RecipientsOverlay.vb changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in Main_Form.ApplyRecipientsOverlayHealth at line 526. 1 of those changes was a fix/bug commit, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.RecipientsOverlay.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.Chrome.vb src/Main_Form.Chrome.vb:800— src/Main_Form.Chrome.vb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in Main_Form.SyncChromeItem at line 800. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.Chrome.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.VideoPlayer.vb src/Main_Form.VideoPlayer.vb:383— src/Main_Form.VideoPlayer.vb changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in Main_Form.PlayVideoWithVlcAsync at line 383. 1 of those changes was a fix/bug commit, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.VideoPlayer.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.OcrTranslate.vb src/Main_Form.OcrTranslate.vb:374— src/Main_Form.OcrTranslate.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Main_Form.RunOcrPipeline at line 374. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.OcrTranslate.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.FileScanning.vb src/Main_Form.FileScanning.vb:60— src/Main_Form.FileScanning.vb changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in Main_Form.BgWorker_DoWork at line 60. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.FileScanning.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.PerspectiveBackground.vb src/Main_Form.PerspectiveBackground.vb:353— src/Main_Form.PerspectiveBackground.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in Main_Form.Draw_Perspective at line 353. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.PerspectiveBackground.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Ocr/TesseractOcrEngine.vb src/Ocr/TesseractOcrEngine.vb:816— src/Ocr/TesseractOcrEngine.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in TesseractOcrEngine.ScoreAttempt at line 816. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Ocr/TesseractOcrEngine.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:122— src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in ShareConfigBuilder.Build at line 122. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Table_Form.vb src/Table_Form.vb:153— src/Table_Form.vb changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Table_Form.PrepareForDisplay at line 153. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Table_Form.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb:197— src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Share_Settings_Form.ApplyHostingState at line 197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/AppFileLogger.vb src/AppFileLogger.vb:90— src/AppFileLogger.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in AppFileLogger.Initialize at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/AppFileLogger.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Chrome/ChromeSurface.vb src/Chrome/ChromeSurface.vb:563— src/Chrome/ChromeSurface.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in ChromeSurface.PaintItemInk at line 563. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Chrome/ChromeSurface.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.MouseInput.vb src/Main_Form.MouseInput.vb:169— src/Main_Form.MouseInput.vb changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in Main_Form.MouseUse at line 169. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.MouseInput.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FastMediaSorterCompanion/Program.vb src/FastMediaSorterCompanion/Program.vb:62— src/FastMediaSorterCompanion/Program.vb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Program.Main at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/FastMediaSorterCompanion/Program.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb:573— src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PackageWizardForm.Rebuild at line 573. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: exchange-server/cmd/fms-exchange-server/args.go exchange-server/cmd/fms-exchange-server/args.go:38— exchange-server/cmd/fms-exchange-server/args.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 77 in main.parseArgs at line 38. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- exchange-server/cmd/fms-exchange-server/args.go`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/FastMediaSorterCompanion/Forms/MainWindow.vb src/FastMediaSorterCompanion/Forms/MainWindow.vb:528— src/FastMediaSorterCompanion/Forms/MainWindow.vb changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in MainWindow.SetBusy at line 528. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/FastMediaSorterCompanion/Forms/MainWindow.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Resources/ResourceSession.vb src/Resources/ResourceSession.vb:204— src/Resources/ResourceSession.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in ResourceSession.TryEnsureLocal at line 204. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Resources/ResourceSession.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Translate/OllamaTranslator.vb src/Translate/OllamaTranslator.vb:428— src/Translate/OllamaTranslator.vb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in OllamaTranslator.PullModelAsync at line 428. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Translate/OllamaTranslator.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Main_Form.ResourceOpen.vb src/Main_Form.ResourceOpen.vb:220— src/Main_Form.ResourceOpen.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Main_Form.ConnectAndEnterResource at line 220. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Main_Form.ResourceOpen.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Utils.vb src/Utils.vb:228— src/Utils.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in Utils.GetImageDimensions at line 228. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-15..2026-10-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-15 16:32:07 +02:00' --until='2026-10-13 16:32:07 +02:00' --full-history --no-merges -- src/Utils.vb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: src/Table_Form.ModernLayout.vb src/Table_Form.ModernLayout.vb— FileTooLong — 1973 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1473 over it, 3.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Main_Form.Chrome.vb src/Main_Form.Chrome.vb— FileTooLong — 1138 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 638 over it, 2.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Localization/Localization.Resources.vb src/Localization/Localization.Resources.vb— FileTooLong — 1099 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 599 over it, 2.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Chrome/ChromeSurface.vb src/Chrome/ChromeSurface.vb— FileTooLong — 1063 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 563 over it, 2.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Main_Form.MediaLoading.vb src/Main_Form.MediaLoading.vb— FileTooLong — 1006 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 506 over it, 2.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Main_Form.VideoControls.vb src/Main_Form.VideoControls.vb— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Table_Form.ExpandedSettings.vb src/Table_Form.ExpandedSettings.vb— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Main_Form.FileOperations.vb src/Main_Form.FileOperations.vb— FileTooLong — 962 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 462 over it, 1.92× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Resource_List_Panel.vb src/Resource_List_Panel.vb— FileTooLong — 917 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 417 over it, 1.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Ocr/TesseractOcrEngine.vb src/Ocr/TesseractOcrEngine.vb— FileTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 351 over it, 1.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Localization/Localization.Manager.vb src/FastMediaSorterCompanion/Localization/Localization.Manager.vb— FileTooLong — 810 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 310 over it, 1.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Image_Editor_Form.Tools.vb src/Image_Editor_Form.Tools.vb— FileTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 298 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Welcome/Welcome_Form.vb src/Welcome/Welcome_Form.vb— FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 295 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Localization/Localization.Share.vb src/FastMediaSorterCompanion/Localization/Localization.Share.vb— FileTooLong — 785 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 285 over it, 1.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Forms/Share_Settings_Form.ExchangeAdmin.vb src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb— FileTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 267 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Forms/PackageWizardForm.vb src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb— FileTooLong — 766 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 266 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Localization/Localization.Files.vb src/Localization/Localization.Files.vb— FileTooLong — 759 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 259 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Support/LogPackage.vb src/Support/LogPackage.vb— FileTooLong — 748 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 248 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Exchange_Devices_Panel.vb src/Exchange_Devices_Panel.vb— FileTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 237 over it, 1.47× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Image_Panel_Form.Modern.vb src/Image_Panel_Form.Modern.vb— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Main_Form.RecipientsOverlay.vb src/Main_Form.RecipientsOverlay.vb— FileTooLong — 715 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 215 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: FastMediaSorterCompanion/TrayContext.vb src/FastMediaSorterCompanion/TrayContext.vb— FileTooLong — 690 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 190 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Core/ExchangeDeviceAgent.vb src/FastMediaSorterCompanion/Core/ExchangeDeviceAgent.vb— FileTooLong — 643 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 143 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/FileDetails.vb src/FileDetails.vb— FileTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 139 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/Table_Form.Ocr.vb src/Table_Form.Ocr.vb— FileTooLong — 631 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 131 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
TooManyMethods: Main_Form src/Main_Form.Archive.vb— TooManyMethods — 17544 significant lines (blank, comment-only and punctuation-only lines excluded), 1065 methods. The bar is 30 methods; this is 1035 over it, 35.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Share_Settings_Form src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb— TooManyMethods — 3903 significant lines (blank, comment-only and punctuation-only lines excluded), 240 methods. The bar is 30 methods; this is 210 over it, 8.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindow src/FastMediaSorterCompanion/Forms/MainWindow.Access.vb— TooManyMethods — 2204 significant lines (blank, comment-only and punctuation-only lines excluded), 155 methods. The bar is 30 methods; this is 125 over it, 5.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Table_Form src/Table_Form.Ocr.vb— TooManyMethods — 2335 significant lines (blank, comment-only and punctuation-only lines excluded), 148 methods. The bar is 30 methods; this is 118 over it, 4.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Table_Form src/Table_Form.ExpandedSettings.vb— TooManyMethods — 2932 significant lines (blank, comment-only and punctuation-only lines excluded), 113 methods. The bar is 30 methods; this is 83 over it, 3.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExchangeAdminText src/FastMediaSorterCompanion/Core/ExchangeAdminText.vb— TooManyMethods — 371 significant lines (blank, comment-only and punctuation-only lines excluded), 87 methods. The bar is 30 methods; this is 57 over it, 2.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Image_Editor_Form src/Image_Editor_Form.Tools.vb— TooManyMethods — 1376 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ChromeSurface src/Chrome/ChromeSurface.vb— TooManyMethods — 1057 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Localization src/Localization/Localization.Activation.vb— TooManyMethods — 9903 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Image_Panel_Form src/Image_Panel_Form.Details.vb— TooManyMethods — 1403 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Resource_List_Panel src/Resource_List_Panel.vb— TooManyMethods — 894 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Welcome_Form src/Welcome/Welcome_Form.vb— TooManyMethods — 790 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Server_Welcome_Form src/FastMediaSorterCompanion/Forms/Server_Welcome_Form.ExchangeFirstRun.vb— TooManyMethods — 740 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PackageWizardForm src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb— TooManyMethods — 759 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Main_Form src/Main_Form.Iconography.vb— TooManyMethods — 676 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Exchange_Devices_Panel src/Exchange_Devices_Panel.vb— TooManyMethods — 719 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExchangeText src/FastMediaSorterCompanion/Core/ExchangeText.vb— TooManyMethods — 245 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Dir exchange-server/internal/directory/directory.go:161— TooManyMethods — 44 methods, declared across 3 files: directory/ops.go (33), directory/directory.go (10), directory/protection.go (1). The bar is 30 methods; this is 14 over it, 1.47× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ShareText src/FastMediaSorterCompanion/Core/ShareText.vb— TooManyMethods — 233 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TesseractOcrEngine src/Ocr/TesseractOcrEngine.vb— TooManyMethods — 818 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ModernViewerPreferences src/ModernViewerPreferences.vb— TooManyMethods — 596 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OptionalRuntimeManager src/OptionalRuntimeManager.vb— TooManyMethods — 482 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExchangeEntryText src/Resources/ExchangeEntryText.vb— TooManyMethods — 180 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LogPackage src/Support/LogPackage.vb— TooManyMethods — 738 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HostingProbesLive src/Support/HostingProbesLive.vb— TooManyMethods — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (5 lines × 2) src/Resources/ExchangeDevices.vb:311— src/Resources/ExchangeDevices.vb:311-315 | src/Resources/ExchangeDevices.vb:323-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/Resources/TransferPlan.vb:401— src/Resources/TransferPlan.vb:401-405 | src/Resources/TransferPlan.vb:430-434 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/DocHtmlTranslateLauncher.vb:51— src/DocHtmlTranslateLauncher.vb:51-55 | src/Translate/OllamaManager.vb:31-35 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/Chrome/ChromeSurface.vb:702— src/Chrome/ChromeSurface.vb:702-706 | src/Chrome/ChromeSurface.vb:736-740 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/Table_Form.SettingsDiscovery.vb:77— src/Table_Form.SettingsDiscovery.vb:77-81 | src/Table_Form.SettingsDiscovery.vb:85-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/Icons/StepArt.vb:320— src/Icons/StepArt.vb:320-324 | src/Table_Form.ModernLayout.vb:2362-2366 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:220— src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:220-224 | src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:405-409 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:412` calls `literal` and `src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:227` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:110— src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:110-114 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:254-258 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb` and `src/FastMediaSorterCompanion/Core/NetworkInfo.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/LiveBroadcast/Producer/TsChunker.vb:228— src/LiveBroadcast/Producer/TsChunker.vb:228-232 | src/LiveBroadcast/Producer/TsChunker.vb:246-250 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Forms/Server_Welcome_Form.vb:207— src/FastMediaSorterCompanion/Forms/Server_Welcome_Form.vb:207-211 | src/Welcome/Welcome_Form.vb:270-274 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:208— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:208-212 | src/Resources/ExportWriter.vb:172-176 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Forms/Exchange_Connection_String_Form.vb:56— src/FastMediaSorterCompanion/Forms/Exchange_Connection_String_Form.vb:56-60 | src/FastMediaSorterCompanion/Forms/Exchange_Link_Form.vb:37-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/Image_Editor_Form.Tools.vb:321— src/Image_Editor_Form.Tools.vb:321-325 | src/Image_Panel_Form.Modern.vb:202-206 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/FastMediaSorterCompanion/Localization/Localization.ExchangeJoin.vb:13— src/FastMediaSorterCompanion/Localization/Localization.ExchangeJoin.vb:13-17 | src/Localization/Localization.ExchangeEntries.vb:33-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/Main_Form.ShareLauncher.vb:406— src/Main_Form.ShareLauncher.vb:406-413 | src/Resources/ExchangeDevices.vb:116-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/Resources/SftpProvider.vb:673— src/Resources/SftpProvider.vb:673-680 | src/Resources/SmbProvider.vb:161-168 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/Video/Video_Convert_Form.vb:41— src/Video/Video_Convert_Form.vb:41-48 | src/Video/Video_Convert_Form.vb:158-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) src/FastMediaSorterCompanion/Forms/SendLogsFlow.vb:184— src/FastMediaSorterCompanion/Forms/SendLogsFlow.vb:184-191 | src/Table_Form.SendLogs.vb:297-304 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:232— src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:232-239 | src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:481-488 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:97— src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:97-104 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:195-202 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb` and `src/FastMediaSorterCompanion/Core/NetworkInfo.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/FastMediaSorterCompanion/Core/NetworkInfo.vb:192` calls `real` and `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:94` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:223— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:223-230 | src/Resources/ExportWriter.vb:187-194 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:309— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:309-316 | src/Resources/ExportWriter.vb:273-280 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/Image_Editor_Form.vb:303— src/Image_Editor_Form.vb:303-310 | src/Image_Panel_Form.Modern.vb:384-391 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) exchange-server/internal/directory/ops.go:230— exchange-server/internal/directory/ops.go:230-237 | exchange-server/internal/directory/ops.go:250-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/internal/directory/ops.go:230` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) exchange-server/internal/rendezvous/conn.go:251— exchange-server/internal/rendezvous/conn.go:251-258 | exchange-server/internal/rendezvous/conn.go:271-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) exchange-server/cmd/fms-exchange-server/setendpoint.go:30— exchange-server/cmd/fms-exchange-server/setendpoint.go:30-37 | exchange-server/cmd/fms-exchange-server/tlscmd.go:71-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/FastMediaSorterCompanion/Localization/Localization.Activation.vb:127— src/FastMediaSorterCompanion/Localization/Localization.Activation.vb:127-136 | src/Localization/Localization.Activation.vb:30-39 — before extracting anything, compare `src/FastMediaSorterCompanion/Localization/Localization.Activation.vb` and `src/Localization/Localization.Activation.vb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/FastMediaSorterCompanion/Localization/Localization.Activation.vb:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/FastMediaSorterCompanion/Core/NetworkInfo.vb:23— src/FastMediaSorterCompanion/Core/NetworkInfo.vb:23-32 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:143-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/AudioMetadata.vb:38— src/AudioMetadata.vb:38-47 | src/FileDetails.vb:565-574 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) src/Imaging/EdgeSampler.vb:117— src/Imaging/EdgeSampler.vb:117-126 | src/Imaging/EdgeSampler.vb:131-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/ExpandedSettingsDialogs.vb:73— src/ExpandedSettingsDialogs.vb:73-82 | src/ExpandedSettingsDialogs.vb:237-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/Streams/StreamCatalogValidator.vb:85— src/Streams/StreamCatalogValidator.vb:85-94 | src/Streams/StreamCatalogValidator.vb:95-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:246— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:246-255 | src/Resources/ExportWriter.vb:210-219 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:343— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:343-352 | src/Resources/ExportWriter.vb:307-316 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) src/FastMediaSorterCompanion/Forms/MainWindow.DiskMenu.vb:72— src/FastMediaSorterCompanion/Forms/MainWindow.DiskMenu.vb:72-82 | src/FastMediaSorterCompanion/Forms/MainWindow.DiskMenu.vb:107-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) src/Table_Form.ExpandedSettings.vb:625— src/Table_Form.ExpandedSettings.vb:625-635 | src/Table_Form.ExpandedSettings.vb:657-666 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Table_Form.ExpandedSettings.vb:625` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) exchange-server/cmd/fms-exchange-server/args.go:79— exchange-server/cmd/fms-exchange-server/args.go:79-88 | exchange-server/cmd/fms-exchange-server/args.go:123-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/cmd/fms-exchange-server/args.go:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
ClassTooLong: Localization src/FastMediaSorterCompanion/Localization/Localization.Activation.vb— ClassTooLong — 5509 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 5109 over it, 13.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WasapiAudioSource src/FastMediaSorterCompanion/Core/WasapiAudioSource.vb— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Live_Broadcast_Form src/FastMediaSorterCompanion/Forms/Live_Broadcast_Form.vb— ClassTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 145 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SftpProvider src/Resources/SftpProvider.vb— ClassTooLong — 539 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 139 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExchangePublisher src/FastMediaSorterCompanion/Core/ExchangePublisher.vb— ClassTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 128 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ArchiveSession src/Archives/ArchiveSession.vb— ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 67 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ChromeMenu src/Chrome/ChromeMenu.vb— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Share_Broadcasts_Form src/FastMediaSorterCompanion/Forms/Share_Broadcasts_Form.vb— ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 18 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Manager_Welcome_Form src/FastMediaSorterCompanion/Forms/Manager_Welcome_Form.vb— ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 9 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LiveBroadcastReader src/LiveBroadcast/LiveBroadcastReader.vb— ClassTooLong — 403 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 3 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Low cohesion: DetailsList (LCOM4 9) src/Image_Panel_Form.Details.vb:21— DetailsList's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Main_Form (LCOM4 5) src/Main_Form.Archive.vb:21— Main_Form's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LocalProvider (LCOM4 5) src/Resources/LocalProvider.vb:17— LocalProvider's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SectionHeader (LCOM4 5) src/FastMediaSorterCompanion/Forms/CollapsibleSection.vb:234— SectionHeader's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Share_Settings_Form (LCOM4 5) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb:10— Share_Settings_Form's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BarLabel (LCOM4 4) src/Main_Form.VideoControls.vb:917— BarLabel's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ExchangeLocalJoinPorts (LCOM4 4) src/FastMediaSorterCompanion/Core/ExchangeLocalJoin.vb:166— ExchangeLocalJoinPorts's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Resource_Edit_Form (LCOM4 4) src/Resource_Edit_Form.vb:20— Resource_Edit_Form's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Resource_Export_Form (LCOM4 4) src/Resource_Export_Form.vb:16— Resource_Export_Form's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (7 lines × 2) src/Resources/ExchangeTunnel.vb:212— src/Resources/ExchangeTunnel.vb:212-218 | src/Resources/ExchangeTunnel.vb:256-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Table_Form.ModernLayout.vb:1952— src/Table_Form.ModernLayout.vb:1952-1958 | src/Table_Form.ModernLayout.vb:1971-1977 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/FastMediaSorterCompanion/Forms/InternetAccessForm.vb:243— src/FastMediaSorterCompanion/Forms/InternetAccessForm.vb:243-249 | src/FastMediaSorterCompanion/Forms/MainWindow.Access.vb:644-650 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/Ocr/TesseractOcrEngine.vb:671— src/Ocr/TesseractOcrEngine.vb:671-677 | src/Ocr/TesseractOcrEngine.vb:697-703 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Ocr/TesseractOcrEngine.vb:706` calls `CLng` and `src/Ocr/TesseractOcrEngine.vb:679` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) src/Exchange/ExchangeTls.vb:126— src/Exchange/ExchangeTls.vb:126-132 | src/FastMediaSorterCompanion/Core/ExchangeExport.vb:53-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) src/FastMediaSorterCompanion/Forms/Live_Broadcast_Form.vb:88— src/FastMediaSorterCompanion/Forms/Live_Broadcast_Form.vb:88-94 | src/FastMediaSorterCompanion/Forms/Share_Broadcasts_Form.vb:44-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/FastMediaSorterCompanion/Core/ServerFeatures.vb:330— src/FastMediaSorterCompanion/Core/ServerFeatures.vb:330-336 | src/FastMediaSorterCompanion/Core/ServiceControl.vb:531-537 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/Main_Form.PerspectiveBackground.vb:324— src/Main_Form.PerspectiveBackground.vb:324-329 | src/Main_Form.PerspectiveBackground.vb:338-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/FastMediaSorterCompanion/Core/ExchangeAccountPasswordStore.vb:117— src/FastMediaSorterCompanion/Core/ExchangeAccountPasswordStore.vb:117-122 | src/FastMediaSorterCompanion/Core/ExchangeProducerStore.vb:160-165 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/Chrome/ChromeTheme.vb:213— src/Chrome/ChromeTheme.vb:213-218 | src/Theming/RecipientPalette.vb:97-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Chrome/ChromeTheme.vb:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Resources/TransferPlan.vb:476— src/Resources/TransferPlan.vb:476-481 | src/Resources/TransferPlan.vb:489-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:243— src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:243-248 | src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:502-507 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/FastMediaSorterCompanion/Localization/Localization.ExchangeJoin.vb:48— src/FastMediaSorterCompanion/Localization/Localization.ExchangeJoin.vb:48-53 | src/Localization/Localization.ExchangeEntries.vb:41-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) exchange-server/internal/directory/ops.go:484— exchange-server/internal/directory/ops.go:484-489 | exchange-server/internal/directory/ops.go:527-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/internal/directory/ops.go:484` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
FunctionTooLong: main.connVectors exchange-server/cmd/exchange-vectors/connstr.go:72— FunctionTooLong — connVectors runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: main.generateRecords exchange-server/cmd/exchange-vectors/records.go:94— FunctionTooLong — generateRecords runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: main.parseArgs exchange-server/cmd/fms-exchange-server/args.go:38— FunctionTooLong — parseArgs runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: main.serveCore REDACTED:97— FunctionTooLong — serveCore runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wave-particles.create assets/wave-particles.js:251— FunctionTooLong — create runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (14 lines × 2) src/Main_Form.LiveBroadcast.vb:291— src/Main_Form.LiveBroadcast.vb:291-304 | src/Main_Form.VideoPlayer.vb:650-663 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) src/FailureText.vb:145— src/FailureText.vb:145-158 | src/PathFailure.vb:172-185 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:259— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:259-272 | src/Resources/ExportWriter.vb:223-236 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) exchange-server/internal/testkit/device.go:199— exchange-server/internal/testkit/device.go:199-212 | exchange-server/internal/testkit/device.go:220-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/internal/testkit/device.go:220` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:112— REDACTED:112-125 | REDACTED:74-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:112` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) src/FastMediaSorterCompanion/Localization/Localization.ServerWelcome.vb:36— src/FastMediaSorterCompanion/Localization/Localization.ServerWelcome.vb:36-50 | src/Localization/Localization.Welcome.vb:284-298 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) src/Main_Form.PerspectiveBackground.vb:266— src/Main_Form.PerspectiveBackground.vb:266-280 | src/Main_Form.PerspectiveBackground.vb:294-308 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/FastMediaSorterCompanion/Forms/Exchange_Connection_String_Form.vb:119— src/FastMediaSorterCompanion/Forms/Exchange_Connection_String_Form.vb:119-133 | src/FastMediaSorterCompanion/Forms/Exchange_Link_Form.vb:73-87 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) src/Main_Form.MediaLoading.vb:822— src/Main_Form.MediaLoading.vb:822-836 | src/Main_Form.MediaLoading.vb:924-938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:751— src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:751-762 | src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:802-813 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:751` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Imaging/EdgeSampler.vb:165— src/Imaging/EdgeSampler.vb:165-176 | src/Imaging/EdgeSampler.vb:186-197 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:101— src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:101-112 | src/FastMediaSorterCompanion/Forms/Exchange_Password_Form.vb:101-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:102— src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:102-115 | src/FastMediaSorterCompanion/Forms/Exchange_Link_Form.vb:54-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/FastMediaSorterCompanion/Forms/Exchange_Link_Form.vb:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) src/FastMediaSorterCompanion/Forms/Broadcast_Create_Form.vb:54— src/FastMediaSorterCompanion/Forms/Broadcast_Create_Form.vb:54-62 | src/FastMediaSorterCompanion/Forms/Share_Status_Form.vb:49-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:100— src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:100-108 | src/FastMediaSorterCompanion/Forms/Exchange_Server_Wizard_Form.vb:103-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/FastMediaSorterCompanion/Forms/Exchange_Server_Wizard_Form.vb:102` calls `Wipe` and `src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:99` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:276— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:276-284 | src/Resources/ExportWriter.vb:240-248 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) exchange-server/internal/tlsid/manage.go:79— exchange-server/internal/tlsid/manage.go:79-87 | exchange-server/internal/tlsid/tlsid.go:86-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) src/Main_Form.FileAssociation.vb:115— src/Main_Form.FileAssociation.vb:115-131 | src/Main_Form.FileAssociation.vb:175-191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) src/FastMediaSorterCompanion/Forms/Share_Access_Test_Form.vb:65— src/FastMediaSorterCompanion/Forms/Share_Access_Test_Form.vb:65-81 | src/FastMediaSorterCompanion/Forms/Share_Enable_Form.vb:44-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) exchange-server/cmd/exchange-fakeproducer/main.go:96— exchange-server/cmd/exchange-fakeproducer/main.go:96-112 | REDACTED:130-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/cmd/exchange-fakeproducer/main.go:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. Check import visibility before settling on that home: `REDACTED` sits under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
Duplicated block (11 lines × 2) src/Main_Form.ToolbarOverflow.vb:219— src/Main_Form.ToolbarOverflow.vb:219-229 | src/Main_Form.ToolbarOverflow.vb:258-268 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/Main_Form.ToolbarOverflow.vb:184— src/Main_Form.ToolbarOverflow.vb:184-195 | src/Main_Form.ToolbarOverflow.vb:241-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 2) src/Exchange/ExchangeFeatures.vb:32— src/Exchange/ExchangeFeatures.vb:32-42 | src/LiveBroadcast/LiveBroadcastFeatures.vb:32-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 3) src/Chrome/ChromeSurface.vb:702— src/Chrome/ChromeSurface.vb:702-706 | src/Chrome/ChromeSurface.vb:715-719 | src/Chrome/ChromeSurface.vb:736-740 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:97— src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:97-101 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:35-39 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:195-199 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb` and `src/FastMediaSorterCompanion/Core/NetworkInfo.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/FastMediaSorterCompanion/Core/NetworkInfo.vb:192` calls `real` and `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:94` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) src/Main_Form.OcrTranslate.vb:841— src/Main_Form.OcrTranslate.vb:841-845 | src/Ocr/OcrTextFilter.vb:151-155 | src/Translate/TranslationQuality.vb:266-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (18 lines × 2) src/Image_Editor_Form.Tools.vb:754— src/Image_Editor_Form.Tools.vb:754-771 | src/Image_Editor_Form.Tools.vb:1066-1084 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:288— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:288-305 | src/Resources/ExportWriter.vb:252-269 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 4) exchange-server/internal/testkit/device.go:113— exchange-server/internal/testkit/device.go:113-120 | exchange-server/internal/testkit/device.go:200-207 | exchange-server/internal/testkit/device.go:221-228 | REDACTED:66-73 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `exchange-server/internal/testkit/device.go:113` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `exchange-server/internal/testkit/device.go:122` calls `Close` and `exchange-server/internal/testkit/device.go:209` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) exchange-server/cmd/fms-exchange-server/setendpoint.go:30— exchange-server/cmd/fms-exchange-server/setendpoint.go:30-37 | exchange-server/cmd/fms-exchange-server/setlisten.go:26-33 | exchange-server/cmd/fms-exchange-server/setportrange.go:40-47 | exchange-server/cmd/fms-exchange-server/tlscmd.go:71-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Appears unstructured (no recognised architecture) — ~155.1k production LoC (2456 types) across 3 project(s) / 43 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
Main_Form.KeybUse (cyclomatic 146) src/Main_Form.KeyboardInput.vb:104— Main_Form.KeybUse has cyclomatic complexity 146 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
prober.run (cyclomatic 111) REDACTED:132— prober.run has cyclomatic complexity 111 (threshold 15). Of this number, 16 points are the body's own statements and 95 belong to 14 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StreamCatalogValidator.ValidateArchive (cyclomatic 87) src/Streams/StreamCatalogValidator.vb:74— StreamCatalogValidator.ValidateArchive has cyclomatic complexity 87 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
main.parseArgs (cyclomatic 77) exchange-server/cmd/fms-exchange-server/args.go:38— main.parseArgs has cyclomatic complexity 77 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Main_Form.SyncChromeItem (cyclomatic 74) src/Main_Form.Chrome.vb:800— Main_Form.SyncChromeItem has cyclomatic complexity 74 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.FinishFileOp (cyclomatic 69) src/Main_Form.FileOperations.vb:1649— Main_Form.FinishFileOp has cyclomatic complexity 69 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
EpubMetadata.Read (cyclomatic 65) src/Documents/EpubMetadata.vb:58— EpubMetadata.Read has cyclomatic complexity 65 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
M3uPlaylistReader.MapLanguageToEnglishName (cyclomatic 64) src/Streams/M3uPlaylistReader.vb:480— M3uPlaylistReader.MapLanguageToEnglishName has cyclomatic complexity 64 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
LiveBroadcastReader.ReadJsonBytes (cyclomatic 57) src/LiveBroadcast/LiveBroadcastReader.vb:279— LiveBroadcastReader.ReadJsonBytes has cyclomatic complexity 57 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
wave-particles.create (cyclomatic 57) assets/wave-particles.js:251— wave-particles.create has cyclomatic complexity 57 (threshold 15). Most of this is not in the body itself: 10 of the 57 points are its own statements and the rest belongs to 15 function items inside it that branch (resize, tick, readSurface, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Main_Form.UpdateCurrentFileAndDisplay (cyclomatic 54) src/Main_Form.MediaLoading.vb:1460— Main_Form.UpdateCurrentFileAndDisplay has cyclomatic complexity 54 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.RunHotkeyAction (cyclomatic 53) src/Main_Form.CustomHotkeys.vb:88— Main_Form.RunHotkeyAction has cyclomatic complexity 53 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.StartBatchAsync (cyclomatic 48) src/Main_Form.Batch.vb:215— Main_Form.StartBatchAsync has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeMenuRules.ResolveKey (cyclomatic 48) src/Chrome/ChromeMenuRules.vb:105— ChromeMenuRules.ResolveKey has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
LiveBroadcastController.Start (cyclomatic 48) src/LiveBroadcast/Producer/LiveProducerController.vb:139— LiveBroadcastController.Start has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.UpdateFileIndexAndList (cyclomatic 46) src/Main_Form.MediaLoading.vb:450— Main_Form.UpdateFileIndexAndList has cyclomatic complexity 46 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeSurface.PaintItemInk (cyclomatic 45) src/Chrome/ChromeSurface.vb:563— ChromeSurface.PaintItemInk has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.Draw_Perspective (cyclomatic 44) src/Main_Form.PerspectiveBackground.vb:353— Main_Form.Draw_Perspective has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeProducerStore.Load (cyclomatic 44) src/FastMediaSorterCompanion/Core/ExchangeProducerStore.vb:153— ExchangeProducerStore.Load has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceSession.TryEnsureLocal (cyclomatic 43) src/Resources/ResourceSession.vb:204— ResourceSession.TryEnsureLocal has cyclomatic complexity 43 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TesseractOcrEngine.ScoreAttempt (cyclomatic 42) src/Ocr/TesseractOcrEngine.vb:816— TesseractOcrEngine.ScoreAttempt has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
StreamCatalogCli.Run (cyclomatic 42) src/Streams/StreamCatalogCli.vb:59— StreamCatalogCli.Run has cyclomatic complexity 42 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ApplyRecipientsOverlayHealth (cyclomatic 41) src/Main_Form.RecipientsOverlay.vb:526— Main_Form.ApplyRecipientsOverlayHealth has cyclomatic complexity 41 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ShareConfigBuilder.Build (cyclomatic 40) src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:122— ShareConfigBuilder.Build has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.ApplyHostingState (cyclomatic 39) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb:197— Share_Settings_Form.ApplyHostingState has cyclomatic complexity 39 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Dir.Publish (cyclomatic 39) exchange-server/internal/directory/ops.go:280— Dir.Publish has cyclomatic complexity 39 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Utils.GetImageDimensions (cyclomatic 38) src/Utils.vb:228— Utils.GetImageDimensions has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsSftpCode.TryParse (cyclomatic 38) src/Exchange/FmsSftpCode.vb:123— FmsSftpCode.TryParse has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.ApplyModernPaletteToTree (cyclomatic 38) src/Table_Form.ModernLayout.vb:2128— Table_Form.ApplyModernPaletteToTree has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: Table_Form.ModernSettingTitle (cyclomatic 149) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
BroadcastConfigBuilder.Build (cyclomatic 37) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:54— BroadcastConfigBuilder.Build has cyclomatic complexity 37 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.BgWorker_DoWork (cyclomatic 36) src/Main_Form.FileScanning.vb:60— Main_Form.BgWorker_DoWork has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsConfigReader.ReadRoots (cyclomatic 36) src/Resources/FmsConfigReader.vb:452— FmsConfigReader.ReadRoots has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AppFileLogger.Initialize (cyclomatic 35) src/AppFileLogger.vb:90— AppFileLogger.Initialize has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.DisplayPdfPage (cyclomatic 35) src/Main_Form.PdfView.vb:92— Main_Form.DisplayPdfPage has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ChromeHandleKey (cyclomatic 35) src/Main_Form.Chrome.vb:1321— Main_Form.ChromeHandleKey has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeGroupModel.Build (cyclomatic 35) src/FastMediaSorterCompanion/Core/ExchangeGroupModel.vb:110— ExchangeGroupModel.Build has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangePublishPlan.Build (cyclomatic 35) src/FastMediaSorterCompanion/Core/ExchangePublishPlan.vb:129— ExchangePublishPlan.Build has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.ApplyExchangeState (cyclomatic 35) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:286— Share_Settings_Form.ApplyExchangeState has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.LoadEmbeddedMp3Cover (cyclomatic 34) src/Main_Form.AudioView.vb:389— Main_Form.LoadEmbeddedMp3Cover has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.LocalizeSettingsDiscovery (cyclomatic 34) src/Table_Form.SettingsDiscovery.vb:263— Table_Form.LocalizeSettingsDiscovery has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ThemeApplier.ApplyOne (cyclomatic 34) src/Theming/ThemeApplier.vb:159— ThemeApplier.ApplyOne has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.BuildChromeRow (cyclomatic 34) src/Main_Form.Chrome.vb:282— Main_Form.BuildChromeRow has cyclomatic complexity 34 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.PersistSettings (cyclomatic 33) src/Main_Form.Lifecycle.vb:1538— Main_Form.PersistSettings has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TextScriptHeuristics.ClassifyScript (cyclomatic 33) src/Translate/ITranslator.vb:320— TextScriptHeuristics.ClassifyScript has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: TranslateLang.DisplayName (cyclomatic 79) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SvgPathData.AppendTo (cyclomatic 33) src/Icons/SvgPathData.vb:27— SvgPathData.AppendTo has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.Chrome_Timer_Tick (cyclomatic 33) src/Main_Form.Chrome.vb:1043— Main_Form.Chrome_Timer_Tick has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ArchiveSession.RunSequentialPass (cyclomatic 32) src/Archives/ArchiveSession.vb:554— ArchiveSession.RunSequentialPass has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
WasapiAudioSource.CaptureLoop (cyclomatic 32) src/FastMediaSorterCompanion/Core/WasapiAudioSource.vb:180— WasapiAudioSource.CaptureLoop has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ConnectAndEnterResource (cyclomatic 32) src/Main_Form.ResourceOpen.vb:220— Main_Form.ConnectAndEnterResource has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.LocalizeModernSettingRows (cyclomatic 32) src/Table_Form.ModernLayout.vb:837— Table_Form.LocalizeModernSettingRows has cyclomatic complexity 32 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: Table_Form.ModernSettingTitle (cyclomatic 149) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Image_Panel_Form.OnFormKeyDown (cyclomatic 31) src/Image_Panel_Form.Modern.vb:751— Image_Panel_Form.OnFormKeyDown has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.UpdateControlVisibility (cyclomatic 30) src/Main_Form.MediaLoading.vb:1363— Main_Form.UpdateControlVisibility has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.Form1_Load (cyclomatic 30) src/Main_Form.Lifecycle.vb:764— Main_Form.Form1_Load has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
OllamaTranslator.PullModelAsync (cyclomatic 30) src/Translate/OllamaTranslator.vb:428— OllamaTranslator.PullModelAsync has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ProtectedConfigWriter.Publish (cyclomatic 30) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:77— ProtectedConfigWriter.Publish has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Program.Main (cyclomatic 30) src/FastMediaSorterCompanion/Program.vb:62— Program.Main has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExportWriter.Publish (cyclomatic 30) src/Resources/ExportWriter.vb:73— ExportWriter.Publish has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
LiveBroadcastReader.ParseEndpoint (cyclomatic 29) src/LiveBroadcast/LiveBroadcastReader.vb:449— LiveBroadcastReader.ParseEndpoint has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.MouseUse (cyclomatic 29) src/Main_Form.MouseInput.vb:169— Main_Form.MouseUse has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.CloseTeardown (cyclomatic 29) src/Main_Form.Lifecycle.vb:1317— Main_Form.CloseTeardown has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
StreamCatalogProducer.Build (cyclomatic 29) src/Streams/StreamCatalogProducer.vb:52— StreamCatalogProducer.Build has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeMenu.PreFilterMessage (cyclomatic 29) src/Chrome/ChromeMenu.vb:399— ChromeMenu.PreFilterMessage has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Server_Welcome_Form.AdvanceExchangeAsync (cyclomatic 29) src/FastMediaSorterCompanion/Forms/Server_Welcome_Form.ExchangeFirstRun.vb:224— Server_Welcome_Form.AdvanceExchangeAsync has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Exchange_Devices_Panel.OnDrawItem (cyclomatic 29) src/Exchange_Devices_Panel.vb:433— Exchange_Devices_Panel.OnDrawItem has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Resource_Edit_Form.Confirm (cyclomatic 29) src/Resource_Edit_Form.vb:230— Resource_Edit_Form.Confirm has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExifReader.TryRead (cyclomatic 28) src/FileDetails.vb:641— ExifReader.TryRead has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: FileDetails.VideoCodecName (cyclomatic 34) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Main_Form.RunOcrPipeline (cyclomatic 28) src/Main_Form.OcrTranslate.vb:374— Main_Form.RunOcrPipeline has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TextFileReader.DetectEncoding (cyclomatic 28) src/Documents/TextFileReader.vb:176— TextFileReader.DetectEncoding has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
main.connVectors (cyclomatic 28) exchange-server/cmd/exchange-vectors/connstr.go:72— main.connVectors has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 10 of the 28 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 91, 115, 134, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LiveHttpPlaybackSession.OpenAsync (cyclomatic 27) src/LiveBroadcast/LiveHttpPlaybackSession.vb:200— LiveHttpPlaybackSession.OpenAsync has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ThemeApplier.OnConvertedButtonPaint (cyclomatic 27) src/Theming/ThemeApplier.vb:445— ThemeApplier.OnConvertedButtonPaint has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeTlsTransport.OpenAsync (cyclomatic 27) src/Exchange/ExchangeTls.vb:213— ExchangeTlsTransport.OpenAsync has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
testkit.StartServer (cyclomatic 27) exchange-server/internal/testkit/env.go:108— testkit.StartServer has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Main_Form.PlayVideoWithVlcAsync (cyclomatic 26) src/Main_Form.VideoPlayer.vb:383— Main_Form.PlayVideoWithVlcAsync has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.BuildRecipientsOverlay (cyclomatic 26) src/Main_Form.RecipientsOverlay.vb:206— Main_Form.BuildRecipientsOverlay has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ReadShowMediaFile (cyclomatic 26) src/Main_Form.MediaLoading.vb:281— Main_Form.ReadShowMediaFile has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.HandlePictureBoxMouseDown (cyclomatic 26) src/Main_Form.MouseInput.vb:16— Main_Form.HandlePictureBoxMouseDown has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.PaintTextDocument (cyclomatic 26) src/Main_Form.TextView.vb:95— Main_Form.PaintTextDocument has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeMenu.HandleKey (cyclomatic 26) src/Chrome/ChromeMenu.vb:351— ChromeMenu.HandleKey has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeAgentStateInfo.TryParse (cyclomatic 26) src/Exchange/ExchangeAgentChannel.vb:90— ExchangeAgentStateInfo.TryParse has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.Parse (cyclomatic 26) src/Exchange/ExchangeConnectionString.vb:149— ExchangeConnectionString.Parse has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.TryCanonicalIPv6 (cyclomatic 26) src/Exchange/ExchangeConnectionString.vb:374— ExchangeConnectionString.TryCanonicalIPv6 has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TesseractOcrEngine.RecognizeAttempts (cyclomatic 25) src/Ocr/TesseractOcrEngine.vb:186— TesseractOcrEngine.RecognizeAttempts has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsConfigReader.ReadAccessPaths (cyclomatic 25) src/Resources/FmsConfigReader.vb:412— FmsConfigReader.ReadAccessPaths has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ChromeConfigure (cyclomatic 25) src/Main_Form.Chrome.vb:623— Main_Form.ChromeConfigure has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ShareConfigBuilder.RootJson (cyclomatic 25) src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:310— ShareConfigBuilder.RootJson has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEnvelopeCodec.ReadMember (cyclomatic 25) src/Exchange/ExchangeEnvelope.vb:504— ExchangeEnvelopeCodec.ReadMember has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceLocator.TryParse (cyclomatic 24) src/Resources/ResourceRegistry.vb:221— ResourceLocator.TryParse has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SmbConnectionManager.AcquireLease (cyclomatic 24) src/Resources/SmbConnectionLease.vb:246— SmbConnectionManager.AcquireLease has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.BatchRunner_ItemFinished (cyclomatic 24) src/Main_Form.Batch.vb:581— Main_Form.BatchRunner_ItemFinished has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FailureText.CauseOf (cyclomatic 24) src/FailureText.vb:51— FailureText.CauseOf has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Image_Editor_Form.Image_Editor_Form_KeyDown (cyclomatic 24) src/Image_Editor_Form.vb:654— Image_Editor_Form.Image_Editor_Form_KeyDown has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Utils.ReadJpegSize (cyclomatic 24) src/Utils.vb:332— Utils.ReadJpegSize has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RegBackup.Parse (cyclomatic 24) src/ProfileReset/RegBackup.vb:56— RegBackup.Parse has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.FitSettingsContent (cyclomatic 24) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb:297— Share_Settings_Form.FitSettingsContent has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEnvelopeCodec.WriteMember (cyclomatic 24) src/Exchange/ExchangeEnvelope.vb:392— ExchangeEnvelopeCodec.WriteMember has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Exchange_Devices_Panel.Render (cyclomatic 24) src/Exchange_Devices_Panel.vb:500— Exchange_Devices_Panel.Render has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
main.serveCore (cyclomatic 24) REDACTED:97— main.serveCore has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Engine.handle (cyclomatic 24) exchange-server/internal/rendezvous/engine_control.go:61— Engine.handle has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SftpProvider.EnumerateDirectoryInternal (cyclomatic 23) src/Resources/SftpProvider.vb:409— SftpProvider.EnumerateDirectoryInternal has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ExecuteRecipientAction (cyclomatic 23) src/Main_Form.FileOperations.vb:909— Main_Form.ExecuteRecipientAction has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.Undo (cyclomatic 23) src/Main_Form.FileOperations.vb:1133— Main_Form.Undo has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FolderLiveList.Apply (cyclomatic 23) src/FolderLiveList.vb:186— FolderLiveList.Apply has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
HostingReport.BuildStateLine (cyclomatic 23) src/Support/HostingReport.vb:498— HostingReport.BuildStateLine has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
StreamCatalogReport.FormatReportText (cyclomatic 23) src/Streams/StreamCatalogReport.vb:35— StreamCatalogReport.FormatReportText has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Utils.ReadExifOrientation (cyclomatic 23) src/Utils.vb:291— Utils.ReadExifOrientation has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Ask_Dialog.Build (cyclomatic 23) src/Ask_Dialog.vb:68— Ask_Dialog.Build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
MainWindow.OnConfigureFolder (cyclomatic 23) src/FastMediaSorterCompanion/Forms/MainWindow.Folders.vb:66— MainWindow.OnConfigureFolder has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PackageWizardForm.OnCellValueChanged (cyclomatic 23) src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb:429— PackageWizardForm.OnCellValueChanged has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
connstr.canonicalHost (cyclomatic 23) exchange-server/internal/connstr/connstr.go:338— connstr.canonicalHost has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
password.parse (cyclomatic 23) exchange-server/internal/password/password.go:132— password.parse has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Server.envelopes (cyclomatic 23) exchange-server/internal/rendezvous/stream.go:213— Server.envelopes has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Enroll.validate (cyclomatic 23) exchange-server/internal/wire/validate.go:54— Enroll.validate has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TransferExecutor.Perform (cyclomatic 22) src/Resources/TransferPlan.vb:276— TransferExecutor.Perform has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SftpProvider.ConnectLocked (cyclomatic 22) src/Resources/SftpProvider.vb:158— SftpProvider.ConnectLocked has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
OcrTextFilter.IsWholeAddress (cyclomatic 22) src/Ocr/OcrTextFilter.vb:247— OcrTextFilter.IsWholeAddress has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CameraCaptureSource.FoldBitmap (cyclomatic 22) src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:234— CameraCaptureSource.FoldBitmap has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DiskDriveLetters.Reconcile (cyclomatic 22) src/FastMediaSorterCompanion/Core/DiskDriveLetters.vb:84— DiskDriveLetters.Reconcile has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEndpointRules.TryParse (cyclomatic 22) src/FastMediaSorterCompanion/Core/ExchangeEndpointRules.vb:48— ExchangeEndpointRules.TryParse has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangePublisher.ChangeLinkAsync (cyclomatic 22) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:598— ExchangePublisher.ChangeLinkAsync has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ScreenCaptureSource.FoldBitmap (cyclomatic 22) src/FastMediaSorterCompanion/Core/ScreenCaptureSource.vb:208— ScreenCaptureSource.FoldBitmap has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
CompanionCommand.CanonicalFolder (cyclomatic 22) src/FastMediaSorterCompanion/Core/ShareActivation.vb:103— CompanionCommand.CanonicalFolder has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Exchange_Account_Form.OnSignInClicked (cyclomatic 22) src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:391— Exchange_Account_Form.OnSignInClicked has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceAddActions.CommitAsync (cyclomatic 22) src/FastMediaSorterCompanion/Forms/MainWindow.ResourceAdd.vb:93— ResourceAddActions.CommitAsync has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Qr_Zoom_Form.HandOff (cyclomatic 22) src/FastMediaSorterCompanion/Forms/Qr_Zoom_Form.vb:221— Qr_Zoom_Form.HandOff has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.OnXApplyPort (cyclomatic 22) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:363— Share_Settings_Form.OnXApplyPort has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.CanonicalHost (cyclomatic 22) src/Exchange/ExchangeConnectionString.vb:331— ExchangeConnectionString.CanonicalHost has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
main.run (cyclomatic 22) exchange-server/cmd/exchange-probe/main.go:31— main.run has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ResourceFailure.FromException (cyclomatic 21) src/Resources/ResourceFailure.vb:77— ResourceFailure.FromException has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
LiveBroadcastReader.InflateSingleGzipMember (cyclomatic 21) src/LiveBroadcast/LiveBroadcastReader.vb:202— LiveBroadcastReader.InflateSingleGzipMember has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
BatchPlan.Build (cyclomatic 21) src/BatchPlan.vb:225— BatchPlan.Build has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PdfDocumentSource.RenderPage (cyclomatic 21) src/Documents/PdfDocumentSource.vb:110— PdfDocumentSource.RenderPage has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
LogPackage.Build (cyclomatic 21) src/Support/LogPackage.vb:144— LogPackage.Build has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.BuildSettingsGroups (cyclomatic 21) src/Table_Form.SettingsGroups.vb:29— Table_Form.BuildSettingsGroups has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.BuildContractGroups (cyclomatic 21) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb:109— Share_Settings_Form.BuildContractGroups has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.OnXAddAccount (cyclomatic 21) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:727— Share_Settings_Form.OnXAddAccount has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
accounts.Open (cyclomatic 21) exchange-server/internal/accounts/store.go:168— accounts.Open has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Config.Validate (cyclomatic 21) exchange-server/internal/config/config.go:213— Config.Validate has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Main_Form.LoadStandardImageInPictureBox (cyclomatic 20) src/Main_Form.MediaLoading.vb:1033— Main_Form.LoadStandardImageInPictureBox has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
EdgeSampler.CalculateBackgroundColor (cyclomatic 20) src/Imaging/EdgeSampler.vb:83— EdgeSampler.CalculateBackgroundColor has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TesseractOcrEngine.EnsureTessData (cyclomatic 20) src/Ocr/TesseractOcrEngine.vb:928— TesseractOcrEngine.EnsureTessData has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
HostingReport.Render (cyclomatic 20) src/Support/HostingReport.vb:299— HostingReport.Render has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.OpenContentInDefaultProgram (cyclomatic 20) src/Main_Form.PlaceholderView.vb:167— Main_Form.OpenContentInDefaultProgram has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ButtonGlyphs.ArrangeContent (cyclomatic 20) src/Icons/ButtonGlyphs.vb:396— ButtonGlyphs.ArrangeContent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DialogLayout.WidenButtons (cyclomatic 20) src/DialogLayout.vb:172— DialogLayout.WidenButtons has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeLayout.ArrangeRow (cyclomatic 20) src/Chrome/ChromeLayout.vb:91— ChromeLayout.ArrangeRow has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RegBackup.CreateBackup (cyclomatic 20) src/ProfileReset/RegBackup.vb:116— RegBackup.CreateBackup has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.ApplyAccountState (cyclomatic 20) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAccount.vb:221— Share_Settings_Form.ApplyAccountState has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.ModernComboBox_Paint (cyclomatic 20) src/Table_Form.ModernLayout.vb:209— Table_Form.ModernComboBox_Paint has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: Table_Form.ModernSettingTitle (cyclomatic 149) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Relay.Listen (cyclomatic 20) exchange-server/internal/rendezvous/relay_handler.go:329— Relay.Listen has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Main_Form.RunFileOp (cyclomatic 19) src/Main_Form.FileOperations.vb:137— Main_Form.RunFileOp has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.TranslateCurrentImage (cyclomatic 19) src/Main_Form.OcrTranslate.vb:286— Main_Form.TranslateCurrentImage has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
EditorGeometry.CropHandleAt (cyclomatic 19) src/EditorGeometry.vb:180— EditorGeometry.CropHandleAt has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
OcrPlateColors.Compute (cyclomatic 19) src/Ocr/OcrPlateColors.vb:97— OcrPlateColors.Compute has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SettingsUiContext.Read (cyclomatic 19) src/SettingsUiContext.vb:57— SettingsUiContext.Read has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsConfigReader.Parse (cyclomatic 19) src/Resources/FmsConfigReader.vb:310— FmsConfigReader.Parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
StreamCsvWriter.ParseRfc4180 (cyclomatic 19) src/Streams/StreamCsvWriter.vb:61— StreamCsvWriter.ParseRfc4180 has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeHost.RefreshInk (cyclomatic 19) src/Chrome/ChromeHost.vb:105— ChromeHost.RefreshInk has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEndpointRules.IsPlausibleHostName (cyclomatic 19) src/FastMediaSorterCompanion/Core/ExchangeEndpointRules.vb:82— ExchangeEndpointRules.IsPlausibleHostName has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangePublisher.HandleOpenAsync (cyclomatic 19) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:722— ExchangePublisher.HandleOpenAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FolderAccess.ScanSubtree (cyclomatic 19) src/FastMediaSorterCompanion/Core/FolderAccess.vb:212— FolderAccess.ScanSubtree has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
NetworkInfo.LocalIPv4ViaAdapterScan (cyclomatic 19) src/FastMediaSorterCompanion/Core/NetworkInfo.vb:140— NetworkInfo.LocalIPv4ViaAdapterScan has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RouterInfo.IsLanLocation (cyclomatic 19) src/FastMediaSorterCompanion/Core/RouterInfo.vb:149— RouterInfo.IsLanLocation has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Broadcasts_Form.PromptCreateBroadcastAsync (cyclomatic 19) src/FastMediaSorterCompanion/Forms/Share_Broadcasts_Form.vb:377— Share_Broadcasts_Form.PromptCreateBroadcastAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeDirectorySnapshot.FromLocalJson (cyclomatic 19) src/Exchange/ExchangeDirectory.vb:270— ExchangeDirectorySnapshot.FromLocalJson has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeJsonWriter.WriteString (cyclomatic 19) src/Exchange/ExchangeJson.vb:149— ExchangeJsonWriter.WriteString has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeSync.AttachAsync (cyclomatic 19) src/Resources/ExchangeDevices.vb:332— ExchangeSync.AttachAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsTunnelPaths.TryReadMembers (cyclomatic 19) src/Resources/FmsTunnelPaths.vb:63— FmsTunnelPaths.TryReadMembers has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceImport.Apply (cyclomatic 19) src/Resources/ResourceImport.vb:156— ResourceImport.Apply has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
connstr.Parse (cyclomatic 19) exchange-server/internal/connstr/connstr.go:185— connstr.Parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Listener.Take (cyclomatic 19) exchange-server/internal/relay/ring.go:201— Listener.Take has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransferExecutor.RenameWithin (cyclomatic 18) src/Resources/TransferPlan.vb:460— TransferExecutor.RenameWithin has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceTransfer.MoveWithin (cyclomatic 18) src/Resources/ResourceTransfer.vb:103— ResourceTransfer.MoveWithin has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.EnsureEntryLocal (cyclomatic 18) src/Main_Form.Resource.vb:274— Main_Form.EnsureEntryLocal has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.PaintEmptyState (cyclomatic 18) src/Main_Form.Notify.vb:168— Main_Form.PaintEmptyState has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FileDetails.JpegSofInfo (cyclomatic 18) src/FileDetails.vb:284— FileDetails.JpegSofInfo has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: FileDetails.VideoCodecName (cyclomatic 34) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Main_Form.ExecuteDelete (cyclomatic 18) src/Main_Form.FileOperations.vb:1537— Main_Form.ExecuteDelete has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.PaintOcrOverlay (cyclomatic 18) src/Main_Form.OcrOverlay.vb:120— Main_Form.PaintOcrOverlay has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PathFailure.Classify (cyclomatic 18) src/PathFailure.vb:102— PathFailure.Classify has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ApplyLiveChanges (cyclomatic 18) src/Main_Form.FolderWatch.vb:356— Main_Form.ApplyLiveChanges has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TransportRules.ArrangeRow (cyclomatic 18) src/TransportRules.vb:53— TransportRules.ArrangeRow has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ViewerProcessDiscovery.Discover (cyclomatic 18) src/ViewerProcessDiscovery.vb:63— ViewerProcessDiscovery.Discover has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
HostingProbesLive.TryReadExchangeNumbers (cyclomatic 18) src/Support/HostingProbesLive.vb:429— HostingProbesLive.TryReadExchangeNumbers has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.BuildSettingsDiscovery (cyclomatic 18) src/Table_Form.SettingsDiscovery.vb:127— Table_Form.BuildSettingsDiscovery has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.PaintContentPlaceholder (cyclomatic 18) src/Main_Form.PlaceholderView.vb:85— Main_Form.PaintContentPlaceholder has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.UpdateWelcomeInvite (cyclomatic 18) src/Main_Form.Welcome.vb:132— Main_Form.UpdateWelcomeInvite has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeSurface.MeasureItemWidth (cyclomatic 18) src/Chrome/ChromeSurface.vb:234— ChromeSurface.MeasureItemWidth has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ChromeSurface.LayoutItems (cyclomatic 18) src/Chrome/ChromeSurface.vb:337— ChromeSurface.LayoutItems has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
RegBackup.ParseValue (cyclomatic 18) src/ProfileReset/RegBackup.vb:236— RegBackup.ParseValue has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeLocalJoin.TryJoinAsync (cyclomatic 18) src/FastMediaSorterCompanion/Core/ExchangeLocalJoin.vb:91— ExchangeLocalJoin.TryJoinAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
NetworkInfo.DefaultGatewayIp (cyclomatic 18) src/FastMediaSorterCompanion/Core/NetworkInfo.vb:21— NetworkInfo.DefaultGatewayIp has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SectionHeader.OnPaint (cyclomatic 18) src/FastMediaSorterCompanion/Forms/CollapsibleSection.vb:426— SectionHeader.OnPaint has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PackageWizardForm.Rebuild (cyclomatic 18) src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb:573— PackageWizardForm.Rebuild has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Share_Settings_Form.ResetPasswordFor (cyclomatic 18) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:780— Share_Settings_Form.ResetPasswordFor has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEntryStore.ReadEntry (cyclomatic 18) src/Exchange/ExchangeEntries.vb:208— ExchangeEntryStore.ReadEntry has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Exchange_Devices_Panel.Toggle (cyclomatic 18) src/Exchange_Devices_Panel.vb:700— Exchange_Devices_Panel.Toggle has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Dir.BroadcastStart (cyclomatic 18) exchange-server/internal/directory/ops.go:443— Dir.BroadcastStart has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
wave-particles.attach (cyclomatic 18) assets/wave-particles.js:462— wave-particles.attach has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ArchiveSession.EnsureExtractedCore (cyclomatic 17) src/Archives/ArchiveSession.vb:344— ArchiveSession.EnsureExtractedCore has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
WorkerShares.ParseDisks (cyclomatic 17) src/Resources/WorkerShares.vb:144— WorkerShares.ParseDisks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceCommit.Commit (cyclomatic 17) src/Resources/ResourceCommit.vb:118— ResourceCommit.Commit has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.SecureVerifyCurrent (cyclomatic 17) src/Main_Form.Secure.vb:945— Main_Form.SecureVerifyCurrent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ApplyModernPreferencesFromSettings (cyclomatic 17) src/Main_Form.ModernPreferences.vb:81— Main_Form.ApplyModernPreferencesFromSettings has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.audio_Visualiser_Timer_Tick (cyclomatic 17) src/Main_Form.AudioView.vb:463— Main_Form.audio_Visualiser_Timer_Tick has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.MediaSectionsFromParse (cyclomatic 17) src/Main_Form.FileDetails.vb:102— Main_Form.MediaSectionsFromParse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.RenameCurrentFile (cyclomatic 17) src/Main_Form.FileOperations.vb:735— Main_Form.RenameCurrentFile has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.BgWorker_ProgressChanged (cyclomatic 17) src/Main_Form.FileScanning.vb:328— Main_Form.BgWorker_ProgressChanged has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.GetFiles (cyclomatic 17) src/Main_Form.FileScanning.vb:522— Main_Form.GetFiles has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.ProcessCmdKey (cyclomatic 17) src/Main_Form.KeyboardInput.vb:35— Main_Form.ProcessCmdKey has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: Main_Form.RecipientSlotFromKey (cyclomatic 21) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
FolderLiveList.Compare (cyclomatic 17) src/FolderLiveList.vb:109— FolderLiveList.Compare has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Table_Form.RefreshSettingsDependencies (cyclomatic 17) src/Table_Form.SettingsDiscovery.vb:310— Table_Form.RefreshSettingsDependencies has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ThemeApplier.ApplyButton (cyclomatic 17) src/Theming/ThemeApplier.vb:378— ThemeApplier.ApplyButton has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DialogLayout.FitContent (cyclomatic 17) src/DialogLayout.vb:74— DialogLayout.FitContent has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeOperatorEndpoint.Check (cyclomatic 17) src/FastMediaSorterCompanion/Core/ExchangeAdminModel.vb:79— ExchangeOperatorEndpoint.Check has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.Build (cyclomatic 17) src/Exchange/ExchangeConnectionString.vb:227— ExchangeConnectionString.Build has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.SplitEndpoint (cyclomatic 17) src/Exchange/ExchangeConnectionString.vb:300— ExchangeConnectionString.SplitEndpoint has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeConnectionString.RenderIPv6 (cyclomatic 17) src/Exchange/ExchangeConnectionString.vb:443— ExchangeConnectionString.RenderIPv6 has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeEnvelopeCodec.Decode (cyclomatic 17) src/Exchange/ExchangeEnvelope.vb:464— ExchangeEnvelopeCodec.Decode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeResourceRecordBuilder.TryBuild (cyclomatic 17) src/Exchange/ExchangeResourceAccess.vb:131— ExchangeResourceRecordBuilder.TryBuild has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsSftpCode.IsUsable (cyclomatic 17) src/Exchange/FmsSftpCode.vb:99— FmsSftpCode.IsUsable has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
main.generateRecords (cyclomatic 17) exchange-server/cmd/exchange-vectors/records.go:94— main.generateRecords has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 116, 177, 237, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RemoteSlotPolicy.Verdict (cyclomatic 16) src/Resources/RemoteSlots.vb:113— RemoteSlotPolicy.Verdict has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SftpProvider.Classify (cyclomatic 16) src/Resources/SftpProvider.vb:318— SftpProvider.Classify has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.EnterResource (cyclomatic 16) src/Main_Form.Resource.vb:108— Main_Form.EnterResource has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.LoadFilesForRandomOrSlideshow (cyclomatic 16) src/Main_Form.MediaLoading.vb:803— Main_Form.LoadFilesForRandomOrSlideshow has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SelectionModel.RemovePaths (cyclomatic 16) src/BatchSelection.vb:112— SelectionModel.RemovePaths has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Main_Form.TrackLanguage (cyclomatic 16) src/Main_Form.VideoTracks.vb:117— Main_Form.TrackLanguage has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
OcrLanguageGuard.RefusalReason (cyclomatic 16) src/Ocr/OcrLanguageGuard.vb:103— OcrLanguageGuard.RefusalReason has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
SshFingerprint.TryParse (cyclomatic 16) src/Resources/SshFingerprint.vb:38— SshFingerprint.TryParse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
StreamIdentity.GetIdentityKey (cyclomatic 16) src/Streams/StreamIdentity.vb:24— StreamIdentity.GetIdentityKey has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
M3uPlaylistReader.ParseAndAddEntry (cyclomatic 16) src/Streams/M3uPlaylistReader.vb:192— M3uPlaylistReader.ParseAndAddEntry has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: M3uPlaylistReader.IsEmptyOrEncoderDefaultName (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
Main_Form.ChromeEdgeHitCode (cyclomatic 16) src/Main_Form.WindowBorder.vb:197— Main_Form.ChromeEdgeHitCode has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeDeviceAgent.HandleAsync (cyclomatic 16) src/FastMediaSorterCompanion/Core/ExchangeDeviceAgent.vb:708— ExchangeDeviceAgent.HandleAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This is NOT this file's highest cyclomatic complexity: ExchangeDeviceAgent.EnrollAsync (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ExchangePublisher.ComputePlanAsync (cyclomatic 16) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:386— ExchangePublisher.ComputePlanAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ShareController.ServeAsync (cyclomatic 16) src/FastMediaSorterCompanion/Core/ShareController.vb:81— ShareController.ServeAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ShareController.EnsureRunningReconciledAsync (cyclomatic 16) src/FastMediaSorterCompanion/Core/ShareController.vb:208— ShareController.EnsureRunningReconciledAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ManagerSettingRow.ArrangeColumns (cyclomatic 16) src/FastMediaSorterCompanion/Forms/ManagerSettingRow.vb:82— ManagerSettingRow.ArrangeColumns has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ExchangeIds.Decodes (cyclomatic 16) src/Exchange/ExchangeWire.vb:159— ExchangeIds.Decodes has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
FmsConfigExport.IsLanLikeHost (cyclomatic 16) src/Resources/FmsConfigExport.vb:182— FmsConfigExport.IsLanLikeHost has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ResourceProbe.ProbeSftpAsync (cyclomatic 16) src/Resources/ResourceProbe.vb:31— ResourceProbe.ProbeSftpAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Ops.Handle (cyclomatic 16) exchange-server/internal/admin/channel.go:133— Ops.Handle has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Dir.Load (cyclomatic 16) exchange-server/internal/directory/directory.go:409— Dir.Load has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StreamCatalogValidator.ValidateArchive (cognitive 203) src/Streams/StreamCatalogValidator.vb:74— StreamCatalogValidator.ValidateArchive has cognitive complexity 203 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
prober.run (cognitive 155) REDACTED:132— prober.run has cognitive complexity 155 (threshold 15). Drivers by points: if/else 82 (131 pts), loops 9 (13 pts), boolean chains 10, match/switch 1 (nesting depth added 53). Of this number, 20 points are the body's own statements and 135 belong to 14 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Main_Form.UpdateCurrentFileAndDisplay (cognitive 136) src/Main_Form.MediaLoading.vb:1460— Main_Form.UpdateCurrentFileAndDisplay has cognitive complexity 136 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.parseArgs (cognitive 128) exchange-server/cmd/fms-exchange-server/args.go:38— main.parseArgs has cognitive complexity 128 (threshold 15). Drivers by points: if/else 37 (99 pts), boolean chains 15, match/switch 7 (13 pts), loops 1 (nesting depth added 68). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Main_Form.FinishFileOp (cognitive 117) src/Main_Form.FileOperations.vb:1649— Main_Form.FinishFileOp has cognitive complexity 117 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.Draw_Perspective (cognitive 101) src/Main_Form.PerspectiveBackground.vb:353— Main_Form.Draw_Perspective has cognitive complexity 101 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.KeybUse (cognitive 90) src/Main_Form.KeyboardInput.vb:104— Main_Form.KeybUse has cognitive complexity 90 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BgWorker_DoWork (cognitive 78) src/Main_Form.FileScanning.vb:60— Main_Form.BgWorker_DoWork has cognitive complexity 78 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ApplyRecipientsOverlayHealth (cognitive 72) src/Main_Form.RecipientsOverlay.vb:526— Main_Form.ApplyRecipientsOverlayHealth has cognitive complexity 72 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.SyncChromeItem (cognitive 72) src/Main_Form.Chrome.vb:800— Main_Form.SyncChromeItem has cognitive complexity 72 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.UpdateFileIndexAndList (cognitive 70) src/Main_Form.MediaLoading.vb:450— Main_Form.UpdateFileIndexAndList has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AppFileLogger.Initialize (cognitive 67) src/AppFileLogger.vb:90— AppFileLogger.Initialize has cognitive complexity 67 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.StartBatchAsync (cognitive 67) src/Main_Form.Batch.vb:215— Main_Form.StartBatchAsync has cognitive complexity 67 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastReader.ReadJsonBytes (cognitive 63) src/LiveBroadcast/LiveBroadcastReader.vb:279— LiveBroadcastReader.ReadJsonBytes has cognitive complexity 63 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeMenuRules.ResolveKey (cognitive 62) src/Chrome/ChromeMenuRules.vb:105— ChromeMenuRules.ResolveKey has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.ApplyModernPaletteToTree (cognitive 62) src/Table_Form.ModernLayout.vb:2128— Table_Form.ApplyModernPaletteToTree has cognitive complexity 62 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EpubMetadata.Read (cognitive 61) src/Documents/EpubMetadata.vb:58— EpubMetadata.Read has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SvgPathData.AppendTo (cognitive 61) src/Icons/SvgPathData.vb:27— SvgPathData.AppendTo has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsConfigReader.ReadRoots (cognitive 59) src/Resources/FmsConfigReader.vb:452— FmsConfigReader.ReadRoots has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ShareConfigBuilder.Build (cognitive 58) src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:122— ShareConfigBuilder.Build has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
StreamCatalogProducer.Build (cognitive 56) src/Streams/StreamCatalogProducer.vb:52— StreamCatalogProducer.Build has cognitive complexity 56 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeSurface.PaintItemInk (cognitive 55) src/Chrome/ChromeSurface.vb:563— ChromeSurface.PaintItemInk has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.LoadStandardImageInPictureBox (cognitive 52) src/Main_Form.MediaLoading.vb:1033— Main_Form.LoadStandardImageInPictureBox has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastController.Start (cognitive 52) src/LiveBroadcast/Producer/LiveProducerController.vb:139— LiveBroadcastController.Start has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ConnectAndEnterResource (cognitive 52) src/Main_Form.ResourceOpen.vb:220— Main_Form.ConnectAndEnterResource has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BuildChromeRow (cognitive 51) src/Main_Form.Chrome.vb:282— Main_Form.BuildChromeRow has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.LocalizeModernSettingRows (cognitive 51) src/Table_Form.ModernLayout.vb:837— Table_Form.LocalizeModernSettingRows has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.MouseUse (cognitive 50) src/Main_Form.MouseInput.vb:169— Main_Form.MouseUse has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PaintTextDocument (cognitive 50) src/Main_Form.TextView.vb:95— Main_Form.PaintTextDocument has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.TryCanonicalIPv6 (cognitive 50) src/Exchange/ExchangeConnectionString.vb:374— ExchangeConnectionString.TryCanonicalIPv6 has cognitive complexity 50 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
create (cognitive 50) assets/wave-particles.js:251— create has cognitive complexity 50 (threshold 15). Drivers by points: if/else 23 (24 pts), boolean chains 16, ternaries 9, loops 1 (nesting depth added 1). Most of this is not in the body itself: 9 of the 50 points are its own statements and the rest belongs to 20 function items inside it that branch (resize, tick, readSurface, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
WasapiAudioSource.CaptureLoop (cognitive 49) src/FastMediaSorterCompanion/Core/WasapiAudioSource.vb:180— WasapiAudioSource.CaptureLoop has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.FitSettingsContent (cognitive 49) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb:297— Share_Settings_Form.FitSettingsContent has cognitive complexity 49 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemeApplier.ApplyOne (cognitive 48) src/Theming/ThemeApplier.vb:159— ThemeApplier.ApplyOne has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ReadShowMediaFile (cognitive 46) src/Main_Form.MediaLoading.vb:281— Main_Form.ReadShowMediaFile has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
StreamCatalogReport.FormatReportText (cognitive 46) src/Streams/StreamCatalogReport.vb:35— StreamCatalogReport.FormatReportText has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeProducerStore.Load (cognitive 46) src/FastMediaSorterCompanion/Core/ExchangeProducerStore.vb:153— ExchangeProducerStore.Load has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ArchiveSession.RunSequentialPass (cognitive 45) src/Archives/ArchiveSession.vb:554— ArchiveSession.RunSequentialPass has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.ApplyHostingState (cognitive 45) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb:197— Share_Settings_Form.ApplyHostingState has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Exchange_Devices_Panel.Render (cognitive 45) src/Exchange_Devices_Panel.vb:500— Exchange_Devices_Panel.Render has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.LoadEmbeddedMp3Cover (cognitive 44) src/Main_Form.AudioView.vb:389— Main_Form.LoadEmbeddedMp3Cover has cognitive complexity 44 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.Chrome_Timer_Tick (cognitive 43) src/Main_Form.Chrome.vb:1043— Main_Form.Chrome_Timer_Tick has cognitive complexity 43 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BuildRecipientsOverlay (cognitive 41) src/Main_Form.RecipientsOverlay.vb:206— Main_Form.BuildRecipientsOverlay has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.LoadFilesForRandomOrSlideshow (cognitive 41) src/Main_Form.MediaLoading.vb:803— Main_Form.LoadFilesForRandomOrSlideshow has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OllamaTranslator.PullModelAsync (cognitive 41) src/Translate/OllamaTranslator.vb:428— OllamaTranslator.PullModelAsync has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ViewerProcessDiscovery.Discover (cognitive 41) src/ViewerProcessDiscovery.vb:63— ViewerProcessDiscovery.Discover has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HostingReport.BuildStateLine (cognitive 41) src/Support/HostingReport.vb:498— HostingReport.BuildStateLine has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangePublishPlan.Build (cognitive 41) src/FastMediaSorterCompanion/Core/ExchangePublishPlan.vb:129— ExchangePublishPlan.Build has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ShareConfigBuilder.RootJson (cognitive 41) src/FastMediaSorterCompanion/Core/ShareConfigBuilder.vb:310— ShareConfigBuilder.RootJson has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsSftpCode.TryParse (cognitive 41) src/Exchange/FmsSftpCode.vb:123— FmsSftpCode.TryParse has cognitive complexity 41 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BatchRunner_ItemFinished (cognitive 40) src/Main_Form.Batch.vb:581— Main_Form.BatchRunner_ItemFinished has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Server_Welcome_Form.AdvanceExchangeAsync (cognitive 40) src/FastMediaSorterCompanion/Forms/Server_Welcome_Form.ExchangeFirstRun.vb:224— Server_Welcome_Form.AdvanceExchangeAsync has cognitive complexity 40 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Listener.Take (cognitive 40) exchange-server/internal/relay/ring.go:201— Listener.Take has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 4 (12 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResourceSession.TryEnsureLocal (cognitive 39) src/Resources/ResourceSession.vb:204— ResourceSession.TryEnsureLocal has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
NetworkInfo.LocalIPv4ViaAdapterScan (cognitive 39) src/FastMediaSorterCompanion/Core/NetworkInfo.vb:140— NetworkInfo.LocalIPv4ViaAdapterScan has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.Form1_Load (cognitive 38) src/Main_Form.Lifecycle.vb:764— Main_Form.Form1_Load has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FolderLiveList.Apply (cognitive 38) src/FolderLiveList.vb:186— FolderLiveList.Apply has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.BuildSettingsDiscovery (cognitive 38) src/Table_Form.SettingsDiscovery.vb:127— Table_Form.BuildSettingsDiscovery has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Exchange_Devices_Panel.OnDrawItem (cognitive 38) src/Exchange_Devices_Panel.vb:433— Exchange_Devices_Panel.OnDrawItem has cognitive complexity 38 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Dir.Publish (cognitive 38) exchange-server/internal/directory/ops.go:280— Dir.Publish has cognitive complexity 38 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 10, match/switch 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Main_Form.UpdateControlVisibility (cognitive 37) src/Main_Form.MediaLoading.vb:1363— Main_Form.UpdateControlVisibility has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EdgeSampler.CalculateBackgroundColor (cognitive 37) src/Imaging/EdgeSampler.vb:83— EdgeSampler.CalculateBackgroundColor has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Utils.ReadJpegSize (cognitive 37) src/Utils.vb:332— Utils.ReadJpegSize has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.BuildContractGroups (cognitive 37) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Contract.vb:109— Share_Settings_Form.BuildContractGroups has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Program.Main (cognitive 36) src/FastMediaSorterCompanion/Program.vb:62— Program.Main has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Resource_Edit_Form.Confirm (cognitive 36) src/Resource_Edit_Form.vb:230— Resource_Edit_Form.Confirm has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceLocator.TryParse (cognitive 35) src/Resources/ResourceRegistry.vb:221— ResourceLocator.TryParse has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SftpProvider.ConnectLocked (cognitive 35) src/Resources/SftpProvider.vb:158— SftpProvider.ConnectLocked has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.Pic_MouseMove (cognitive 35) src/Main_Form.MouseInput.vb:419— Main_Form.Pic_MouseMove has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PersistSettings (cognitive 35) src/Main_Form.Lifecycle.vb:1538— Main_Form.PersistSettings has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
StreamCsvWriter.ParseRfc4180 (cognitive 35) src/Streams/StreamCsvWriter.vb:61— StreamCsvWriter.ParseRfc4180 has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
StreamCatalogCli.Run (cognitive 35) src/Streams/StreamCatalogCli.vb:59— StreamCatalogCli.Run has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeLayout.ArrangeRow (cognitive 35) src/Chrome/ChromeLayout.vb:91— ChromeLayout.ArrangeRow has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BroadcastConfigBuilder.Build (cognitive 35) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:54— BroadcastConfigBuilder.Build has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.connVectors (cognitive 35) exchange-server/cmd/exchange-vectors/connstr.go:72— main.connVectors has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 6, loops 3 (4 pts), jumps 1 (nesting depth added 6). Most of this is not in the body itself: 15 of the 35 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 91, 115, 134, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ExifReader.TryRead (cognitive 34) src/FileDetails.vb:641— ExifReader.TryRead has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.HandlePictureBoxMouseDown (cognitive 34) src/Main_Form.MouseInput.vb:16— Main_Form.HandlePictureBoxMouseDown has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.CloseTeardown (cognitive 33) src/Main_Form.Lifecycle.vb:1317— Main_Form.CloseTeardown has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.RunOcrPipeline (cognitive 33) src/Main_Form.OcrTranslate.vb:374— Main_Form.RunOcrPipeline has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.DisplayPdfPage (cognitive 33) src/Main_Form.PdfView.vb:92— Main_Form.DisplayPdfPage has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeTlsTransport.OpenAsync (cognitive 33) src/Exchange/ExchangeTls.vb:213— ExchangeTlsTransport.OpenAsync has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsConfigReader.ReadAccessPaths (cognitive 32) src/Resources/FmsConfigReader.vb:412— FmsConfigReader.ReadAccessPaths has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RegBackup.Parse (cognitive 32) src/ProfileReset/RegBackup.vb:56— RegBackup.Parse has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RegBackup.ParseValue (cognitive 32) src/ProfileReset/RegBackup.vb:236— RegBackup.ParseValue has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.Parse (cognitive 32) src/Exchange/ExchangeConnectionString.vb:149— ExchangeConnectionString.Parse has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceImport.Apply (cognitive 32) src/Resources/ResourceImport.vb:156— ResourceImport.Apply has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SftpProvider.EnumerateDirectoryInternal (cognitive 31) src/Resources/SftpProvider.vb:409— SftpProvider.EnumerateDirectoryInternal has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastReader.ParseEndpoint (cognitive 31) src/LiveBroadcast/LiveBroadcastReader.vb:449— LiveBroadcastReader.ParseEndpoint has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveHttpPlaybackSession.OpenAsync (cognitive 31) src/LiveBroadcast/LiveHttpPlaybackSession.vb:200— LiveHttpPlaybackSession.OpenAsync has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Image_Panel_Form.OnFormKeyDown (cognitive 31) src/Image_Panel_Form.Modern.vb:751— Image_Panel_Form.OnFormKeyDown has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.MediaSectionsFromParse (cognitive 31) src/Main_Form.FileDetails.vb:102— Main_Form.MediaSectionsFromParse has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TesseractOcrEngine.RecognizeAttempts (cognitive 31) src/Ocr/TesseractOcrEngine.vb:186— TesseractOcrEngine.RecognizeAttempts has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
NetworkInfo.DefaultGatewayIp (cognitive 31) src/FastMediaSorterCompanion/Core/NetworkInfo.vb:21— NetworkInfo.DefaultGatewayIp has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.serveCore (cognitive 31) REDACTED:97— main.serveCore has cognitive complexity 31 (threshold 15). Drivers by points: if/else 24 (29 pts), loops 1, match/switch 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
testkit.StartServer (cognitive 31) exchange-server/internal/testkit/env.go:108— testkit.StartServer has cognitive complexity 31 (threshold 15). Drivers by points: if/else 23 (28 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Main_Form.PlayVideoWithVlcAsync (cognitive 30) src/Main_Form.VideoPlayer.vb:383— Main_Form.PlayVideoWithVlcAsync has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DialogLayout.WidenButtons (cognitive 30) src/DialogLayout.vb:172— DialogLayout.WidenButtons has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.ApplyExchangeState (cognitive 30) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:286— Share_Settings_Form.ApplyExchangeState has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEnvelopeCodec.ReadMember (cognitive 30) src/Exchange/ExchangeEnvelope.vb:504— ExchangeEnvelopeCodec.ReadMember has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastStore.WriteDescriptor (cognitive 29) src/LiveBroadcast/LiveBroadcastStore.vb:122— LiveBroadcastStore.WriteDescriptor has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastRunner.RunAsync (cognitive 29) src/LiveBroadcast/LiveBroadcastRunner.vb:161— LiveBroadcastRunner.RunAsync has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TesseractOcrEngine.EnsureTessData (cognitive 29) src/Ocr/TesseractOcrEngine.vb:928— TesseractOcrEngine.EnsureTessData has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeMenu.PreFilterMessage (cognitive 29) src/Chrome/ChromeMenu.vb:399— ChromeMenu.PreFilterMessage has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeGroupModel.Build (cognitive 29) src/FastMediaSorterCompanion/Core/ExchangeGroupModel.vb:110— ExchangeGroupModel.Build has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FolderAccess.ScanSubtree (cognitive 29) src/FastMediaSorterCompanion/Core/FolderAccess.vb:212— FolderAccess.ScanSubtree has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PackageWizardForm.Rebuild (cognitive 29) src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb:573— PackageWizardForm.Rebuild has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeAgentStateInfo.TryParse (cognitive 29) src/Exchange/ExchangeAgentChannel.vb:90— ExchangeAgentStateInfo.TryParse has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Control.Await (cognitive 29) exchange-server/internal/testkit/device.go:290— Control.Await has cognitive complexity 29 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 3 (8 pts), match/switch 2 (5 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Main_Form.Undo (cognitive 28) src/Main_Form.FileOperations.vb:1133— Main_Form.Undo has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ProcessCmdKey (cognitive 28) src/Main_Form.KeyboardInput.vb:35— Main_Form.ProcessCmdKey has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TextScriptHeuristics.ClassifyScript (cognitive 28) src/Translate/ITranslator.vb:320— TextScriptHeuristics.ClassifyScript has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LogPackage.Build (cognitive 28) src/Support/LogPackage.vb:144— LogPackage.Build has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
StreamCatalogProducer.ReadExistingArchiveUrls (cognitive 28) src/Streams/StreamCatalogProducer.vb:234— StreamCatalogProducer.ReadExistingArchiveUrls has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProtectedConfigWriter.Publish (cognitive 28) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:77— ProtectedConfigWriter.Publish has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Exchange_Account_Form.OnSignInClicked (cognitive 28) src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:391— Exchange_Account_Form.OnSignInClicked has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExportWriter.Publish (cognitive 28) src/Resources/ExportWriter.vb:73— ExportWriter.Publish has cognitive complexity 28 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LogSessionDiagnostics.UnfinishedSessions (cognitive 27) src/LogSessionDiagnostics.vb:18— LogSessionDiagnostics.UnfinishedSessions has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
NaturalNameComparer.Compare (cognitive 27) src/PanelRows.vb:126— NaturalNameComparer.Compare has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BgWorker_ProgressChanged (cognitive 27) src/Main_Form.FileScanning.vb:328— Main_Form.BgWorker_ProgressChanged has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BatchPlan.Build (cognitive 27) src/BatchPlan.vb:225— BatchPlan.Build has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Broadcasts_Form.PromptCreateBroadcastAsync (cognitive 27) src/FastMediaSorterCompanion/Forms/Share_Broadcasts_Form.vb:377— Share_Broadcasts_Form.PromptCreateBroadcastAsync has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeDirectorySnapshot.FromLocalJson (cognitive 27) src/Exchange/ExchangeDirectory.vb:270— ExchangeDirectorySnapshot.FromLocalJson has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
connstr.canonicalHost (cognitive 27) exchange-server/internal/connstr/connstr.go:338— connstr.canonicalHost has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 10, loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Relay.Listen (cognitive 27) exchange-server/internal/rendezvous/relay_handler.go:329— Relay.Listen has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (4 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 11). Of this number, 24 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Main_Form.ExecuteRecipientAction (cognitive 26) src/Main_Form.FileOperations.vb:909— Main_Form.ExecuteRecipientAction has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ApplyArgument (cognitive 26) src/Main_Form.Lifecycle.vb:538— Main_Form.ApplyArgument has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ArgumentProbing.Probe (cognitive 26) src/OpenCoordination.vb:57— ArgumentProbing.Probe has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TesseractOcrEngine.ScoreAttempt (cognitive 26) src/Ocr/TesseractOcrEngine.vb:816— TesseractOcrEngine.ScoreAttempt has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TextFileReader.DetectEncoding (cognitive 26) src/Documents/TextFileReader.vb:176— TextFileReader.DetectEncoding has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
GlyphRenderer.ApplyTransform (cognitive 26) src/Icons/GlyphRenderer.vb:171— GlyphRenderer.ApplyTransform has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.CanonicalHost (cognitive 26) src/Exchange/ExchangeConnectionString.vb:331— ExchangeConnectionString.CanonicalHost has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEnvelopeCodec.WriteMember (cognitive 26) src/Exchange/ExchangeEnvelope.vb:392— ExchangeEnvelopeCodec.WriteMember has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
connstr.Parse (cognitive 26) exchange-server/internal/connstr/connstr.go:185— connstr.Parse has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), match/switch 2 (4 pts), boolean chains 3, loops 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dir.Load (cognitive 26) exchange-server/internal/directory/directory.go:409— Dir.Load has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wire.CheckReceiver (cognitive 26) exchange-server/internal/wire/record.go:168— wire.CheckReceiver has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Main_Form.ApplyLiveChanges (cognitive 25) src/Main_Form.FolderWatch.vb:356— Main_Form.ApplyLiveChanges has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HostingReport.Render (cognitive 25) src/Support/HostingReport.vb:299— HostingReport.Render has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangePublisher.ComputePlanAsync (cognitive 25) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:386— ExchangePublisher.ComputePlanAsync has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FileDoDiskManager.RegisteredInstallDirectories (cognitive 25) src/FastMediaSorterCompanion/Core/FileDoDiskManager.vb:99— FileDoDiskManager.RegisteredInstallDirectories has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceAddActions.CommitAsync (cognitive 25) src/FastMediaSorterCompanion/Forms/MainWindow.ResourceAdd.vb:93— ResourceAddActions.CommitAsync has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceTransfer.MoveWithin (cognitive 24) src/Resources/ResourceTransfer.vb:103— ResourceTransfer.MoveWithin has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.LoadFilesForExternalInput (cognitive 24) src/Main_Form.MediaLoading.vb:894— Main_Form.LoadFilesForExternalInput has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrPlateColors.Compute (cognitive 24) src/Ocr/OcrPlateColors.vb:97— OcrPlateColors.Compute has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemeApplier.OnConvertedButtonPaint (cognitive 24) src/Theming/ThemeApplier.vb:445— ThemeApplier.OnConvertedButtonPaint has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DialogReflow.GrowTowardsStart (cognitive 24) src/DialogRules.vb:252— DialogReflow.GrowTowardsStart has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeSurface.LayoutItems (cognitive 24) src/Chrome/ChromeSurface.vb:337— ChromeSurface.LayoutItems has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ChromeConfigure (cognitive 24) src/Main_Form.Chrome.vb:623— Main_Form.ChromeConfigure has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RegBackup.CreateBackup (cognitive 24) src/ProfileReset/RegBackup.vb:116— RegBackup.CreateBackup has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.OnXAddAccount (cognitive 24) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:727— Share_Settings_Form.OnXAddAccount has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.StyleModernSettingsControlTree (cognitive 24) src/Table_Form.ModernLayout.vb:2369— Table_Form.StyleModernSettingsControlTree has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TransferExecutor.RenameWithin (cognitive 23) src/Resources/TransferPlan.vb:460— TransferExecutor.RenameWithin has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastReader.InflateSingleGzipMember (cognitive 23) src/LiveBroadcast/LiveBroadcastReader.vb:202— LiveBroadcastReader.InflateSingleGzipMember has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ProbeSlot (cognitive 23) src/Main_Form.SlotHealth.vb:306— Main_Form.ProbeSlot has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ProbeScheduler.Submit (cognitive 23) src/ProbeScheduler.vb:122— ProbeScheduler.Submit has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HostingReport.Gather (cognitive 23) src/Support/HostingReport.vb:225— HostingReport.Gather has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.BuildSettingsGroups (cognitive 23) src/Table_Form.SettingsGroups.vb:29— Table_Form.BuildSettingsGroups has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Utils.ReadExifOrientation (cognitive 23) src/Utils.vb:291— Utils.ReadExifOrientation has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
GlyphRenderer.Walk (cognitive 23) src/Icons/GlyphRenderer.vb:137— GlyphRenderer.Walk has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Ask_Dialog.Build (cognitive 23) src/Ask_Dialog.vb:68— Ask_Dialog.Build has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeMenu.HandleKey (cognitive 23) src/Chrome/ChromeMenu.vb:351— ChromeMenu.HandleKey has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ConfigureFloatingMediaChrome (cognitive 23) src/Main_Form.Chrome.vb:731— Main_Form.ConfigureFloatingMediaChrome has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CameraCaptureSource.FoldBitmap (cognitive 23) src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:234— CameraCaptureSource.FoldBitmap has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangePublisher.ChangeLinkAsync (cognitive 23) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:598— ExchangePublisher.ChangeLinkAsync has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangePublisher.HandleOpenAsync (cognitive 23) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:722— ExchangePublisher.HandleOpenAsync has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ScreenCaptureSource.FoldBitmap (cognitive 23) src/FastMediaSorterCompanion/Core/ScreenCaptureSource.vb:208— ScreenCaptureSource.FoldBitmap has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Qr_Zoom_Form.HandOff (cognitive 23) src/FastMediaSorterCompanion/Forms/Qr_Zoom_Form.vb:221— Qr_Zoom_Form.HandOff has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.OnXApplyPort (cognitive 23) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:363— Share_Settings_Form.OnXApplyPort has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsConfigExport.IsLanLikeHost (cognitive 23) src/Resources/FmsConfigExport.vb:182— FmsConfigExport.IsLanLikeHost has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Resource_List_Panel.OnTest (cognitive 23) src/Resource_List_Panel.vb:998— Resource_List_Panel.OnTest has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.run (cognitive 23) exchange-server/cmd/exchange-probe/main.go:31— main.run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, loops 2 (3 pts), match/switch 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransferExecutor.Perform (cognitive 22) src/Resources/TransferPlan.vb:276— TransferExecutor.Perform has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AdtsFrameCounter.Feed (cognitive 22) src/LiveBroadcast/AdtsFrameCounter.vb:59— AdtsFrameCounter.Feed has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ResolveConfiguredCollision (cognitive 22) src/Main_Form.FileOperations.vb:628— Main_Form.ResolveConfiguredCollision has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TransportRules.ArrangeRow (cognitive 22) src/TransportRules.vb:53— TransportRules.ArrangeRow has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.LocalizeSettingsDiscovery (cognitive 22) src/Table_Form.SettingsDiscovery.vb:263— Table_Form.LocalizeSettingsDiscovery has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Utils.GetImageDimensions (cognitive 22) src/Utils.vb:228— Utils.GetImageDimensions has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ChromeHandleKey (cognitive 22) src/Main_Form.Chrome.vb:1321— Main_Form.ChromeHandleKey has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEndpointRules.TryParse (cognitive 22) src/FastMediaSorterCompanion/Core/ExchangeEndpointRules.vb:48— ExchangeEndpointRules.TryParse has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WasapiAudioSource.PumpPackets (cognitive 22) src/FastMediaSorterCompanion/Core/WasapiAudioSource.vb:328— WasapiAudioSource.PumpPackets has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.ResetPasswordFor (cognitive 22) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAdmin.vb:780— Share_Settings_Form.ResetPasswordFor has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.SplitEndpoint (cognitive 22) src/Exchange/ExchangeConnectionString.vb:300— ExchangeConnectionString.SplitEndpoint has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.RenderIPv6 (cognitive 22) src/Exchange/ExchangeConnectionString.vb:443— ExchangeConnectionString.RenderIPv6 has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PaintHaloFade (cognitive 22) src/Main_Form.PerspectiveHalo.vb:367— Main_Form.PaintHaloFade has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeSync.AttachAsync (cognitive 22) src/Resources/ExchangeDevices.vb:332— ExchangeSync.AttachAsync has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.ModernComboBox_Paint (cognitive 22) src/Table_Form.ModernLayout.vb:209— Table_Form.ModernComboBox_Paint has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Enroll.validate (cognitive 22) exchange-server/internal/wire/validate.go:54— Enroll.validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, loops 2, match/switch 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Main_Form.EnterResource (cognitive 21) src/Main_Form.Resource.vb:108— Main_Form.EnterResource has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.InitializeVlcCoreAsync (cognitive 21) src/Main_Form.VideoPlayer.vb:259— Main_Form.InitializeVlcCoreAsync has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.TranslateCurrentImage (cognitive 21) src/Main_Form.OcrTranslate.vb:286— Main_Form.TranslateCurrentImage has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrOverlayFit.MedianLineHeight (cognitive 21) src/Ocr/OcrOverlayFit.vb:70— OcrOverlayFit.MedianLineHeight has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsConfigReader.FindDuplicate (cognitive 21) src/Resources/FmsConfigReader.vb:578— FmsConfigReader.FindDuplicate has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PaintContentPlaceholder (cognitive 21) src/Main_Form.PlaceholderView.vb:85— Main_Form.PaintContentPlaceholder has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.UpdateWelcomeInvite (cognitive 21) src/Main_Form.Welcome.vb:132— Main_Form.UpdateWelcomeInvite has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeDeviceAgent.HandleAsync (cognitive 21) src/FastMediaSorterCompanion/Core/ExchangeDeviceAgent.vb:708— ExchangeDeviceAgent.HandleAsync has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TrayContext.Dispose (cognitive 21) src/FastMediaSorterCompanion/TrayContext.vb:862— TrayContext.Dispose has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeControlSession.RunAsync (cognitive 21) src/Exchange/ExchangeControlSession.vb:173— ExchangeControlSession.RunAsync has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEntryStore.ReadEntry (cognitive 21) src/Exchange/ExchangeEntries.vb:208— ExchangeEntryStore.ReadEntry has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Exchange_Devices_Panel.Toggle (cognitive 21) src/Exchange_Devices_Panel.vb:700— Exchange_Devices_Panel.Toggle has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceImport.FindExisting (cognitive 21) src/Resources/ResourceImport.vb:209— ResourceImport.FindExisting has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceMatching.FindMatchingDescriptor (cognitive 20) src/Resources/ResourcePolicy.vb:181— ResourceMatching.FindMatchingDescriptor has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceMatching.FindForAddress (cognitive 20) src/Resources/ResourcePolicy.vb:217— ResourceMatching.FindForAddress has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceCommit.Commit (cognitive 20) src/Resources/ResourceCommit.vb:118— ResourceCommit.Commit has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SmbConnectionManager.ReleaseLease (cognitive 20) src/Resources/SmbConnectionLease.vb:323— SmbConnectionManager.ReleaseLease has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.EnsureEntryLocal (cognitive 20) src/Main_Form.Resource.vb:274— Main_Form.EnsureEntryLocal has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.RunFileOp (cognitive 20) src/Main_Form.FileOperations.vb:137— Main_Form.RunFileOp has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.RenameCurrentFile (cognitive 20) src/Main_Form.FileOperations.vb:735— Main_Form.RenameCurrentFile has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.LayoutRow1 (cognitive 20) src/Main_Form.ToolbarOverflow.vb:172— Main_Form.LayoutRow1 has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PaintOcrOverlay (cognitive 20) src/Main_Form.OcrOverlay.vb:120— Main_Form.PaintOcrOverlay has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Image_Editor_Form.Image_Editor_Form_KeyDown (cognitive 20) src/Image_Editor_Form.vb:654— Image_Editor_Form.Image_Editor_Form_KeyDown has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrBlockBuilder.BuildBlocks (cognitive 20) src/Ocr/OcrBlockBuilder.vb:133— OcrBlockBuilder.BuildBlocks has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrOverlayFit.GrowthBudget (cognitive 20) src/Ocr/OcrOverlayFit.vb:137— OcrOverlayFit.GrowthBudget has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TesseractOcrEngine.ReadPageLines (cognitive 20) src/Ocr/TesseractOcrEngine.vb:520— TesseractOcrEngine.ReadPageLines has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ButtonGlyphs.ArrangeContent (cognitive 20) src/Icons/ButtonGlyphs.vb:396— ButtonGlyphs.ArrangeContent has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DialogReflow.GrowVertical (cognitive 20) src/DialogRules.vb:209— DialogReflow.GrowVertical has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeSurface.PaintMenuRowTail (cognitive 20) src/Chrome/ChromeSurface.vb:768— ChromeSurface.PaintMenuRowTail has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEndpointRules.IsPlausibleHostName (cognitive 20) src/FastMediaSorterCompanion/Core/ExchangeEndpointRules.vb:82— ExchangeEndpointRules.IsPlausibleHostName has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
InternetAccessForm.RefreshStatusAsync (cognitive 20) src/FastMediaSorterCompanion/Forms/InternetAccessForm.vb:159— InternetAccessForm.RefreshStatusAsync has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.OnConfigureFolder (cognitive 20) src/FastMediaSorterCompanion/Forms/MainWindow.Folders.vb:66— MainWindow.OnConfigureFolder has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.SettingsSearchEntries (cognitive 20) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Discovery.vb:61— Share_Settings_Form.SettingsSearchEntries has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeJsonWriter.WriteString (cognitive 20) src/Exchange/ExchangeJson.vb:149— ExchangeJsonWriter.WriteString has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsSftpCode.IsUsable (cognitive 20) src/Exchange/FmsSftpCode.vb:99— FmsSftpCode.IsUsable has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeLinkTunnelSource.OpenAsync (cognitive 20) src/Resources/ExchangeTunnel.vb:301— ExchangeLinkTunnelSource.OpenAsync has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
accounts.Open (cognitive 20) exchange-server/internal/accounts/store.go:168— accounts.Open has cognitive complexity 20 (threshold 15). Drivers by points: if/else 16, loops 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Store.Enroll (cognitive 20) exchange-server/internal/accounts/store.go:497— Store.Enroll has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dir.BroadcastStart (cognitive 20) exchange-server/internal/directory/ops.go:443— Dir.BroadcastStart has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
wave-particles.drawFrame (cognitive 20) assets/wave-particles.js:172— wave-particles.drawFrame has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 3 (4 pts), ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wave-particles.attach (cognitive 20) assets/wave-particles.js:462— wave-particles.attach has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, boolean chains 7, ternaries 2. Of this number, 14 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FileManager.LoadImageWithStream (cognitive 19) src/FileManager.vb:27— FileManager.LoadImageWithStream has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ActivateShareEntryPointAsync (cognitive 19) src/Main_Form.ShareLauncher.vb:200— Main_Form.ActivateShareEntryPointAsync has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DeleteVolumeProbe.ReadBinSettings (cognitive 19) src/DeleteVolumeProbe.vb:132— DeleteVolumeProbe.ReadBinSettings has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.TryHandleCustomHotkey (cognitive 19) src/Main_Form.CustomHotkeys.vb:47— Main_Form.TryHandleCustomHotkey has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrTextFilter.IsWholeAddress (cognitive 19) src/Ocr/OcrTextFilter.vb:247— OcrTextFilter.IsWholeAddress has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrDiagnostics.BuildDumpLine (cognitive 19) src/Ocr/OcrDiagnostics.vb:167— OcrDiagnostics.BuildDumpLine has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OllamaManager.DownloadInstallerAsync (cognitive 19) src/Translate/OllamaManager.vb:132— OllamaManager.DownloadInstallerAsync has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LogPackage.DescribeSettings (cognitive 19) src/Support/LogPackage.vb:861— LogPackage.DescribeSettings has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FmsConfigReader.Parse (cognitive 19) src/Resources/FmsConfigReader.vb:310— FmsConfigReader.Parse has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.OpenContentInDefaultProgram (cognitive 19) src/Main_Form.PlaceholderView.vb:167— Main_Form.OpenContentInDefaultProgram has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemeApplier.ApplyButton (cognitive 19) src/Theming/ThemeApplier.vb:378— ThemeApplier.ApplyButton has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangePublisher.PublishOneAsync (cognitive 19) src/FastMediaSorterCompanion/Core/ExchangePublisher.vb:496— ExchangePublisher.PublishOneAsync has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RouterInfo.SsdpDiscoverIgdLocation (cognitive 19) src/FastMediaSorterCompanion/Core/RouterInfo.vb:86— RouterInfo.SsdpDiscoverIgdLocation has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ShareController.EnsureRunningReconciledAsync (cognitive 19) src/FastMediaSorterCompanion/Core/ShareController.vb:208— ShareController.EnsureRunningReconciledAsync has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.UpdateSectionSummaries (cognitive 19) src/FastMediaSorterCompanion/Forms/MainWindow.Access.vb:426— MainWindow.UpdateSectionSummaries has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectFlow.RunAsync (cognitive 19) src/Exchange/ExchangeConnectFlow.vb:65— ExchangeConnectFlow.RunAsync has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.Build (cognitive 19) src/Exchange/ExchangeConnectionString.vb:227— ExchangeConnectionString.Build has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModernViewerPreferences.NormalizeExtensionJson (cognitive 19) src/ModernViewerPreferences.vb:858— ModernViewerPreferences.NormalizeExtensionJson has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.RefreshModernSettingsHeader (cognitive 19) src/Table_Form.ModernLayout.vb:763— Table_Form.RefreshModernSettingsHeader has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.generateRecords (cognitive 19) exchange-server/cmd/exchange-vectors/records.go:94— main.generateRecords has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 2, loops 1 (nesting depth added 5). None of this is in the body itself: all 19 points belong to 6 function literals inside it that branch (lines 116, 256, 193, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Config.Validate (cognitive 19) exchange-server/internal/config/config.go:213— Config.Validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, loops 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ArchiveSession.EnsureExtractedCore (cognitive 18) src/Archives/ArchiveSession.vb:344— ArchiveSession.EnsureExtractedCore has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceFailure.FromException (cognitive 18) src/Resources/ResourceFailure.vb:77— ResourceFailure.FromException has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
VlcArtCache.PlanScrub (cognitive 18) src/VlcArtCache.vb:76— VlcArtCache.PlanScrub has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.PaintEmptyState (cognitive 18) src/Main_Form.Notify.vb:168— Main_Form.PaintEmptyState has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.OnLiveState (cognitive 18) src/Main_Form.LiveBroadcast.vb:324— Main_Form.OnLiveState has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
RecycleBinIndex.TryParse (cognitive 18) src/RecycleBinIndex.vb:74— RecycleBinIndex.TryParse has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SelectionModel.RemovePaths (cognitive 18) src/BatchSelection.vb:112— SelectionModel.RemovePaths has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DocHtmlTranslate.FindExe (cognitive 18) src/DocHtmlTranslateLauncher.vb:36— DocHtmlTranslate.FindExe has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.TrackLanguage (cognitive 18) src/Main_Form.VideoTracks.vb:117— Main_Form.TrackLanguage has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ApplyFolderChangesAsync (cognitive 18) src/Main_Form.FolderWatch.vb:292— Main_Form.ApplyFolderChangesAsync has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EditorGeometry.CropHandleAt (cognitive 18) src/EditorGeometry.vb:180— EditorGeometry.CropHandleAt has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrLineSplitter.RegroupIntoColumns (cognitive 18) src/Ocr/OcrLineSplitter.vb:186— OcrLineSplitter.RegroupIntoColumns has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrPlateColors.RingSaysInverted (cognitive 18) src/Ocr/OcrPlateColors.vb:164— OcrPlateColors.RingSaysInverted has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LogPackage.BuildReport (cognitive 18) src/Support/LogPackage.vb:660— LogPackage.BuildReport has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HostingProbesLive.ReadListeners (cognitive 18) src/Support/HostingProbesLive.vb:534— HostingProbesLive.ReadListeners has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SettingsUiContext.Read (cognitive 18) src/SettingsUiContext.vb:57— SettingsUiContext.Read has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Table_Form.RefreshSettingsDependencies (cognitive 18) src/Table_Form.SettingsDiscovery.vb:310— Table_Form.RefreshSettingsDependencies has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
M3uPlaylistReader.ParseAndAddEntry (cognitive 18) src/Streams/M3uPlaylistReader.vb:192— M3uPlaylistReader.ParseAndAddEntry has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
M3uPlaylistReader.ClassifyMediaKind (cognitive 18) src/Streams/M3uPlaylistReader.vb:378— M3uPlaylistReader.ClassifyMediaKind has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BuildStreamCatalogViaDialog (cognitive 18) src/Main_Form.Streams.vb:16— Main_Form.BuildStreamCatalogViaDialog has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HelpCardRows.SlotKeys (cognitive 18) src/HelpCardRows.vb:157— HelpCardRows.SlotKeys has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DialogLayout.FitContent (cognitive 18) src/DialogLayout.vb:74— DialogLayout.FitContent has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BuildChromeMenuEntries (cognitive 18) src/Main_Form.ChromeMenus.vb:42— Main_Form.BuildChromeMenuEntries has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ChromePanelRect (cognitive 18) src/Main_Form.Chrome.vb:918— Main_Form.ChromePanelRect has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
BroadcastConfigBuilder.ClassifyMediaKind (cognitive 18) src/FastMediaSorterCompanion/Core/BroadcastConfigBuilder.vb:170— BroadcastConfigBuilder.ClassifyMediaKind has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiskDriveLetters.Reconcile (cognitive 18) src/FastMediaSorterCompanion/Core/DiskDriveLetters.vb:84— DiskDriveLetters.Reconcile has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeService.TryControl (cognitive 18) src/FastMediaSorterCompanion/Core/ExchangeService.vb:220— ExchangeService.TryControl has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CompanionCommand.CanonicalFolder (cognitive 18) src/FastMediaSorterCompanion/Core/ShareActivation.vb:103— CompanionCommand.CanonicalFolder has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ShareRootParamsStore.Map (cognitive 18) src/FastMediaSorterCompanion/Core/ShareRootParams.vb:204— ShareRootParamsStore.Map has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.RefreshExternalRoots (cognitive 18) src/FastMediaSorterCompanion/Forms/MainWindow.Disks.vb:30— MainWindow.RefreshExternalRoots has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.PaintSettingsNavigation (cognitive 18) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Navigation.vb:444— Share_Settings_Form.PaintSettingsNavigation has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEntrySession.GetDirectoryAsync (cognitive 18) src/Exchange/ExchangeEntrySession.vb:229— ExchangeEntrySession.GetDirectoryAsync has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeResourceRecordBuilder.TryBuild (cognitive 18) src/Exchange/ExchangeResourceAccess.vb:131— ExchangeResourceRecordBuilder.TryBuild has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.run (cognitive 18) exchange-server/cmd/exchange-vectors/main.go:26— main.run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
relay.pump (cognitive 18) exchange-server/internal/relay/splice.go:76— relay.pump has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Server.envelopes (cognitive 18) exchange-server/internal/rendezvous/stream.go:213— Server.envelopes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3, boolean chains 2 (nesting depth added 4). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppFileLogger.ResetForTesting (cognitive 17) src/AppFileLogger.vb:54— AppFileLogger.ResetForTesting has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceLocator.TryDecodePath (cognitive 17) src/Resources/ResourceRegistry.vb:414— ResourceLocator.TryDecodePath has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.AskForPasswordAndOpen (cognitive 17) src/Main_Form.Secure.vb:377— Main_Form.AskForPasswordAndOpen has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.SecureVerifyCurrent (cognitive 17) src/Main_Form.Secure.vb:945— Main_Form.SecureVerifyCurrent has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FileManager.MoveFile (cognitive 17) src/FileManager.vb:356— FileManager.MoveFile has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ExecuteDelete (cognitive 17) src/Main_Form.FileOperations.vb:1537— Main_Form.ExecuteDelete has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BgWorker_RunWorkerCompleted (cognitive 17) src/Main_Form.FileScanning.vb:405— Main_Form.BgWorker_RunWorkerCompleted has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.CompanionExePath (cognitive 17) src/Main_Form.ShareLauncher.vb:391— Main_Form.CompanionExePath has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.SendToCompanionOnce (cognitive 17) src/Main_Form.ShareLauncher.vb:439— Main_Form.SendToCompanionOnce has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OcrLanguageGuard.RefusalReason (cognitive 17) src/Ocr/OcrLanguageGuard.vb:103— OcrLanguageGuard.RefusalReason has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TranslateHttp.JsonItemToString (cognitive 17) src/Translate/OllamaTranslator.vb:125— TranslateHttp.JsonItemToString has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TextFileReader.ReadBytes (cognitive 17) src/Documents/TextFileReader.vb:103— TextFileReader.ReadBytes has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SettingsNumericStepper.PaintButtons (cognitive 17) src/SettingsNumericStepper.vb:81— SettingsNumericStepper.PaintButtons has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemeApplier.ApplyNative (cognitive 17) src/Theming/ThemeApplier.vb:606— ThemeApplier.ApplyNative has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeTheme.FillFor (cognitive 17) src/Chrome/ChromeTheme.vb:154— ChromeTheme.FillFor has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ChromeSurface.MeasureItemWidth (cognitive 17) src/Chrome/ChromeSurface.vb:234— ChromeSurface.MeasureItemWidth has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LiveBroadcastHost.EnumerateLanCandidates (cognitive 17) src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:66— LiveBroadcastHost.EnumerateLanCandidates has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SectionHeader.OnPaint (cognitive 17) src/FastMediaSorterCompanion/Forms/CollapsibleSection.vb:426— SectionHeader.OnPaint has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Share_Settings_Form.ApplyAccountState (cognitive 17) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAccount.vb:221— Share_Settings_Form.ApplyAccountState has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TrayContext.ViewerExePath (cognitive 17) src/FastMediaSorterCompanion/TrayContext.vb:801— TrayContext.ViewerExePath has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeEntrySession.GetAccessAsync (cognitive 17) src/Exchange/ExchangeEntrySession.vb:257— ExchangeEntrySession.GetAccessAsync has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeAgentLocator.CompanionExePath (cognitive 17) src/Resources/ExchangeDevices.vb:108— ExchangeAgentLocator.CompanionExePath has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeSync.FollowAllAsync (cognitive 17) src/Resources/ExchangeDevices.vb:435— ExchangeSync.FollowAllAsync has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.runInspect (cognitive 17) exchange-server/cmd/fms-exchange-server/inspect.go:35— main.runInspect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Engine.handle (cognitive 17) exchange-server/internal/rendezvous/engine_control.go:61— Engine.handle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 2 (3 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MyApplication.TryForwardOnce (cognitive 16) src/Application_Events.vb:348— MyApplication.TryForwardOnce has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceLocator.TryDecode (cognitive 16) src/Resources/ResourceRegistry.vb:378— ResourceLocator.TryDecode has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HostKeyGate.VerifyCore (cognitive 16) src/Resources/HostKeyGate.vb:124— HostKeyGate.VerifyCore has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PanelThumbnailLoader.Work (cognitive 16) src/PanelThumbnailLoader.vb:165— PanelThumbnailLoader.Work has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ApplyModernPreferencesFromSettings (cognitive 16) src/Main_Form.ModernPreferences.vb:81— Main_Form.ApplyModernPreferencesFromSettings has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FileDetails.JpegSofInfo (cognitive 16) src/FileDetails.vb:284— FileDetails.JpegSofInfo has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.BatchOpFinished (cognitive 16) src/Main_Form.Batch.vb:518— Main_Form.BatchOpFinished has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ISizeChanged (cognitive 16) src/Main_Form.UILayout.vb:16— Main_Form.ISizeChanged has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.ApplyScriptFont (cognitive 16) src/Main_Form.Localization.vb:170— Main_Form.ApplyScriptFont has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.RunningCompanionVersion (cognitive 16) src/Main_Form.ShareLauncher.vb:291— Main_Form.RunningCompanionVersion has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DiskCacheTrim.Measure (cognitive 16) src/DiskCacheTrim.vb:80— DiskCacheTrim.Measure has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Main_Form.RefreshVideoControlsState (cognitive 16) src/Main_Form.VideoControls.vb:546— Main_Form.RefreshVideoControlsState has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
OptionalRuntimeManager.InstallRuntimePackageAsyncCore (cognitive 16) src/OptionalRuntimeManager.vb:544— OptionalRuntimeManager.InstallRuntimePackageAsyncCore has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Localization.HighestPlaceholder (cognitive 16) src/Localization/Localization.vb:201— Localization.HighestPlaceholder has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SettingsImportBackupStore.Create (cognitive 16) src/SettingsImport.vb:101— SettingsImportBackupStore.Create has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SettingsImportBackupStore.EnsurePrivateDirectory (cognitive 16) src/SettingsImport.vb:174— SettingsImportBackupStore.EnsurePrivateDirectory has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ThemedMenuRenderer.OnRenderItemText (cognitive 16) src/Theming/ThemedMenuRenderer.vb:26— ThemedMenuRenderer.OnRenderItemText has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
HelpCardPanel.OnPaint (cognitive 16) src/HelpCardPanel.vb:330— HelpCardPanel.OnPaint has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WasapiAudioSource.ConvertToPcm (cognitive 16) src/FastMediaSorterCompanion/Core/WasapiAudioSource.vb:361— WasapiAudioSource.ConvertToPcm has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
InternetAccessForm.Render (cognitive 16) src/FastMediaSorterCompanion/Forms/InternetAccessForm.vb:181— InternetAccessForm.Render has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MainWindow.OnToggle (cognitive 16) src/FastMediaSorterCompanion/Forms/MainWindow.Folders.vb:588— MainWindow.OnToggle has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PackageWizardForm.PopulateGrid (cognitive 16) src/FastMediaSorterCompanion/Forms/PackageWizardForm.vb:373— PackageWizardForm.PopulateGrid has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeConnectionString.TryCanonicalIPv4 (cognitive 16) src/Exchange/ExchangeConnectionString.vb:354— ExchangeConnectionString.TryCanonicalIPv4 has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ExchangeResourceAccess.TryRead (cognitive 16) src/Exchange/ExchangeResourceAccess.vb:76— ExchangeResourceAccess.TryRead has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Exchange_Devices_Panel.Relayout (cognitive 16) src/Exchange_Devices_Panel.vb:368— Exchange_Devices_Panel.Relayout has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
main.serveSFTP (cognitive 16) exchange-server/cmd/exchange-fakeproducer/main.go:95— main.serveSFTP has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 112). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
connstr.splitEndpoint (cognitive 16) exchange-server/internal/connstr/connstr.go:280— connstr.splitEndpoint has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scmHandler.Execute (cognitive 16) exchange-server/internal/deploy/service_windows.go:76— scmHandler.Execute has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 1 (5 pts), loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/Exchange_Connect_Form.vb:60— src/Exchange_Connect_Form.vb:60-127 | src/Resource_Credential_Form.vb:49-137 | src/Resource_Edit_Form.vb:62-167 | src/Resource_Export_Form.vb:31-106 | src/Resource_Manager_Form.vb:43-92 | src/Secure_Password_Form.vb:66-156 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) exchange-server/cmd/fms-exchange-server/connstring.go:27— exchange-server/cmd/fms-exchange-server/connstring.go:27-75 | exchange-server/cmd/fms-exchange-server/setendpoint.go:15-40 | exchange-server/cmd/fms-exchange-server/setlisten.go:15-36 | exchange-server/cmd/fms-exchange-server/setportrange.go:18-50 | exchange-server/cmd/fms-exchange-server/tlscmd.go:35-81 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) exchange-server/internal/testkit/device.go:107— exchange-server/internal/testkit/device.go:107-127 | exchange-server/internal/testkit/device.go:198-212 | exchange-server/internal/testkit/device.go:215-233 | REDACTED:57-79 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (57–59 lines × 2) src/Resource_Credential_Form.vb:81— src/Resource_Credential_Form.vb:81-137 | src/Secure_Password_Form.vb:98-156 — before extracting anything, compare `src/Resource_Credential_Form.vb` and `src/Secure_Password_Form.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Secure_Password_Form.vb:96` calls `Sub`, `ClearWarning` and `src/Resource_Credential_Form.vb:79` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (50 lines × 2) src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:101— src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb:101-150 | src/Resources/ExportWriter.vb:97-146 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/ProtectedConfigWriter.vb` and `src/Resources/ExportWriter.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 132 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (48–50 lines × 2) src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:235— src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:235-282 | src/FastMediaSorterCompanion/Core/ScreenCaptureSource.vb:209-258 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:233` calls `walks` and `src/FastMediaSorterCompanion/Core/ScreenCaptureSource.vb:206` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (29–31 lines × 2) src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:288— src/FastMediaSorterCompanion/Core/CameraCaptureSource.vb:288-316 | src/FastMediaSorterCompanion/Core/ScreenCaptureSource.vb:265-295 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (28 lines × 2) src/Streams/StreamIdentity.vb:38— src/Streams/StreamIdentity.vb:38-65 | src/Streams/StreamIdentity.vb:81-108 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 3) src/Exchange/ExchangeCredentialStore.vb:90— src/Exchange/ExchangeCredentialStore.vb:90-109 | src/FastMediaSorterCompanion/Core/ExchangeAccountPasswordStore.vb:146-165 | src/FastMediaSorterCompanion/Core/ExchangeProducerStore.vb:228-247 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (18–19 lines × 2) src/Resource_Credential_Form.vb:56— src/Resource_Credential_Form.vb:56-73 | src/Secure_Password_Form.vb:72-90 — before extracting anything, compare `src/Resource_Credential_Form.vb` and `src/Secure_Password_Form.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Resource_Credential_Form.vb:56` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) src/FastMediaSorterCompanion/Core/ShareController.vb:55— src/FastMediaSorterCompanion/Core/ShareController.vb:55-68 | src/FastMediaSorterCompanion/Core/ShareController.vb:289-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 6) src/Exchange_Connect_Form.vb:64— src/Exchange_Connect_Form.vb:64-75 | src/Resource_Credential_Form.vb:52-63 | src/Resource_Edit_Form.vb:69-80 | src/Resource_Export_Form.vb:36-47 | src/Resource_Manager_Form.vb:46-57 | src/Secure_Password_Form.vb:68-79 — before extracting anything, compare `src/Resource_Credential_Form.vb` and `src/Secure_Password_Form.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Resource_Export_Form.vb:35` calls `Size` and `src/Secure_Password_Form.vb:67` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 4) src/FastMediaSorterCompanion/Forms/Exchange_Account_Admin_Form.vb:93— src/FastMediaSorterCompanion/Forms/Exchange_Account_Admin_Form.vb:93-103 | src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:102-112 | src/FastMediaSorterCompanion/Forms/Exchange_Link_Form.vb:54-64 | src/FastMediaSorterCompanion/Forms/Exchange_Password_Form.vb:103-113 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/FastMediaSorterCompanion/Forms/Exchange_Account_Form.vb:100` calls `Cancel`, `Dispose` and `src/FastMediaSorterCompanion/Forms/Exchange_Password_Form.vb:102` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 3) src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:68— src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:68-78 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:23-34 | src/FastMediaSorterCompanion/Core/NetworkInfo.vb:143-154 — before extracting anything, compare `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb` and `src/FastMediaSorterCompanion/Core/NetworkInfo.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/FastMediaSorterCompanion/Core/NetworkInfo.vb:155` calls `IsPhysicalNic`, `LooksVirtualNic` and `src/FastMediaSorterCompanion/Core/LiveBroadcastHost.vb:80` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) src/Main_Form.FileScanning.vb:668— src/Main_Form.FileScanning.vb:668-677 | src/Main_Form.vb:798-808 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) src/FastMediaSorterCompanion/TrayContext.vb:812— src/FastMediaSorterCompanion/TrayContext.vb:812-818 | src/Main_Form.ShareLauncher.vb:404-410 | src/Resources/ExchangeDevices.vb:114-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/FastMediaSorterCompanion/TrayContext.vb:812` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–8 lines × 2) src/Ocr/OcrDiagnostics.vb:177— src/Ocr/OcrDiagnostics.vb:177-182 | src/Ocr/OcrDiagnostics.vb:206-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Ocr/OcrDiagnostics.vb:206` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) src/Exchange/ExchangeConnectionString.vb:513— src/Exchange/ExchangeConnectionString.vb:513-519 | src/Exchange/FmsSftpCode.vb:235-242 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 2) src/FastMediaSorterCompanion/Localization/Localization.AppUx.vb:199— src/FastMediaSorterCompanion/Localization/Localization.AppUx.vb:199-205 | src/Localization/Localization.Support.vb:19-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/FastMediaSorterCompanion/Localization/Localization.AppUx.vb:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (35 lines × 2) src/FastMediaSorterCompanion/Core/SecureClipboard.vb:43— src/FastMediaSorterCompanion/Core/SecureClipboard.vb:43-78 | src/Resources/SecretClipboard.vb:42-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 4) src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:102— src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Exchange.vb:102-106 | src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeAccount.vb:90-94 | src/FastMediaSorterCompanion/Forms/Share_Settings_Form.ExchangeProducer.vb:66-70 | src/FastMediaSorterCompanion/Forms/Share_Settings_Form.Hosting.vb:137-142 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (13 lines × 3) REDACTED:108— REDACTED:108-120 | REDACTED:70-82 | REDACTED:229-241 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 5) exchange-server/cmd/fms-exchange-server/connstring.go:28— exchange-server/cmd/fms-exchange-server/connstring.go:28-36 | exchange-server/cmd/fms-exchange-server/setendpoint.go:16-24 | exchange-server/cmd/fms-exchange-server/setlisten.go:16-24 | exchange-server/cmd/fms-exchange-server/setportrange.go:19-27 | exchange-server/cmd/fms-exchange-server/tlscmd.go:36-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Coverage not measured — no coverage collector is wired up — 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.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
README/code drift exchange-server/README.md:160— exchange-server/README.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists. 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.
README/code drift docs/contracts/ANYWHERE-ACCESS.md:12— docs/contracts/ANYWHERE-ACCESS.md names `vectors/descriptor-v2.json`, but no file or folder `vectors/descriptor-v2.json` exists. 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.
README/code drift docs/contracts/DEVICE-EXCHANGE.md:33— docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-11-fmsw-vectors.md`, but no file or folder `PROPOSAL-2026-10-11-fmsw-vectors.md` exists. 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.
README/code drift docs/contracts/DEVICE-EXCHANGE.md:41— docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-10-exchange-connection-string.md`, but no file or folder `PROPOSAL-2026-10-10-exchange-connection-string.md` exists. 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.
README/code drift docs/contracts/DEVICE-EXCHANGE.md:62— docs/contracts/DEVICE-EXCHANGE.md names `PROPOSAL-2026-10-12-access-and-connection-experience.md`, but no file or folder `PROPOSAL-2026-10-12-access-and-connection-experience.md` exists. 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.
README/code drift docs/contracts/FDSEC.md:7— docs/contracts/FDSEC.md names `FDSEC-FORMAT.md`, but no file or folder `FDSEC-FORMAT.md` exists. 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.
README/code drift docs/contracts/FDSEC.md:7— docs/contracts/FDSEC.md names `FD-SEC-CONTRACT.md`, but no file or folder `FD-SEC-CONTRACT.md` exists. 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.
README/code drift docs/contracts/FDSEC.md:64— docs/contracts/FDSEC.md names `PROPOSAL-2026-09-22-streaming-reader.md`, but no file or folder `PROPOSAL-2026-09-22-streaming-reader.md` exists. 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.
README/code drift docs/contracts/FDSEC.md:74— docs/contracts/FDSEC.md names `PROPOSAL-2026-09-30-sealed-name-parity.md`, but no file or folder `PROPOSAL-2026-09-30-sealed-name-parity.md` exists. 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.
README/code drift docs/contracts/FMSCFG.md:7— docs/contracts/FMSCFG.md names `CONFIG_FORMAT.md`, but no file or folder `CONFIG_FORMAT.md` exists. 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.
README/code drift docs/contracts/FMSCFG.md:31— docs/contracts/FMSCFG.md names `PROPOSAL-2026-09-25-fms-windows-producer.md`, but no file or folder `PROPOSAL-2026-09-25-fms-windows-producer.md` exists. 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.
README/code drift docs/contracts/FMSCFG.md:94— docs/contracts/FMSCFG.md names `PROPOSAL-2026-09-22-canonical-vectors-per-producer.md`, but no file or folder `PROPOSAL-2026-09-22-canonical-vectors-per-producer.md` exists. 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.
README/code drift docs/contracts/INSTALL-TRUST.md:7— docs/contracts/INSTALL-TRUST.md names `TRUST_GUIDE.md`, but no file or folder `TRUST_GUIDE.md` exists. 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.
README/code drift docs/contracts/LETTERBOX-FILL.md:7— docs/contracts/LETTERBOX-FILL.md names `vectors/letterbox-fill-vectors.json`, but no file or folder `vectors/letterbox-fill-vectors.json` exists. 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.
README/code drift docs/contracts/LIVE-BROADCAST.md:7— docs/contracts/LIVE-BROADCAST.md names `11_live_broadcast_contract.md`, but no file or folder `11_live_broadcast_contract.md` exists. 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.
README/code drift docs/contracts/LIVE-BROADCAST.md:7— docs/contracts/LIVE-BROADCAST.md names `13_contract_amendment_2026-10-07.md`, but no file or folder `13_contract_amendment_2026-10-07.md` exists. 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.
README/code drift docs/contracts/RULE-ADOPTION.md:31— docs/contracts/RULE-ADOPTION.md documents the environment variable `RELEASE_AND_DISTRIBUTION`, but no code, script or configuration file names it. 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.
README/code drift docs/contracts/SHARE-SESSION.md:7— docs/contracts/SHARE-SESSION.md names `share-session-reconnect.md`, but no file or folder `share-session-reconnect.md` exists. 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.
README/code drift docs/contracts/STREAM-BANK.md:18— docs/contracts/STREAM-BANK.md names `streams.csv`, but no file or folder `streams.csv` exists. 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.
README/code drift docs/contracts/WAVE-PARTICLES.md:30— docs/contracts/WAVE-PARTICLES.md documents the environment variable `SPI_GETCLIENTAREAANIMATION`, but no code, script or configuration file names it. 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.
README/code drift docs/contracts/WAVE-PARTICLES.md:38— docs/contracts/WAVE-PARTICLES.md documents the environment variable `DWMWA_CLOAKED`, but no code, script or configuration file names it. 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.
README/code drift docs/contracts/WORKER-IPC.md:11— docs/contracts/WORKER-IPC.md names `SPECIFICATION_ANDROID_FOLDER_SHARE.md`, but no file or folder `SPECIFICATION_ANDROID_FOLDER_SHARE.md` exists. 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.
README/code drift docs/contracts/WORKER-IPC.md:65— docs/contracts/WORKER-IPC.md names `PROPOSAL-2026-10-07-broadcast-supported.md`, but no file or folder `PROPOSAL-2026-10-07-broadcast-supported.md` exists. 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.
README/code drift docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md:129— docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md names `project.assets.json`, but no file or folder `project.assets.json` exists. 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.
README/code drift docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md:175— docs/guides/PROGRESS_DOTNET10_MODERN_BUILD.md documents the environment variable `ATTACH_VIRTUAL_DISK_FLAG_READ_ONLY`, but no code, script or configuration file names it. 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.
Duplicated predicate exchange-server/cmd/fms-exchange-server/connstring.go:30— `err != nil && !errors.Is(err, os.ErrNotExist)` appears character-identically in 5 files — exchange-server/cmd/fms-exchange-server/connstring.go, exchange-server/cmd/fms-exchange-server/setendpoint.go, exchange-server/cmd/fms-exchange-server/setlisten.go, exchange-server/cmd/fms-exchange-server/setportrange.go. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:115— `len(raw) == 0 || tlsid.Fingerprint(raw[0]) != pin` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `FastMediaSorter.Modern` (116245 LoC, 153 public types across 1 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean as a CI step. What was searched, so you can tell an absence from a miss: the 22606 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a15f51-2fba-7977-a73b-51ce1e2ecc91 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 524 · Warnings: 935 · Recommendations: 56 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 16:35 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.