Public report — PS5-BACKPORK-KITCHEN, published 3 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
259findings with an exact file:lineof 271 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
31/94dimensions across the health lenses36468 LoC · 1 projects — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
rajeshca911/PS5-BACKPORK-KITCHEN carries serious gaps (46%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Security (100%) — its security and compliance posture is in good shape. Architecture (91%) is solid too.
The area that most needs attention is Readiness (24%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Code Health (56%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Document RTO/RPO and a tested restore procedure (a backup… (DR & Backup); 1 No automated tests finding(s) in Code Coverage (Code Coverage).
For scale: Medium (~36,468 production lines); rebuilding it from scratch would take roughly ~0.3 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Security foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
0.7× (at 46% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.3 person-years of build effort (about ~€41,000 to rebuild). Its weakest lens is Readiness at 24% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.3) — desktop/game, DDD/clean architecture × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 No automated tests finding(s) in Code Coverage.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.3 person-years to rebuild), and its weakest lens is Readiness at 24%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
Architecture — module dependency matrix
16 modules, 26 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
First, establish a continuous integration workflow to automatically build and test every code change. Next, document and test a disaster recovery plan that goes beyond simple backups. Then, address the single gaps in automated testing and dependency security to improve code coverage and reduce vulnerabilities.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No automated tests finding(s) in Code Coverage.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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. 28 of 31 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — 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 — 31 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 259 of 271 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
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 (jscpd) — 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").
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.
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.
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 (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 SelfFile.ExtractElf (cyclomatic 52) finding(s) in Cyclomatic Complexity — start with SelfFile.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PatchingHistoryRepository.GetStatistics (cyclomatic 35) finding(s) in Cyclomatic Complexity — start with PatchingHistoryRepository.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DirectDownloadService.DownloadVikingFileAsync (cyclomatic 33) finding(s) in Cyclomatic Complexity — start with DirectDownloadService.vb. — One of this dimension's main actionable groups (1 warning-level).
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.
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.
+ 56 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 SelfFile.ExtractElf (cognitive 92) finding(s) in Cognitive Complexity — start with SelfFile.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DirectDownloadService.DownloadVikingFileAsync (cognitive 64) finding(s) in Cognitive Complexity — start with DirectDownloadService.vb. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TorrentGalaxyProvider.ParseSearchResults (cognitive 62) finding(s) in Cognitive Complexity — start with TorrentGalaxyProvider.vb. — One of this dimension's main actionable groups (1 warning-level).
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 Classes7.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 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).
Resolve the 2 TooManyMethods finding(s) in God Classes — start with Form1.vb, JsonConfigurationStore.vb. — One of this dimension's main actionable groups (2 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.
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.
+ 11 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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.
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.
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.
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
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.
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.
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.
The single README is a solid one-page project disclaimer plus an unpolished one-paragraph description of the tool and its features. It states the project is no longer actively maintained and lists six features with requirements, a step-by-step How To Use guide, and a Roadmap outline; however it contains only one visible document body (the single README) and no architecture or design documentation, so most of the intended structure and depth is absent.
Improve Documentation Quality — currently 4.0/10. — The single README is a solid one-page project disclaimer plus an unpolished one-paragraph description of the tool and its features. It states the project is no longer actively maintained and lists six features with requirements, a step-by-step How To Use guide, and a Roadmap outline; however it contains only one visible document body (the single README) and no architecture or design documentation, so most of the intended structure and depth is absent.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
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; coupling through a build step, config, or non-source file isn't seen.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
`IConfigurationStore` declares 36 members. 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. — IConfigurationStore.vb:5
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — 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.
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 `NNNN-title.md` documents 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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.
No test surface was found — there are no tests here to separate from production code, so the folder question hasn't been reached yet.
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.
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.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package (or `semgrep --config=auto`, which runs on any language) — 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 to do
Run what this repository's stack ships: CodeQL's csharp pack (it analyses VB.NET too), or a security analyzer package — or `semgrep --config=auto`, which runs on any language — — 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).
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?
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.
Not included — 63 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
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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.
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.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — Test reliability not included
D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
D16 Bus Factor — early-stage repository — too few commits for a meaningful bus factor
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — At only 36468 LoC in a single project the codebase is trivially small despite the absence of declared bounded contexts.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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 for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D34 Knowledge Freshness — early-stage repository — too little history to judge knowledge freshness
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); 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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — The target did not build, so no IL was available to measure.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no MSBuild project graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this check looks for (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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 check 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
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, 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
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) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — 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.
PF2 Allocation 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.
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
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
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
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock 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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
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`.
ClassTooLong: ElfInspectorForm PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:0— ClassTooLong — 1053 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. 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:0— ClassTooLong — 969 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. 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:0— ClassTooLong — 744 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. 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:0— ClassTooLong — 702 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. 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:0— ClassTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. 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:0— ClassTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. 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:0— ClassTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. 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:0— ClassTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. 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:0— ClassTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. 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:0— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. 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:0— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. 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:0— ClassTooLong — 445 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. 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:0— ClassTooLong — 423 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. 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:0— ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. 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:0— ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. 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.
FileTooLong: PS5 BACKPORK KITCHEN/Form1.vb PS5 BACKPORK KITCHEN/Form1.vb:0— FileTooLong — 1307 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 1056 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 974 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded). 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:0— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). 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.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:458— PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:458-467 | PS5 BACKPORK KITCHEN/01Frms/GameLibraryForm.vb:480-489 — 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/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: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733— PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:733-744 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:882-891 — 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 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:105— PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:105-114 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:109-118 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:956— PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:956-968 | PS5 BACKPORK KITCHEN/01Frms/FirmwareManagerForm.vb:1070-1082 — 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/01Frms/FirmwareManagerForm.vb:956` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:211— PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:211-223 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:716-728 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
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/Forms/DownloadAutoFailoverForm.vb:257— PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:257-269 | PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:194-208 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (16 lines × 2) PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb:276— PS5 BACKPORK KITCHEN/01Frms/CustomLibraryForm.vb:276-293 | PS5 BACKPORK KITCHEN/01Frms/OperationModeForm.vb:290-305 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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 (16 lines × 2) PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:63— PS5 BACKPORK KITCHEN/01Frms/PackageManagerForm.vb:63-78 | PS5 BACKPORK KITCHEN/01Frms/UFS2ImageForm.vb:52-67 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (16 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:85— PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:85-101 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:79-94 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (15 lines × 2) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:60— PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:60-76 | PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:112-126 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (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.
Duplicated block (15 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:105— PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:105-119 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:203-217 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
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.
TooManyMethods: Form1 PS5 BACKPORK KITCHEN/Form1.vb:0— TooManyMethods — 1300 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. 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:0— TooManyMethods — 171 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (12 lines × 2) PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:110— PS5 BACKPORK KITCHEN/01Frms/FPKGBuilderForm.vb:110-121 | PS5 BACKPORK KITCHEN/01Frms/SFOViewerForm.vb:46-57 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:317— PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:317-328 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:256-267 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
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: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:127— PS5 BACKPORK KITCHEN/Services/GameSearch/GameSearchManager.vb:127-133 | PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:117-123 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:215-221 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Duplicated block (49 lines × 2) PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:81— PS5 BACKPORK KITCHEN/Forms/DownloadAutoFailoverForm.vb:81-129 | PS5 BACKPORK KITCHEN/Forms/DownloadProgressForm.vb:72-122 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (15 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:237— PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:237-251 | PS5 BACKPORK KITCHEN/Services/GameSearch/RuTrackerProvider.vb:339-353 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:265-279 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 3) PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:266— PS5 BACKPORK KITCHEN/Services/GameSearch/LeetxProvider.vb:266-283 | PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:355-367 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:292-304 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:369— PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:369-379 | PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:483-494 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 5) PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:145— PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:145-153 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:197-205 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:216-224 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:235-243 | PS5 BACKPORK KITCHEN/Services/KeyboardShortcutManager.vb:254-262 — 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.
Duplicated block (9 lines × 2) PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:709— PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:709-718 | PS5 BACKPORK KITCHEN/Forms/GameSearchForm.vb:833-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:709` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:661— PS5 BACKPORK KITCHEN/01Frms/ElfInspectorForm.vb:661-668 | PS5 BACKPORK KITCHEN/Services/FirmwareManagerService.vb:463-470 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:314— PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:314-320 | PS5 BACKPORK KITCHEN/Services/GameSearch/DirectDownloadService.vb:400-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:349— PS5 BACKPORK KITCHEN/Services/GameSearch/PirateBayProvider.vb:349-354 | PS5 BACKPORK KITCHEN/Services/GameSearch/TorrentGalaxyProvider.vb:286-291 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
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.
Recommendation — 6 finding(s)
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — No test suite was found, so reliability couldn't be assessed.
early-stage repository — too few commits for a meaningful bus factor — early-stage repository — too few commits for a meaningful bus factor (3 author(s) across 37 commit(s) sampled).
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.
Split PS5 BACKPORK KITCHEN — A huge 36k-LoC project that is spread over 13 unrelated namespaces despite its size. Suggested: by namespace: BackporkKitchenergies, BackporkBeverages, BackporkFoods
early-stage repository — too little history to judge knowledge freshness — early-stage repository — too little history to judge knowledge freshness (37 commit(s) sampled).
No tests found — No test suite could be collected — nothing here references a test framework (xUnit, NUnit or MSTest), so there were no discoverable tests to count. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
dotnet: not applicable — 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 for NuGet CVEs — excluded rather than scored; re-run on an SDK that can restore this solution
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
semgrep: not applicable — Data compliance (PII/GDPR) was not assessed in this scan — no ruleset is currently available for it. This says nothing about how this repository handles personal data, in either direction.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fc776-5bce-795e-a049-24b32fc4a3f4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 110 · Warnings: 150 · Recommendations: 6 · Info: 5 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 03-08-2026 @ 11:50 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.