rajeshca911/PS5-BACKPORK-KITCHEN

Executive summary

rajeshca911/PS5-BACKPORK-KITCHEN scores 43 out of 100 and is rated Weak, while four of its five lenses score higher still: Security and Compliance at 100, rated Exemplary, and Architecture at 92, Code Health at 55 and Maturity at 51, all rated Adequate.

The score is lower than those four because the weakest lens counts most, and here that is Production Readiness, which scores 21 and is rated Critical. Its Code Coverage dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 3 Leaked secret finding(s) in Secret Scanning and to resolve the 1 No automated tests finding(s) in Code Coverage, and if Production Readiness rose to 70, the score would rise from 43 to about 60.

113 findings are critical: 108 in Explicit Debt, three in Secret Scanning, one in Code Coverage and one in Dependency Hygiene.

Watchdog couldn't measure 36 dimensions in this code, among them IL Efficiency, Data Protection and Access Controls, so they are left out of the score. The product code is 36,468 lines, which would take an estimated 0.3 person-years, around €40,000, to rebuild.

Code Health 55 Adequate Architecture 92 Adequate, capped by Project Cohesion Maturity 51 Adequate, capped by Architecture documentation Production Readiness 21 ⚠ Critical, capped by Code Coverage, Test Distribution, Secret Scanning, CI/CD gates and Security & performance tooling Security and Compliance 100 ★ Exemplary

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 21 · counts for 47%Maturity 51 · counts for 26%Code Health 55 · counts for 14%Architecture 92 · counts for 8%Security and Compliance 100 · counts for 4%

If Production Readiness rose from 21 to 70, the lowest score rated Strong, the score would rise from 43 to about 60.

Code composition: what the lines of code are

Product code 100%

New since the last survey: 3 findings

These 3 critical or serious findings weren't in the previous survey, on 7 October 2026.

Secret Scanning · REDACTED
Secret Scanning · REDACTED
Secret Scanning · REDACTED

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Rebuild cost: about €40,000 · Estimate

Cost to rebuild	€13,000 to €66,000, for 219 to 694 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 43. 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: 36,468 lines of product code

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

Top priorities

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

Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED.

Raises the score by about 17 points · Low effort · Secret Scanning

Resolve the 1 No automated tests finding(s) in Code Coverage.

Raises the score by about 17 points · Low effort · Code Coverage

Resolve the 1 No tests found finding(s) in Test Distribution.

Raises the score by about 17 points · Low effort · Test Distribution

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €40,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 21 (Critical). 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 3 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 17 points for low effort, because it clears the 3 Secret Scanning findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

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.

15 modules, with 26 dependencies between them. One loop runs through 6 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.
uses →	2 PS5_BACKPORK_KITCHEN.Architecture.Domain.Errors	5 PS5_BACKPORK_KITCHEN.Services.GameSearch	6 PS5_BACKPORK_KITCHEN.Architecture.Domain.Models	7 PS5_BACKPORK_KITCHEN.Architecture.Domain.Results	9 PS5_BACKPORK_KITCHEN.Architecture.Infrastructure.Adapters	10 PS5_BACKPORK_KITCHEN.Architecture.Infrastructure.Repositories	11 PS5_BACKPORK_KITCHEN.Architecture.Application.Services	13 PS5_BACKPORK_KITCHEN.Architecture.Application.Coordinators	14 PS5_BACKPORK_KITCHEN
1 Microsoft.VisualBasic
2 PS5_BACKPORK_KITCHEN.Architecture.Domain.Errors
3 PS5_BACKPORK_KITCHEN.My
4 PS5_BACKPORK_KITCHEN.PS5_Payload_Sender
5 PS5_BACKPORK_KITCHEN.Services.GameSearch
6 PS5_BACKPORK_KITCHEN.Architecture.Domain.Models								2
7 PS5_BACKPORK_KITCHEN.Architecture.Domain.Results	1
8 PS5_BACKPORK_KITCHEN.Architecture.Application.Context			1
9 PS5_BACKPORK_KITCHEN.Architecture.Infrastructure.Adapters			2	2			1		1
10 PS5_BACKPORK_KITCHEN.Architecture.Infrastructure.Repositories			2
11 PS5_BACKPORK_KITCHEN.Architecture.Application.Services			2	5	4				1
12 PS5_BACKPORK_KITCHEN.Architecture.Infrastructure.Adapters.Testing					3
13 PS5_BACKPORK_KITCHEN.Architecture.Application.Coordinators			6	3	6		3		1
14 PS5_BACKPORK_KITCHEN	1	11	5			1	1	1
15 PS5_BACKPORK_KITCHEN.Architecture.Composition					3			3

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 55% · Adequate ·

The Good

D4 · .NET / C# Code Duplication 9.4 D18 · .NET / C# Solution Shape 8.0 GD1 · Repo Unfinished & placeholder code 10.0 X28 · Repo Index access outside its own emptiness guard 10.0

The Bad

D1 · .NET / C# Cyclomatic Complexity 6.7 D3 · .NET / C# God Classes 6.6

The Ugly

D2 · .NET / C# Cognitive Complexity 4.8 D17 · .NET / C# Explicit Debt 4.4

At a glance — Architecture · 92% · Adequate · gated by D26 ·

The Good

D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 10.0 D27 · .NET / C# Navigability 9.7 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 9.8 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.4

The Ugly

D26 · .NET / C# Project Cohesion 0.0

At a glance — Maturity · 51% · Adequate · gated by M2 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 9.7 D21 · .NET / C# Naming Consistency 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

D19 · .NET / C# Documentation Quality 5.0 M1 · Repo Documentation (README) 6.0 M3 · Repo Folder & project structure 6.0

The Ugly

D20 · .NET / C# ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 21% · Critical · gated by D8, D9, D13, P1, P3 ·

The Good

D12 · .NET / C# Dependency Hygiene 8.1 D14 · .NET / C# License Compliance 10.0 P2 · Repo Observability 7.0 P6 · Repo Release Hygiene 10.0

The Ugly

D8 · .NET / C# Code Coverage 0.0 D13 · .NET / C# Secret Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P5 · Repo DR & Backup 4.0

At a glance — Security · 100% · Exemplary ·

The Good

D28 · .NET / C# Secrets (history) 10.0 D29 · .NET / C# Static Analysis (SAST) 10.0 D44 · .NET / C# Platform End-of-Life 10.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A07:2025 — Authentication Failures	3	High / Critical

Roadmap

Begin by resolving three leaked secrets in the codebase, specifically addressing issues in REDACTED and REDACTED. Next, establish automated testing by addressing the lack of code coverage and ensuring tests are properly distributed. Simultaneously, remediate vulnerable dependencies and systematically eliminate empty catch blocks, prioritizing fixes in ThemeManager.vb, Form1.vb, and DirectDownloadService.vb.

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

Do this	Helps	Effort	Dimension
Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED.	+17.5 pts	Low	Secret Scanning
Resolve the 1 No automated tests finding(s) in Code Coverage.	+17.5 pts	Low	Code Coverage
Resolve the 1 No tests found finding(s) in Test Distribution.	+17.5 pts	Low	Test Distribution
Resolve the 1 Vulnerable finding(s) in Dependency Hygiene.	+9.5 pts	Low	Dependency Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+5.3 pts	Low	ADR Quality
Resolve the 2 OnErrorResumeSwallow finding(s) in Explicit Debt — start with commonfunctions.vb, Form1.vb.	+2.9 pts	Low	Explicit Debt
Add a CI workflow that builds and runs the test suite on every push/PR.	+5.1 pts	Medium	CI/CD gates
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.	+3.8 pts	Medium	Architecture documentation

File quality

Per-file score 0–10 — a quality signature. Of 76 files carrying findings, judged against the Production bar: 12% slop · 74% mixed · 14% near-clean.

File	Score	Band	Worst signal
PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb	2.2	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Form1.vb	2.4	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/ThemeManager.vb	3.0	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb	3.4	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb	3.4	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb	3.6	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/RemotePkgInstallService.vb	3.6	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb	3.8	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb	3.8	Slop	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb	4.2	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/ElfInspector.vb	4.2	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/JsonConfigurationStore.vb	4.2	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb	4.2	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb	4.2	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb	4.6	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb	4.6	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb	4.6	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb	4.7	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb	4.8	Mixed	Explicit Debt: EmptyCatchBlock
PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb	4.8	Mixed	Explicit Debt: EmptyCatchBlock

How the grades work

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

Critical — 113

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 — 197

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 — 11

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

Could not be resolved — 37

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 35 of 39 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 39 dimensions across the health lenses

D1D2D3D4D5D6D8D9D12D13D14D15D17D18D19D20D21D26D27D28D29D35D44AX10AX3AX4AX5AX6GD1M1M2M3M4P1P2P3P5P6X28

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, 307 of 321 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a160d4-99fa-7cbb-acda-d6435cb9d2ef.

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

Run transparency — what happened this run

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

D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits for a meaningful bus factor (37 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
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.
D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (37 commit(s) sampled).
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
PF3 Async & latency hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X10 Duplicated predicate — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's 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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity6.7 / 10Adequate✓ Tool-verified

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

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

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

31 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SelfFile.ExtractElf at 52.

SelfFile.ExtractElf (cyclomatic 52)PS5 BACKPORK KITCHEN/Services/SelfUtilCode/SelfFile.vb:104

PatchingHistoryRepository.GetStatistics (cyclomatic 35)PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:171

DirectDownloadService.DownloadVikingFileAsync (cyclomatic 33)PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:226

TorrentGalaxyProvider.ParseSearchResults (cyclomatic 32)PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:145

FirmwareDownloadModule.DownloadFileWithProgressAsync (cyclomatic 27)PS5 BACKPORK KITCHEN/Services/FirmwareDownloadModule.vb:266

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

What to do

Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with SelfFile.ExtractElf (cyclomatic 52), PatchingHistoryRepository.GetStatistics (cyclomatic 35), DirectDownloadService.DownloadVikingFileAsync (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D2 · Cognitive Complexity4.8 / 10Weak✓ Tool-verified

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

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

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

61 method(s) exceeded the cognitive complexity threshold of 15; the worst was SelfFile.ExtractElf at 92.

SelfFile.ExtractElf (cognitive 92)PS5 BACKPORK KITCHEN/Services/SelfUtilCode/SelfFile.vb:104

DirectDownloadService.DownloadVikingFileAsync (cognitive 64)PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:226

TorrentGalaxyProvider.ParseSearchResults (cognitive 62)PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:145

RuTrackerProvider.ParseSearchResults (cognitive 47)PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:239

PatchingHistoryRepository.GetStatistics (cognitive 43)PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:171

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

What to do

Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with SelfFile.ExtractElf (cognitive 92), DirectDownloadService.DownloadVikingFileAsync (cognitive 64), TorrentGalaxyProvider.ParseSearchResults (cognitive 62). — 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 3 together lifts Cognitive Complexity from 4.8 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes6.6 / 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.

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

46 god class(es) detected.

MethodTooLong: FirmwareManagerForm.InitializeComponent · ×19PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:87

ClassTooLong: ElfInspectorForm · ×15PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb

FileTooLong: PS5 BACKPORK KITCHEN/Form1.vb · ×10PS5 BACKPORK KITCHEN/Form1.vb

TooManyMethods: Form1 · ×2PS5 BACKPORK KITCHEN/Form1.vb

What to do

Resolve the 19 MethodTooLong finding(s) in God Classes — start with DirectDownloadService.vb (2), FirmwareManagerForm.vb, PayloadManagerForm.vb. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 15 ClassTooLong finding(s) in God Classes — start with ElfInspectorForm.vb, FirmwareManagerForm.vb, PackageManagerForm.vb. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 10 FileTooLong finding(s) in God Classes — start with Form1.vb, ElfInspectorForm.vb, FirmwareManagerForm.vb. — One of this dimension's main actionable groups (10 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.4 / 10Stronggated by 53 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

49 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (10 lines × 2) · ×5PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:112

Duplicated block (9 lines × 2) · ×5PS5 BACKPORK KITCHEN/core/ElfPatcher.vb:23

Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:58

Duplicated block (13 lines × 2) · ×3PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:316

Duplicated block (8 lines × 2) · ×3PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:458

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

What to do

Resolve the 5 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with FPKGBuilderForm.vb, PayloadManagerForm.vb, commonfunctions.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ElfPatcher.vb, ElfInspectorForm.vb, InputValidator.vb. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 3 Members sharing a duplicated core (5 members, 50+ identical tokens) finding(s) in Code Duplication — start with ElfInspectorForm.vb, GameSearchManager.vb, LeetxProvider.vb. — One of this dimension's main actionable groups (3 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 72 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.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 coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, 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.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Code Coverage in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

No test suite found.

No tests found

What to do

Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D12 · Dependency Hygiene8.1 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

3 outdated, 1 vulnerable, 0 deprecated packages.

Vulnerable: SharpCompress

Outdated: FluentFTP · ×3

What to do

Resolve the 1 Vulnerable finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 issue-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

2 secret(s) detected.

REDACTED

What to do

Resolve the 3 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Stand up a CI pipeline, then gate Secret Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

0 of 96 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 5 direct `PackageReference`(s), and 91 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

Top hotspots: PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb (6×23=138)

Hotspot: PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vbPS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb:259

What to do

Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ElfPatchingService.vb. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

110 deducted debt markers + 0 dead symbols across 36468 LoC in the .NET projects (2.8/KLoC) → score 4.4.

EmptyCatchBlock · ×106PS5 BACKPORK KITCHEN/01Frms/AdvancedSettingsForm.vb:326

OnErrorResumeSwallow · ×2PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:35

TodoComment · ×2PS5 BACKPORK KITCHEN/01Frms/AboutBox1.vb:13

What to do

Resolve the 106 EmptyCatchBlock finding(s) in Explicit Debt — start with ThemeManager.vb (8), Form1.vb (7), DirectDownloadService.vb (7). — One of this dimension's main actionable groups (106 issue-level).
Resolve the 2 OnErrorResumeSwallow finding(s) in Explicit Debt — start with commonfunctions.vb, Form1.vb. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with AboutBox1.vb, StatisticsForm.vb. — One of this dimension's main actionable groups (2 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D18 · Solution Shape8.0 / 10Strong✓ Tool-verified

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

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

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

1 projects, 169 source files, 36468 hand-written lines of code (36468 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 2856 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges.

Single-project monolith

What to do

Resolve the 1 Single-project monolith finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D19 · Documentation QualityAdequate◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's single README is a project-discontinuation notice with no overview of what PS5 BackPork Kitchen does or how to use it. It describes features, requirements, and a step-by-step 'How To Use' but omits the core missing elements: an installation/usage guide for the tool itself (not the project root README), contribution guidance, and a licence statement. The document is well written with a clear title, features list, and roadmap; its single file scope limits what it can cover.

What to do

Improve Documentation Quality — currently 5.0/10. — The repository's single README is a project-discontinuation notice with no overview of what PS5 BackPork Kitchen does or how to use it. It describes features, requirements, and a step-by-step 'How To Use' but omits the core missing elements: an installation/usage guide for the tool itself (not the project root README), contribution guidance, and a licence statement. The document is well written with a clear title, features list, and roadmap; its single file scope limits what it can cover.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

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

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

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

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

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

1 of 1 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

`IConfigurationStore` declares 36 members: `GetDefaultPs5SdkAsync`, `SetDefaultPs5SdkAsync`, `GetDefaultPs4SdkAsync`, `SetDefaultPs4SdkAsync`, `GetAutoBackupAsync`, `SetAutoBackupAsync`, `GetAutoVerifyAsync`, `SetAutoVerifyAsync`, `GetEnableFileLoggingAsync`, `SetEnableFileLoggingAsync`, `GetLogLevelAsync`, `SetLogLevelAsync`, `GetThemeAsync`, `SetThemeAsync`, `GetLastUsedFolderAsync`, `SetLastUsedFolderAsync`, `GetCheckForUpdatesOnStartupAsync`, `SetCheckForUpdatesOnStartupAsync`, `GetLastUpdateCheckAsync`, `SetLastUpdateCheckAsync`, `GetSkippedUpdateVersionAsync`, `SetSkippedUpdateVersionAsync`, `GetExportReportsAutomaticallyAsync`, `SetExportReportsAutomaticallyAsync`, `GetReportOutputDirectoryAsync`, `SetReportOutputDirectoryAsync`, `GetLanguageAsync`, `SetLanguageAsync`, `GetMaxConcurrentOperationsAsync`, `SetMaxConcurrentOperationsAsync`, `GetTempFolderCleanupOnExitAsync`, `SetTempFolderCleanupOnExitAsync`, `GetConfigurationAsync`, `SetConfigurationAsync`, `SaveAsync`, `ReloadAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/IConfigurationStore.vb:5

What to do

Split fat interfaces into focused role-interfaces so clients depend only on what they use.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

This repository declares its own end of life: `README.md` line 2 reads “# ⚠️ Project Discontinued”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on. — README.md:2

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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

Production code isn't grouped under a src/ folder — it all sits under PS5 BACKPORK KITCHEN/ alongside the root build files, so the conventional src/ boundary between the product and its tooling isn't drawn.

What to do

Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates0.0 / 10Critical✓ 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.

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

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.

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

What to do

For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

No static application security testing detected. For this repository's stack, add 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 — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Run 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 — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.

Do you agree with this assessment?

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	55%	Adequate	Acceptable, with room to improve.
Architecture	92%	Adequate — gated by D26	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	51%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	21%	Critical — gated by D8, D9, D13, P1, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	100%	Exemplary	Strongest area.

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 — 4 control(s) we could not find positive evidence for

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

C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release

Not included — 74 check(s) not relevant to this codebase

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

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — 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.
D16 Bus Factor — too few commits for a meaningful bus factor
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
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) — 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.
D34 Knowledge Freshness — too few commits to judge knowledge freshness
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
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 (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Visual Basic code has 43,573 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X10 Duplicated predicate — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository

Appendix A — Findings (grouped)

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

Critical — 113 finding(s)

D17 · Explicit Debt · EmptyCatchBlock · ×106

EmptyCatchBlock PS5 BACKPORK KITCHEN/01Frms/AdvancedSettingsForm.vb:326 — 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 PS5 BACKPORK KITCHEN/01Frms/AdvancedSettingsForm.vb:346 — 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 PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb:885 — 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 PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.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 PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:511 — 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 PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:386 — 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 PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:705 — 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 PS5 BACKPORK KITCHEN/01Frms/OperationHistoryForm.vb:149 — 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 PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:542 — 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 PS5 BACKPORK KITCHEN/01Frms/RemotePkgInstallForm.vb:413 — 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 PS5 BACKPORK KITCHEN/01Frms/RemotePkgInstallForm.vb:426 — 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 PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:643 — 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 PS5 BACKPORK KITCHEN/01global/ModernUIHelpers.vb:279 — 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 PS5 BACKPORK KITCHEN/01global/ModernUIHelpers.vb:296 — 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 PS5 BACKPORK KITCHEN/01global/ModernUIHelpers.vb:323 — 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 PS5 BACKPORK KITCHEN/01global/ModernUIHelpers.vb:356 — 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 PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/JsonConfigurationStore.vb:47 — 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 PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/JsonConfigurationStore.vb:57 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/LoggerAdapter.vb:21 — 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 PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:132 — 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 PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:161 — 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 PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:224 — 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 PS5 BACKPORK KITCHEN/Form1.vb:779 — 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 PS5 BACKPORK KITCHEN/Form1.vb:790 — 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 PS5 BACKPORK KITCHEN/Form1.vb:805 — 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.
+ 81 more in this group — see findings.md.

D13 · Secret Scanning · Leaked secret · ×3

REDACTED
REDACTED
REDACTED

D17 · Explicit Debt · OnErrorResumeSwallow · ×2

OnErrorResumeSwallow PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:35 — 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 PS5 BACKPORK KITCHEN/Form1.vb:346 — 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`.

D12 · Dependency Hygiene · Vulnerable · ×1

Vulnerable: SharpCompress — SharpCompress 0.44.5 — Moderate severity. https://github.com/advisories/[GHSA redacted]

D8 · Code Coverage · No automated tests · ×1

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.

Serious — 197 finding(s)

D3 · God Classes · MethodTooLong · ×19

MethodTooLong: FirmwareManagerForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:87 — MethodTooLong — InitializeComponent runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PayloadManagerForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb:182 — MethodTooLong — InitializeComponent runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× 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: SelfFile.ExtractElf PS5 BACKPORK KITCHEN/Services/SelfUtilCode/SelfFile.vb:104 — MethodTooLong — ExtractElf runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.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: KeyboardShortcutManager.ConfigureForm1Shortcuts PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:98 — MethodTooLong — ConfigureForm1Shortcuts runs 174 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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: FtpConnectionForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/FtpConnectionForm.vb:41 — MethodTooLong — InitializeComponent runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GameLibraryForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:48 — MethodTooLong — InitializeComponent runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SigningOptionsDialog.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/SigningOptionsDialog.vb:61 — MethodTooLong — InitializeComponent runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FtpBrowserForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/FtpBrowserForm.vb:35 — MethodTooLong — InitializeComponent runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: GameSearchForm.InitializeComponent PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:39 — MethodTooLong — InitializeComponent runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: DashboardForm.InitializeComponent PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb:434 — MethodTooLong — InitializeComponent runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: ElfInspectorForm.MnuPatch_Click PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:922 — MethodTooLong — MnuPatch_Click runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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: RemotePkgInstallForm.InitializeComponent PS5 BACKPORK KITCHEN/01Frms/RemotePkgInstallForm.vb:45 — MethodTooLong — InitializeComponent 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: Form1.BtnStart_Click PS5 BACKPORK KITCHEN/Form1.vb:42 — MethodTooLong — BtnStart_Click runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× 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: DirectDownloadService.DownloadVikingFileAsync PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:226 — MethodTooLong — DownloadVikingFileAsync runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: ElfPatchingService.PatchFileAsync PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb:259 — MethodTooLong — PatchFileAsync runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DirectDownloadService.DownloadAkiraboxAsync PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:574 — MethodTooLong — DownloadAkiraboxAsync runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.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: SignedElfFile.Prepare PS5 BACKPORK KITCHEN/signelf/SignedElfFile.vb:54 — MethodTooLong — Prepare 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: FirmwareExtractorModule.ExtractFirmwareAsync PS5 BACKPORK KITCHEN/Services/FirmwareExtractorModule.vb:159 — MethodTooLong — ExtractFirmwareAsync runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× 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: PackageManagerForm.InitializeFormLayout PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:61 — MethodTooLong — InitializeFormLayout runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D3 · God Classes · ClassTooLong · ×15

ClassTooLong: ElfInspectorForm PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb — ClassTooLong — 1053 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 653 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FirmwareManagerForm PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb — ClassTooLong — 969 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 569 over it, 2.42× 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: PackageManagerForm PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb — ClassTooLong — 744 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 344 over it, 1.86× 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: DirectDownloadService PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb — ClassTooLong — 702 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 302 over it, 1.76× 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: GameSearchForm PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb — ClassTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 264 over it, 1.66× 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: PayloadManagerForm PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb — ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 206 over it, 1.52× 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: UFS2ImageForm PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb — ClassTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 180 over it, 1.45× 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: GameLibraryForm PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb — ClassTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 138 over it, 1.35× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DashboardForm PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb — ClassTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 106 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.
ClassTooLong: CustomLibraryForm PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb — ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: OperationModeForm PS5 BACKPORK KITCHEN/01Frms/OperationModeForm.vb — ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LocalizationService PS5 BACKPORK KITCHEN/Services/LocalizationService.vb — ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 45 over it, 1.11× 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: commonfunctions PS5 BACKPORK KITCHEN/01global/commonfunctions.vb — ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 23 over it, 1.06× 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: FirmwareDownloadModule PS5 BACKPORK KITCHEN/Services/FirmwareDownloadModule.vb — ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 6 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FPKGBuilderForm PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 2 over it, 1.01× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FileTooLong · ×10

FileTooLong: PS5 BACKPORK KITCHEN/Form1.vb PS5 BACKPORK KITCHEN/Form1.vb — FileTooLong — 1307 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 807 over it, 2.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: 01Frms/ElfInspectorForm.vb PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb — FileTooLong — 1056 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 556 over it, 2.11× 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: 01Frms/FirmwareManagerForm.vb PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb — FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 474 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: 01Frms/PackageManagerForm.vb PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb — FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 246 over it, 1.49× 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: GameSearch/DirectDownloadService.vb PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb — FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Forms/GameSearchForm.vb PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb — FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 167 over it, 1.33× 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: 01Frms/GameLibraryForm.vb PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb — FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 115 over it, 1.23× 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: 01Frms/PayloadManagerForm.vb PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb — FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 111 over it, 1.22× 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: 01Frms/UFS2ImageForm.vb PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb — FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 82 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Forms/DashboardForm.vb PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb — FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 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.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5

Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:112 — PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:112-121 | PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:48-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:122` calls `Add`, `RowStyle` and `PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:58` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb:159 — PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb:159-168 | PS5 BACKPORK KITCHEN/01Frms/StatisticsForm.vb:28-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:407 — PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:407-416 | PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:432-441 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:287 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:287-297 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:309-318 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:308` calls `IsNullOrEmpty` and `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:286` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:684 — PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:684-693 | PS5 BACKPORK KITCHEN/Services/FtpManager.vb:440-449 — 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.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5

Duplicated block (9 lines × 2) PS5 BACKPORK KITCHEN/core/ElfPatcher.vb:23 — PS5 BACKPORK KITCHEN/core/ElfPatcher.vb:23-31 | PS5 BACKPORK KITCHEN/core/Models/ElfInfo.vb:67-75 — 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 (9 lines × 2) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:661 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:661-669 | PS5 BACKPORK KITCHEN/Services/FirmwareManagerService.vb:463-471 — 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 (9 lines × 2) PS5 BACKPORK KITCHEN/Services/InputValidator.vb:117 — PS5 BACKPORK KITCHEN/Services/InputValidator.vb:117-125 | PS5 BACKPORK KITCHEN/Services/IntegrityVerifier.vb:27-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) PS5 BACKPORK KITCHEN/Form1.vb:1986 — PS5 BACKPORK KITCHEN/Form1.vb:1986-1994 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:332-340 — 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 (9 lines × 2) PS5 BACKPORK KITCHEN/Services/ElfInspector.vb:281 — PS5 BACKPORK KITCHEN/Services/ElfInspector.vb:281-289 | PS5 BACKPORK KITCHEN/Services/InputValidator.vb:148-156 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3

Members sharing a duplicated core (5 members, 50+ identical tokens) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:58 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:58-178 | PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:109-201 | PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:62-201 | PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:45-119 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:51-174 — 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:106 — PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:106-138 | PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:82-138 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:82-122 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:182-236 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:77-126 — 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.
Members sharing a duplicated core (5 members, 50+ identical tokens) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:158 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:158-254 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:126-204 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:249-337 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:240-356 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:146-282 — 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 · Duplicated block (13 lines × 2) · ×3

Duplicated block (13 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:316 — PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:316-328 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:255-267 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb:152 — PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb:152-164 | PS5 BACKPORK KITCHEN/Forms/DashboardForm.vb:210-222 — 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 (13 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:142 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:142-154 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:130-142 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3

Duplicated block (8 lines × 2) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:458 — PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:458-465 | PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:480-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) PS5 BACKPORK KITCHEN/Services/InputValidator.vb:117 — PS5 BACKPORK KITCHEN/Services/InputValidator.vb:117-124 | PS5 BACKPORK KITCHEN/Services/IntegrityVerifier.vb:123-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) PS5 BACKPORK KITCHEN/Services/BackupService.vb:40 — PS5 BACKPORK KITCHEN/Services/BackupService.vb:40-48 | PS5 BACKPORK KITCHEN/Services/IntegrityVerifier.vb:124-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `PS5 BACKPORK KITCHEN/Services/BackupService.vb:40` 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.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3

Duplicated block (5 lines × 2) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:443 — PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:443-447 | PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:868-872 — 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) PS5 BACKPORK KITCHEN/core/UFS2/UFS2FileNode.vb:83 — PS5 BACKPORK KITCHEN/core/UFS2/UFS2FileNode.vb:83-87 | PS5 BACKPORK KITCHEN/core/UFS2/UFS2FileNode.vb:88-92 — 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) PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:237 — PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:237-241 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:245-249 — 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.

D17 · Explicit Debt · TodoComment · ×2

TodoComment PS5 BACKPORK KITCHEN/01Frms/AboutBox1.vb:13 — ' TODO: Customize the application's assembly information in the "Application" pane of the project — 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 PS5 BACKPORK KITCHEN/01Frms/StatisticsForm.vb:432 — ' TODO: Implement clear all stats in database — 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.

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: Form1 PS5 BACKPORK KITCHEN/Form1.vb — TooManyMethods — 1300 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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: JsonConfigurationStore PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/JsonConfigurationStore.vb — TooManyMethods — 171 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.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2

Duplicated block (10 lines × 3) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733 — PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733-744 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:855-864 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:882-891 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:127 — PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:127-136 | PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:117-126 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:215-224 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D1 · Cyclomatic Complexity · SelfFile.ExtractElf (cyclomatic 52) · ×1

SelfFile.ExtractElf (cyclomatic 52) PS5 BACKPORK KITCHEN/Services/SelfUtilCode/SelfFile.vb:104 — SelfFile.ExtractElf 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.

D1 · Cyclomatic Complexity · PatchingHistoryRepository.GetStatistics (cyclomatic 35) · ×1

PatchingHistoryRepository.GetStatistics (cyclomatic 35) PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:171 — PatchingHistoryRepository.GetStatistics 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.

D1 · Cyclomatic Complexity · DirectDownloadService.DownloadVikingFileAsync (cyclomatic 33) · ×1

DirectDownloadService.DownloadVikingFileAsync (cyclomatic 33) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:226 — DirectDownloadService.DownloadVikingFileAsync 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.

D1 · Cyclomatic Complexity · TorrentGalaxyProvider.ParseSearchResults (cyclomatic 32) · ×1

TorrentGalaxyProvider.ParseSearchResults (cyclomatic 32) PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:145 — TorrentGalaxyProvider.ParseSearchResults 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.

D1 · Cyclomatic Complexity · FirmwareDownloadModule.DownloadFileWithProgressAsync (cyclomatic 27) · ×1

FirmwareDownloadModule.DownloadFileWithProgressAsync (cyclomatic 27) PS5 BACKPORK KITCHEN/Services/FirmwareDownloadModule.vb:266 — FirmwareDownloadModule.DownloadFileWithProgressAsync 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.

D1 · Cyclomatic Complexity · PackageManagerForm.MnuPreview_Click (cyclomatic 26) · ×1

PackageManagerForm.MnuPreview_Click (cyclomatic 26) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:863 — PackageManagerForm.MnuPreview_Click 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.

D1 · Cyclomatic Complexity · GameLibraryForm.DgvGames_ColumnHeaderMouseClick (cyclomatic 25) · ×1

GameLibraryForm.DgvGames_ColumnHeaderMouseClick (cyclomatic 25) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:618 — GameLibraryForm.DgvGames_ColumnHeaderMouseClick 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.

D1 · Cyclomatic Complexity · RuTrackerProvider.ParseSearchResults (cyclomatic 25) · ×1

RuTrackerProvider.ParseSearchResults (cyclomatic 25) PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:239 — RuTrackerProvider.ParseSearchResults 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.

D1 · Cyclomatic Complexity · PackageManagerForm.BtnValidate_Click (cyclomatic 23) · ×1

PackageManagerForm.BtnValidate_Click (cyclomatic 23) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:551 — PackageManagerForm.BtnValidate_Click 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.

D1 · Cyclomatic Complexity · ElfPatchingService.PatchFileAsync (cyclomatic 23) · ×1

ElfPatchingService.PatchFileAsync (cyclomatic 23) PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb:259 — ElfPatchingService.PatchFileAsync 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.

D1 · Cyclomatic Complexity · PayloadLibrary.GetStatistics (cyclomatic 23) · ×1

PayloadLibrary.GetStatistics (cyclomatic 23) PS5 BACKPORK KITCHEN/Services/PayloadLibrary.vb:322 — PayloadLibrary.GetStatistics 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.

D1 · Cyclomatic Complexity · ThemeManager.ApplyThemeToControls (cyclomatic 23) · ×1

ThemeManager.ApplyThemeToControls (cyclomatic 23) PS5 BACKPORK KITCHEN/Services/ThemeManager.vb:182 — ThemeManager.ApplyThemeToControls 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.

D1 · Cyclomatic Complexity · DirectDownloadService.DownloadAkiraboxAsync (cyclomatic 21) · ×1

DirectDownloadService.DownloadAkiraboxAsync (cyclomatic 21) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:574 — DirectDownloadService.DownloadAkiraboxAsync 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.

D1 · Cyclomatic Complexity · DLPSGameProvider.SearchAsync (cyclomatic 20) · ×1

DLPSGameProvider.SearchAsync (cyclomatic 20) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:87 — DLPSGameProvider.SearchAsync 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.

D1 · Cyclomatic Complexity · RuTrackerProvider.LoginAsync (cyclomatic 20) · ×1

RuTrackerProvider.LoginAsync (cyclomatic 20) PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:85 — RuTrackerProvider.LoginAsync 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.

D1 · Cyclomatic Complexity · ElfInspectorForm.DgvFiles_SelectionChanged (cyclomatic 19) · ×1

ElfInspectorForm.DgvFiles_SelectionChanged (cyclomatic 19) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:460 — ElfInspectorForm.DgvFiles_SelectionChanged 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.

D1 · Cyclomatic Complexity · ElfInspectorForm.MnuPatch_Click (cyclomatic 18) · ×1

ElfInspectorForm.MnuPatch_Click (cyclomatic 18) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:922 — ElfInspectorForm.MnuPatch_Click 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.

D1 · Cyclomatic Complexity · PirateBayProvider.SearchViaApiAsync (cyclomatic 18) · ×1

PirateBayProvider.SearchViaApiAsync (cyclomatic 18) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:125 — PirateBayProvider.SearchViaApiAsync 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.

D1 · Cyclomatic Complexity · PirateBayProvider.ParseHtmlResults (cyclomatic 18) · ×1

PirateBayProvider.ParseHtmlResults (cyclomatic 18) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:248 — PirateBayProvider.ParseHtmlResults 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.

D1 · Cyclomatic Complexity · SigningService.IsSelfFile (cyclomatic 18) · ×1

SigningService.IsSelfFile (cyclomatic 18) PS5 BACKPORK KITCHEN/Services/SigningService.vb:319 — SigningService.IsSelfFile 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.

D1 · Cyclomatic Complexity · DirectDownloadService.StreamResponseToFileAsync (cyclomatic 17) · ×1

DirectDownloadService.StreamResponseToFileAsync (cyclomatic 17) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:845 — DirectDownloadService.StreamResponseToFileAsync 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.

D1 · Cyclomatic Complexity · filedownloads.DownloadLatestRelease (cyclomatic 16) · ×1

filedownloads.DownloadLatestRelease (cyclomatic 16) PS5 BACKPORK KITCHEN/01global/filedownloads.vb:21 — filedownloads.DownloadLatestRelease 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.

D1 · Cyclomatic Complexity · ElfInspector.ReadInfo (cyclomatic 16) · ×1

ElfInspector.ReadInfo (cyclomatic 16) PS5 BACKPORK KITCHEN/core/Models/ElfInfo.vb:19 — ElfInspector.ReadInfo 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.

D1 · Cyclomatic Complexity · PKGMetadata.Load (cyclomatic 16) · ×1

PKGMetadata.Load (cyclomatic 16) PS5 BACKPORK KITCHEN/core/PKG/PKGMetadata.vb:39 — PKGMetadata.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.

D1 · Cyclomatic Complexity · DownloadProgressForm.DownloadProgressForm_Shown (cyclomatic 16) · ×1

DownloadProgressForm.DownloadProgressForm_Shown (cyclomatic 16) PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:141 — DownloadProgressForm.DownloadProgressForm_Shown 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.

D1 · Cyclomatic Complexity · GameSearchForm.DownloadFile_Click (cyclomatic 16) · ×1

GameSearchForm.DownloadFile_Click (cyclomatic 16) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:704 — GameSearchForm.DownloadFile_Click 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.

D1 · Cyclomatic Complexity · DirectDownloadService.Download1FichierAsync (cyclomatic 16) · ×1

DirectDownloadService.Download1FichierAsync (cyclomatic 16) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:390 — DirectDownloadService.Download1FichierAsync 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.

D1 · Cyclomatic Complexity · DLPSGameProvider.ParseListingPage (cyclomatic 16) · ×1

DLPSGameProvider.ParseListingPage (cyclomatic 16) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:174 — DLPSGameProvider.ParseListingPage 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.

D1 · Cyclomatic Complexity · LeetxProvider.ParseSearchResults (cyclomatic 16) · ×1

LeetxProvider.ParseSearchResults (cyclomatic 16) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:157 — LeetxProvider.ParseSearchResults 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.

D1 · Cyclomatic Complexity · OperationReport.GenerateReport (cyclomatic 16) · ×1

OperationReport.GenerateReport (cyclomatic 16) PS5 BACKPORK KITCHEN/Services/OperationReport.vb:31 — OperationReport.GenerateReport 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.

D1 · Cyclomatic Complexity · RemotePkgInstallService.HandleRequest (cyclomatic 16) · ×1

RemotePkgInstallService.HandleRequest (cyclomatic 16) PS5 BACKPORK KITCHEN/Services/RemotePkgInstallService.vb:161 — RemotePkgInstallService.HandleRequest 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.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb:259 — PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in ElfPatchingService.PatchFileAsync at line 259. 3 of those changes were fix/bug commits, and the other 3 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-01-25..2026-04-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-01-25 11:28:46 +05:30' --until='2026-04-25 11:28:46 +05:30' --full-history --no-merges -- PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.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.

D2 · Cognitive Complexity · SelfFile.ExtractElf (cognitive 92) · ×1

SelfFile.ExtractElf (cognitive 92) PS5 BACKPORK KITCHEN/Services/SelfUtilCode/SelfFile.vb:104 — SelfFile.ExtractElf has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · DirectDownloadService.DownloadVikingFileAsync (cognitive 64) · ×1

DirectDownloadService.DownloadVikingFileAsync (cognitive 64) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:226 — DirectDownloadService.DownloadVikingFileAsync 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.

D2 · Cognitive Complexity · TorrentGalaxyProvider.ParseSearchResults (cognitive 62) · ×1

TorrentGalaxyProvider.ParseSearchResults (cognitive 62) PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:145 — TorrentGalaxyProvider.ParseSearchResults 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.

D2 · Cognitive Complexity · RuTrackerProvider.ParseSearchResults (cognitive 47) · ×1

RuTrackerProvider.ParseSearchResults (cognitive 47) PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:239 — RuTrackerProvider.ParseSearchResults has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.

D2 · Cognitive Complexity · PatchingHistoryRepository.GetStatistics (cognitive 43) · ×1

PatchingHistoryRepository.GetStatistics (cognitive 43) PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Repositories/PatchingHistoryRepository.vb:171 — PatchingHistoryRepository.GetStatistics 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.

D2 · Cognitive Complexity · PackageManagerForm.MnuPreview_Click (cognitive 40) · ×1

PackageManagerForm.MnuPreview_Click (cognitive 40) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:863 — PackageManagerForm.MnuPreview_Click 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.

D2 · Cognitive Complexity · PackageManagerForm.BtnValidate_Click (cognitive 39) · ×1

PackageManagerForm.BtnValidate_Click (cognitive 39) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:551 — PackageManagerForm.BtnValidate_Click 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.

D2 · Cognitive Complexity · GameLibraryForm.DgvGames_ColumnHeaderMouseClick (cognitive 37) · ×1

GameLibraryForm.DgvGames_ColumnHeaderMouseClick (cognitive 37) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:618 — GameLibraryForm.DgvGames_ColumnHeaderMouseClick 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.

D2 · Cognitive Complexity · ElfInspectorForm.MnuFullPipeline_Click (cognitive 36) · ×1

ElfInspectorForm.MnuFullPipeline_Click (cognitive 36) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:1214 — ElfInspectorForm.MnuFullPipeline_Click 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.

D2 · Cognitive Complexity · FirmwareDownloadModule.DownloadFileWithProgressAsync (cognitive 35) · ×1

FirmwareDownloadModule.DownloadFileWithProgressAsync (cognitive 35) PS5 BACKPORK KITCHEN/Services/FirmwareDownloadModule.vb:266 — FirmwareDownloadModule.DownloadFileWithProgressAsync 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.

D2 · Cognitive Complexity · PirateBayProvider.ParseHtmlResults (cognitive 34) · ×1

PirateBayProvider.ParseHtmlResults (cognitive 34) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:248 — PirateBayProvider.ParseHtmlResults 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.

D2 · Cognitive Complexity · ElfInspectorForm.MnuPatch_Click (cognitive 33) · ×1

ElfInspectorForm.MnuPatch_Click (cognitive 33) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:922 — ElfInspectorForm.MnuPatch_Click 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.

D2 · Cognitive Complexity · ThemeManager.ApplyThemeToControls (cognitive 31) · ×1

ThemeManager.ApplyThemeToControls (cognitive 31) PS5 BACKPORK KITCHEN/Services/ThemeManager.vb:182 — ThemeManager.ApplyThemeToControls 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.

D2 · Cognitive Complexity · DirectDownloadService.DownloadAkiraboxAsync (cognitive 29) · ×1

DirectDownloadService.DownloadAkiraboxAsync (cognitive 29) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:574 — DirectDownloadService.DownloadAkiraboxAsync 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.

D2 · Cognitive Complexity · ElfInspectorForm.MnuDecrypt_Click (cognitive 28) · ×1

ElfInspectorForm.MnuDecrypt_Click (cognitive 28) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:682 — ElfInspectorForm.MnuDecrypt_Click 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. This shape REPEATS in the file: one other method here (ElfInspectorForm.MnuSign_Click) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · ElfInspectorForm.MnuSign_Click (cognitive 28) · ×1

ElfInspectorForm.MnuSign_Click (cognitive 28) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:1117 — ElfInspectorForm.MnuSign_Click 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. This shape REPEATS in the file: one other method here (ElfInspectorForm.MnuDecrypt_Click) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · ElfInspectorForm.DgvFiles_SelectionChanged (cognitive 27) · ×1

ElfInspectorForm.DgvFiles_SelectionChanged (cognitive 27) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:460 — ElfInspectorForm.DgvFiles_SelectionChanged 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.

D2 · Cognitive Complexity · PirateBayProvider.SearchViaApiAsync (cognitive 26) · ×1

PirateBayProvider.SearchViaApiAsync (cognitive 26) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:125 — PirateBayProvider.SearchViaApiAsync 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.

D2 · Cognitive Complexity · GameLibraryForm.LoadCoverArtAsync (cognitive 25) · ×1

GameLibraryForm.LoadCoverArtAsync (cognitive 25) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:359 — GameLibraryForm.LoadCoverArtAsync 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.

D2 · Cognitive Complexity · LeetxProvider.ParseSearchResults (cognitive 25) · ×1

LeetxProvider.ParseSearchResults (cognitive 25) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:157 — LeetxProvider.ParseSearchResults 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.

D2 · Cognitive Complexity · DirectDownloadService.StreamResponseToFileAsync (cognitive 24) · ×1

DirectDownloadService.StreamResponseToFileAsync (cognitive 24) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:845 — DirectDownloadService.StreamResponseToFileAsync 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.

D2 · Cognitive Complexity · PayloadLibrary.GetStatistics (cognitive 24) · ×1

PayloadLibrary.GetStatistics (cognitive 24) PS5 BACKPORK KITCHEN/Services/PayloadLibrary.vb:322 — PayloadLibrary.GetStatistics 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.

D2 · Cognitive Complexity · PKGMetadata.Load (cognitive 23) · ×1

PKGMetadata.Load (cognitive 23) PS5 BACKPORK KITCHEN/core/PKG/PKGMetadata.vb:39 — PKGMetadata.Load 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.

D2 · Cognitive Complexity · DLPSGameProvider.FetchGamePageAsync (cognitive 23) · ×1

DLPSGameProvider.FetchGamePageAsync (cognitive 23) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:238 — DLPSGameProvider.FetchGamePageAsync 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.

D2 · Cognitive Complexity · ElfPatchingService.PatchFileAsync (cognitive 22) · ×1

ElfPatchingService.PatchFileAsync (cognitive 22) PS5 BACKPORK KITCHEN/Architecture/Application/Services/ElfPatchingService.vb:259 — ElfPatchingService.PatchFileAsync 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.

D2 · Cognitive Complexity · ElfInspectorService.ExtractLibraryDependencies (cognitive 22) · ×1

ElfInspectorService.ExtractLibraryDependencies (cognitive 22) PS5 BACKPORK KITCHEN/Services/ElfInspector.vb:131 — ElfInspectorService.ExtractLibraryDependencies 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.

D2 · Cognitive Complexity · SdkDetector.AnalyzeFolderSdkVersions (cognitive 22) · ×1

SdkDetector.AnalyzeFolderSdkVersions (cognitive 22) PS5 BACKPORK KITCHEN/Services/SdkDetector.vb:62 — SdkDetector.AnalyzeFolderSdkVersions 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.

D2 · Cognitive Complexity · DLPSGameProvider.SearchAsync (cognitive 21) · ×1

DLPSGameProvider.SearchAsync (cognitive 21) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:87 — DLPSGameProvider.SearchAsync 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.

D2 · Cognitive Complexity · RemotePkgInstallService.HandleRequest (cognitive 21) · ×1

RemotePkgInstallService.HandleRequest (cognitive 21) PS5 BACKPORK KITCHEN/Services/RemotePkgInstallService.vb:161 — RemotePkgInstallService.HandleRequest 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.

D2 · Cognitive Complexity · ElfInspectorForm.MnuDowngrade_Click (cognitive 20) · ×1

ElfInspectorForm.MnuDowngrade_Click (cognitive 20) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:796 — ElfInspectorForm.MnuDowngrade_Click 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.

D2 · Cognitive Complexity · HexViewerForm.RenderHex (cognitive 20) · ×1

HexViewerForm.RenderHex (cognitive 20) PS5 BACKPORK KITCHEN/01Frms/HexViewerForm.vb:115 — HexViewerForm.RenderHex 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.

D2 · Cognitive Complexity · PayloadManagerForm.BtnBatchSend_Click (cognitive 20) · ×1

PayloadManagerForm.BtnBatchSend_Click (cognitive 20) PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb:895 — PayloadManagerForm.BtnBatchSend_Click 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.

D2 · Cognitive Complexity · commonfunctions.PatchPrxString (cognitive 20) · ×1

commonfunctions.PatchPrxString (cognitive 20) PS5 BACKPORK KITCHEN/01global/commonfunctions.vb:490 — commonfunctions.PatchPrxString 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.

D2 · Cognitive Complexity · filedownloads.DownloadLatestRelease (cognitive 20) · ×1

filedownloads.DownloadLatestRelease (cognitive 20) PS5 BACKPORK KITCHEN/01global/filedownloads.vb:21 — filedownloads.DownloadLatestRelease 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.

D2 · Cognitive Complexity · BackupServiceAdapter.ListBackupsAsync (cognitive 20) · ×1

BackupServiceAdapter.ListBackupsAsync (cognitive 20) PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/BackupServiceAdapter.vb:74 — BackupServiceAdapter.ListBackupsAsync 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.

D2 · Cognitive Complexity · flibs.DownloadAllArchivesAsync (cognitive 20) · ×1

flibs.DownloadAllArchivesAsync (cognitive 20) PS5 BACKPORK KITCHEN/Downloadslibs/flibs.vb:191 — flibs.DownloadAllArchivesAsync 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.

D2 · Cognitive Complexity · DecryptSignService.ExecuteDecryptSignWorkflow (cognitive 20) · ×1

DecryptSignService.ExecuteDecryptSignWorkflow (cognitive 20) PS5 BACKPORK KITCHEN/Services/DecryptSignService.vb:57 — DecryptSignService.ExecuteDecryptSignWorkflow 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.

D2 · Cognitive Complexity · RuTrackerProvider.LoginAsync (cognitive 20) · ×1

RuTrackerProvider.LoginAsync (cognitive 20) PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:85 — RuTrackerProvider.LoginAsync 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.

D2 · Cognitive Complexity · FtpConnectionForm.BtnConnect_Click (cognitive 19) · ×1

FtpConnectionForm.BtnConnect_Click (cognitive 19) PS5 BACKPORK KITCHEN/01Frms/FtpConnectionForm.vb:456 — FtpConnectionForm.BtnConnect_Click 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.

D2 · Cognitive Complexity · PatchingCoordinator.ExecutePatchingAsync (cognitive 19) · ×1

PatchingCoordinator.ExecutePatchingAsync (cognitive 19) PS5 BACKPORK KITCHEN/Architecture/Application/Coordinators/PatchingCoordinator.vb:30 — PatchingCoordinator.ExecutePatchingAsync 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.

D2 · Cognitive Complexity · JsonConfigurationStore.LoadConfig (cognitive 19) · ×1

JsonConfigurationStore.LoadConfig (cognitive 19) PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/JsonConfigurationStore.vb:21 — JsonConfigurationStore.LoadConfig 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.

D2 · Cognitive Complexity · ElfInspector.ReadInfo (cognitive 19) · ×1

ElfInspector.ReadInfo (cognitive 19) PS5 BACKPORK KITCHEN/core/Models/ElfInfo.vb:19 — ElfInspector.ReadInfo 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.

D2 · Cognitive Complexity · DownloadProgressForm.DownloadProgressForm_Shown (cognitive 19) · ×1

DownloadProgressForm.DownloadProgressForm_Shown (cognitive 19) PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:141 — DownloadProgressForm.DownloadProgressForm_Shown 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.

D2 · Cognitive Complexity · PirateBayProvider.SearchViaScrapingAsync (cognitive 19) · ×1

PirateBayProvider.SearchViaScrapingAsync (cognitive 19) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:207 — PirateBayProvider.SearchViaScrapingAsync 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.

D2 · Cognitive Complexity · GameSearchForm.DownloadFile_Click (cognitive 18) · ×1

GameSearchForm.DownloadFile_Click (cognitive 18) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:704 — GameSearchForm.DownloadFile_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.

D2 · Cognitive Complexity · FirmwareExtractorModule.DownloadToolAsync (cognitive 18) · ×1

FirmwareExtractorModule.DownloadToolAsync (cognitive 18) PS5 BACKPORK KITCHEN/Services/FirmwareExtractorModule.vb:82 — FirmwareExtractorModule.DownloadToolAsync 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.

D2 · Cognitive Complexity · FirmwareExtractorModule.ExtractFirmwareAsync (cognitive 18) · ×1

FirmwareExtractorModule.ExtractFirmwareAsync (cognitive 18) PS5 BACKPORK KITCHEN/Services/FirmwareExtractorModule.vb:159 — FirmwareExtractorModule.ExtractFirmwareAsync 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.

D2 · Cognitive Complexity · DirectDownloadService.Download1FichierAsync (cognitive 18) · ×1

DirectDownloadService.Download1FichierAsync (cognitive 18) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:390 — DirectDownloadService.Download1FichierAsync 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.

D2 · Cognitive Complexity · DirectDownloadService.Try1FichierPost (cognitive 18) · ×1

DirectDownloadService.Try1FichierPost (cognitive 18) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:502 — DirectDownloadService.Try1FichierPost 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.

D2 · Cognitive Complexity · OperationReport.GenerateReport (cognitive 18) · ×1

OperationReport.GenerateReport (cognitive 18) PS5 BACKPORK KITCHEN/Services/OperationReport.vb:31 — OperationReport.GenerateReport 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.

D2 · Cognitive Complexity · FirmwareManagerForm.LoadArchiveData (cognitive 17) · ×1

FirmwareManagerForm.LoadArchiveData (cognitive 17) PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:546 — FirmwareManagerForm.LoadArchiveData 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.

D2 · Cognitive Complexity · PackageManagerForm.ExtractSelectedEntries (cognitive 17) · ×1

PackageManagerForm.ExtractSelectedEntries (cognitive 17) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:805 — PackageManagerForm.ExtractSelectedEntries 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.

D2 · Cognitive Complexity · PayloadManagerForm.BtnSend_Click (cognitive 17) · ×1

PayloadManagerForm.BtnSend_Click (cognitive 17) PS5 BACKPORK KITCHEN/01Frms/PayloadManagerForm.vb:736 — PayloadManagerForm.BtnSend_Click 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.

D2 · Cognitive Complexity · PKGEntryTable.ResolveFilenames (cognitive 17) · ×1

PKGEntryTable.ResolveFilenames (cognitive 17) PS5 BACKPORK KITCHEN/core/PKG/PKGEntryTable.vb:100 — PKGEntryTable.ResolveFilenames 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.

D2 · Cognitive Complexity · ElfInspectorForm.AnalyzeFolder (cognitive 16) · ×1

ElfInspectorForm.AnalyzeFolder (cognitive 16) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:361 — ElfInspectorForm.AnalyzeFolder 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.

D2 · Cognitive Complexity · FirmwareManagerForm.LoadFirmwareData (cognitive 16) · ×1

FirmwareManagerForm.LoadFirmwareData (cognitive 16) PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:465 — FirmwareManagerForm.LoadFirmwareData 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.

D2 · Cognitive Complexity · SFOViewerForm.FormatHexDump (cognitive 16) · ×1

SFOViewerForm.FormatHexDump (cognitive 16) PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:200 — SFOViewerForm.FormatHexDump 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.

D2 · Cognitive Complexity · UFS2ImageForm.FormatHexDump (cognitive 16) · ×1

UFS2ImageForm.FormatHexDump (cognitive 16) PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:705 — UFS2ImageForm.FormatHexDump 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.

D2 · Cognitive Complexity · DownloadAutoFailoverForm.UpdateProgress (cognitive 16) · ×1

DownloadAutoFailoverForm.UpdateProgress (cognitive 16) PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:256 — DownloadAutoFailoverForm.UpdateProgress 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.

D2 · Cognitive Complexity · DirectDownloadService.DownloadRootzAsync (cognitive 16) · ×1

DirectDownloadService.DownloadRootzAsync (cognitive 16) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:726 — DirectDownloadService.DownloadRootzAsync 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.

D2 · Cognitive Complexity · DLPSGameProvider.ParseListingPage (cognitive 16) · ×1

DLPSGameProvider.ParseListingPage (cognitive 16) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:174 — DLPSGameProvider.ParseListingPage 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 (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) PS5 BACKPORK KITCHEN/Services/BackupService.vb:21 — PS5 BACKPORK KITCHEN/Services/BackupService.vb:21-94 | PS5 BACKPORK KITCHEN/Services/InputValidator.vb:115-132 | PS5 BACKPORK KITCHEN/Services/IntegrityVerifier.vb:19-58 | PS5 BACKPORK KITCHEN/Services/IntegrityVerifier.vb:121-142 — 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 · Duplicated block (51–53 lines × 2) · ×1

Duplicated block (51–53 lines × 2) PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:80 — PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:80-130 | PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:71-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (34–39 lines × 2) · ×1

Duplicated block (34–39 lines × 2) PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:257 — PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:257-290 | PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:194-232 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:233` calls `CInt` and `PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:291` 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 · Duplicated block (30 lines × 2) · ×1

Duplicated block (30 lines × 2) PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:202 — PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:202-231 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:707-736 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1

Duplicated block (27 lines × 2) PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb:265 — PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb:265-291 | PS5 BACKPORK KITCHEN/01Frms/OperationModeForm.vb:277-303 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1

Duplicated block (26 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:107 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:107-132 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:205-230 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1

Duplicated block (23–24 lines × 2) PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:953 — PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:953-976 | PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:1068-1090 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (18–23 lines × 3) · ×1

Duplicated block (18–23 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:261 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:261-283 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:350-367 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:287-304 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:259` calls `Replace`, `Trim` and `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:349` 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 · Duplicated block (22 lines × 2) · ×1

Duplicated block (22 lines × 2) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:63 — PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:63-84 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:52-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (19–21 lines × 2) · ×1

Duplicated block (19–21 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:82 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:82-102 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:77-95 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1

Duplicated block (20 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:181 — PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:181-200 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:259-278 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 84 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1

Duplicated block (17 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:238 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:238-254 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:340-356 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:266-282 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (16–18 lines × 2) · ×1

Duplicated block (16–18 lines × 2) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:59 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:59-76 | PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:111-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:59` 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.

D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1

Duplicated block (15 lines × 4) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:124 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:124-138 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:108-122 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:222-236 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:112-126 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1

Duplicated block (13–16 lines × 2) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733 — PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733-748 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:855-867 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1

Duplicated block (13 lines × 4) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:238 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:238-250 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:188-200 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:340-352 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:266-278 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1

Duplicated block (15 lines × 2) PS5 BACKPORK KITCHEN/Services/BackupService.vb:122 — PS5 BACKPORK KITCHEN/Services/BackupService.vb:122-136 | PS5 BACKPORK KITCHEN/Services/BackupService.vb:147-161 — 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 `PS5 BACKPORK KITCHEN/Services/BackupService.vb:122` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `PS5 BACKPORK KITCHEN/Services/BackupService.vb:120` calls `GetFileName` and `PS5 BACKPORK KITCHEN/Services/BackupService.vb:146` 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.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) PS5 BACKPORK KITCHEN/Downloadslibs/flibs.vb:151 — PS5 BACKPORK KITCHEN/Downloadslibs/flibs.vb:151-161 | PS5 BACKPORK KITCHEN/Downloadslibs/flibs.vb:351-361 — 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 `PS5 BACKPORK KITCHEN/Downloadslibs/flibs.vb:151` 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.

D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1

Duplicated block (12–14 lines × 2) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:705 — PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:705-718 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:830-841 — 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 `PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:705` 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.

D4 · Code Duplication · Duplicated block (11–13 lines × 3) · ×1

Duplicated block (11–13 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:110 — PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:110-122 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:208-220 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:102-112 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:123` calls `OrderByDescending`, `Function`, `ToList` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:113` 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 · Duplicated block (12–13 lines × 2) · ×1

Duplicated block (12–13 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:369 — PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:369-380 | PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:483-495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1

Duplicated block (12 lines × 4) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:63 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:63-76 | PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:115-126 | PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:73-84 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:62-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:63` 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, `PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:86` calls `ToolStripLabel` and `PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:128` 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 · Duplicated block (9–11 lines × 3) · ×1

Duplicated block (9–11 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:314 — PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:314-322 | PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:400-409 | PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:507-517 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1

Duplicated block (5 lines × 5) PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:148 — PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:148-152 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:200-204 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:219-223 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:238-242 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:257-261 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1

Duplicated block (7 lines × 3) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:594 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:594-608 | PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:739-745 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:748-754 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1

Duplicated block (6 lines × 2) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:832 — PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:832-837 | PS5 BACKPORK KITCHEN/core/PKG/PKGReader.vb:135-144 — 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.

D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1

Duplicated block (5 lines × 4) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:683 — PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:683-687 | PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:797-801 | PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:923-927 | PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:1118-1122 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×1

Duplicated block (7 lines × 2) PS5 BACKPORK KITCHEN/01Frms/OperationModeForm.vb:874 — PS5 BACKPORK KITCHEN/01Frms/OperationModeForm.vb:874-880 | PS5 BACKPORK KITCHEN/Services/DecryptSignService.vb:282-288 — 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.

D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1

Duplicated block (9 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:34 — PS5 BACKPORK KITCHEN/Services/GameSearch/DLPSGameProvider.vb:34-44 | PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:28-36 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:25-33 — before extracting anything, compare `PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb` and `PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 137 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

M1 · Documentation (README) · Repository declared end-of-life · ×1

Repository declared end-of-life README.md:2 — This repository declares its own end of life: `README.md` line 2 reads “# ⚠️ Project Discontinued”. That is a first-party statement of intent, not an inference — the Maturity and Knowledge lenses otherwise approximate the same fact from decayed commit history (D16 reports a dormant codebase, D34 orphaned files), and this row says the maintainer already told you. It does NOT change any score: an honest end-of-life notice is the README doing its job, and every dimension below still measures the code as it stands. Read the whole report as an assessment of software the author has stopped working on.

P1 · CI/CD gates · No CI pipeline · ×1

No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

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.

Minor — 8 finding(s)

AX6 · Interface segregation · Fat interface · ×1

Fat interface: IConfigurationStore (36 members) PS5 BACKPORK KITCHEN/Architecture/Infrastructure/Adapters/IConfigurationStore.vb:5 — `IConfigurationStore` declares 36 members: `GetDefaultPs5SdkAsync`, `SetDefaultPs5SdkAsync`, `GetDefaultPs4SdkAsync`, `SetDefaultPs4SdkAsync`, `GetAutoBackupAsync`, `SetAutoBackupAsync`, `GetAutoVerifyAsync`, `SetAutoVerifyAsync`, `GetEnableFileLoggingAsync`, `SetEnableFileLoggingAsync`, `GetLogLevelAsync`, `SetLogLevelAsync`, `GetThemeAsync`, `SetThemeAsync`, `GetLastUsedFolderAsync`, `SetLastUsedFolderAsync`, `GetCheckForUpdatesOnStartupAsync`, `SetCheckForUpdatesOnStartupAsync`, `GetLastUpdateCheckAsync`, `SetLastUpdateCheckAsync`, `GetSkippedUpdateVersionAsync`, `SetSkippedUpdateVersionAsync`, `GetExportReportsAutomaticallyAsync`, `SetExportReportsAutomaticallyAsync`, `GetReportOutputDirectoryAsync`, `SetReportOutputDirectoryAsync`, `GetLanguageAsync`, `SetLanguageAsync`, `GetMaxConcurrentOperationsAsync`, `SetMaxConcurrentOperationsAsync`, `GetTempFolderCleanupOnExitAsync`, `SetTempFolderCleanupOnExitAsync`, `GetConfigurationAsync`, `SetConfigurationAsync`, `SaveAsync`, `ReloadAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.

D18 · Solution Shape · Single-project monolith · ×1

Single-project monolith — The whole codebase lives in one project — at this size, splitting along clear seams (domain / infrastructure / hosting) would make boundaries explicit and builds faster.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `PS5 BACKPORK KITCHEN` (36468 LoC, 283 public types across 13 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.

D9 · Test Distribution · No tests found · ×1

No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.

M2 · Architecture documentation · No ADRs · ×1

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

M3 · Folder & project structure · No src/ separation · ×1

No src/ separation — Production code isn't grouped under a src/ folder — it all sits under PS5 BACKPORK KITCHEN/ alongside the root build files, so the conventional src/ boundary between the product and its tooling isn't drawn.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.

Minor — 3 finding(s)

D12 · Dependency Hygiene · Outdated · ×3

Outdated: FluentFTP — FluentFTP 53.0.2 → 55.1.0 available (referenced by PS5 BACKPORK KITCHEN).
Outdated: ReaLTaiizor — ReaLTaiizor 3.8.1.5 → 3.8.2.1 available (referenced by PS5 BACKPORK KITCHEN).
Outdated: SharpCompress — SharpCompress 0.44.5 → 0.50.7 available (referenced by PS5 BACKPORK KITCHEN).

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.

Dimension	Tool	Version	Command	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ed832a5aa35448bdb0d3610ca4ce0e97/history.json --exit-code 0 --source .	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ed832a5aa35448bdb0d3610ca4ce0e97/tree.json --exit-code 0 --source .	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	nuget	—	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	—
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.	—
D37 · Vulnerability-disclosure Policy	disclosure	—	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.	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	—
D43 · Malicious Dependencies	none (no readable dependency manifest)	—	none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).	—

Run 01a160d4-99fa-7cbb-acda-d6435cb9d2ef · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture: which parts of the code depend on which

At a glance — Code Health · 55% · Adequate ·

At a glance — Architecture · 92% · Adequate · gated by D26 ·

At a glance — Maturity · 51% · Adequate · gated by M2 ·

At a glance — Readiness · 21% · Critical · gated by D8, D9, D13, P1, P3 ·

At a glance — Security · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts