Public report of CortexaX/OpenPCL, published 15 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 15 November 2026, 02:46 UTC · Survey ID cd_39146126793843fe837c9cbd6f00f969
CortexaX/OpenPCL
Measured 15 November 2026, 02:45 UTC, at code version 5e947bf
Boundary Type-Coupling is not measured: Bounded contexts not declared.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 1 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 medium codebase: 44,295 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 32
Findings by how serious they are
68 critical492 serious15 minor
13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 02:45 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
40of 40 dimensions measured by tools.
563of 575 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
40dimensions across 6 lenses, read from 44,295 lines of product code in 2 projects.
CortexaX/OpenPCL falls short of our standard for production because the project has no automated tests and we found no automated security scanning of the code, its secrets or its dependencies. It scores 48 out of 100 and is rated Weak, and eight of its 68 critical findings are security problems in the build pipeline.
Production Readiness, at 32, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 8 points. Adding automated tests would lift Production Readiness itself, worth about 15 points. Raising Production Readiness to 70 would lift the score to about 61.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. The project has no automated tests, so a change can break it without warning, and fifty-eight errors are caught and ignored, so failures can go unnoticed. Adding automated tests, pinning each tool to an exact version and handling or logging the ignored errors would close these risks. The analysis rule switched off in the settings needs switching back on in the settings file.
The product code is 44,295 lines, about €49,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.
If Production Readiness rose from 32 to 70, the lowest score rated Strong, the score would rise from 48 to about 61.
Code composition: what the lines of code are
Business logic 22%Supporting code 27%Generated by tools 51%
New since the last survey: 29 findings
These 29 critical or serious findings weren't in the previous survey, on 29 October 2026.
Code Duplication · Edited copy of a member (69 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb
Code Duplication · Edited copy of a member (36 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb
Code Duplication · Edited copy of a member (74 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb
Code Duplication · Edited copy of a member (34 corresponding lines) Plain Craft Launcher 2/Controls/MyPageRight.vb
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb
Code Duplication · Edited copy of a member (34 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModValidate.vb
Code Duplication · Edited copy of a member (17 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb
Code Duplication · Edited copy of a member (21 corresponding lines) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb
Code Duplication · Edited copy of a member (12 corresponding lines) Plain Craft Launcher 2/Pages/PageSetup/Settings.vb
Code Duplication · Edited copy of a member (30 corresponding lines) Plain Craft Launcher 2/Controls/MyPageRight.vb
Code Duplication · Edited copies of one member (5 members, 17+ corresponding lines) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb
Code Duplication · Edited copy of a member (14 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb
Code Duplication · Edited copy of a member (12 corresponding lines) Plain Craft Launcher 2/Pages/PageOther/PageOtherLeft.xaml.vb
Code Duplication · Edited copy of a member (19 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb
Code Duplication · Edited copy of a member (9 corresponding lines) Plain Craft Launcher 2/Controls/MyCard.vb
Code Duplication · Edited copy of a member (13 corresponding lines) Plain Craft Launcher 2/Modules/ModMain.vb
Code Duplication · Edited copy of a member (16 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModLoader.vb
Code Duplication · Edited copy of a member (24 corresponding lines) Plain Craft Launcher 2/Controls/MyMenuItem.vb
Code Duplication · Edited copy of a member (8 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModBase.vb
Code Duplication · Edited copy of a member (11 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb
Code Duplication · Edited copy of a member (13 corresponding lines) Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb
Code Duplication · Edited copy of a member (8 corresponding lines) Plain Craft Launcher 2/Pages/PageSetup/PageSetupSystem.xaml.vb
Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Plain Craft Launcher 2/Modules/ModTaowa.vb
Code Duplication · Edited copy of a member (6 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb
Code Duplication · Edited copy of a member (2 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb
Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) Plain Craft Launcher 2/Controls/MyCheckBox.xaml.vb
Code Duplication · Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb
Code Duplication · Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceModDisabled.xaml.vb
Code Duplication · Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb
We compare 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: 5 findings
These 5 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one.
€16,000 to €82,000, for 271 to 860 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 48. 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
Medium: 44,295 lines of product code
Comment lines
The estimate prices 44,059 lines. Comment lines count towards the size of 44,295 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Plain Craft Launcher 2.vbproj.
Raises the score by about 8 points · Low effort · ADR Quality
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 15 points · High effort · Code Coverage
3
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.
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 €49,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 32 (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 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 5.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 16% on every change. The history of the code shows how much it changes: about 50,594 lines over the last 90 days, which is about 205,187 lines a year. At that pace, the extra work comes to an estimated 37 to 221.9 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 our 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, never less than 2% to 5% and never more than 40% to 60% in all; 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, which only happens where the projects form a dependency cycle. A graph without cycles 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.
36 modules, with 17 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
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.
terracotta.controller.api uses terracotta.controller.rooms, so a change to terracotta.controller.rooms can break terracotta.controller.api, while a change to terracotta.controller.api can't break terracotta.controller.rooms.
Position
Below the diagonal: terracotta.controller.api uses a module listed above it, which is the healthy direction.
terracotta.controller.rooms.scaffolding.room uses terracotta.controller.rooms, so a change to terracotta.controller.rooms can break terracotta.controller.rooms.scaffolding.room, while a change to terracotta.controller.rooms.scaffolding.room can't break terracotta.controller.rooms.
Position
Below the diagonal: terracotta.controller.rooms.scaffolding.room uses a module listed above it, which is the healthy direction.
terracotta.controller.rooms.scaffolding.room uses terracotta.controller.states, so a change to terracotta.controller.states can break terracotta.controller.rooms.scaffolding.room, while a change to terracotta.controller.rooms.scaffolding.room can't break terracotta.controller.states.
Position
Below the diagonal: terracotta.controller.rooms.scaffolding.room uses a module listed above it, which is the healthy direction.
terracotta.controller.rooms.scaffolding.room uses terracotta.easytier.argument, so a change to terracotta.easytier.argument can break terracotta.controller.rooms.scaffolding.room, while a change to terracotta.controller.rooms.scaffolding.room can't break terracotta.easytier.argument.
Position
Below the diagonal: terracotta.controller.rooms.scaffolding.room uses a module listed above it, which is the healthy direction.
terracotta.easytier.executable_impl uses terracotta.easytier.argument, so a change to terracotta.easytier.argument can break terracotta.easytier.executable_impl, while a change to terracotta.easytier.executable_impl can't break terracotta.easytier.argument.
Position
Below the diagonal: terracotta.easytier.executable_impl uses a module listed above it, which is the healthy direction.
30→34 terracotta.easytier.executable_impl uses terracotta.easytierpart of a loop✕
Connections
1 pair of types, where a type in terracotta.easytier.executable_impl uses a type in terracotta.easytier.
terracotta.easytier.executable_impl uses terracotta.easytier, so a change to terracotta.easytier can break terracotta.easytier.executable_impl, while a change to terracotta.easytier.executable_impl can't break terracotta.easytier.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
terracotta.easytier.publics uses terracotta.controller.rooms, so a change to terracotta.controller.rooms can break terracotta.easytier.publics, while a change to terracotta.easytier.publics can't break terracotta.controller.rooms.
Position
Below the diagonal: terracotta.easytier.publics uses a module listed above it, which is the healthy direction.
terracotta.lock_windows uses terracotta.lock_unix, so a change to terracotta.lock_unix can break terracotta.lock_windows, while a change to terracotta.lock_windows can't break terracotta.lock_unix.
Position
Below the diagonal: terracotta.lock_windows uses a module listed above it, which is the healthy direction.
terracotta.scaffolding.client uses terracotta.scaffolding, so a change to terracotta.scaffolding can break terracotta.scaffolding.client, while a change to terracotta.scaffolding.client can't break terracotta.scaffolding.
Position
Below the diagonal: terracotta.scaffolding.client uses a module listed above it, which is the healthy direction.
terracotta.easytier uses terracotta.controller.rooms, so a change to terracotta.controller.rooms can break terracotta.easytier, while a change to terracotta.easytier can't break terracotta.controller.rooms.
Position
Below the diagonal: terracotta.easytier uses a module listed above it, which is the healthy direction.
terracotta.easytier uses terracotta.easytier.argument, so a change to terracotta.easytier.argument can break terracotta.easytier, while a change to terracotta.easytier can't break terracotta.easytier.argument.
Position
Below the diagonal: terracotta.easytier uses a module listed above it, which is the healthy direction.
terracotta.easytier uses terracotta.easytier.executable_impl, so a change to terracotta.easytier.executable_impl can break terracotta.easytier, while a change to terracotta.easytier can't break terracotta.easytier.executable_impl.
Position
Below the diagonal: terracotta.easytier uses a module listed above it, which is the healthy direction.
terracotta.easytier.linkage_impl uses terracotta.easytier.argument, so a change to terracotta.easytier.argument can break terracotta.easytier.linkage_impl, while a change to terracotta.easytier.linkage_impl can't break terracotta.easytier.argument.
Position
Below the diagonal: terracotta.easytier.linkage_impl uses a module listed above it, which is the healthy direction.
terracotta.easytier.linkage_impl uses terracotta.easytier.executable_impl, so a change to terracotta.easytier.executable_impl can break terracotta.easytier.linkage_impl, while a change to terracotta.easytier.linkage_impl can't break terracotta.easytier.executable_impl.
Position
Below the diagonal: terracotta.easytier.linkage_impl uses a module listed above it, which is the healthy direction.
terracotta.easytier.linkage_impl uses terracotta.easytier, so a change to terracotta.easytier can break terracotta.easytier.linkage_impl, while a change to terracotta.easytier.linkage_impl can't break terracotta.easytier.
Position
Below the diagonal: terracotta.easytier.linkage_impl uses a module listed above it, which is the healthy direction.
terracotta uses terracotta.easytier.linkage_impl, so a change to terracotta.easytier.linkage_impl can break terracotta, while a change to terracotta can't break terracotta.easytier.linkage_impl.
Position
Below the diagonal: terracotta uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 70% · Adequate · gated by D1, D2 ·
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
8
High / Critical
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Plain Craft Launcher 2.vbproj; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Plain Craft Launcher 2.vbproj.
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 — 68
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 — 492
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 — 15
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 40 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, 563 of 575 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "MeloongCore/Shared/MeloongCore.csproj" was not found. [Plain Craft Launcher 2.sln].
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Project file not found: 'MeloongCore/Shared/MeloongCore.csproj'.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (44,295 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `PCLCS/Java.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (ThirdParty/Terracotta). the service did not build — `cargo build --bin 'terracotta'` exited 101: Party/Terracotta/timestamp)
Compiling chrono v0.4.45
Compiling num-bigint v0.4.8
Compiling local-ip-address v0.6.13
Compiling rand_chacha v0.9.0
Compiling open v5.4.5
Compiling hex v…; runtime evidence skipped (launch chosen because 'rocket' dependency in ThirdParty/Terracotta/Cargo.toml, binary 'terracotta').
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
126 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ResourceProject.New.ctor at 156. A further 4 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 PageLaunchRight.RefreshReal at 25 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchRight.xaml.vb (PageLaunchRight.RefreshReal at 25), Plain Craft Launcher 2/Controls/MyCard.vb (MyCard.StackInstall at 22), Plain Craft Launcher 2/Modules/ModTaowaEasyTier.vb (Pcl2TaowaEasyTier.BuildCommandArguments at 19). 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.
+ 121 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 ResourceProject.New.ctor (cyclomatic 156). — Refactoring it lifts Cyclomatic Complexity from 2.0 to about 2.6/10.
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.
+ 180 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 24 bodies over 60 down to 60 or less in Cognitive Complexity — start with CrashAnalyzer.AnalyzeCrit1 (cognitive 148), ResourceSearcher.Run (cognitive 127), CrashAnalyzer.Prepare (cognitive 117). — 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 24 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes6.9 / 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 29 MethodTooLong finding(s) in God Classes — start with ModDownloadLib.vb (5), ModLaunch.vb (3), ResourceProject.vb (2). — One of this dimension's main actionable groups (29 warning-level).
Resolve the 18 FileTooLong finding(s) in God Classes — start with ModMinecraft.vb, ModLaunch.vb, ModDownloadLib.vb. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 13 ClassTooLong finding(s) in God Classes — start with ModMinecraft.vb (2), ModSecret.vb, ModEvent.vb. — One of this dimension's main actionable groups (13 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
23 duplicated block group(s) detected. 3.5 % of the production lines (1,553 of 44,295) are in a reported copy. A further 31 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (34 corresponding lines) · ×2Plain Craft Launcher 2/Controls/MyPageRight.vb:67
Edited copy of a member (12 corresponding lines) · ×2Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:432
+ 36 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with ModModpack.vb (2), ModTaowa.vb, ModTaowaCore.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with PageLoginAuth.xaml.vb, PageInstanceModDisabled.xaml.vb, MyLocalModItem.xaml.vb. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ModLaunch.vb, Settings.vb, PageInstanceSetup.xaml.vb. — One of this dimension's main actionable groups (3 warning-level).
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 16 Low cohesion finding(s) in Cohesion (LCOM4) — start with PageSetupLaunch.xaml.vb, PageInstanceSetup.xaml.vb, PageSelectLeft.xaml.vb. — One of this dimension's main actionable groups (16 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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 1 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (1 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is.
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 31 Hotspot finding(s) in Churn × Complexity Hotspots — start with FormMain.xaml.vb, Application.xaml.vb, ModLaunch.vb. — One of this dimension's main actionable groups (31 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.5 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Plain Craft Launcher 2/Modules/Base/ModAnimation.vb. Counted over 95 of the 117 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
67 deducted debt markers + unmeasured dead symbols across 44295 LoC in the .NET projects (1.3/KLoC) → score 7.4. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 46 EmptyCatchBlock finding(s) in Explicit Debt — start with ModTaowaCore.vb (15), ModTaowaEasyTier.vb (6), ModDownloadLib.vb (4). — One of this dimension's main actionable groups (46 issue-level).
Resolve the 12 OnErrorResumeSwallow finding(s) in Explicit Debt — start with FormMain.xaml.vb (2), ModNet.vb (2), ModMain.vb (2). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 1 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
2 projects, 117 source files, 44295 hand-written lines of code (44295 production / 0 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 284 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 1 inter-project edges (build status unknown — did not finish).
Solution references 2 projects that do not existPlain Craft Launcher 2.sln
What to do
Resolve the 1 Solution references 2 projects that do not exist finding(s) in Solution Shape — start with Plain Craft Launcher 2.sln. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
✓ 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: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
No ADRs foundPlain Craft Launcher 2/Plain Craft Launcher 2.vbproj:8
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Plain Craft Launcher 2.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionPlain Craft Launcher 2/Plain Craft Launcher 2.vbproj:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Plain Craft Launcher 2.vbproj. — 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.
54 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 8 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 7 file(s) — `.github/ISSUE_TEMPLATE/bug1.yml`, `.github/ISSUE_TEMPLATE/bug2.yml`, `.github/ISSUE_TEMPLATE/bug9.yml`, `.github/ISSUE_TEMPLATE/ch.yml`, `.github/ISSUE_TEMPLATE/feature.yml`, … (+2 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 1 of those file(s) — `PCLCS/Java.cs` — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. 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
What to do
No action in Static Analysis (SAST) — all 8 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 (8 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 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.
1 of 95 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb. Counted over 95 of the 117 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 any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
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.
~44.3k production LoC (447 types) across 2 project(s) / 41 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 read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
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 repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:6
`PCLCS/PCLCS.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — PCLCS/PCLCS.csproj:18
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
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.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 2730 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
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 — 1 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX6 Interface segregation — AX6 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the service did not build — `cargo build --bin 'terracotta'` exited 101: Party/Terracotta/timestamp)
Compiling chrono v0.4.45
Compiling num-bigint v0.4.8
Compiling local-ip-address v0.6.13
Compiling rand_chacha v0.9.0
Compiling open v5.4.5
Compiling hex v…; runtime evidence skipped (launch chosen because 'rocket' dependency in ThirdParty/Terracotta/Cargo.toml, binary 'terracotta') This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D21 Naming Consistency — Naming consistency does not read Visual Basic, html yet; not measured.
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 — 3418 of 3418 comment blocks were not judged (3186 in a non-Latin script, 232 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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
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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
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 — IC1 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
X1 Async correctness — X1 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — X12 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — X2 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — X23 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 1% of this repository's production lines — vbnet (43,788 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 Plain Craft Launcher 2/Application.xaml.vb:143— 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 Plain Craft Launcher 2/Controls/MyImage.vb:94— 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 Plain Craft Launcher 2/Controls/MyImage.vb:137— 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 Plain Craft Launcher 2/Controls/MyResizer.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 Plain Craft Launcher 2/Controls/MyResizer.vb:299— 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 Plain Craft Launcher 2/Modules/Base/ModNet.vb:123— 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 Plain Craft Launcher 2/Modules/Base/ModNet.vb:131— 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 Plain Craft Launcher 2/Modules/Base/ModNet.vb:1572— 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 Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:100— 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 Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:829— 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 Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2233— 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 Plain Craft Launcher 2/Modules/ModMain.vb:951— 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 Plain Craft Launcher 2/Modules/ModMusic.vb:200— 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 Plain Craft Launcher 2/Modules/ModSecret.vb:497— 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 Plain Craft Launcher 2/Modules/ModTaowa.vb:43— 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 Plain Craft Launcher 2/Modules/ModTaowa.vb:55— 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 Plain Craft Launcher 2/Modules/ModTaowa.vb:95— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:254— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:261— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:268— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:506— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:516— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:531— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:730— 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 Plain Craft Launcher 2/Modules/ModTaowaCore.vb:737— 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.
OnErrorResumeSwallow Plain Craft Launcher 2/Application.xaml.vb:188— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:93— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Controls/MyMsg/MyMsgSelect.xaml.vb:100— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Controls/MyMsg/MyMsgText.xaml.vb:104— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/FormMain.xaml.vb:578— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/FormMain.xaml.vb:603— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Modules/Base/ModNet.vb:1356— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Modules/Base/ModNet.vb:1428— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Modules/Base/ModValidate.vb:271— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Modules/ModMain.vb:966— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Modules/ModMain.vb:977— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
OnErrorResumeSwallow Plain Craft Launcher 2/Pages/PageLaunch/MyMsgLogin.xaml.vb:67— On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
AnalyzerSeverityNone .editorconfig:14— IDE0305 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Hotspot: Plain Craft Launcher 2/FormMain.xaml.vb Plain Craft Launcher 2/FormMain.xaml.vb:9— Plain Craft Launcher 2/FormMain.xaml.vb changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in FormMain.ShowUpdateLog at line 9. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/FormMain.xaml.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: Plain Craft Launcher 2/Application.xaml.vb Plain Craft Launcher 2/Application.xaml.vb:8— Plain Craft Launcher 2/Application.xaml.vb changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Application.Application_Startup at line 8. 5 of those changes were fix/bug commits, and the other 8 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Application.xaml.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: Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1716— Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in ModLaunch.McLaunchPrerun at line 1716. 1 of those changes was a fix/bug commit, and the other 4 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.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: Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:436— Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in PageSetupUI.HiddenRefresh at line 436. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.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: Plain Craft Launcher 2/Modules/ModSecret.vb Plain Craft Launcher 2/Modules/ModSecret.vb:76— Plain Craft Launcher 2/Modules/ModSecret.vb changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ModSecret.ThemeRefresh at line 76. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/ModSecret.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: Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb:164— Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 83 in ResourceSearcher.Run at line 164. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.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: Plain Craft Launcher 2/Modules/ModMain.vb Plain Craft Launcher 2/Modules/ModMain.vb:670— Plain Craft Launcher 2/Modules/ModMain.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ModMain.TimerFool at line 670. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/ModMain.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: Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1429— Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in ModMinecraft.InitMcInstanceListWithoutCache at line 1429. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.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: Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:494— Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in PageLinkMain.InitLaunch at line 494. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.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: Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1850— Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in ModDownloadLib.McInstallLoader at line 1850. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.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: Plain Craft Launcher 2/Modules/Base/ModAnimation.vb Plain Craft Launcher 2/Modules/Base/ModAnimation.vb:932— Plain Craft Launcher 2/Modules/Base/ModAnimation.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in ModAnimation.AniRun at line 932. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Base/ModAnimation.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: Plain Craft Launcher 2/Modules/ModEvent.vb Plain Craft Launcher 2/Modules/ModEvent.vb:176— Plain Craft Launcher 2/Modules/ModEvent.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in CustomEvent.Raise at line 176. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/ModEvent.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: Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:158— Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in PageDownloadResourceDetail.UpdateFilterResult at line 158. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.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: Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:407— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in PageInstanceExport.StartExport at line 407. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.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: Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb:115— Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in ResourceVersion.FromPlatformJson at line 115. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Resource/ResourceVersion.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: Plain Craft Launcher 2/Modules/Base/ModLoader.vb Plain Craft Launcher 2/Modules/Base/ModLoader.vb:584— Plain Craft Launcher 2/Modules/Base/ModLoader.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in LoaderCombo.Update at line 584. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Base/ModLoader.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: Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:157— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in PageInstanceMod.RefreshBars at line 157. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.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: Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb:69— Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in PageSpeedLeft.TaskRefresh at line 69. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.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: Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.vb Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.vb:181— Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in Watcher.GameLog at line 181. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.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: Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:443— Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in PageDownloadInstall.LoadMinecraft_OnFinish at line 443. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.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: Plain Craft Launcher 2/Controls/MyIconButton.xaml.vb Plain Craft Launcher 2/Controls/MyIconButton.xaml.vb:95— Plain Craft Launcher 2/Controls/MyIconButton.xaml.vb changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in MyIconButton.RefreshAnim at line 95. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Controls/MyIconButton.xaml.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: Plain Craft Launcher 2/Modules/ModTaowa.vb Plain Craft Launcher 2/Modules/ModTaowa.vb:254— Plain Craft Launcher 2/Modules/ModTaowa.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Pcl2Taowa.JoinWorker at line 254. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/ModTaowa.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: Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:455— Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in ResourceProject.ToResourceItem at line 455. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Resource/ResourceProject.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: Plain Craft Launcher 2/Modules/Base/ModValidate.vb Plain Craft Launcher 2/Modules/Base/ModValidate.vb:380— Plain Craft Launcher 2/Modules/Base/ModValidate.vb changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in ValidateFolderPath.Validate at line 380. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Base/ModValidate.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: Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:5— Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in LocalResourceLoaders.LocalResourceFileLoad at line 5. 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-04-27..2026-07-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-04-27 13:51:19 +08:00' --until='2026-07-26 13:51:19 +08:00' --full-history --no-merges -- Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.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.
MethodTooLong: ResourceSearcher.Run Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb:164— MethodTooLong — Run runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× 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: PageInstanceExport.StartExport Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:407— MethodTooLong — StartExport runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× 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: ResourceProject.New(…) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:123— MethodTooLong — New(…) runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× 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: ModDownloadLib.McDownloadForgelikeLoader Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1074— MethodTooLong — McDownloadForgelikeLoader runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.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: FormMain.ShowUpdateLog Plain Craft Launcher 2/FormMain.xaml.vb:9— MethodTooLong — ShowUpdateLog runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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: ModLaunch.McLaunchPrerun Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1716— MethodTooLong — McLaunchPrerun runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.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: LocalResourceLoaders.LocalResourceOnlineLoad Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:106— MethodTooLong — LocalResourceOnlineLoad runs 200 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× 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: ModSecret.ServerSub Plain Craft Launcher 2/Modules/ModSecret.vb:588— MethodTooLong — ServerSub runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.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: PageDownloadInstall.ReloadSelected Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:180— MethodTooLong — ReloadSelected runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× 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: ModJava.SelectOrDownloadJava Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:272— MethodTooLong — SelectOrDownloadJava runs 141 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 41 over it, 1.41× 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: PageDownloadResourceDetail.Save_Click Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:340— MethodTooLong — Save_Click runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: ModMinecraft.InitMcInstanceListWithoutCache Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1429— MethodTooLong — InitMcInstanceListWithoutCache runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: CustomEvent.Raise Plain Craft Launcher 2/Modules/ModEvent.vb:176— MethodTooLong — Raise runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: ModSecret.ThemeRefresh Plain Craft Launcher 2/Modules/ModSecret.vb:76— MethodTooLong — ThemeRefresh 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.
MethodTooLong: ModDownloadLib.MergeJson Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1990— MethodTooLong — MergeJson runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.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: Application.Application_Startup Plain Craft Launcher 2/Application.xaml.vb:8— MethodTooLong — Application_Startup runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: ModLaunch.McLaunchArgumentsJVM Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1210— MethodTooLong — McLaunchArgumentsJVM runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: ModDownloadLib.McDownloadOptiFineLoader Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:467— MethodTooLong — McDownloadOptiFineLoader runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: PageSpeedLeft.TaskRefresh Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb:69— MethodTooLong — TaskRefresh runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× 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: ModAnimation.AniRun Plain Craft Launcher 2/Modules/Base/ModAnimation.vb:932— MethodTooLong — AniRun runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: PageInstanceMod.UpdateMods Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:535— MethodTooLong — UpdateMods runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: ModLaunch.McLoginRequestLogin Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:750— MethodTooLong — McLoginRequestLogin runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.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: ModDownloadLib.McDownloadOptiFineInstall Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:344— MethodTooLong — McDownloadOptiFineInstall runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.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: FormMain.UpdateBackgroundAndTitleBar Plain Craft Launcher 2/FormMain.xaml.vb:635— MethodTooLong — UpdateBackgroundAndTitleBar runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: ModDownloadLib.McInstallLoader Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1850— MethodTooLong — McInstallLoader runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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.
FileTooLong: Minecraft/ModMinecraft.vb Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb— FileTooLong — 1821 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1321 over it, 3.64× 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: Minecraft/ModLaunch.vb Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb— FileTooLong — 1735 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1235 over it, 3.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: PageDownload/ModDownloadLib.vb Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb— FileTooLong — 1720 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1220 over it, 3.44× 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: Plain Craft Launcher 2/FormMain.xaml.vb Plain Craft Launcher 2/FormMain.xaml.vb— FileTooLong — 1360 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 860 over it, 2.72× 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: Modules/ModTaowaCore.vb Plain Craft Launcher 2/Modules/ModTaowaCore.vb— FileTooLong — 1065 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 565 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: Minecraft/ModDownload.vb Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb— FileTooLong — 937 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 437 over it, 1.87× 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: PageDownload/PageDownloadInstall.xaml.vb Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb— FileTooLong — 915 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 415 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: Modules/ModSecret.vb Plain Craft Launcher 2/Modules/ModSecret.vb— FileTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 348 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: PageLink/PageLinkMain.xaml.vb Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb— FileTooLong — 805 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 305 over it, 1.61× 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: Modules/ModMain.vb Plain Craft Launcher 2/Modules/ModMain.vb— FileTooLong — 774 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 274 over it, 1.55× 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: PageInstance/PageInstanceMod.xaml.vb Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 159 over it, 1.32× 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: PageInstance/PageInstanceExport.xaml.vb Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb— FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 98 over it, 1.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: Base/ModLoader.vb Plain Craft Launcher 2/Modules/Base/ModLoader.vb— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 96 over it, 1.19× 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: Base/ModAnimation.vb Plain Craft Launcher 2/Modules/Base/ModAnimation.vb— FileTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 50 over it, 1.10× 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: Resource/ResourceProject.vb Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 over it, 1.07× 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: PageSetup/PageSetupUI.xaml.vb Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb— FileTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 35 over it, 1.07× 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: Controls/MyListItem.xaml.vb Plain Craft Launcher 2/Controls/MyListItem.xaml.vb— FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× 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: Modules/ModTaowaEasyTier.vb Plain Craft Launcher 2/Modules/ModTaowaEasyTier.vb— FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9 over it, 1.02× 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.
Low cohesion: PageSetupLaunch (LCOM4 10) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:1— PageSetupLaunch's methods fall into 10 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 10 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: PageInstanceSetup (LCOM4 9) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:1— PageInstanceSetup'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: PageSelectLeft (LCOM4 9) Plain Craft Launcher 2/Pages/PageSelectLeft.xaml.vb:1— PageSelectLeft'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: FormMain (LCOM4 9) Plain Craft Launcher 2/FormMain.xaml.vb:4— FormMain'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: PageInstanceMod (LCOM4 8) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:1— PageInstanceMod's methods fall into 8 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 8 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: PageOtherTest (LCOM4 8) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:4— PageOtherTest's methods fall into 8 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 8 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: MyComboBox (LCOM4 7) Plain Craft Launcher 2/Controls/MyComboBox.vb:1— MyComboBox's methods fall into 7 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 7 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: PageLoginAuth (LCOM4 7) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:1— PageLoginAuth's methods fall into 7 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 7 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: PageInstanceOverall (LCOM4 6) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceOverall.xaml.vb:1— PageInstanceOverall's methods fall into 6 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 6 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: PageLoginNide (LCOM4 6) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginNide.xaml.vb:1— PageLoginNide's methods fall into 6 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 6 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: PageLaunchLeft (LCOM4 6) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:3— PageLaunchLeft's methods fall into 6 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 6 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: PageLoginMsSkin (LCOM4 4) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginMsSkin.xaml.vb:1— PageLoginMsSkin'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: PageInstanceExport (LCOM4 4) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:16— PageInstanceExport'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: PageInstanceLeft (LCOM4 4) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceLeft.xaml.vb:1— PageInstanceLeft'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: PageLoginLegacy (LCOM4 4) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginLegacy.xaml.vb:3— PageLoginLegacy'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: PageOtherLeft (LCOM4 4) Plain Craft Launcher 2/Pages/PageOther/PageOtherLeft.xaml.vb:1— PageOtherLeft'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.
ClassTooLong: ModMinecraft Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb— ClassTooLong — 1821 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 1421 over it, 4.55× 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: ModSecret Plain Craft Launcher 2/Modules/ModSecret.vb— ClassTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 448 over it, 2.12× 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: ModMain Plain Craft Launcher 2/Modules/ModEvent.vb— ClassTooLong — 786 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 386 over it, 1.97× 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: ModLoader Plain Craft Launcher 2/Modules/Base/ModLoader.vb— ClassTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 196 over it, 1.49× 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: PageInstanceExport Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb— ClassTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 188 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.
ClassTooLong: ModMinecraft.McInstance Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb— ClassTooLong — 577 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 177 over it, 1.44× 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: ResourceProject Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb— ClassTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 137 over it, 1.34× 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: MyListItem Plain Craft Launcher 2/Controls/MyListItem.xaml.vb— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 127 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: PageDownloadResourceDetail Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb— ClassTooLong — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 40 over it, 1.10× 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: MyLocalModItem Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 39 over it, 1.10× 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: PageInstanceSetup Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb— ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 38 over it, 1.10× 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: ModJava Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb— ClassTooLong — 433 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 33 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: PageSetupLaunch Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 4 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.
TooManyMethods: PageDownloadInstall Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb— TooManyMethods — 915 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: ModDownloadLib Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb— TooManyMethods — 1720 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× 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: FormMain Plain Craft Launcher 2/FormMain.xaml.vb— TooManyMethods — 1358 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: ModLaunch Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb— TooManyMethods — 1735 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: Pcl2TaowaCore Plain Craft Launcher 2/Modules/ModTaowaCore.vb— TooManyMethods — 443 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: PageLinkMain Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb— TooManyMethods — 800 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× 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: PageInstanceMod Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb— TooManyMethods — 659 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: ModDownload Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb— TooManyMethods — 937 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 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.
TooManyMethods: PageSetupUI Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb— TooManyMethods — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 30 methods; this is 5 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.
TooManyMethods: ModAnimation Plain Craft Launcher 2/Controls/MyCard.vb— TooManyMethods — 616 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.
TodoComment Plain Craft Launcher 2/FormMain.xaml.vb:709— 'TODO: 和 FrmSetupUI 解耦 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:507— 'TODO: 写一个更简单的 Lazy,允许重置缓存 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:95— 'TODO: 添加信息获取中提示 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1798— 'TODO: 自动选择安装成功的版本 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:327— 'TODO: 这会不会导致拖拽改变第三方登录的时候版本列表缓存没有更新? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:442— 'TODO: 可能不会显示错误原因? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `' REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (6 lines × 2) Plain Craft Launcher 2/Modules/ModTaowa.vb:194— Plain Craft Launcher 2/Modules/ModTaowa.vb:194-199 | Plain Craft Launcher 2/Modules/ModTaowa.vb:300-305 — 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) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:529— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:529-534 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:583-588 — 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) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:420— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:420-425 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:534-539 — 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 `Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:420` 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) Plain Craft Launcher 2/Modules/ModTaowaCore.vb:527— Plain Craft Launcher 2/Modules/ModTaowaCore.vb:527-532 | Plain Craft Launcher 2/Modules/ModTaowaCore.vb:1238-1243 — 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) Plain Craft Launcher 2/Modules/ModSecret.vb:725— Plain Craft Launcher 2/Modules/ModSecret.vb:725-730 | Plain Craft Launcher 2/Modules/ModSecret.vb:732-737 — 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 `Plain Craft Launcher 2/Modules/ModSecret.vb:732` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Plain Craft Launcher 2/Modules/ModSecret.vb:737` calls `If`, `Buttons` and `Plain Craft Launcher 2/Modules/ModSecret.vb:730` 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.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:58— Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:58-62 | Plain Craft Launcher 2/Pages/PageLaunch/PageLoginNide.xaml.vb:58-62 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceModDisabled.xaml.vb:12— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceModDisabled.xaml.vb:12-16 | Plain Craft Launcher 2/Pages/PageSelectRight.xaml.vb:228-232 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:80— Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:80-84 | Plain Craft Launcher 2/Pages/PageDownload/Resource/MyResourceItem.xaml.vb:69-73 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (5 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:239— Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:239-243 | Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:256-260 — 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 `Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:239` 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 (5 lines × 2) Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:432— Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:432-436 | Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:450-454 — 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) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:563— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:563-567 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:499-503 — before extracting anything, compare `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb` and `Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 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.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×2
Edited copy of a member (34 corresponding lines) Plain Craft Launcher 2/Controls/MyPageRight.vb:67— Plain Craft Launcher 2/Controls/MyPageRight.vb:67-100 | Plain Craft Launcher 2/Controls/MyPageRight.vb:116-151 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (34 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModValidate.vb:275— Plain Craft Launcher 2/Modules/Base/ModValidate.vb:275-308 | Plain Craft Launcher 2/Modules/Base/ModValidate.vb:330-365 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:432— Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:432-443 | Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:450-461 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Plain Craft Launcher 2/Pages/PageOther/PageOtherLeft.xaml.vb:7— Plain Craft Launcher 2/Pages/PageOther/PageOtherLeft.xaml.vb:7-18 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLeft.xaml.vb:7-19 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) Plain Craft Launcher 2/Modules/ModMain.vb:288— Plain Craft Launcher 2/Modules/ModMain.vb:288-300 | Plain Craft Launcher 2/Modules/ModMain.vb:311-323 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:83— Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:83-96 | Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:99-111 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModBase.vb:487— Plain Craft Launcher 2/Modules/Base/ModBase.vb:487-494 | Plain Craft Launcher 2/Modules/Base/ModBase.vb:506-513 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Plain Craft Launcher 2/Pages/PageSetup/PageSetupSystem.xaml.vb:83— Plain Craft Launcher 2/Pages/PageSetup/PageSetupSystem.xaml.vb:83-90 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupSystem.xaml.vb:93-100 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:115— Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:115-124 | Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:132-141 — 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) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadLeft.xaml.vb:50— Plain Craft Launcher 2/Pages/PageDownload/PageDownloadLeft.xaml.vb:50-59 | Plain Craft Launcher 2/Pages/PageInstance/PageInstanceLeft.xaml.vb:62-71 — 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.
Appears unstructured (no recognised architecture) — ~44.3k production LoC (447 types) across 2 project(s) / 41 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.
ResourceProject.New.ctor (cyclomatic 156) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:123— ResourceProject.New.ctor has cyclomatic complexity 156 (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.
ResourceSearcher.Run (cyclomatic 83) Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb:164— ResourceSearcher.Run has cyclomatic complexity 83 (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.
CrashAnalyzer.AnalyzeCrit1 (cyclomatic 80) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:474— CrashAnalyzer.AnalyzeCrit1 has cyclomatic complexity 80 (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.
NetFile.Thread (cyclomatic 75) Plain Craft Launcher 2/Modules/Base/ModNet.vb:975— NetFile.Thread has cyclomatic complexity 75 (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.
CrashAnalyzer.GetAnalyzeResult (cyclomatic 74) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:928— CrashAnalyzer.GetAnalyzeResult 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.
ModLaunch.McLaunchPrerun (cyclomatic 73) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1716— ModLaunch.McLaunchPrerun has cyclomatic complexity 73 (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.
ModLaunch.McLaunchArgumentsJVM (cyclomatic 63) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1210— ModLaunch.McLaunchArgumentsJVM has cyclomatic complexity 63 (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.
ModSecret.ServerSub (cyclomatic 62) Plain Craft Launcher 2/Modules/ModSecret.vb:588— ModSecret.ServerSub has cyclomatic complexity 62 (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.
CrashAnalyzer.Prepare (cyclomatic 59) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:139— CrashAnalyzer.Prepare has cyclomatic complexity 59 (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.
PageSetupUI.HiddenRefresh (cyclomatic 58) Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:436— PageSetupUI.HiddenRefresh has cyclomatic complexity 58 (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.
ModJava.GetJavaRequirement (cyclomatic 57) Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:127— ModJava.GetJavaRequirement 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.
NetFile.TryBeginThread (cyclomatic 57) Plain Craft Launcher 2/Modules/Base/ModNet.vb:881— NetFile.TryBeginThread 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.
FormMain.ShowUpdateLog (cyclomatic 57) Plain Craft Launcher 2/FormMain.xaml.vb:9— FormMain.ShowUpdateLog 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.
ModDownloadLib.McInstallLoader (cyclomatic 54) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1850— ModDownloadLib.McInstallLoader 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.
ModJava.SelectOrDownloadJava (cyclomatic 52) Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:272— ModJava.SelectOrDownloadJava has cyclomatic complexity 52 (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.
CustomEvent.Raise (cyclomatic 49) Plain Craft Launcher 2/Modules/ModEvent.vb:176— CustomEvent.Raise has cyclomatic complexity 49 (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.
ModAnimation.AniRun (cyclomatic 49) Plain Craft Launcher 2/Modules/Base/ModAnimation.vb:932— ModAnimation.AniRun has cyclomatic complexity 49 (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.
ModDownloadLib.MergeJson (cyclomatic 46) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1990— ModDownloadLib.MergeJson 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.
ModMinecraft.InitMcInstanceListWithoutCache (cyclomatic 46) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1429— ModMinecraft.InitMcInstanceListWithoutCache 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.
PageDownloadInstall.ReloadSelected (cyclomatic 44) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:180— PageDownloadInstall.ReloadSelected 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.
PageDownloadResourceDetail.UpdateFilterResult (cyclomatic 43) Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:158— PageDownloadResourceDetail.UpdateFilterResult 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.
ResourceVersion.FromPlatformJson (cyclomatic 42) Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb:115— ResourceVersion.FromPlatformJson 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.
ModDownloadLib.McUpdateLogShow (cyclomatic 42) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:259— ModDownloadLib.McUpdateLogShow 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.
McInstance.Load (cyclomatic 39) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:734— McInstance.Load 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.
MyListItem.SetChecked (cyclomatic 37) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:358— MyListItem.SetChecked 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.
ModDownloadLib.McDownloadOptiFineInstall (cyclomatic 36) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:344— ModDownloadLib.McDownloadOptiFineInstall 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.
ResourceProject.ToResourceItem (cyclomatic 35) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:455— ResourceProject.ToResourceItem 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.
ResourceProject.GetControlTitle (cyclomatic 34) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:579— ResourceProject.GetControlTitle 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.
PageSelectRight.McInstanceListUI (cyclomatic 34) Plain Craft Launcher 2/Pages/PageSelectRight.xaml.vb:25— PageSelectRight.McInstanceListUI 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.
PageSpeedLeft.TaskRefresh (cyclomatic 33) Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb:69— PageSpeedLeft.TaskRefresh 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.
LocalResourceLoaders.LocalResourceFileLoad (cyclomatic 32) Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:5— LocalResourceLoaders.LocalResourceFileLoad 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.
PageInstanceExport.StartExport (cyclomatic 32) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:407— PageInstanceExport.StartExport 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.
NetFile.SourceFail (cyclomatic 32) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1146— NetFile.SourceFail 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.
ModLaunch.McLaunchArgumentsGame (cyclomatic 32) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1378— ModLaunch.McLaunchArgumentsGame 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.
ModModpack.ModpackInstall (cyclomatic 31) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:27— ModModpack.ModpackInstall 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.
CrashAnalyzer.AnalyzeModName (cyclomatic 31) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:737— CrashAnalyzer.AnalyzeModName 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.
ModSecret.ThemeRefresh (cyclomatic 31) Plain Craft Launcher 2/Modules/ModSecret.vb:76— ModSecret.ThemeRefresh 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.
PageDownloadInstall.LoadMinecraft_OnFinish (cyclomatic 31) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:443— PageDownloadInstall.LoadMinecraft_OnFinish 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.
ModMinecraft.CompareVersion (cyclomatic 31) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2426— ModMinecraft.CompareVersion 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.
Application.Application_Startup (cyclomatic 31) Plain Craft Launcher 2/Application.xaml.vb:8— Application.Application_Startup 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.
ModMain.TimerFool (cyclomatic 31) Plain Craft Launcher 2/Modules/ModMain.vb:670— ModMain.TimerFool 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.
McInstance.Version.Get (cyclomatic 30) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:314— McInstance.Version.Get 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.
PageLaunchLeft.LaunchingRefresh (cyclomatic 30) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:719— PageLaunchLeft.LaunchingRefresh 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.
MyResizer.updateSize (cyclomatic 30) Plain Craft Launcher 2/Controls/MyResizer.vb:206— MyResizer.updateSize 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.
LocalResourceLoaders.LocalResourceOnlineLoad (cyclomatic 29) Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:106— LocalResourceLoaders.LocalResourceOnlineLoad 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.
PageLinkMain.InitLaunch (cyclomatic 29) Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:494— PageLinkMain.InitLaunch 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.
FormMain.UpdateBackgroundAndTitleBar (cyclomatic 29) Plain Craft Launcher 2/FormMain.xaml.vb:635— FormMain.UpdateBackgroundAndTitleBar 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.
FormMain.PageChangeActual (cyclomatic 29) Plain Craft Launcher 2/FormMain.xaml.vb:1358— FormMain.PageChangeActual 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.
NetFile.Merge (cyclomatic 28) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1239— NetFile.Merge 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.
ModModpack.InstallPackCurseForge (cyclomatic 27) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:176— ModModpack.InstallPackCurseForge 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.
LoaderCombo.Update (cyclomatic 27) Plain Craft Launcher 2/Modules/Base/ModLoader.vb:584— LoaderCombo.Update 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.
McInstance.VersionDisplayName (cyclomatic 27) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:865— McInstance.VersionDisplayName 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.
MyIconButton.RefreshAnim (cyclomatic 27) Plain Craft Launcher 2/Controls/MyIconButton.xaml.vb:95— MyIconButton.RefreshAnim 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.
ModLaunch.McLoginRequestLogin (cyclomatic 26) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:750— ModLaunch.McLoginRequestLogin 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.
FormMain.UpgradeSub (cyclomatic 26) Plain Craft Launcher 2/FormMain.xaml.vb:436— FormMain.UpgradeSub 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.
PageInstanceMod.RefreshBars (cyclomatic 25) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:157— PageInstanceMod.RefreshBars 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.
ModMinecraft.McLibListGetWithJson (cyclomatic 25) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1944— ModMinecraft.McLibListGetWithJson 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.
MyListItem.RefreshColor (cyclomatic 25) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:546— MyListItem.RefreshColor 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.
ModModpack.InstallPackModrinth (cyclomatic 24) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:381— ModModpack.InstallPackModrinth 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.
Watcher.GameLog (cyclomatic 24) Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.vb:181— Watcher.GameLog 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.
PageLinkMain.GetTargetPeers (cyclomatic 24) Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:620— PageLinkMain.GetTargetPeers 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.
ModDownload.DlSourceLoader (cyclomatic 24) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1313— ModDownload.DlSourceLoader 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.
ModLaunch.McLaunchCustom (cyclomatic 24) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1989— ModLaunch.McLaunchCustom 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.
ModMinecraft.McFolderListLoadSub (cyclomatic 24) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:58— ModMinecraft.McFolderListLoadSub 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.
FormMain.FormMain_KeyDown (cyclomatic 23) Plain Craft Launcher 2/FormMain.xaml.vb:760— FormMain.FormMain_KeyDown 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.
ModMusic.MusicLoop (cyclomatic 22) Plain Craft Launcher 2/Modules/ModMusic.vb:277— ModMusic.MusicLoop 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.
ModLaunch.McLoginServerStart (cyclomatic 22) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:601— ModLaunch.McLoginServerStart 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.
MyRadioBox.SetChecked (cyclomatic 22) Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:37— MyRadioBox.SetChecked 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.
ModSecret.ServerRequirement (cyclomatic 21) Plain Craft Launcher 2/Modules/ModSecret.vb:783— ModSecret.ServerRequirement 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.
LoaderDownload.CheckExistingFile (cyclomatic 21) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1585— LoaderDownload.CheckExistingFile 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.
ModLaunch.McLaunchStart (cyclomatic 21) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:97— ModLaunch.McLaunchStart 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.
PageOtherTest.BtnClick_Click (cyclomatic 21) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:189— PageOtherTest.BtnClick_Click 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.
PclLogger.HandleBehavior (cyclomatic 20) Plain Craft Launcher 2/Modules/Base/PclLogger.vb:12— PclLogger.HandleBehavior 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.
ModDownloadLib.McDownloadForgelikeLoader (cyclomatic 20) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1074— ModDownloadLib.McDownloadForgelikeLoader 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.
ModMinecraft.InitMcInstanceList (cyclomatic 20) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1266— ModMinecraft.InitMcInstanceList 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.
PageSelectLeft.McFolderListUI (cyclomatic 20) Plain Craft Launcher 2/Pages/PageSelectLeft.xaml.vb:12— PageSelectLeft.McFolderListUI 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.
ModMain.HelpLoad (cyclomatic 20) Plain Craft Launcher 2/Modules/ModMain.vb:566— ModMain.HelpLoad 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.
MyIconTextButton.RefreshColor (cyclomatic 19) Plain Craft Launcher 2/Controls/MyIconTextButton.xaml.vb:92— MyIconTextButton.RefreshColor 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.
MyLocalModItem.Refresh (cyclomatic 19) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:328— MyLocalModItem.Refresh 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.
CrashAnalyzer.Output (cyclomatic 19) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:860— CrashAnalyzer.Output 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.
Pcl2Taowa.JoinWorker (cyclomatic 19) Plain Craft Launcher 2/Modules/ModTaowa.vb:254— Pcl2Taowa.JoinWorker 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.
ModDownloadLib.ForgelikeInjector (cyclomatic 19) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:934— ModDownloadLib.ForgelikeInjector 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.
ModNet.SendRequest (cyclomatic 19) Plain Craft Launcher 2/Modules/Base/ModNet.vb:216— ModNet.SendRequest 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.
ModLaunch.McLaunchPrecheck (cyclomatic 19) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:225— ModLaunch.McLaunchPrecheck 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.
McVersion.NameToVersion (cyclomatic 19) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1180— McVersion.NameToVersion 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.
ModMinecraft.McSkinGetAddress (cyclomatic 19) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1696— ModMinecraft.McSkinGetAddress 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.
PageLaunchLeft.RefreshButtonsUI (cyclomatic 19) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:634— PageLaunchLeft.RefreshButtonsUI 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.
CrashAnalyzer.Collect (cyclomatic 18) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:21— CrashAnalyzer.Collect 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.
PageInstanceMod.UpdateMods (cyclomatic 18) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:535— PageInstanceMod.UpdateMods 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.
ModMinecraft.InitMcInstanceListWithCache (cyclomatic 18) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1345— ModMinecraft.InitMcInstanceListWithCache 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.
ModMinecraft.McJsonRuleCheck (cyclomatic 18) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1845— ModMinecraft.McJsonRuleCheck 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.
PageOtherHelp.HelpListLoad (cyclomatic 18) Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:20— PageOtherHelp.HelpListLoad 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.
MyButton.RefreshColor (cyclomatic 18) Plain Craft Launcher 2/Controls/MyButton.xaml.vb:74— MyButton.RefreshColor 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.
MyRadioButton.SetChecked (cyclomatic 18) Plain Craft Launcher 2/Controls/MyRadioButton.xaml.vb:47— MyRadioButton.SetChecked 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.
MyPageRight.PageLoaderState (cyclomatic 17) Plain Craft Launcher 2/Controls/MyPageRight.vb:353— MyPageRight.PageLoaderState 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.
CrashAnalyzer.Analyze (cyclomatic 17) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:391— CrashAnalyzer.Analyze 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.
CrashAnalyzer.AnalyzeCrit2 (cyclomatic 17) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:588— CrashAnalyzer.AnalyzeCrit2 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.
ModSecret.UpdateReplace (cyclomatic 17) Plain Craft Launcher 2/Modules/ModSecret.vb:494— ModSecret.UpdateReplace 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.
PageDownloadInstall.IsFabricApiCompatible (cyclomatic 17) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:916— PageDownloadInstall.IsFabricApiCompatible 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.
PageDownloadResourceDetail.Save_Click (cyclomatic 17) Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:340— PageDownloadResourceDetail.Save_Click 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.
PageInstanceMod.InstallMods (cyclomatic 17) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:286— PageInstanceMod.InstallMods 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.
PageInstanceMod.EDMods (cyclomatic 17) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:455— PageInstanceMod.EDMods 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.
PageInstanceSetup.RefreshRamText (cyclomatic 17) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:159— PageInstanceSetup.RefreshRamText 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.
PageInstanceSetup.GetRam (cyclomatic 17) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:240— PageInstanceSetup.GetRam 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.
ValidateFolderPath.Validate (cyclomatic 17) Plain Craft Launcher 2/Modules/Base/ModValidate.vb:380— ValidateFolderPath.Validate 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.
ModLaunch.McLoginLegacyUuidWithCustomSkin (cyclomatic 17) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1091— ModLaunch.McLoginLegacyUuidWithCustomSkin 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.
ModLaunch.McLaunchArgumentsReplace (cyclomatic 17) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1479— ModLaunch.McLaunchArgumentsReplace 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.
ModMinecraft.McLibNetFilesFromTokens (cyclomatic 17) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2136— ModMinecraft.McLibNetFilesFromTokens 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.
PageLaunchLeft.SkinLegacyLoad (cyclomatic 17) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:449— PageLaunchLeft.SkinLegacyLoad 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.
PageSetupLeft.PageSetupLeft_Loaded (cyclomatic 17) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLeft.xaml.vb:5— PageSetupLeft.PageSetupLeft_Loaded 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.
PageSetupLaunch.RefreshRamText (cyclomatic 17) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:190— PageSetupLaunch.RefreshRamText 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.
MyRadioButton.RefreshColor (cyclomatic 17) Plain Craft Launcher 2/Controls/MyRadioButton.xaml.vb:169— MyRadioButton.RefreshColor 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.
FormMain.FrmMain_Drop (cyclomatic 17) Plain Craft Launcher 2/FormMain.xaml.vb:900— FormMain.FrmMain_Drop 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.
Java.CheckAsync (cyclomatic 17) PCLCS/Java.cs:27— Java.CheckAsync has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Pcl2TaowaInternal.ResolveScaffoldingServer (cyclomatic 16) Plain Craft Launcher 2/Modules/ModTaowaInternal.vb:158— Pcl2TaowaInternal.ResolveScaffoldingServer 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.
Pcl2TaowaInternal.ParseServerProfiles (cyclomatic 16) Plain Craft Launcher 2/Modules/ModTaowaInternal.vb:295— Pcl2TaowaInternal.ParseServerProfiles 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.
ModSecret.CheckPotatoCode (cyclomatic 16) Plain Craft Launcher 2/Modules/ModSecret.vb:861— ModSecret.CheckPotatoCode 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.
PageInstanceSetup._UpdateJavaRelatedUi (cyclomatic 16) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:396— PageInstanceSetup._UpdateJavaRelatedUi 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.
MyDropShadow.OnRender (cyclomatic 16) Plain Craft Launcher 2/Controls/MyDropShadow.vb:56— MyDropShadow.OnRender 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.
McInstance.JsonObject.Get (cyclomatic 16) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:525— McInstance.JsonObject.Get 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.
PageOtherTest.Jrrp (cyclomatic 16) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:151— PageOtherTest.Jrrp 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.
MySkin.Load (cyclomatic 16) Plain Craft Launcher 2/Pages/PageLaunch/MySkin.xaml.vb:78— MySkin.Load 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.
PageLaunchLeft.RefreshPage (cyclomatic 16) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:291— PageLaunchLeft.RefreshPage 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.
PageSetupLaunch.GetRam (cyclomatic 16) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:273— PageSetupLaunch.GetRam 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.
PageSetupUI.BackgroundRefresh (cyclomatic 16) Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:118— PageSetupUI.BackgroundRefresh 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.
ModBase.GetObjectFromXML (cyclomatic 16) Plain Craft Launcher 2/Modules/Base/ModBase.vb:1157— ModBase.GetObjectFromXML 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.
D18 · Solution Shape· Solution references 2 projects that do not exist · ×1
Solution references 2 projects that do not exist Plain Craft Launcher 2.sln— `Plain Craft Launcher 2.sln` declares 2 project file(s) that are missing from the tree (`MeloongCore/Shared/MeloongCore.csproj`, `MeloongCore/Wpf/MeloongCore.Wpf.csproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
CrashAnalyzer.AnalyzeCrit1 (cognitive 148) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:474— CrashAnalyzer.AnalyzeCrit1 has cognitive complexity 148 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceSearcher.Run (cognitive 127) Plain Craft Launcher 2/Modules/Resource/ResourceSearcher.vb:164— ResourceSearcher.Run has cognitive complexity 127 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrashAnalyzer.Prepare (cognitive 117) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:139— CrashAnalyzer.Prepare 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.
NetFile.Thread (cognitive 115) Plain Craft Launcher 2/Modules/Base/ModNet.vb:975— NetFile.Thread has cognitive complexity 115 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
FormMain.ShowUpdateLog (cognitive 112) Plain Craft Launcher 2/FormMain.xaml.vb:9— FormMain.ShowUpdateLog has cognitive complexity 112 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModSecret.ServerSub (cognitive 109) Plain Craft Launcher 2/Modules/ModSecret.vb:588— ModSecret.ServerSub has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ResourceProject.New.ctor (cognitive 108) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:123— ResourceProject.New.ctor has cognitive complexity 108 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModLaunch.McLaunchArgumentsJVM (cognitive 107) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1210— ModLaunch.McLaunchArgumentsJVM has cognitive complexity 107 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModLaunch.McLaunchPrerun (cognitive 100) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1716— ModLaunch.McLaunchPrerun has cognitive complexity 100 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CrashAnalyzer.GetAnalyzeResult (cognitive 91) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:928— CrashAnalyzer.GetAnalyzeResult has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MyListItem.SetChecked (cognitive 91) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:358— MyListItem.SetChecked has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PageDownloadResourceDetail.UpdateFilterResult (cognitive 82) Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:158— PageDownloadResourceDetail.UpdateFilterResult has cognitive complexity 82 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModJava.SelectOrDownloadJava (cognitive 78) Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:272— ModJava.SelectOrDownloadJava 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.
PageDownloadInstall.ReloadSelected (cognitive 77) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:180— PageDownloadInstall.ReloadSelected has cognitive complexity 77 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PageSetupUI.HiddenRefresh (cognitive 76) Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:436— PageSetupUI.HiddenRefresh has cognitive complexity 76 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
MyResizer.updateSize (cognitive 75) Plain Craft Launcher 2/Controls/MyResizer.vb:206— MyResizer.updateSize has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModAnimation.AniRun (cognitive 75) Plain Craft Launcher 2/Modules/Base/ModAnimation.vb:932— ModAnimation.AniRun has cognitive complexity 75 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModMinecraft.InitMcInstanceListWithoutCache (cognitive 72) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1429— ModMinecraft.InitMcInstanceListWithoutCache 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.
ResourceVersion.FromPlatformJson (cognitive 67) Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb:115— ResourceVersion.FromPlatformJson 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.
ModLaunch.McLaunchArgumentsGame (cognitive 66) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1378— ModLaunch.McLaunchArgumentsGame has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModDownload.DlSourceLoader (cognitive 64) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1313— ModDownload.DlSourceLoader has cognitive complexity 64 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModJava.GetJavaRequirement (cognitive 62) Plain Craft Launcher 2/Modules/Minecraft/ModJava.vb:127— ModJava.GetJavaRequirement 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.
ModMinecraft.McLibListGetWithJson (cognitive 62) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1944— ModMinecraft.McLibListGetWithJson 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.
CrashAnalyzer.AnalyzeModName (cognitive 61) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:737— CrashAnalyzer.AnalyzeModName 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.
MyListItem.RefreshColor (cognitive 58) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:546— MyListItem.RefreshColor 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.
PageSpeedLeft.TaskRefresh (cognitive 57) Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb:69— PageSpeedLeft.TaskRefresh has cognitive complexity 57 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModDownloadLib.MergeJson (cognitive 56) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1990— ModDownloadLib.MergeJson 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.
ResourceProject.ToResourceItem (cognitive 55) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:455— ResourceProject.ToResourceItem 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.
ModMinecraft.CompareVersion (cognitive 55) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2426— ModMinecraft.CompareVersion 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.
LoaderCombo.Update (cognitive 54) Plain Craft Launcher 2/Modules/Base/ModLoader.vb:584— LoaderCombo.Update has cognitive complexity 54 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ModLaunch.McLoginRequestLogin (cognitive 50) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:750— ModLaunch.McLoginRequestLogin 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.
PageSelectRight.McInstanceListUI (cognitive 49) Plain Craft Launcher 2/Pages/PageSelectRight.xaml.vb:25— PageSelectRight.McInstanceListUI 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.
CustomEvent.Raise (cognitive 48) Plain Craft Launcher 2/Modules/ModEvent.vb:176— CustomEvent.Raise 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.
ResourceProject.GetControlTitle (cognitive 46) Plain Craft Launcher 2/Modules/Resource/ResourceProject.vb:579— ResourceProject.GetControlTitle 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.
PageInstanceMod.RefreshBars (cognitive 46) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:157— PageInstanceMod.RefreshBars 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.
Application.Application_Startup (cognitive 46) Plain Craft Launcher 2/Application.xaml.vb:8— Application.Application_Startup 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.
MyButton.RefreshColor (cognitive 46) Plain Craft Launcher 2/Controls/MyButton.xaml.vb:74— MyButton.RefreshColor 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.
NetFile.TryBeginThread (cognitive 45) Plain Craft Launcher 2/Modules/Base/ModNet.vb:881— NetFile.TryBeginThread 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.
ModDownloadLib.McInstallLoader (cognitive 44) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1850— ModDownloadLib.McInstallLoader 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.
NetFile.SourceFail (cognitive 43) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1146— NetFile.SourceFail 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.
MyRadioBox.SetChecked (cognitive 43) Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:37— MyRadioBox.SetChecked 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.
PageLinkMain.InitLaunch (cognitive 42) Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:494— PageLinkMain.InitLaunch has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
McInstance.Load (cognitive 42) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:734— McInstance.Load has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
LocalResourceLoaders.LocalResourceFileLoad (cognitive 41) Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:5— LocalResourceLoaders.LocalResourceFileLoad 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.
ModMinecraft.InitMcInstanceListWithCache (cognitive 41) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1345— ModMinecraft.InitMcInstanceListWithCache 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.
ModLaunch.DeduplicateJavaArguments (cognitive 40) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1591— ModLaunch.DeduplicateJavaArguments 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.
McInstance.Version.Get (cognitive 40) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:314— McInstance.Version.Get 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.
McInstance.JsonObject.Get (cognitive 40) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:525— McInstance.JsonObject.Get 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.
ModModpack.ModpackInstall (cognitive 39) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:27— ModModpack.ModpackInstall 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.
ModDownloadLib.McUpdateLogShow (cognitive 39) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:259— ModDownloadLib.McUpdateLogShow 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.
PageLaunchLeft.LaunchingRefresh (cognitive 39) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:719— PageLaunchLeft.LaunchingRefresh 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.
ModAnimation.AniTimer (cognitive 39) Plain Craft Launcher 2/Modules/Base/ModAnimation.vb:856— ModAnimation.AniTimer 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.
NetFile.Merge (cognitive 38) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1239— NetFile.Merge 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.
ModMinecraft.McJsonRuleCheck (cognitive 38) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1845— ModMinecraft.McJsonRuleCheck 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.
PageSetupUI.BackgroundRefresh (cognitive 38) Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:118— PageSetupUI.BackgroundRefresh 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.
FormMain.PageChangeActual (cognitive 38) Plain Craft Launcher 2/FormMain.xaml.vb:1358— FormMain.PageChangeActual 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.
ModLaunch.McLaunchNatives (cognitive 37) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1635— ModLaunch.McLaunchNatives 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.
ModMinecraft.InitMcInstanceList (cognitive 37) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1266— ModMinecraft.InitMcInstanceList 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.
MyLocalModItem.Refresh (cognitive 36) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:328— MyLocalModItem.Refresh 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.
LoaderDownload.CheckExistingFile (cognitive 36) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1585— LoaderDownload.CheckExistingFile 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.
MyRadioButton.SetChecked (cognitive 36) Plain Craft Launcher 2/Controls/MyRadioButton.xaml.vb:47— MyRadioButton.SetChecked 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.
FormMain.FrmMain_Drop (cognitive 36) Plain Craft Launcher 2/FormMain.xaml.vb:900— FormMain.FrmMain_Drop 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.
ModModpack.InstallPackCurseForge (cognitive 35) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:176— ModModpack.InstallPackCurseForge 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.
PageInstanceExport.StartExport (cognitive 35) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:407— PageInstanceExport.StartExport 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.
LocalResourceLoaders.LocalResourceOnlineLoad (cognitive 34) Plain Craft Launcher 2/Modules/Resource/LocalResourceLoaders.vb:106— LocalResourceLoaders.LocalResourceOnlineLoad 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.
PageLinkMain.GetTargetPeers (cognitive 34) Plain Craft Launcher 2/Pages/PageLink/PageLinkMain.xaml.vb:620— PageLinkMain.GetTargetPeers 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.
ModMinecraft.McLibNetFilesFromTokens (cognitive 34) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2136— ModMinecraft.McLibNetFilesFromTokens 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.
PageInstanceMod.EDMods (cognitive 33) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:455— PageInstanceMod.EDMods 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.
ModMain.HelpLoad (cognitive 33) Plain Craft Launcher 2/Modules/ModMain.vb:566— ModMain.HelpLoad 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.
MyIconTextButton.RefreshColor (cognitive 32) Plain Craft Launcher 2/Controls/MyIconTextButton.xaml.vb:92— MyIconTextButton.RefreshColor 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.
ModLaunch.McLaunchCustom (cognitive 32) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1989— ModLaunch.McLaunchCustom 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.
ModMinecraft.McFolderListLoadSub (cognitive 32) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:58— ModMinecraft.McFolderListLoadSub 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.
ModDownloadLib.McDownloadOptiFineInstall (cognitive 31) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:344— ModDownloadLib.McDownloadOptiFineInstall 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.
ModLaunch.McLaunchStart (cognitive 31) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:97— ModLaunch.McLaunchStart 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.
PageOtherHelp.HelpListLoad (cognitive 31) Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:20— PageOtherHelp.HelpListLoad 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.
FormMain.FormMain_KeyDown (cognitive 31) Plain Craft Launcher 2/FormMain.xaml.vb:760— FormMain.FormMain_KeyDown 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.
ModMain.MyMsgBox (cognitive 31) Plain Craft Launcher 2/Modules/ModMain.vb:230— ModMain.MyMsgBox 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.
ModMain.TimerFool (cognitive 31) Plain Craft Launcher 2/Modules/ModMain.vb:670— ModMain.TimerFool 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.
CrashAnalyzer.Analyze (cognitive 30) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:391— CrashAnalyzer.Analyze 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.
PageInstanceMod.UpdateMods (cognitive 30) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:535— PageInstanceMod.UpdateMods 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.
MyDropShadow.OnRender (cognitive 30) Plain Craft Launcher 2/Controls/MyDropShadow.vb:56— MyDropShadow.OnRender 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.
MyRadioBox.SyncUI (cognitive 30) Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:101— MyRadioBox.SyncUI 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.
ModModpack.InstallPackModrinth (cognitive 29) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:381— ModModpack.InstallPackModrinth 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.
Pcl2TaowaInternal.ResolveScaffoldingServer (cognitive 29) Plain Craft Launcher 2/Modules/ModTaowaInternal.vb:158— Pcl2TaowaInternal.ResolveScaffoldingServer 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.
PageInstanceExport.ReloadSubOptions (cognitive 29) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:60— PageInstanceExport.ReloadSubOptions 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.
PageOtherHelp.SearchRun (cognitive 29) Plain Craft Launcher 2/Pages/PageOther/PageOtherHelp.xaml.vb:117— PageOtherHelp.SearchRun 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.
MyLocalModItem.Checked.Set (cognitive 28) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:151— MyLocalModItem.Checked.Set 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.
PageInstanceSetup.GetRam (cognitive 28) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:240— PageInstanceSetup.GetRam 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.
MyRadioButton.RefreshColor (cognitive 28) Plain Craft Launcher 2/Controls/MyRadioButton.xaml.vb:169— MyRadioButton.RefreshColor 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.
PclLogger.HandleBehavior (cognitive 27) Plain Craft Launcher 2/Modules/Base/PclLogger.vb:12— PclLogger.HandleBehavior 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.
ModMusic.MusicLoop (cognitive 27) Plain Craft Launcher 2/Modules/ModMusic.vb:277— ModMusic.MusicLoop 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.
ModNet.NetRequestByClientMultiple (cognitive 27) Plain Craft Launcher 2/Modules/Base/ModNet.vb:93— ModNet.NetRequestByClientMultiple 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.
McInstance.VersionDisplayName (cognitive 27) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:865— McInstance.VersionDisplayName 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.
PageSetupLaunch.GetRam (cognitive 27) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:273— PageSetupLaunch.GetRam 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.
MyCheckBox.SyncUI (cognitive 27) Plain Craft Launcher 2/Controls/MyCheckBox.xaml.vb:65— MyCheckBox.SyncUI 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.
MyIconButton.RefreshAnim (cognitive 27) Plain Craft Launcher 2/Controls/MyIconButton.xaml.vb:95— MyIconButton.RefreshAnim 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.
MyPageLeft.TriggerShowAnimation (cognitive 26) Plain Craft Launcher 2/Controls/MyPageLeft.vb:16— MyPageLeft.TriggerShowAnimation 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.
ResourceVersion.FromProjectId (cognitive 26) Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb:226— ResourceVersion.FromProjectId 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.
CrashAnalyzer.Output (cognitive 26) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:860— CrashAnalyzer.Output 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.
PageDownloadInstall.IsFabricApiCompatible (cognitive 26) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:916— PageDownloadInstall.IsFabricApiCompatible 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.
PageDownloadResourceDetail.Load_OnFinish (cognitive 26) Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:93— PageDownloadResourceDetail.Load_OnFinish 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.
ValidateFolderPath.Validate (cognitive 26) Plain Craft Launcher 2/Modules/Base/ModValidate.vb:380— ValidateFolderPath.Validate 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.
MyResourceItem.RefreshColor (cognitive 25) Plain Craft Launcher 2/Pages/PageDownload/Resource/MyResourceItem.xaml.vb:166— MyResourceItem.RefreshColor 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.
PageDownloadInstall.LoadMinecraft_OnFinish (cognitive 25) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:443— PageDownloadInstall.LoadMinecraft_OnFinish 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.
PageInstanceMod.SearchRun (cognitive 25) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:806— PageInstanceMod.SearchRun 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.
PageInstanceSetup._UpdateJavaRelatedUi (cognitive 25) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:396— PageInstanceSetup._UpdateJavaRelatedUi 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.
ModLaunch.McLoginServerStart (cognitive 25) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:601— ModLaunch.McLoginServerStart 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.
PageSelectLeft.McFolderListUI (cognitive 25) Plain Craft Launcher 2/Pages/PageSelectLeft.xaml.vb:12— PageSelectLeft.McFolderListUI 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.
PageLaunchLeft.RefreshPage (cognitive 25) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:291— PageLaunchLeft.RefreshPage 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.
PageLaunchLeft.SkinLegacyLoad (cognitive 25) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:449— PageLaunchLeft.SkinLegacyLoad 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.
Application.MyIconButton_Click (cognitive 25) Plain Craft Launcher 2/Application.xaml.vb:249— Application.MyIconButton_Click 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.
FormMain.UpdateBackgroundAndTitleBar (cognitive 25) Plain Craft Launcher 2/FormMain.xaml.vb:635— FormMain.UpdateBackgroundAndTitleBar 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.
ModMusic.MusicRefreshPlay (cognitive 24) Plain Craft Launcher 2/Modules/ModMusic.vb:181— ModMusic.MusicRefreshPlay 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.
Pcl2TaowaCore.ParseRoom (cognitive 24) Plain Craft Launcher 2/Modules/ModTaowaCore.vb:38— Pcl2TaowaCore.ParseRoom 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.
ModDownloadLib.McDownloadForgelikeLoader (cognitive 24) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1074— ModDownloadLib.McDownloadForgelikeLoader 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.
ModMinecraft.McLibListGet (cognitive 24) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1892— ModMinecraft.McLibListGet 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.
ModMain.HintTick (cognitive 24) Plain Craft Launcher 2/Modules/ModMain.vb:35— ModMain.HintTick 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.
CrashAnalyzer.Collect (cognitive 23) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:21— CrashAnalyzer.Collect 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.
CrashAnalyzer.AnalyzeCrit2 (cognitive 23) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:588— CrashAnalyzer.AnalyzeCrit2 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.
Watcher.GameLog (cognitive 23) Plain Craft Launcher 2/Modules/Minecraft/ModWatcher.vb:181— Watcher.GameLog 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.
PageInstanceMod.InstallMods (cognitive 23) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:286— PageInstanceMod.InstallMods 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.
ModNet.SendRequest (cognitive 23) Plain Craft Launcher 2/Modules/Base/ModNet.vb:216— ModNet.SendRequest 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.
McVersion.NameToVersion (cognitive 23) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1180— McVersion.NameToVersion 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.
MySlider.Value.Set (cognitive 23) Plain Craft Launcher 2/Controls/MySlider.xaml.vb:31— MySlider.Value.Set 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.
ModBase.GetObjectFromXML (cognitive 23) Plain Craft Launcher 2/Modules/Base/ModBase.vb:1157— ModBase.GetObjectFromXML 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.
PageInstanceSetup.RefreshRamText (cognitive 22) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:159— PageInstanceSetup.RefreshRamText 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.
ModDownload.DlForgeVersionBmclapiMain (cognitive 22) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:739— ModDownload.DlForgeVersionBmclapiMain 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.
PageSetupLaunch.RefreshRamText (cognitive 22) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:190— PageSetupLaunch.RefreshRamText 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.
CrashAnalyzer.AnalyzeStackKeyword (cognitive 21) Plain Craft Launcher 2/Modules/Minecraft/ModCrash.vb:673— CrashAnalyzer.AnalyzeStackKeyword 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.
Pcl2Taowa.JoinWorker (cognitive 21) Plain Craft Launcher 2/Modules/ModTaowa.vb:254— Pcl2Taowa.JoinWorker 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.
Pcl2TaowaInternal.ParseServerProfiles (cognitive 21) Plain Craft Launcher 2/Modules/ModTaowaInternal.vb:295— Pcl2TaowaInternal.ParseServerProfiles 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.
PageDownloadInstall.LoadOptiFabricGetError (cognitive 21) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:1047— PageDownloadInstall.LoadOptiFabricGetError 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.
PageLoginMsSkin.EditSkin (cognitive 21) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginMsSkin.xaml.vb:85— PageLoginMsSkin.EditSkin 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.
ModLaunch.McLoginLegacyUuidWithCustomSkin (cognitive 21) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1091— ModLaunch.McLoginLegacyUuidWithCustomSkin 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.
PageOtherTest.BtnClick_Click (cognitive 21) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:189— PageOtherTest.BtnClick_Click 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.
PageOtherTest.MemoryOptimize (cognitive 21) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:365— PageOtherTest.MemoryOptimize 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.
PageSetupLeft.Reset (cognitive 21) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLeft.xaml.vb:146— PageSetupLeft.Reset 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.
ModBase.SearchSimilarity (cognitive 21) Plain Craft Launcher 2/Modules/Base/ModBase.vb:680— ModBase.SearchSimilarity 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.
MyLocalModItem.PanTitle_SizeChanged (cognitive 20) Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:489— MyLocalModItem.PanTitle_SizeChanged 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.
ModSecret.UpdateReplace (cognitive 20) Plain Craft Launcher 2/Modules/ModSecret.vb:494— ModSecret.UpdateReplace 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.
MyMsgLogin.WorkThread (cognitive 20) Plain Craft Launcher 2/Pages/PageLaunch/MyMsgLogin.xaml.vb:98— MyMsgLogin.WorkThread 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.
ValidateFileName.Validate (cognitive 20) Plain Craft Launcher 2/Modules/Base/ModValidate.vb:329— ValidateFileName.Validate 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.
MyListItem.Type.Set (cognitive 20) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:299— MyListItem.Type.Set 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.
FormMain.UpgradeSub (cognitive 20) Plain Craft Launcher 2/FormMain.xaml.vb:436— FormMain.UpgradeSub 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.
ModDownloadLib.ForgelikeInjector (cognitive 19) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:934— ModDownloadLib.ForgelikeInjector 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.
ModDownloadLib.NeoForgeDownloadListItemPreload (cognitive 19) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1505— ModDownloadLib.NeoForgeDownloadListItemPreload 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.
PageInstanceExport.GetAllOptions (cognitive 19) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:181— PageInstanceExport.GetAllOptions 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.
ModLaunch.McLaunchPrecheck (cognitive 19) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:225— ModLaunch.McLaunchPrecheck 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.
ModLaunch.McLaunchArgumentsReplace (cognitive 19) Plain Craft Launcher 2/Modules/Minecraft/ModLaunch.vb:1479— ModLaunch.McLaunchArgumentsReplace 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.
ModMinecraft.McSkinGetAddress (cognitive 19) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:1696— ModMinecraft.McSkinGetAddress 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.
Java.CheckAsync (cognitive 19) PCLCS/Java.cs:27— Java.CheckAsync has cognitive complexity 19 (threshold 15). 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.
MyTextBox.RefreshColor (cognitive 18) Plain Craft Launcher 2/Controls/MyTextBox.vb:237— MyTextBox.RefreshColor 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.
PageDownloadInstall.LoadOptiFineGetError (cognitive 18) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:553— PageDownloadInstall.LoadOptiFineGetError 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.
PageDownloadInstall.LoadForgeGetError (cognitive 18) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadInstall.xaml.vb:716— PageDownloadInstall.LoadForgeGetError 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.
PageInstanceExport.RefreshAllOptionsUI (cognitive 18) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceExport.xaml.vb:93— PageInstanceExport.RefreshAllOptionsUI 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.
PageInstanceMod.Info_Click (cognitive 18) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:734— PageInstanceMod.Info_Click 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.
ModNet.NetRequestByClientRetry (cognitive 18) Plain Craft Launcher 2/Modules/Base/ModNet.vb:44— ModNet.NetRequestByClientRetry 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.
McInstance.GetJsonPath (cognitive 18) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:461— McInstance.GetJsonPath 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.
ModMinecraft.McLibNetFilesFromInstance (cognitive 18) Plain Craft Launcher 2/Modules/Minecraft/ModMinecraft.vb:2057— ModMinecraft.McLibNetFilesFromInstance 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.
PageOtherTest.Jrrp (cognitive 18) Plain Craft Launcher 2/Pages/PageOther/PageOtherTest.xaml.vb:151— PageOtherTest.Jrrp 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.
PageLaunchLeft.RefreshButtonsUI (cognitive 18) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:634— PageLaunchLeft.RefreshButtonsUI 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.
MyListItem.Buttons.Set (cognitive 18) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:122— MyListItem.Buttons.Set 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.
FormMain.PageChange (cognitive 18) Plain Craft Launcher 2/FormMain.xaml.vb:1307— FormMain.PageChange 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.
MyBitmap.New.ctor (cognitive 18) Plain Craft Launcher 2/Modules/Base/MyBitmap.vb:61— MyBitmap.New.ctor 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.
MyPageRight.TriggerEnterAnimation (cognitive 17) Plain Craft Launcher 2/Controls/MyPageRight.vb:392— MyPageRight.TriggerEnterAnimation 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.
ModModpack.InstallPackMCBBS (cognitive 17) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:698— ModModpack.InstallPackMCBBS 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.
CustomEvent.GetAbsoluteUrls (cognitive 17) Plain Craft Launcher 2/Modules/ModEvent.vb:339— CustomEvent.GetAbsoluteUrls 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.
ModLoader.LoaderFolderRun (cognitive 17) Plain Craft Launcher 2/Modules/Base/ModLoader.vb:751— ModLoader.LoaderFolderRun 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.
ModNet.NetRequestByClient (cognitive 17) Plain Craft Launcher 2/Modules/Base/ModNet.vb:10— ModNet.NetRequestByClient 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.
LoaderDownload.OnFail (cognitive 17) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1667— LoaderDownload.OnFail 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.
ModDownload.DlForgeVersionOfficialMain (cognitive 17) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:666— ModDownload.DlForgeVersionOfficialMain 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.
PageSetupLeft.PageSetupLeft_Loaded (cognitive 17) Plain Craft Launcher 2/Pages/PageSetup/PageSetupLeft.xaml.vb:5— PageSetupLeft.PageSetupLeft_Loaded 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.
MyListItem.OnSizeChanged (cognitive 17) Plain Craft Launcher 2/Controls/MyListItem.xaml.vb:329— MyListItem.OnSizeChanged 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.
JavaUtils.SearchFoldersAsync (cognitive 17) PCLCS/Java.cs:161— JavaUtils.SearchFoldersAsync has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (HasReparsePoint, a function literal at line 165). 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.
MyPageRight.PageLoaderState (cognitive 16) Plain Craft Launcher 2/Controls/MyPageRight.vb:353— MyPageRight.PageLoaderState 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.
ModModpack.InstallPackMMC (cognitive 16) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:572— ModModpack.InstallPackMMC 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.
Pcl2TaowaCore.DisposeStateResourcesLocked (cognitive 16) Plain Craft Launcher 2/Modules/ModTaowaCore.vb:248— Pcl2TaowaCore.DisposeStateResourcesLocked 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.
PageDownloadResourceDetail.Save_Click (cognitive 16) Plain Craft Launcher 2/Pages/PageDownload/Resource/PageDownloadCompDetail.xaml.vb:340— PageDownloadResourceDetail.Save_Click 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.
PageInstanceMod.DeleteMods (cognitive 16) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceMod.xaml.vb:663— PageInstanceMod.DeleteMods 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.
LoaderDownload.FailCount.Set (cognitive 16) Plain Craft Launcher 2/Modules/Base/ModNet.vb:1424— LoaderDownload.FailCount.Set 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.
MySkin.Load (cognitive 16) Plain Craft Launcher 2/Pages/PageLaunch/MySkin.xaml.vb:78— MySkin.Load 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.
PageSelectRight.DeleteInstance (cognitive 16) Plain Craft Launcher 2/Pages/PageSelectRight.xaml.vb:184— PageSelectRight.DeleteInstance 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.
Settings.Get (cognitive 16) Plain Craft Launcher 2/Pages/PageSetup/Settings.vb:307— Settings.Get 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.
PageSetupUI.RadioLogoType3_Check (cognitive 16) Plain Craft Launcher 2/Pages/PageSetup/PageSetupUI.xaml.vb:184— PageSetupUI.RadioLogoType3_Check 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.
MyRadioBox.Radiobox_MouseLeaveAnimation (cognitive 16) Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:223— MyRadioBox.Radiobox_MouseLeaveAnimation 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:180— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:180-377 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:384-515 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:521-568 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:574-694 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:701-773 — 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) Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:34— Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:34-53 | Plain Craft Launcher 2/Controls/MyMsg/MyMsgSelect.xaml.vb:43-60 | Plain Craft Launcher 2/Controls/MyMsg/MyMsgText.xaml.vb:33-51 | Plain Craft Launcher 2/Pages/PageLaunch/MyMsgLogin.xaml.vb:28-41 — 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.
D4 · Code Duplication· Edited copy of a member (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:242— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:242-319 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:279-347 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:114— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:114-149 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:145-180 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (74 corresponding lines) · ×1
Edited copy of a member (74 corresponding lines) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:161— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:161-234 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:192-267 — These two members are one piece of code written twice and then edited apart: 74 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:390— Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:390-426 | Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:512-548 | Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb:560-596 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:8— Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:8-24 | Plain Craft Launcher 2/Pages/PageLaunch/PageLoginNide.xaml.vb:8-24 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1028— Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1028-1048 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1056-1076 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) Plain Craft Launcher 2/Controls/MyPageRight.vb:393— Plain Craft Launcher 2/Controls/MyPageRight.vb:393-427 | Plain Craft Launcher 2/Controls/MyPageRight.vb:432-461 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 17+ corresponding lines) · ×1
Edited copies of one member (5 members, 17+ corresponding lines) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:389— Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:389-405 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:495-511 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:879-895 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1004-1020 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1103-1119 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:115— Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:115-128 | Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:132-146 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:91— Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:91-111 | Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:150-168 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) Plain Craft Launcher 2/Controls/MyCard.vb:179— Plain Craft Launcher 2/Controls/MyCard.vb:179-187 | Plain Craft Launcher 2/Controls/MyCard.vb:190-198 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) Plain Craft Launcher 2/Modules/Base/ModLoader.vb:212— Plain Craft Launcher 2/Modules/Base/ModLoader.vb:212-227 | Plain Craft Launcher 2/Modules/Base/ModLoader.vb:235-250 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) Plain Craft Launcher 2/Controls/MyMenuItem.vb:26— Plain Craft Launcher 2/Controls/MyMenuItem.vb:26-56 | Plain Craft Launcher 2/Controls/MyTextButton.vb:61-84 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:62— Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:62-72 | Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:76-87 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) Plain Craft Launcher 2/Modules/ModTaowa.vb:39— Plain Craft Launcher 2/Modules/ModTaowa.vb:39-44 | Plain Craft Launcher 2/Modules/ModTaowaEasyTier.vb:274-279 | Plain Craft Launcher 2/Modules/ModTaowaInternal.vb:362-367 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:30— Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:30-35 | Plain Craft Launcher 2/Pages/PageLaunch/PageLoginNide.xaml.vb:30-35 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (2 corresponding lines) · ×1
Edited copy of a member (2 corresponding lines) Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:82— Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuth.xaml.vb:82-83 | Plain Craft Launcher 2/Pages/PageLaunch/PageLoginAuthSkin.xaml.vb:81-82 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) Plain Craft Launcher 2/Controls/MyCheckBox.xaml.vb:142— Plain Craft Launcher 2/Controls/MyCheckBox.xaml.vb:142-153 | Plain Craft Launcher 2/Controls/MyCheckBox.xaml.vb:156-166 | Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:179-184 | Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb:187-192 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (37 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:328— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:328-364 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:466-502 — 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 (25 lines × 2) Plain Craft Launcher 2/Controls/MyPageRight.vb:67— Plain Craft Launcher 2/Controls/MyPageRight.vb:67-91 | Plain Craft Launcher 2/Controls/MyPageRight.vb:116-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 (26 lines × 2) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:117— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:117-142 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:148-173 — before extracting anything, compare `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb` and `Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 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. Read the line range as the matched WINDOW rather than a finished unit: at `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:117` 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 (24 lines × 2) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:161— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:161-184 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:192-215 — before extracting anything, compare `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb` and `Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 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. Read the line range as the matched WINDOW rather than a finished unit: at `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:161` 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–21 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:779— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:779-784 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:854-874 — 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 `Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:779` 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 (18 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1029— Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1029-1046 | Plain Craft Launcher 2/Modules/Minecraft/ModDownload.vb:1057-1074 — 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) Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:253— Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:253-269 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb:281-297 — before extracting anything, compare `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb` and `Plain Craft Launcher 2/Pages/PageSetup/PageSetupLaunch.xaml.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 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. Read the line range as the matched WINDOW rather than a finished unit: at `Plain Craft Launcher 2/Pages/PageInstance/PageInstanceSetup.xaml.vb:253` 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 (8 lines × 4) Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:41— Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:41-48 | Plain Craft Launcher 2/Controls/MyMsg/MyMsgSelect.xaml.vb:48-55 | Plain Craft Launcher 2/Controls/MyMsg/MyMsgText.xaml.vb:39-46 | Plain Craft Launcher 2/Pages/PageLaunch/MyMsgLogin.xaml.vb:30-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Plain Craft Launcher 2/Controls/MyMsg/MyMsgInput.xaml.vb:38` calls `Focus` and `Plain Craft Launcher 2/Controls/MyMsg/MyMsgSelect.xaml.vb:46` 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 (9 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:189— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:189-198 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:412-420 — 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 (8 lines × 2) Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1781— Plain Craft Launcher 2/Pages/PageDownload/ModDownloadLib.vb:1781-1788 | Plain Craft Launcher 2/Pages/PageInstance/PageInstanceOverall.xaml.vb:277-284 — 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 (7 lines × 2) Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:421— Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:421-427 | Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:719-725 — 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 `Plain Craft Launcher 2/Modules/Minecraft/ModModpack.vb:421` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Plain Craft Launcher 2/Pages/PageDownload/Resource/MyResourceItem.xaml.vb:48— Plain Craft Launcher 2/Pages/PageDownload/Resource/MyResourceItem.xaml.vb:48-58 | Plain Craft Launcher 2/Pages/PageInstance/MyLocalModItem.xaml.vb:49-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.
Duplicated block (16 lines × 4) Plain Craft Launcher 2/Pages/PageDownload/PageDownloadLeft.xaml.vb:62— Plain Craft Launcher 2/Pages/PageDownload/PageDownloadLeft.xaml.vb:62-79 | Plain Craft Launcher 2/Pages/PageInstance/PageInstanceLeft.xaml.vb:74-89 | Plain Craft Launcher 2/Pages/PageOther/PageOtherLeft.xaml.vb:92-107 | Plain Craft Launcher 2/Pages/PageSetup/PageSetupLeft.xaml.vb:124-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: Plain Craft Launcher 2/Modules/Base/ModAnimation.vb, Plain Craft Launcher 2/Pages/PageLaunch/PageLaunchLeft.xaml.vb, Plain Craft Launcher 2/Controls/MyPageRight.vb, Plain Craft Launcher 2/Modules/Resource/ResourceVersion.vb, Plain Craft Launcher 2/Pages/PageSpeedLeft.xaml.vb, Plain Craft Launcher 2/Controls/MyRadioBox.xaml.vb, Plain Craft Launcher 2/Controls/MyRadioButton.xaml.vb, Plain Craft Launcher 2/Pages/PageLaunch/PageLoginMs.xaml.vb (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: Plain Craft Launcher 2/Modules/ModTaowaCore.vb, Plain Craft Launcher 2/Modules/ModTaowaEasyTier.vb, Plain Craft Launcher 2/Modules/ModTaowa.vb, Plain Craft Launcher 2/Modules/ModTaowaInternal.vb. Pair on, review, or document these before any departure.
No ADRs found Plain Craft Launcher 2/Plain Craft Launcher 2.vbproj:8— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Plain Craft Launcher 2/Plain Craft Launcher 2.vbproj` makes this repository a deployable product (line 8).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion Plain Craft Launcher 2/Plain Craft Launcher 2.vbproj:1— `Plain Craft Launcher 2` overshoots its size bounds (43909 LoC, 301 public types across 2 namespaces). 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 95 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 95 of the 117 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file Plain Craft Launcher 2/Controls/Behaviors/ClipboardInterceptor.vb:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST REDACTED:6— 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 2 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 dependency-update automation PCLCS/PCLCS.csproj:18— `PCLCS/PCLCS.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Null-forgiving operator (`!`) suppressions override nullable warnings — ~2.2 `!` suppressions per 1k syntax nodes — 6 suppression(s) across the 2730 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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. semgrep could not parse 1 file(s) — `PCLCS/Java.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1dd18-c91c-76bc-9bff-94cb392751fd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 68 · Warnings: 492 · Recommendations: 15 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 02:45 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.