Public report of HanFengRuYue/XUnityToolkit-WebUI, published 16 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 16:44 UTC · Survey ID cd_3dd15d90b29f4d0882d6afa6230b5645

HanFengRuYue/XUnityToolkit-WebUI

Measured 16 November 2026, 16:44 UTC, at code version 627ea51

First survey, so nothing to compare with yet Code coverage: not measuredBoundary Type-Coupling: not measured

Code coverage is not measured: Suite not runnable in-image.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 34.9out of 100 At risk

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 55,247 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Security and Compliance, 22.7

Findings by how serious they are

212 critical 814 serious 212 minor

3 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 16:44 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

86of 86 dimensions measured by tools.
1129of 1238 findings point to an exact file and line, so you can open each one in the code. The other 109 concern the repository as a whole, such as missing documentation.
86dimensions across 7 lenses, read from 55,247 lines of product code in 8 projects.
Chapters

Executive summary

HanFengRuYue/XUnityToolkit-WebUI is rated At risk because critical security findings are open. Its score is held back because we found no access checks on the code's endpoints or handlers and it has security weaknesses in the code. It scores 34.9 out of 100, which the At risk rating leaves unchanged.

Security and Compliance, at 22.7, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 9.4 points. Adding the security headers comes next, worth about 6.7 points. Raising Security and Compliance to 70 would lift the score to about 45.5.

Sixteen weaknesses in the code could be used by an attacker. Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eighty-seven errors are caught and ignored, so failures can go unnoticed. Fixing the weaknesses the scanner points to, pinning each tool to an exact version and handling or logging the ignored errors would close these risks. Passing outside input through environment variables would fix the seven pipeline steps that put outside input straight into a shell command, and updating the vulnerable packages would deal with the four packages with a known security hole. The 37 controls that only work with a mouse need to work with the keyboard, or to become a real button.

The product code is 55,247 lines, about €250,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Security and Compliance 22.7 · counts for 46%Production Readiness 37.7 · counts for 25%Code Health 44.3 · counts for 14%Accessibility 45.7 · counts for 8%Maturity 68.2 · counts for 4%Performance 70.0 · counts for 2%Architecture 80.8 · counts for 1%

If Security and Compliance rose from 22.7 to 70, the lowest score rated Strong, the score would rise from 34.9 to about 45.5.

Code composition: what the lines of code are
Business logic 64%Supporting code 26%Tests 9%
Rebuild cost: about €250,000 · Estimate
Cost to rebuild€79,000 to €410,000, for 1,321 to 4,339 hours of work, about 1.7 person-years for 1 to 4 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 35. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 55,247 lines of product code
Comment linesThe estimate prices 53,822 lines. Comment lines count towards the size of 55,247 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 9.4 points · Medium effort · Access Controls
2
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Raises the score by about 6.7 points · Medium effort · Web-Security Posture
3
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RuntimeFontLoader.Il2Cpp.csproj.
Raises the score by about 3.2 points · Low effort · Platform End-of-Life

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €250,000 to build again, about 1.7 person-years of work. Its weakest lens is Security and Compliance, at 22.7 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. Of all the actions in this report, it raises the score most for the work it takes: about 9.4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.3 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 15% on every change. The history of the code shows how much it changes: about 27,064 lines over the last 90 days, which is about 109,760 lines a year. At that pace, the extra work comes to an estimated 18.3 to 109.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch UnityEngine.Reference Reference

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

11 modules, with 3 dependencies between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 UnityEngine2 XUnityToolkit-Vue.src3 XUnityToolkit-Vue.src.api4 XUnityToolkit-Vue.src.api.client5 XUnityToolkit-Vue.src.api.types6 XUnityToolkit-Vue.src.composables.useFileExplorer7 XUnityToolkit-Vue.src.stores.install8 XUnityToolkit-Vue.src.stores.theme9 XUnityToolkit-Vue.src.utils10 XUnityToolkit-Vue.src.composables11 XUnityToolkit-Vue.src.stores
1 UnityEngine
2 XUnityToolkit-Vue.src
3 XUnityToolkit-Vue.src.api
4 XUnityToolkit-Vue.src.api.client
5 XUnityToolkit-Vue.src.api.types
6 XUnityToolkit-Vue.src.composables.useFileExplorer
7 XUnityToolkit-Vue.src.stores.install
8 XUnityToolkit-Vue.src.stores.theme
9 XUnityToolkit-Vue.src.utils
10 XUnityToolkit-Vue.src.composables1
11 XUnityToolkit-Vue.src.stores51
Uses a module listed above itPart of a loopThe module itself
1 UnityEngine2 XUnityToolkit-Vue.src3 XUnityToolkit-Vue.src.api4 XUnityToolkit-Vue.src.api.client5 XUnityToolkit-Vue.src.api.types6 XUnityToolkit-Vue.src.composables.useFileExplorer7 XUnityToolkit-Vue.src.stores.install8 XUnityToolkit-Vue.src.stores.theme9 XUnityToolkit-Vue.src.utils10 XUnityToolkit-Vue.src.composables11 XUnityToolkit-Vue.src.storesUnityEngine1XUnityToolkit-Vue.src2XUnityToolkit-Vue.src.api3XUnityToolkit-Vue.src.api.client4XUnityToolkit-Vue.src.api.types5XUnityToolkit-Vue.src.composables.useFileExplorer6XUnityToolkit-Vue.src.stores.install7XUnityToolkit-Vue.src.stores.theme8XUnityToolkit-Vue.src.utils9XUnityToolkit-Vue.src.composables10XUnityToolkit-Vue.src.stores11151

At a glance — Code Health · 44.3 · Weak · gated by D1, D2, R3 ·

At a glance — Architecture · 80.8 · Strong ·

At a glance — Maturity · 68.2 · Adequate · gated by M2 ·

At a glance — Readiness · 37.7 · Weak · gated by R4, P3 ·

At a glance — Security · 22.7 · Critical · gated by D29, D36, C2 ·

At a glance — Accessibility · 45.7 · Weak · gated by AC4 ·

At a glance — Performance · 70.0 · Strong ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection293High / Critical
A03:2025 — Software Supply Chain Failures11High / Critical

Roadmap

Top priorities: Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler; Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them; Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RuntimeFontLoader.Il2Cpp.csproj.

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

Do thisHelpsEffortDimension
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.+9.4 ptsMediumAccess Controls
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.+6.7 ptsMediumWeb-Security Posture
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RuntimeFontLoader.Il2Cpp.csproj.+3.2 ptsLowPlatform End-of-Life
Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RuntimeFontBootstrap.cs, Program.cs, REDACTED.+1.6 ptsLowExplicit Debt
Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene.+2.8 ptsLowDependency Hygiene
Resolve the 87 EmptyCatchBlock finding(s) in Explicit Debt — start with FontReplacementService.cs (14), REDACTED (14), Program.cs (9).+2.4 ptsMediumExplicit Debt
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with RuntimeFontLoader.Tests.csproj, XUnityToolkit-WebUI.Tests.csproj.+1.9 ptsLowDependency Hygiene
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (2).+1.6 ptsMediumStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 95 files carrying findings, judged against the Production bar: 19% slop · 63% mixed · 18% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.0SlopExplicit Debt: EmptyCatchBlock
Updater/Program.cs1.4SlopExplicit Debt: EmptyCatchBlock
XUnityToolkit-WebUI/Services/TranslationMemoryService.cs1.8SlopExplicit Debt: EmptyCatchBlock
XUnityToolkit-WebUI/Program.cs1.8SlopExplicit Debt: EmptyCatchBlock
REDACTED1.9SlopStatic Analysis (SAST): High: REDACTED
XUnityToolkit-WebUI/Services/FontReplacementService.cs2.2SlopExplicit Debt: EmptyCatchBlock
REDACTED2.2SlopExplicit Debt: EmptyCatchBlock
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs2.5SlopExplicit Debt: EmptyCatchBlock
RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs2.7SlopExplicit Debt: EmptyCatchBlock
XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs2.8SlopExplicit Debt: EmptyCatchBlock
XUnityToolkit-WebUI/Services/GameImageService.cs3.4SlopExplicit Debt: EmptyCatchBlock
XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs3.5SlopExplicit Debt: EmptyCatchBlock
REDACTED3.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED

How the grades work

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

Critical — 212

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 814

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 212

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

Could not be resolved — 3

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 86 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 86 dimensions across the health lenses
D1D2D3D4D5D6D10D11D12D13D14D15D17D18D19D21D24D26D27D28D29D30D34D35D36D43D44AC1AC2AC3AC4AC5AC6AX1AX10AX2AX3AX5AX6AX8C2GD1IC1M1M2M3M4P1P2P3P4P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X16X18X2X20X21X22X23X24X25X26X27X28X29X3X30X4X5

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
  1. 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, 1129 of 1238 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e53e-d2ee-7ad0-a36a-9a3c1d129923.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the test suite could not be built/run in-image (commonly external-service dependencies — a database, a broker — we won't provision). To have it measured, make the suite runnable without them. For context only, test code is ≈ 10% of production LoC (3,217 test / 32,100 production) — a rough proxy, NOT a coverage measurement, so it is excluded from the score. You can widen what we reach: optional: make the suite runnable without a database, broker or other service we do not provision, and real coverage is measured on the next scan.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 772 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'XUnityToolkit-WebUI.Tests/XUnityToolkit-WebUI.Tests.csproj' with message: The command ""/tmp/nuget-packages/microsoft.windows.sdk.buildtools/10.0.26100.4654/bin/10.0.26100.0/x86/mt.exe" -nologo -manifest "XUnityToolkit-WebUI.Tests/obj/Debug/net….
  • D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 2 error(s). None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (32,100 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `REDACTED`, `XUnityToolkit-WebUI/Infrastructure/AppDataPaths.cs`, `XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs`, `XUnityToolkit-WebUI/Services/AppSettingsService.cs`, `XUnityToolkit-WebUI/Services/BackupService.cs`, … (+42 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 131 further occurrence(s) are not listed individually; the score already reflects all 171.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 reads a prose claim (a path, a setting, a variable, a route, a version, a project, an install, a bare project name in a command) only in text identified as English: the cues that tell a claim from an absence, the past, a plan or an example are an English lexicon, and on other text they would let a false claim through. Links, image targets, fenced commands with an explicit path or a package-manager script, and env-fence variables are checked in every language. 'und' is text the identifier could not name (too short, mixed script, no function words).
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 133 further occurrence(s) are not listed individually; the score already reflects all 173.
  • X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X13 Undrained process stream — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X14 Bypassable address classification — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
  • X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X22 Contradicted release guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X23 Unguarded diagnostic materialisation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X25 Inert configuration knob — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X28 Index access outside its own emptiness guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 49 further occurrence(s) are not listed individually; the score already reflects all 89.
  • X30 Support guard that admits what it rejects — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity3.9 / 10Weak✓ Tool-verified

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

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

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

50 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LlmTranslationService.TranslateDetailedAsync at 170. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ToolboxAgentToolExecutor.IsAllowedApiCall at 24 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: XUnityToolkit-WebUI/Services/GameImageService.cs (GameImageService.TryDetectSupportedImageContentType at 23), XUnityToolkit-WebUI/Infrastructure/PathSecurity.cs (PathSecurity.IsPrivateIPv4 at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

LlmTranslationService.TranslateDetailedAsync (cyclomatic 170)XUnityToolkit-WebUI/Services/LlmTranslationService.cs:240
GameEndpoints.MapGameEndpoints (cyclomatic 115)REDACTED:12
ImageEndpoints.MapImageEndpoints (cyclomatic 73)REDACTED:8
TmpFontGeneratorService.InjectIntoTemplate (cyclomatic 65)XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:508
FontGenerationEndpoints.MapFontGenerationEndpoints (cyclomatic 53)REDACTED:16

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with LlmTranslationService.TranslateDetailedAsync (cyclomatic 170). — Refactoring it lifts Cyclomatic Complexity from 3.9 to about 4.5/10.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

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

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

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

77 method(s) exceeded the cognitive complexity threshold of 15; the worst was LlmTranslationService.TranslateDetailedAsync at 446.

LlmTranslationService.TranslateDetailedAsync (cognitive 446)XUnityToolkit-WebUI/Services/LlmTranslationService.cs:240
TmpFontGeneratorService.InjectIntoTemplate (cognitive 166)XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:508
GameEndpoints.MapGameEndpoints (cognitive 127)REDACTED:12
FontReplacementService.ReplaceFontsAsync (cognitive 81)XUnityToolkit-WebUI/Services/FontReplacementService.cs:948
ImageEndpoints.MapImageEndpoints (cognitive 72)REDACTED:8

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

What to do

  1. Bring the 7 bodies over 60 down to 60 or less in Cognitive Complexity — start with LlmTranslationService.TranslateDetailedAsync (cognitive 446), TmpFontGeneratorService.InjectIntoTemplate (cognitive 166), GameEndpoints.MapGameEndpoints (cognitive 127). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 7 together lifts Cognitive Complexity from 2.0 to about 4.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes6.2 / 10Adequate✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

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

50 god class(es) detected.

MethodTooLong: GameEndpoints.MapGameEndpoints · ×21REDACTED:12
FileTooLong: Services/FontReplacementService.cs · ×13XUnityToolkit-WebUI/Services/FontReplacementService.cs
TooManyMethods: LocalLlmService · ×7REDACTED
ClassTooLong: TmpFontGeneratorService · ×5XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs
FunctionTooLong: update.useUpdateStore · ×4XUnityToolkit-Vue/src/stores/update.ts:8

What to do

  1. Resolve the 21 MethodTooLong finding(s) in God Classes — start with FontReplacementService.cs (5), TmpFontGeneratorService.cs (2), REDACTED (2). — One of this dimension's main actionable groups (21 warning-level).
  2. Resolve the 13 FileTooLong finding(s) in God Classes — start with FontReplacementService.cs, LlmTranslationService.cs, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 7 TooManyMethods finding(s) in God Classes — start with REDACTED, FontReplacementService.cs, LlmTranslationService.cs. — One of this dimension's main actionable groups (7 warning-level).

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

D4 · Code Duplication5.4 / 10Adequate✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

85 duplicated block group(s) detected. 11.5 % of the production lines (3,704 of 32,201) are in a reported copy. A further 44 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (9 lines × 2) · ×7REDACTED:124
Duplicated block (8 lines × 2) · ×5REDACTED:108
Edited copy of a member (19 corresponding lines) · ×4XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:49
Edited copy of a member (7 corresponding lines) · ×4XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1673
Duplicated block (12 lines × 2) · ×4REDACTED:798

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

What to do

  1. Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with FontReplacementService.cs (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with REDACTED, REDACTED, TmpFontGeneratorService.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 4 Edited copy of a member (19 corresponding lines) finding(s) in Code Duplication — start with BuiltinCharsets.cs, REDACTED, PluginDiagnosticAgentService.cs. — One of this dimension's main actionable groups (4 warning-level).

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

0 of 51 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 126 tests.

No assertions: ValidateAppPackageInventory_ShouldAcceptMatchingPackageAndManifestXUnityToolkit-WebUI.Tests/Services/UpdateManifestFileSetTests.cs:197

What to do

  1. Resolve the 1 No assertions finding(s) in Test Quality — start with UpdateManifestFileSetTests.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). unit: measured (0 flaky); other: measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene7.1 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

9 outdated, 1 vulnerable, 1 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 81 outdated of 141 package(s) across 1 lockfile(s).

Deprecated: xunit · ×2RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj:10
Outdated (npm): eventsource · ×5
Outdated (npm): @babel/generator · ×76
Outdated: Microsoft.NET.Test.Sdk · ×9

What to do

  1. Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (5 recommendation-level).
  2. Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with RuntimeFontLoader.Tests.csproj, XUnityToolkit-WebUI.Tests.csproj. — One of this dimension's main actionable groups (2 warning-level).

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

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 124 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 20 direct `PackageReference`(s), and 98 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.3 / 10Stronggated by 10 serious findings✓ Tool-verified

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

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

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

Top hotspots: REDACTED (3×115=345); XUnityToolkit-WebUI/Program.cs (7×32=224); REDACTED (5×25=125)

Hotspot: REDACTED · ×10REDACTED:12

What to do

  1. Resolve the 10 Hotspot finding(s) in Churn × Complexity Hotspots — start with Program.cs (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).

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

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

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

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

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

94 deducted debt markers + unmeasured dead symbols across 32100 LoC in the .NET projects (2.7/KLoC) → score 4.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×87RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:295
WriteOnlyPrivateField · ×3RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:26
NoWarnInCsproj · ×3XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:26
DeadPreprocessorBranchXUnityToolkit-WebUI/Services/TranslationMemoryService.cs:166

What to do

  1. Resolve the 87 EmptyCatchBlock finding(s) in Explicit Debt — start with FontReplacementService.cs (14), REDACTED (14), Program.cs (9). — One of this dimension's main actionable groups (87 issue-level).
  2. Resolve the 3 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RuntimeFontBootstrap.cs, Program.cs, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with XUnityToolkit-WebUI.csproj (2), XUnityToolkit-WebUI.Tests.csproj. — One of this dimension's main actionable groups (3 issue-level).

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

D18 · Solution Shape10.0 / 10Exemplary✓ Tool-verified

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

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

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

5 projects, 159 source files, 34742 hand-written lines of code (31525 production / 3217 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 1 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 1 documentation facets pass in full. 1 document(s) read across 3 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D21 · Naming Consistency1.7 / 10Critical✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

1 naming inconsistencies among 12 declarations measured against a convention their peers follow.

`OpenAI` spells `AI` where 13 names in the project spell it `Ai`XUnityToolkit-WebUI/Models/AiTranslationSettings.cs:3

What to do

  1. Resolve the 1 `OpenAI` spells `AI` where 13 names in the project spell it `Ai` finding(s) in Naming Consistency — start with AiTranslationSettings.cs. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value7.3 6.9 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 95% · ceiling Documented

18 of 663 judged comments only repeat the code they sit on (2.7 %). 47 comment(s) in another language or script were not judged.

redundant comment · ×18XUnityToolkit-Vue/src/api/games.ts:271

What to do

  1. Resolve the 18 redundant comment finding(s) in Comment Value — start with REDACTED (3), LlmTranslationService.cs (3), Program.cs (2). — One of this dimension's main actionable groups (18 recommendation-level).

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

D26 · Project Cohesion7.5 / 10Strong✓ Tool-verified

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

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

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

1 of 8 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionXUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:1

What to do

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

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

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

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

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

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

293 finding(s): 0 critical, 35 high, 258 medium, 0 low. 11 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 49 file(s) — `XUnityToolkit-WebUI.Tests/Infrastructure/PathSecurityTests.cs` (lines 123–124, line 128), `XUnityToolkit-WebUI.Tests/Services/ConnectionResilienceTests.cs` (lines 563–564, line 669), `REDACTED` (lines 4–51, line 77, lines 211–212), `XUnityToolkit-WebUI/Infrastructure/AppDataPaths.cs` (line 3), `XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs` (line 197), … (+44 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 48 of those file(s) — `XUnityToolkit-WebUI.Tests/Infrastructure/PathSecurityTests.cs`, `XUnityToolkit-WebUI.Tests/Services/ConnectionResilienceTests.cs`, `XUnityToolkit-WebUI/Infrastructure/AppDataPaths.cs`, `XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs`, `XUnityToolkit-WebUI/Services/AppSettingsService.cs`, … (+43 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 3 of those file(s) — `REDACTED`, `XUnityToolkit-WebUI/Services/RuntimeTmpFontService.cs`, `XUnityToolkit-WebUI/Services/ToolboxAgentService.cs` — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (10 issue-level).
  2. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
  3. No action in Static Analysis (SAST) — all 11 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (11 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities6.9 / 10Adequate✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

4 finding(s): 1 critical, 3 high, 0 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED
REDACTED

What to do

  1. Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 98 of the 140 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling8.9 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: index.ts↔GameDetailView.vue 79%; types.ts↔index.ts 79%; InstallProgressDrawer.vue↔InstallOrchestrator.cs 67%

Boundary-crossing change coupling: Program.cs ↔ TranslationMemoryService.csUpdater/Program.cs:1
Change coupling: InstallProgressDrawer.vue ↔ InstallOrchestrator.cs · ×8XUnityToolkit-Vue/src/components/progress/InstallProgressDrawer.vue:1
Change-coupling hub: index.ts → games.ts, types.ts, GameDetailView.vueXUnityToolkit-Vue/src/router/index.ts

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with Program.cs. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 8 Change coupling finding(s) in Change Coupling — start with FontReplacementView.vue (2), InstallProgressDrawer.vue, games.ts. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with index.ts. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life6.0 / 10Adequate✓ Tool-verified

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

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

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

1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 8 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

End-of-life runtime: .NET net6.0RuntimeFontLoader/Il2Cpp/RuntimeFontLoader.Il2Cpp.csproj:3

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with RuntimeFontLoader.Il2Cpp.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives5.3 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:206, XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:254

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.1 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:702, XUnityToolkit-Vue/src/views/ConfigEditorView.vue:110
  • A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — XUnityToolkit-Vue/src/components/layout/AppShell.vue:165
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×37) — XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:85, XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:101, XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:117, …

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure7.2 / 10Strong✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — XUnityToolkit-Vue/src/views/LibraryView.vue:255

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.1 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×35) — XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:355, XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:199, XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:242, …
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×3) — XUnityToolkit-Vue/src/components/layout/AppShell.vue:228, XUnityToolkit-Vue/src/components/layout/AppShell.vue:246, XUnityToolkit-Vue/src/components/layout/AppShell.vue:262
  • This <div> binds mousedown and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabindex="0", so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabindex="0" + a key handler alongside the double-click. — XUnityToolkit-Vue/src/components/layout/AppShell.vue:274
  • This <h1> binds double-click and nothing else. No click, no key handler, and no tabindex="0", so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabindex="0" + a key handler alongside the double-click. — XUnityToolkit-Vue/src/views/GameDetailView.vue:652

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety7.7 / 10Strong✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.level-pill` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — XUnityToolkit-Vue/src/views/LogView.vue:335

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition8.3 / 10Strong✓ Tool-verified

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

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

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

AX2 · Stateful singletons4.9 / 10Weak✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `FileLoggerProvider` is a singleton (one shared instance) but mutates instance state outside any lock (_writer, LogBroadcast; e.g. `_writer` at line 113). — XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:12
  • `LocalLlmService` is a singleton (one shared instance) but mutates instance state outside any lock (_settingsCache, _gpuCache, _error, _process; e.g. `_settingsCache` at line 70). — REDACTED:15
  • `TmpFontGeneratorService` is a singleton (one shared instance) but mutates instance state outside any lock (_cts; e.g. `_cts` at line 141). — XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:20
  • `UpdateService` is a singleton (one shared instance) but mutates instance state outside any lock (_status, _lastCheckResult, _remoteManifest, _releaseAssets, _availableInfo, _dismissedVersion; e.g. `_status` at line 130). — REDACTED:13
  • `SystemTrayService` is a singleton (one shared instance) but mutates instance state outside any lock (_cachedIcon, _openMenuItem; e.g. `_cachedIcon` at line 83). — XUnityToolkit-WebUI/Services/SystemTrayService.cs:7
  • `TranslationMemoryBuffer` is not registered, but the singleton `LlmTranslationService` creates it and keeps it in `_translationMemory`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_entries; e.g. `_entries` at line 43). — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:32
  • `DesktopApp` is not registered, but `Program` creates it and keeps it in the static `_desktopApplication`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_mainWindow, _startupTask; e.g. `_mainWindow` at line 35). — XUnityToolkit-WebUI/App.xaml.cs:8
  • `MainWindow` is not registered, but the singleton `DesktopApp` creates it and keeps it in `_mainWindow`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_webViewPrepared; e.g. `_webViewPrepared` at line 110). — XUnityToolkit-WebUI/MainWindow.xaml.cs:17
  • `NativeWindowMinimumSizeHook` is not registered, but the singleton `MainWindow` creates it and keeps it in `_minimumSizeHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_attached; e.g. `_attached` at line 440). — XUnityToolkit-WebUI/MainWindow.xaml.cs:412
  • `RuntimeFontBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_activeFont, _overridePrefix; e.g. `_activeFont` at line 97). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:13

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
  • A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

C2 · Access Controls0.0 / 10Critical✓ Tool-verified

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

  • No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:13, REDACTED:20
  • `MapGet("/download")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:35
  • `MapPost("/analyze")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:52
  • `MapPost("/install")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:37
  • `MapPost("/upload")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×3) — REDACTED:80, REDACTED:20, REDACTED:183
  • `MapDelete("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:123
  • `MapPost("/toggle")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:157
  • `MapGet("/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:191
  • `MapGet("/api/games/{id}/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:10
  • `MapPut("/api/games/{id}/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:20
  • `MapGet("/api/games/{id}/config/raw")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:31
  • `MapPut("/api/games/{id}/config/raw")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:42
  • `MapPost("/api/games/{id}/detect")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:10
  • `MapGet("/drives")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:14
  • `MapGet("/quick-access")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:40
  • `MapPost("/read-text")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:54
  • `MapPost("/list")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:83
  • `MapPost("/upload-from-path")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:55
  • `MapPost("/generate")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:84
  • `MapGet("/status")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — REDACTED:136, REDACTED:171
  • `MapPost("/cancel")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:139
  • `MapGet("/download/{fileName}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:145
  • `MapGet("/history")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:154
  • `MapDelete("/{fileName}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:205
  • `MapGet("/charsets")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:229
  • `MapPost("/charset/preview")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:233
  • `MapPost("/charset/upload-custom")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:250
  • `MapPost("/charset/upload-custom-from-path")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:286
  • `MapPost("/charset/upload-translation")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:319
  • `MapPost("/charset/upload-translation-from-path")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:343
  • `MapGet("/report/{fileName}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:365
  • `MapPost("/install-tmp-font/{gameId}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:379
  • `MapPost("/scan")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:67
  • `MapPost("/replace")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:79
  • `MapPost("/restore")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — REDACTED:162

What to do

  • Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs8.4 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • Code inside a `#if false` block is permanently excluded from the build — disabled code that should be removed or restored. — XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:166
  • `DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:226

What to do

  • Remove the dead code that looks live: delete dead if(false) / #if false branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async methods, which promise work they never wait for.
M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

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

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

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

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

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P2 · Observability6.2 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

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

What to do

  • Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj:9

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — 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.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

PF3 · Async & latency hygiene7.0 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — XUnityToolkit-WebUI/Program.cs:594, XUnityToolkit-WebUI/Program.cs:604

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

R10 · Code Duplication6.2 / 10Adequate✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 5 duplicated blocks under XUnityToolkit-Vue/src/ have copies in at least two of the sibling directories api, components, stores, views — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:57
  • XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:10 — the two spans are one implementation copied and then locally edited — 812 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10
  • XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:10 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10 — the two spans are one implementation copied and then locally edited — 643 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:10
  • XUnityToolkit-Vue/src/views/FontGeneratorView.vue:349 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:425 — 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. — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:349
  • XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:147 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:134 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:100 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:147
  • XUnityToolkit-Vue/src/views/FontGeneratorView.vue:208 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:226 — 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. — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:208
  • XUnityToolkit-Vue/src/views/FontReplacementView.vue:578 · XUnityToolkit-Vue/src/views/FontReplacementView.vue:652 — 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. — XUnityToolkit-Vue/src/views/FontReplacementView.vue:578
  • XUnityToolkit-Vue/src/views/TermEditorView.vue:329 · XUnityToolkit-Vue/src/views/TermEditorView.vue:354 — 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. — XUnityToolkit-Vue/src/views/TermEditorView.vue:329
  • XUnityToolkit-Vue/src/views/TranslationEditorView.vue:77 · XUnityToolkit-Vue/src/views/TranslationEditorView.vue:95 — 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. — XUnityToolkit-Vue/src/views/TranslationEditorView.vue:77
  • XUnityToolkit-Vue/src/stores/aiTranslation.ts:27 · XUnityToolkit-Vue/src/stores/log.ts:89 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/stores/aiTranslation.ts:27
  • XUnityToolkit-Vue/src/stores/install.ts:101 · XUnityToolkit-Vue/src/stores/install.ts:136 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/stores/install.ts:101
  • XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:280 · XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:298 — 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. — XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:280
  • XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:66 · XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:81 — 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. — XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:66
  • XUnityToolkit-Vue/src/stores/update.ts:38 · XUnityToolkit-Vue/src/stores/update.ts:90 — 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. — XUnityToolkit-Vue/src/stores/update.ts:38
  • XUnityToolkit-Vue/src/views/AiTranslationView.vue:194 · XUnityToolkit-Vue/src/views/SettingsView.vue:130 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — XUnityToolkit-Vue/src/views/AiTranslationView.vue:194
  • XUnityToolkit-Vue/src/views/TermEditorView.vue:311 · XUnityToolkit-Vue/src/views/TermEditorView.vue:336 · XUnityToolkit-Vue/src/views/TermEditorView.vue:361 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/views/TermEditorView.vue:311
  • XUnityToolkit-Vue/src/api/games.ts:73 · XUnityToolkit-Vue/src/api/games.ts:100 · XUnityToolkit-Vue/src/api/games.ts:151 · XUnityToolkit-Vue/src/api/games.ts:304 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/api/games.ts:73
  • XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:205 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:166 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:205
  • XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:277 · XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:307 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:277
  • XUnityToolkit-Vue/src/views/FontGeneratorView.vue:149 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:216 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:234 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:149
  • XUnityToolkit-Vue/src/stores/localLlm.ts:67 · XUnityToolkit-Vue/src/stores/log.ts:77 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/stores/localLlm.ts:67
  • XUnityToolkit-Vue/src/views/FontReplacementView.vue:40 · XUnityToolkit-Vue/src/views/PluginManagerView.vue:20 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — XUnityToolkit-Vue/src/views/FontReplacementView.vue:40
  • XUnityToolkit-Vue/src/views/GameDetailView.vue:69 · XUnityToolkit-Vue/src/views/TranslationEditorView.vue:39 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — XUnityToolkit-Vue/src/views/GameDetailView.vue:69
  • XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:58 · XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:27 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:34 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:28 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:58
  • XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:33 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:27 · XUnityToolkit-Vue/src/components/library/WebImageSearchTab.vue:21 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:33
  • XUnityToolkit-Vue/src/api/games.ts:109 · XUnityToolkit-Vue/src/views/GameDetailView.vue:513 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/api/games.ts:109
  • XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:50 · XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:25 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:50
  • XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:26 · XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:32 — 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. — XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:26
  • XUnityToolkit-Vue/src/views/AiTranslationView.vue:520 · XUnityToolkit-Vue/src/views/AiTranslationView.vue:528 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — XUnityToolkit-Vue/src/views/AiTranslationView.vue:520

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity9.7 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • parseCsvImport has cyclomatic complexity 28 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/TermEditorView.vue:624
  • computeConnections has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/AiTranslationView.vue:437
  • parseJsonImport has cyclomatic complexity 24 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/TermEditorView.vue:556
  • getReasoningHint has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:229
  • loadPreferences has cyclomatic complexity 17 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/stores/games.ts:72
  • addGameCore has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/composables/useAddGameFlow.ts:26
  • handleImportClick has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/TermEditorView.vue:514
  • (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/AiTranslationView.vue:614
  • doReplace has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/FontReplacementView.vue:342
  • send has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:234
  • handleIconContextMenuSelect has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/GameDetailView.vue:379
  • (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — XUnityToolkit-Vue/src/views/TermEditorView.vue:216
R3 · Large Files0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • XUnityToolkit-Vue/src/views/AiTranslationView.vue has 2694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/AiTranslationView.vue:1
  • XUnityToolkit-Vue/src/views/GameDetailView.vue has 2158 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/GameDetailView.vue:1
  • XUnityToolkit-Vue/src/views/SettingsView.vue has 1278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/SettingsView.vue:1
  • XUnityToolkit-Vue/src/views/FontReplacementView.vue has 1137 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/FontReplacementView.vue:1
  • XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue has 1078 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:1
  • XUnityToolkit-Vue/src/views/FontGeneratorView.vue has 1046 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:1
  • XUnityToolkit-Vue/src/views/TermEditorView.vue has 1016 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/TermEditorView.vue:1
  • XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue has 960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:1
  • XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue has 797 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:1
  • XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue has 764 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:1
  • XUnityToolkit-Vue/src/views/LibraryView.vue has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/LibraryView.vue:1
  • XUnityToolkit-Vue/src/components/config/ConfigPanel.vue has 720 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:1
  • XUnityToolkit-Vue/src/components/layout/AppShell.vue has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/layout/AppShell.vue:1
  • XUnityToolkit-Vue/src/views/LogView.vue has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/LogView.vue:1
  • XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:1
  • XUnityToolkit-Vue/src/views/TranslationEditorView.vue has 487 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/TranslationEditorView.vue:1
  • XUnityToolkit-Vue/src/components/library/IconPickerModal.vue has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:1
  • XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:1
  • XUnityToolkit-Vue/src/views/BepInExLogView.vue has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — XUnityToolkit-Vue/src/views/BepInExLogView.vue:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 0% of 47 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness9.2 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling6.7 / 10Adequate✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add eslint as package.json scripts and run them in CI.
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×3) — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:153, XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:119, XUnityToolkit-Vue/src/views/FontGeneratorView.vue:120

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture4.0 / 10Weak✓ Tool-verified

Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — XUnityToolkit-WebUI/Program.cs:84
  • No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — XUnityToolkit-WebUI/Program.cs:84
  • No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
  • `MapGet("/")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. (×2) — REDACTED:13, REDACTED:20
  • `MapGet("/download")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:35
  • `MapPost("/analyze")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:52
  • `MapPost("/install")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:37
  • `MapPost("/upload")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. (×2) — REDACTED:80, REDACTED:20
  • `MapDelete("/")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:123
  • `MapPost("/toggle")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:157
  • `MapGet("/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:191
  • `MapGet("/api/games/{id}/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:10
  • `MapPut("/api/games/{id}/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:20
  • `MapGet("/api/games/{id}/config/raw")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:31
  • `MapPut("/api/games/{id}/config/raw")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:42
  • `MapPost("/api/games/{id}/detect")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:10
  • `MapGet("/drives")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:14
  • `MapGet("/quick-access")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:40
  • `MapPost("/read-text")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:54
  • `MapPost("/list")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:83
  • `MapPost("/upload-from-path")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:55
  • `MapPost("/generate")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:84
  • `MapGet("/status")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:136
  • `MapPost("/cancel")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:139
  • `MapGet("/download/{fileName}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:145
  • `MapGet("/history")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:154
  • `MapDelete("/{fileName}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:205
  • `MapGet("/charsets")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:229
  • `MapPost("/charset/preview")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:233
  • `MapPost("/charset/upload-custom")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:250
  • `MapPost("/charset/upload-custom-from-path")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:286
  • `MapPost("/charset/upload-translation")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:319
  • `MapPost("/charset/upload-translation-from-path")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:343
  • `MapGet("/report/{fileName}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:365
  • `MapPost("/install-tmp-font/{gameId}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:379
  • `MapPost("/scan")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard. — REDACTED:67

What to do

  • Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
  • Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
  • Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
X1 · Async correctness6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×2) — XUnityToolkit-WebUI/Program.cs:124, REDACTED:255
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×2) — XUnityToolkit-WebUI/Program.cs:594, XUnityToolkit-WebUI/Program.cs:604
  • `File.ReadAllBytes` blocks the thread on I/O while `File.ReadAllBytesAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×2) — XUnityToolkit-WebUI/Services/FontReplacementService.cs:990, XUnityToolkit-WebUI/Services/FontReplacementService.cs:1001
  • `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×3) — REDACTED:297, REDACTED:1338, XUnityToolkit-WebUI/Services/PluginPackageService.cs:239
  • `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin. (×2) — XUnityToolkit-WebUI/Services/PluginPackageService.cs:151, XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:821
  • `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). — XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:278

What to do

  • Blocking `File.ReadAllText` inside an `async` method
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness6.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `_writer` is a `StreamWriter` this type creates itself, and here (line 113) a new instance is written over it — but `FileLoggerProvider` creates `_writer` when it is constructed, so every later call finds an instance there, and nothing earlier in `ResumeFileLog` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_writer?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:113
  • `listener` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 1169). Every use of it in `GetAvailablePort` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var listener = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:1169

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X2 · Cancellation propagation8.5 / 10Strong✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 307/404 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×2) — XUnityToolkit-WebUI/App.xaml.cs:47, REDACTED:15
  • This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on. (×36) — REDACTED:13, REDACTED:35, REDACTED:10, …
  • Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`). — REDACTED:112

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped2.7 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `highlightText(line.text)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — XUnityToolkit-Vue/src/views/BepInExLogView.vue:308
  • `changelogHtml` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — XUnityToolkit-Vue/src/views/SettingsView.vue:663

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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

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

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

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×38) — TranslatorEndpoint/ToolkitConnectionManager.cs:75, TranslatorEndpoint/ToolkitConnectionManager.cs:165, Updater/Program.cs:4, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). — XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:116
  • `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — XUnityToolkit-WebUI/Services/BackupService.cs:23

What to do

  • Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

X5 · Nullable reference types6.7 / 10Adequate✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 2/3 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
  • ~1.1 `!` suppressions per 1k syntax nodes — 4 suppression(s) across the 3733 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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.

LensScoreRatingImpact
Code Health44.3Weak — gated by D1, D2, R3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture80.8StrongStrongest area.
Maturity68.2Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness37.7Weak — gated by R4, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security22.7Critical — gated by D29, D36, C2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility45.7Weak — gated by AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance70.0StrongSolid.
Unscored — 4 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • SC1 Supply-chain hygiene — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 37 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 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.

  • AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • 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 intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 47 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 212 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×87
  • EmptyCatchBlock RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:295 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:425 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:457 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock TranslatorEndpoint/ToolkitConnectionManager.cs:75 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock TranslatorEndpoint/ToolkitConnectionManager.cs:165 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Updater/Program.cs:4 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Updater/Program.cs:623 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:184 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:990 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:1027 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:1058 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:111 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock REDACTED:135 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:79 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:91 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:101 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:115 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:186 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:190 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:55 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:112 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:94 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:116 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Program.cs:48 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock XUnityToolkit-WebUI/Program.cs:77 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • + 62 more in this group — see findings.md.
AC2 · Forms & labels · <label> that labels no control · ×37
  • <label> that labels no control XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:85 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:101 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:117 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/library/LibraryCustomizer.vue:123 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:388 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:401 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:426 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:440 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:514 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:523 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:532 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:543 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:554 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:566 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:600 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:610 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:641 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:394 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:405 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:417 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:438 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:451 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:463 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:476 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:491 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • + 12 more in this group — see findings.md.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×31
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:355 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:199 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:242 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:267 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:247 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:291 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:316 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:341 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/GameCard.vue:91 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:207 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:231 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:258 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/library/WebImageSearchTab.vue:135 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:656 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/AiTranslationView.vue:1029 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/AiTranslationView.vue:1226 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/AiTranslationView.vue:1288 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/FontGeneratorView.vue:499 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/FontGeneratorView.vue:579 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:632 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:986 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:1066 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:1080 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:1090 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> XUnityToolkit-Vue/src/views/GameDetailView.vue:1100 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • + 6 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC4 · Keyboard semantics · Click handler on a non-interactive <span> · ×4
  • Click handler on a non-interactive <span> XUnityToolkit-Vue/src/views/TermEditorView.vue:877 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> XUnityToolkit-Vue/src/views/TermEditorView.vue:880 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> XUnityToolkit-Vue/src/views/TermEditorView.vue:883 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <span> XUnityToolkit-Vue/src/views/TermEditorView.vue:889 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D17 · Explicit Debt · WriteOnlyPrivateField · ×3
  • WriteOnlyPrivateField RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:26 — private DynamicMethod _overridePrefix — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField XUnityToolkit-WebUI/Program.cs:16 — private DesktopApp? _desktopApplication — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField REDACTED:40 — private string? _dismissedVersion — assigned 3 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D17 · Explicit Debt · NoWarnInCsproj · ×3
  • NoWarnInCsproj XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:26 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj XUnityToolkit-WebUI.Tests/XUnityToolkit-WebUI.Tests.csproj:14 — MSB3277 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:26 — NU1900 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×2
  • <img> without a text alternative XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:206 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:254 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <input> without a programmatic label · ×1
  • <input> without a programmatic label XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:702 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <button> with no accessible text · ×1
  • <button> with no accessible text XUnityToolkit-Vue/src/components/layout/AppShell.vue:165 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label XUnityToolkit-Vue/src/views/ConfigEditorView.vue:110 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics · Double-click handler on a non-interactive <div> · ×1
  • Double-click handler on a non-interactive <div> XUnityToolkit-Vue/src/components/layout/AppShell.vue:274 — This <div> binds mousedown and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabindex="0", so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabindex="0" + a key handler alongside the double-click.
AC4 · Keyboard semantics · Double-click handler on a non-interactive <h1> · ×1
  • Double-click handler on a non-interactive <h1> XUnityToolkit-Vue/src/views/GameDetailView.vue:652 — This <h1> binds double-click and nothing else. No click, no key handler, and no tabindex="0", so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabindex="0" + a key handler alongside the double-click.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: Program.cs ↔ TranslationMemoryService.cs Updater/Program.cs:1 — `Updater/Program.cs` (context Updater) and `XUnityToolkit-WebUI/Services/TranslationMemoryService.cs` (context XUnityToolkit-WebUI) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `822fbd0f` fix: 全面代码审查——修复竞态条件、安全漏洞和性能问题; `60af9d43` fix: 全面代码审查——修复竞态条件、安全漏洞和性能问题; `09d22daf` fix: 第六轮审查修复竞态、安全、生命周期和死代码问题 — run `git show` on any of them.
Serious — 814 finding(s)
D29 · Static Analysis (SAST) · REDACTED · ×184
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 159 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×71
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 46 more in this group — see findings.md.
C2 · Access Controls · No authorization · ×40
  • No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
  • No authorization REDACTED:13 — `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:35 — `MapGet("/download")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:52 — `MapPost("/analyze")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:20 — `MapGet("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:37 — `MapPost("/install")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:80 — `MapPost("/upload")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:123 — `MapDelete("/")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:157 — `MapPost("/toggle")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:191 — `MapGet("/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:10 — `MapGet("/api/games/{id}/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:20 — `MapPut("/api/games/{id}/config")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:31 — `MapGet("/api/games/{id}/config/raw")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:42 — `MapPut("/api/games/{id}/config/raw")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:10 — `MapPost("/api/games/{id}/detect")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:14 — `MapGet("/drives")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:40 — `MapGet("/quick-access")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:54 — `MapPost("/read-text")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:83 — `MapPost("/list")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:20 — `MapPost("/upload")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:55 — `MapPost("/upload-from-path")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:84 — `MapPost("/generate")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:136 — `MapGet("/status")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:139 — `MapPost("/cancel")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • No authorization REDACTED:145 — `MapGet("/download/{fileName}")` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
  • + 15 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×39
  • Swallowed exception (empty catch) TranslatorEndpoint/ToolkitConnectionManager.cs:75 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) TranslatorEndpoint/ToolkitConnectionManager.cs:165 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Updater/Program.cs:4 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) Updater/Program.cs:623 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:184 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:990 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:1027 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:1058 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:111 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:135 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:79 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:91 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:101 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:115 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:186 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:190 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:55 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:112 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:94 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:116 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Program.cs:48 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Program.cs:77 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Program.cs:133 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Program.cs:344 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) XUnityToolkit-WebUI/Program.cs:348 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 14 more in this group — see findings.md.
X2 · Cancellation propagation · Async endpoint handler without CancellationToken · ×36
  • Async endpoint handler without CancellationToken: / REDACTED:13 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /download REDACTED:35 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /api/games/{id}/config REDACTED:10 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /api/games/{id}/config REDACTED:20 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /api/games/{id}/config/raw REDACTED:31 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /api/games/{id}/config/raw REDACTED:42 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /api/games/{id}/detect REDACTED:10 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /read-text REDACTED:54 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /upload REDACTED:20 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /generate REDACTED:84 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /history REDACTED:154 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /charset/preview REDACTED:233 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /charset/upload-custom REDACTED:250 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /charset/upload-custom-from-path REDACTED:286 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /charset/upload-translation REDACTED:319 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /report/{fileName} REDACTED:365 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /restore REDACTED:162 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /status REDACTED:171 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /upload REDACTED:183 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /upload-from-path REDACTED:227 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: / REDACTED:16 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /{id} REDACTED:22 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: / REDACTED:83 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /{id} REDACTED:272 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • Async endpoint handler without CancellationToken: /{id}/open-folder REDACTED:580 — This endpoint's handler takes no CancellationToken, while it calls something that takes one — a client that disconnects leaves that work running. Add a `CancellationToken` parameter (minimal APIs bind it to the request's) and pass it on.
  • + 11 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×21
  • MethodTooLong: GameEndpoints.MapGameEndpoints REDACTED:12 — MethodTooLong — MapGameEndpoints runs 602 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 502 over it, 6.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LlmTranslationService.TranslateDetailedAsync XUnityToolkit-WebUI/Services/LlmTranslationService.cs:240 — MethodTooLong — TranslateDetailedAsync runs 560 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 460 over it, 5.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ImageEndpoints.MapImageEndpoints REDACTED:8 — MethodTooLong — MapImageEndpoints runs 410 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 310 over it, 4.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Program.BuildApplicationAsync XUnityToolkit-WebUI/Program.cs:66 — MethodTooLong — BuildApplicationAsync runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontGenerationEndpoints.MapFontGenerationEndpoints REDACTED:16 — MethodTooLong — MapFontGenerationEndpoints runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TmpFontGeneratorService.InjectIntoTemplate XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:508 — MethodTooLong — InjectIntoTemplate runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementService.ReplaceFontsAsync XUnityToolkit-WebUI/Services/FontReplacementService.cs:1250 — MethodTooLong — ReplaceFontsAsync runs 193 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TmpFontGeneratorService.GenerateCore XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:204 — MethodTooLong — GenerateCore runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SettingsEndpoints.MapSettingsEndpoints REDACTED:16 — MethodTooLong — MapSettingsEndpoints runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementService.ReplaceFontsAsync XUnityToolkit-WebUI/Services/FontReplacementService.cs:948 — MethodTooLong — ReplaceFontsAsync runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ToolboxAgentService.ChatAsync XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:97 — MethodTooLong — ChatAsync runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementService.ProcessBundleFile XUnityToolkit-WebUI/Services/FontReplacementService.cs:1665 — MethodTooLong — ProcessBundleFile runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementEndpoints.MapFontReplacementEndpoints REDACTED:63 — MethodTooLong — MapFontReplacementEndpoints runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementService.ProcessBundleFile XUnityToolkit-WebUI/Services/FontReplacementService.cs:2059 — MethodTooLong — ProcessBundleFile runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UpdateService.DownloadUpdateAsync REDACTED:339 — MethodTooLong — DownloadUpdateAsync runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: InstallOrchestrator.ExecuteInstallAsync XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:147 — MethodTooLong — ExecuteInstallAsync runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: BepInExPluginEndpoints.MapBepInExPluginEndpoints REDACTED:15 — MethodTooLong — MapBepInExPluginEndpoints runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UpdateService.CheckForUpdateAsync REDACTED:140 — MethodTooLong — CheckForUpdateAsync runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FontReplacementService.ClearAddressablesCrcAsync XUnityToolkit-WebUI/Services/FontReplacementService.cs:2732 — MethodTooLong — ClearAddressablesCrcAsync runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TranslationEditorEndpoints.MapTranslationEditorEndpoints REDACTED:8 — MethodTooLong — MapTranslationEditorEndpoints runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LocalLlmService.DownloadLlamaAsync REDACTED:1216 — MethodTooLong — DownloadLlamaAsync runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · FileTooLong · ×13
  • FileTooLong: Services/FontReplacementService.cs XUnityToolkit-WebUI/Services/FontReplacementService.cs — FileTooLong — 1954 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1454 over it, 3.91× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/LlmTranslationService.cs XUnityToolkit-WebUI/Services/LlmTranslationService.cs — FileTooLong — 1480 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 980 over it, 2.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 845 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 345 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: api/types.ts XUnityToolkit-Vue/src/api/types.ts — FileTooLong — 765 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 265 over it, 1.53× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/ToolboxAgentToolExecutor.cs XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs — FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/TmpFontGeneratorService.cs XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs — FileTooLong — 716 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 216 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 693 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 193 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/ToolboxAgentHostAccessService.cs XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs — FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 72 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/PluginDiagnosticArtifactCollector.cs XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs — FileTooLong — 569 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 69 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 557 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 57 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/PluginHealthCheckService.cs XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/PluginDiagnosticAgentService.cs XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs — FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Services/GameImageService.cs XUnityToolkit-WebUI/Services/GameImageService.cs — FileTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 7 over it, 1.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D15 · Churn × Complexity Hotspots · Hotspot · ×10
  • Hotspot: REDACTED REDACTED:12 — REDACTED changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 115 in GameEndpoints.MapGameEndpoints at line 12. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: XUnityToolkit-WebUI/Program.cs XUnityToolkit-WebUI/Program.cs:66 — XUnityToolkit-WebUI/Program.cs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Program.BuildApplicationAsync at line 66. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- XUnityToolkit-WebUI/Program.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:16 — REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in SettingsEndpoints.MapSettingsEndpoints at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: XUnityToolkit-WebUI/Services/ToolboxAgentService.cs XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:97 — XUnityToolkit-WebUI/Services/ToolboxAgentService.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ToolboxAgentService.ChatAsync at line 97. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- XUnityToolkit-WebUI/Services/ToolboxAgentService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:393 — XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in PluginHealthCheckService.CheckDoorstopConfigAsync at line 393. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Updater/Program.cs Updater/Program.cs:4 — Updater/Program.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in top-level statements at line 4. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- Updater/Program.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: XUnityToolkit-WebUI/Services/InstallOrchestrator.cs XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:147 — XUnityToolkit-WebUI/Services/InstallOrchestrator.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in InstallOrchestrator.ExecuteInstallAsync at line 147. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- XUnityToolkit-WebUI/Services/InstallOrchestrator.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:339 — REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in UpdateService.DownloadUpdateAsync at line 339. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:10 — REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in TranslateEndpoints.MapTranslateEndpoints at line 10. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:8 — REDACTED changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in PluginHealthEndpoints.MapPluginHealthEndpoints at line 8. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 09:26:45 +00:00' --until='2026-11-06 09:26:45 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D35 · Change Coupling · Change coupling · ×8
  • Change coupling: InstallProgressDrawer.vue ↔ InstallOrchestrator.cs XUnityToolkit-Vue/src/components/progress/InstallProgressDrawer.vue:1 — `XUnityToolkit-Vue/src/components/progress/InstallProgressDrawer.vue` and `XUnityToolkit-WebUI/Services/InstallOrchestrator.cs` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `8abf73aa` feat: 添加一键安装高级选项,允许用户控制可选安装步骤; `62afc2ca` feat: 添加一键安装高级选项,允许用户控制可选安装步骤; `4efeb033` feat: 插件健康检查功能——三级诊断、启动验证与安装后自动验证 — run `git show` on any of them.
  • Change coupling: FontReplacementView.vue ↔ FontReplacementService.cs XUnityToolkit-Vue/src/views/FontReplacementView.vue:1 — `XUnityToolkit-Vue/src/views/FontReplacementView.vue` and `XUnityToolkit-WebUI/Services/FontReplacementService.cs` change together 62% of the time (13 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `2b30cb87` feat: 发布 v4.4; `4648d6ef` fix: 修复字体替换卡死并优化替换流程; `7fe8d404` refactor: 完善字体替换流程并同步仓库文档 — run `git show` on any of them.
  • Change coupling: games.ts ↔ InstallProgressDrawer.vue XUnityToolkit-Vue/src/api/games.ts:1 — `XUnityToolkit-Vue/src/api/games.ts` and `XUnityToolkit-Vue/src/components/progress/InstallProgressDrawer.vue` change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `8abf73aa` feat: 添加一键安装高级选项,允许用户控制可选安装步骤; `62afc2ca` feat: 添加一键安装高级选项,允许用户控制可选安装步骤; `4efeb033` feat: 插件健康检查功能——三级诊断、启动验证与安装后自动验证 — run `git show` on any of them.
  • Change coupling: types.ts ↔ AppShell.vue XUnityToolkit-Vue/src/api/types.ts:1 — `XUnityToolkit-Vue/src/api/types.ts` and `XUnityToolkit-Vue/src/components/layout/AppShell.vue` change together 52% of the time (12 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `e3d89c13` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `1af88ec8` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `559aaa62` chore: 版本号从 3.7 提升至 3.8 — run `git show` on any of them.
  • Change coupling: FontReplacementView.vue ↔ REDACTED XUnityToolkit-Vue/src/views/FontReplacementView.vue:1 — `XUnityToolkit-Vue/src/views/FontReplacementView.vue` and `REDACTED` change together 50% of the time (10 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `4648d6ef` fix: 修复字体替换卡死并优化替换流程; `7fe8d404` refactor: 完善字体替换流程并同步仓库文档; `24957e14` feat: 自定义字体分离 TTF/TMP 管理,上下文长度改用滑块控件 — run `git show` on any of them.
  • Change coupling: FontGeneratorView.vue ↔ REDACTED XUnityToolkit-Vue/src/views/FontGeneratorView.vue:1 — `XUnityToolkit-Vue/src/views/FontGeneratorView.vue` and `REDACTED` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e3d89c13` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `1af88ec8` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `dd8ea958` feat: v1.5 — 修复6项问题并提升版本号 — run `git show` on any of them.
  • Change coupling: update.ts ↔ REDACTED XUnityToolkit-Vue/src/stores/update.ts:1 — `XUnityToolkit-Vue/src/stores/update.ts` and `REDACTED` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4578ac17` fix: 全面代码审查 — 修复 15 项安全/逻辑/性能问题; `5a4640c5` fix: 全面代码审查 — 修复 15 项安全/逻辑/性能问题; `99b3e488` feat: v2.1 — 修复自动更新功能并增强更新体验 — run `git show` on any of them.
  • Change coupling: AiTranslationView.vue ↔ TranslationMemoryService.cs XUnityToolkit-Vue/src/views/AiTranslationView.vue:1 — `XUnityToolkit-Vue/src/views/AiTranslationView.vue` and `XUnityToolkit-WebUI/Services/TranslationMemoryService.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e3d89c13` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `1af88ec8` feat: 字体生成全字符模式 + 启动优化 + Sakura 模型 + 文档重组; `09d22daf` fix: 第六轮审查修复竞态、安全、生命周期和死代码问题 — run `git show` on any of them.
D3 · God Classes · TooManyMethods · ×7
  • TooManyMethods: LocalLlmService REDACTED — TooManyMethods — 833 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FontReplacementService XUnityToolkit-WebUI/Services/FontReplacementService.cs — TooManyMethods — 1897 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LlmTranslationService XUnityToolkit-WebUI/Services/LlmTranslationService.cs — TooManyMethods — 1441 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ToolboxAgentToolExecutor XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs — TooManyMethods — 731 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ToolboxAgentHostAccessService XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs — TooManyMethods — 551 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PluginDiagnosticArtifactCollector XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs — TooManyMethods — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GameImageService XUnityToolkit-WebUI/Services/GameImageService.cs — TooManyMethods — 499 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×7
  • Duplicated block (9 lines × 2) REDACTED:124 — REDACTED:124-132 | REDACTED:192-200 — 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 `REDACTED:124` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) REDACTED:820 — REDACTED:820-828 | REDACTED:878-886 — 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 `REDACTED:820` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) REDACTED:204 — REDACTED:204-212 | REDACTED:248-256 — 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 `REDACTED:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) XUnityToolkit-WebUI/Services/GameImageService.cs:266 — XUnityToolkit-WebUI/Services/GameImageService.cs:266-274 | XUnityToolkit-WebUI/Services/GameImageService.cs:290-298 — 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 × 2) XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:59 — XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:59-67 | XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:82-90 — 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 `XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:38 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:38-46 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:28-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1034 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1034-1043 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:519-527 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×6
  • NuGet dependencies are not locked RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj:9 — RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked RuntimeFontLoader/Mono/RuntimeFontLoader.Mono.csproj:13 — RuntimeFontLoader/Mono/RuntimeFontLoader.Mono.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked RuntimeFontLoader/ReferenceStubs/UnityEngine.Reference.csproj:11 — RuntimeFontLoader/ReferenceStubs/UnityEngine.Reference.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked TranslatorEndpoint/TranslatorEndpoint.csproj:24 — TranslatorEndpoint/TranslatorEndpoint.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked XUnityToolkit-WebUI.Tests/XUnityToolkit-WebUI.Tests.csproj:18 — XUnityToolkit-WebUI.Tests/XUnityToolkit-WebUI.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:55 — XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
AX2 · Stateful singletons · Stateful singleton · ×5
  • Stateful singleton: FileLoggerProvider XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:12 — `FileLoggerProvider` is a singleton (one shared instance) but mutates instance state outside any lock (_writer, LogBroadcast; e.g. `_writer` at line 113).
  • Stateful singleton: LocalLlmService REDACTED:15 — `LocalLlmService` is a singleton (one shared instance) but mutates instance state outside any lock (_settingsCache, _gpuCache, _error, _process; e.g. `_settingsCache` at line 70).
  • Stateful singleton: TmpFontGeneratorService XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:20 — `TmpFontGeneratorService` is a singleton (one shared instance) but mutates instance state outside any lock (_cts; e.g. `_cts` at line 141).
  • Stateful singleton: UpdateService REDACTED:13 — `UpdateService` is a singleton (one shared instance) but mutates instance state outside any lock (_status, _lastCheckResult, _remoteManifest, _releaseAssets, _availableInfo, _dismissedVersion; e.g. `_status` at line 130).
  • Stateful singleton: SystemTrayService XUnityToolkit-WebUI/Services/SystemTrayService.cs:7 — `SystemTrayService` is a singleton (one shared instance) but mutates instance state outside any lock (_cachedIcon, _openMenuItem; e.g. `_cachedIcon` at line 83).
D3 · God Classes · ClassTooLong · ×5
  • ClassTooLong: TmpFontGeneratorService XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs — ClassTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 285 over it, 1.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: UpdateService REDACTED — ClassTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 147 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PluginHealthCheckService XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs — ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 113 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PluginDiagnosticAgentService XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs — ClassTooLong — 483 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 83 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ToolboxAgentService XUnityToolkit-WebUI/Services/ToolboxAgentService.cs — ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 18 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×5
  • Duplicated block (8 lines × 2) REDACTED:108 — REDACTED:108-115 | XUnityToolkit-WebUI/Services/BepInExLogService.cs:116-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) REDACTED:647 — REDACTED:647-654 | REDACTED:704-711 — 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 `REDACTED:647` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (8 lines × 2) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:313 — XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:313-320 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:323-330 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) REDACTED:29 — REDACTED:29-36 | REDACTED:55-62 — 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 `REDACTED:29` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:64` calls `GetStatus`, `Conflict`, `Fail` and `REDACTED:38` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1007 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1007-1014 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1285-1292 — 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.
AX2 · Stateful singletons · Stateful shared instance · ×4
  • Stateful shared instance: TranslationMemoryBuffer XUnityToolkit-WebUI/Services/LlmTranslationService.cs:32 — `TranslationMemoryBuffer` is not registered, but the singleton `LlmTranslationService` creates it and keeps it in `_translationMemory`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_entries; e.g. `_entries` at line 43).
  • Stateful shared instance: DesktopApp XUnityToolkit-WebUI/App.xaml.cs:8 — `DesktopApp` is not registered, but `Program` creates it and keeps it in the static `_desktopApplication`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_mainWindow, _startupTask; e.g. `_mainWindow` at line 35).
  • Stateful shared instance: MainWindow XUnityToolkit-WebUI/MainWindow.xaml.cs:17 — `MainWindow` is not registered, but the singleton `DesktopApp` creates it and keeps it in `_mainWindow`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_webViewPrepared; e.g. `_webViewPrepared` at line 110).
  • Stateful shared instance: NativeWindowMinimumSizeHook XUnityToolkit-WebUI/MainWindow.xaml.cs:412 — `NativeWindowMinimumSizeHook` is not registered, but the singleton `MainWindow` creates it and keeps it in `_minimumSizeHook`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_attached; e.g. `_attached` at line 440).
D3 · God Classes · FunctionTooLong · ×4
  • FunctionTooLong: update.useUpdateStore XUnityToolkit-Vue/src/stores/update.ts:8 — FunctionTooLong — useUpdateStore runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: localLlm.useLocalLlmStore XUnityToolkit-Vue/src/stores/localLlm.ts:7 — FunctionTooLong — useLocalLlmStore runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: install.useInstallStore XUnityToolkit-Vue/src/stores/install.ts:16 — FunctionTooLong — useInstallStore runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: games.useGamesStore XUnityToolkit-Vue/src/stores/games.ts:7 — FunctionTooLong — useGamesStore runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×4
  • Edited copy of a member (19 corresponding lines) XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:49 — XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:49-67 | XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:71-90 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) REDACTED:42 — REDACTED:42-65 | REDACTED:370-388 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs:555 — XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs:555-575 | XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:534-552 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) XUnityToolkit-WebUI/Services/PluginDetectionService.cs:109 — XUnityToolkit-WebUI/Services/PluginDetectionService.cs:109-127 | XUnityToolkit-WebUI/Services/PluginDetectionService.cs:130-150 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1673 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1673-1679 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1726-1732 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:711 — XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:711-717 | XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:917-923 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) XUnityToolkit-WebUI/Infrastructure/FileHelper.cs:30 — XUnityToolkit-WebUI/Infrastructure/FileHelper.cs:30-36 | REDACTED:153-159 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) XUnityToolkit-WebUI/Services/ScriptTagService.cs:146 — XUnityToolkit-WebUI/Services/ScriptTagService.cs:146-153 | XUnityToolkit-WebUI/Services/TermService.cs:175-181 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) REDACTED:798 — REDACTED:798-809 | REDACTED:856-867 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:798` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (12 lines × 2) REDACTED:27 — REDACTED:27-38 | REDACTED:46-57 — 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 `REDACTED:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) REDACTED:303 — REDACTED:303-314 | REDACTED:42-53 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:303` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) XUnityToolkit-WebUI/MainWindow.xaml.cs:340 — XUnityToolkit-WebUI/MainWindow.xaml.cs:340-351 | XUnityToolkit-WebUI/MainWindow.xaml.cs:355-366 — 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 `XUnityToolkit-WebUI/MainWindow.xaml.cs:340` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×4
  • Duplicated block (10 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:3008 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:3008-3017 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:3030-3039 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:3008` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:536 — XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:536-545 | XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:577-586 — 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 `XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:536` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) REDACTED:43 — REDACTED:43-55 | REDACTED:371-380 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) XUnityToolkit-WebUI/Services/GameImageService.cs:788 — XUnityToolkit-WebUI/Services/GameImageService.cs:788-797 | XUnityToolkit-WebUI/Services/GameImageService.cs:799-808 — 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×4
  • Duplicated block (17 lines × 2 locations) XUnityToolkit-Vue/src/views/FontGeneratorView.vue:208 — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:208 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2 locations) XUnityToolkit-Vue/src/views/FontReplacementView.vue:578 — XUnityToolkit-Vue/src/views/FontReplacementView.vue:578 · XUnityToolkit-Vue/src/views/FontReplacementView.vue:652 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2 locations) XUnityToolkit-Vue/src/views/TermEditorView.vue:329 — XUnityToolkit-Vue/src/views/TermEditorView.vue:329 · XUnityToolkit-Vue/src/views/TermEditorView.vue:354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (17 lines × 2 locations) XUnityToolkit-Vue/src/views/TranslationEditorView.vue:77 — XUnityToolkit-Vue/src/views/TranslationEditorView.vue:77 · XUnityToolkit-Vue/src/views/TranslationEditorView.vue:95 — 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.
AC4 · Keyboard semantics · Anchor without href · ×3
  • Anchor without href XUnityToolkit-Vue/src/components/layout/AppShell.vue:228 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href XUnityToolkit-Vue/src/components/layout/AppShell.vue:246 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href XUnityToolkit-Vue/src/components/layout/AppShell.vue:262 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:17 — REDACTED:17-408 | REDACTED:13-963 | REDACTED:9-651 | REDACTED:17-281 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) XUnityToolkit-WebUI/Services/GameImageService.cs:85 — XUnityToolkit-WebUI/Services/GameImageService.cs:85-123 | XUnityToolkit-WebUI/Services/GameImageService.cs:128-159 | XUnityToolkit-WebUI/Services/GameImageService.cs:162-195 | XUnityToolkit-WebUI/Services/GameImageService.cs:407-474 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) XUnityToolkit-WebUI/Services/GameImageService.cs:494 — XUnityToolkit-WebUI/Services/GameImageService.cs:494-526 | XUnityToolkit-WebUI/Services/GameImageService.cs:581-644 | XUnityToolkit-WebUI/Services/GameImageService.cs:675-708 | XUnityToolkit-WebUI/Services/GameImageService.cs:713-744 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) XUnityToolkit-WebUI/Services/TermService.cs:117 — XUnityToolkit-WebUI/Services/TermService.cs:117-123 | XUnityToolkit-WebUI/Services/TermService.cs:194-200 — 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 `XUnityToolkit-WebUI/Services/TermService.cs:117` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) REDACTED:14 — REDACTED:14-20 | REDACTED:29-35 — 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 `REDACTED:14` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (7 lines × 2) XUnityToolkit-WebUI/Services/CharacterSetService.cs:218 — XUnityToolkit-WebUI/Services/CharacterSetService.cs:218-224 | XUnityToolkit-WebUI/Services/XUnityTranslationFormat.cs:76-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) REDACTED:252 — REDACTED:252-257 | REDACTED:321-326 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:712 — XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:712-717 | XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:918-923 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) REDACTED:773 — REDACTED:773-778 | REDACTED:834-839 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) REDACTED:35 — REDACTED:35-39 | REDACTED:67-71 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) XUnityToolkit-WebUI/Services/ScriptTagService.cs:122 — XUnityToolkit-WebUI/Services/ScriptTagService.cs:122-126 | XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:651-655 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) XUnityToolkit-WebUI/Services/ConfigurationService.cs:165 — XUnityToolkit-WebUI/Services/ConfigurationService.cs:165-169 | XUnityToolkit-WebUI/Services/ConfigurationService.cs:355-363 — 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 `XUnityToolkit-WebUI/Services/ConfigurationService.cs:165` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×3
  • Sync-over-async blocking — 2 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking XUnityToolkit-WebUI/Program.cs:594 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking XUnityToolkit-WebUI/Program.cs:604 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×3
  • Duplicated block (8 lines × 2 locations) XUnityToolkit-Vue/src/stores/localLlm.ts:67 — XUnityToolkit-Vue/src/stores/localLlm.ts:67 · XUnityToolkit-Vue/src/stores/log.ts:77 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (8 lines × 2 locations) XUnityToolkit-Vue/src/views/FontReplacementView.vue:40 — XUnityToolkit-Vue/src/views/FontReplacementView.vue:40 · XUnityToolkit-Vue/src/views/PluginManagerView.vue:20 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2 locations) XUnityToolkit-Vue/src/views/GameDetailView.vue:69 — XUnityToolkit-Vue/src/views/GameDetailView.vue:69 · XUnityToolkit-Vue/src/views/TranslationEditorView.vue:39 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
X1 · Async correctness · Blocking `File.WriteAllText` inside an `async` method · ×3
  • Blocking `File.WriteAllText` inside an `async` method REDACTED:297 — `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `File.WriteAllText` inside an `async` method REDACTED:1338 — `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `File.WriteAllText` inside an `async` method XUnityToolkit-WebUI/Services/PluginPackageService.cs:239 — `File.WriteAllText` blocks the thread on I/O while `File.WriteAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
D12 · Dependency Hygiene · Deprecated · ×2
  • Deprecated: xunit RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj:10 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
  • Deprecated: xunit XUnityToolkit-WebUI.Tests/XUnityToolkit-WebUI.Tests.csproj:19 — xunit 2.9.3 — Legacy — the publisher's replacement is `xunit.v3`; that is the next major line under a new package id, so the move is a breaking rename rather than a version bump — budget for API changes in the code that uses it, not only the reference swap.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×2
  • Edited copy of a member (20 corresponding lines) XUnityToolkit-WebUI/Services/CharacterSetService.cs:227 — XUnityToolkit-WebUI/Services/CharacterSetService.cs:227-246 | XUnityToolkit-WebUI/Services/ConfigurationService.cs:509-539 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) XUnityToolkit-WebUI/Services/ScriptTagService.cs:116 — XUnityToolkit-WebUI/Services/ScriptTagService.cs:116-135 | XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:642-667 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) XUnityToolkit-WebUI/Services/GameImageService.cs:31 — XUnityToolkit-WebUI/Services/GameImageService.cs:31-52 | XUnityToolkit-WebUI/Services/GameImageService.cs:651-672 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) Updater/Program.cs:137 — Updater/Program.cs:137-162 | Updater/Program.cs:170-191 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) XUnityToolkit-WebUI/Services/GameImageService.cs:287 — XUnityToolkit-WebUI/Services/GameImageService.cs:287-312 | XUnityToolkit-WebUI/Services/GameImageService.cs:315-341 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) XUnityToolkit-WebUI/Services/GameImageService.cs:198 — XUnityToolkit-WebUI/Services/GameImageService.cs:198-223 | XUnityToolkit-WebUI/Services/GameImageService.cs:747-772 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) XUnityToolkit-WebUI/Services/GlossaryExtractionService.cs:339 — XUnityToolkit-WebUI/Services/GlossaryExtractionService.cs:339-359 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2281-2302 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) XUnityToolkit-WebUI/Infrastructure/LlmResponseParser.cs:46 — XUnityToolkit-WebUI/Infrastructure/LlmResponseParser.cs:46-69 | XUnityToolkit-WebUI/Infrastructure/LlmResponseParser.cs:76-96 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:23 — XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:23-45 | XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:121-134 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1822 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1822-1835 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1883-1896 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) XUnityToolkit-WebUI/Services/TermMatchingService.cs:158 — XUnityToolkit-WebUI/Services/TermMatchingService.cs:158-166 | XUnityToolkit-WebUI/Services/TermMatchingService.cs:169-176 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) XUnityToolkit-WebUI/Services/CharacterSetService.cs:217 — XUnityToolkit-WebUI/Services/CharacterSetService.cs:217-224 | XUnityToolkit-WebUI/Services/XUnityTranslationFormat.cs:75-82 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:712 — XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:712-717 | XUnityToolkit-WebUI/Services/BepInExLogService.cs:76-81 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) XUnityToolkit-WebUI/Services/PluginConnectionRegistry.cs:74 — XUnityToolkit-WebUI/Services/PluginConnectionRegistry.cs:74-79 | XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:602-607 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×2
  • Duplicated block (29–30 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:824 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:824-852 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1038-1067 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:824` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (29–30 lines × 2) XUnityToolkit-WebUI/Services/GameImageService.cs:531 — XUnityToolkit-WebUI/Services/GameImageService.cs:531-560 | XUnityToolkit-WebUI/Services/WebImageSearchService.cs:83-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/GameImageService.cs:531` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24 lines × 3) · ×2
  • Duplicated block (24 lines × 3) REDACTED:384 — REDACTED:384-407 | REDACTED:263-286 | REDACTED:568-591 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:384` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (24 lines × 3) REDACTED:441 — REDACTED:441-464 | REDACTED:106-129 | REDACTED:323-346 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:441` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1632 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1632-1647 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2026-2041 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1632` 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 (16 lines × 2) XUnityToolkit-WebUI/Services/GameImageService.cs:37 — XUnityToolkit-WebUI/Services/GameImageService.cs:37-52 | XUnityToolkit-WebUI/Services/GameImageService.cs:657-672 — 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 `XUnityToolkit-WebUI/Services/GameImageService.cs:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) REDACTED:194 — REDACTED:194-208 | REDACTED:253-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2826 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:2826-2840 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2932-2946 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:2826` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×2
  • Duplicated block (16 lines × 3) REDACTED:329 — REDACTED:329-344 | REDACTED:67-82 | REDACTED:530-545 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:329` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (16 lines × 3) REDACTED:425 — REDACTED:425-440 | REDACTED:305-322 | REDACTED:608-623 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:425` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2378 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2378-2391 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2405-2418 — 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 `XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2378` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1537 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1537-1550 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1927-1941 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1537` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1551` calls `Create` and `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1943` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) REDACTED:291 — REDACTED:291-301 | REDACTED:30-40 | REDACTED:494-504 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:291` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (11 lines × 3) XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:374 — XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:374-384 | XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:494-504 | XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:865-875 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:374` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) XUnityToolkit-WebUI/Services/FontReplacementService.cs:247 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:247-256 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2826-2835 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2932-2941 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/FontReplacementService.cs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 3) XUnityToolkit-WebUI/Services/FontReplacementService.cs:828 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:828-837 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1043-1052 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:529-539 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/FontReplacementService.cs:828` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) XUnityToolkit-WebUI/Services/PluginPackageService.cs:83 — XUnityToolkit-WebUI/Services/PluginPackageService.cs:83-93 | XUnityToolkit-WebUI/Services/PluginPackageService.cs:96-106 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:708 — XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:708-718 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:734-744 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) REDACTED:12 — REDACTED:12-22 | REDACTED:43-54 — 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 `REDACTED:12` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (11–12 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2354 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:2354-2364 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2392-2403 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×2
  • Duplicated block (16 lines × 2 locations) XUnityToolkit-Vue/src/stores/aiTranslation.ts:27 — XUnityToolkit-Vue/src/stores/aiTranslation.ts:27 · XUnityToolkit-Vue/src/stores/log.ts:89 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (16 lines × 2 locations) XUnityToolkit-Vue/src/stores/install.ts:101 — XUnityToolkit-Vue/src/stores/install.ts:101 · XUnityToolkit-Vue/src/stores/install.ts:136 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×2
  • Duplicated block (14 lines × 2 locations) XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:280 — XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:280 · XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:298 — 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 (14 lines × 2 locations) XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:66 — XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:66 · XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:81 — 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.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×2
  • Duplicated block (6 lines × 2 locations) XUnityToolkit-Vue/src/api/games.ts:109 — XUnityToolkit-Vue/src/api/games.ts:109 · XUnityToolkit-Vue/src/views/GameDetailView.vue:513 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (6 lines × 2 locations) XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:50 — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:50 · XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:25 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×2
  • Duplicated block (5 lines × 2 locations) XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:26 — XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:26 · XUnityToolkit-Vue/src/components/health/PluginDiagnosticReport.vue:32 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2 locations) XUnityToolkit-Vue/src/views/AiTranslationView.vue:520 — XUnityToolkit-Vue/src/views/AiTranslationView.vue:520 · XUnityToolkit-Vue/src/views/AiTranslationView.vue:528 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
X1 · Async correctness · Blocking `File.ReadAllText` inside an `async` method · ×2
  • Blocking `File.ReadAllText` inside an `async` method XUnityToolkit-WebUI/Program.cs:124 — `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `File.ReadAllText` inside an `async` method REDACTED:255 — `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×2
  • Sync-over-async (deadlock risk) XUnityToolkit-WebUI/Program.cs:594 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) XUnityToolkit-WebUI/Program.cs:604 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
X1 · Async correctness · Blocking `File.ReadAllBytes` inside an `async` method · ×2
  • Blocking `File.ReadAllBytes` inside an `async` method XUnityToolkit-WebUI/Services/FontReplacementService.cs:990 — `File.ReadAllBytes` blocks the thread on I/O while `File.ReadAllBytesAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `File.ReadAllBytes` inside an `async` method XUnityToolkit-WebUI/Services/FontReplacementService.cs:1001 — `File.ReadAllBytes` blocks the thread on I/O while `File.ReadAllBytesAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X1 · Async correctness · Blocking `StreamReader.ReadToEnd` inside an `async` method · ×2
  • Blocking `StreamReader.ReadToEnd` inside an `async` method XUnityToolkit-WebUI/Services/PluginPackageService.cs:151 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
  • Blocking `StreamReader.ReadToEnd` inside an `async` method XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:821 — `StreamReader.ReadToEnd` blocks the thread on I/O while `StreamReader.ReadToEndAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X2 · Cancellation propagation · Async method without CancellationToken · ×2
  • Async method without CancellationToken: StartBackendAndWebViewAsync XUnityToolkit-WebUI/App.xaml.cs:47 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BroadcastFontReplacementProgressAsync REDACTED:15 — No CancellationToken parameter — this work can't be stopped early once started.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×2
  • Untrusted text written into markup unescaped XUnityToolkit-Vue/src/views/BepInExLogView.vue:308 — `highlightText(line.text)` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped XUnityToolkit-Vue/src/views/SettingsView.vue:663 — `changelogHtml` is text this program did not author, and it is written into the text of an element through Vue's `v-html` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC3 · Page structure · Heading level jumps from h1 to h3 · ×1
  • Heading level jumps from h1 to h3 XUnityToolkit-Vue/src/views/LibraryView.vue:255 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×1
  • Focus outline removed in CSS without a :focus replacement XUnityToolkit-Vue/src/views/LogView.vue:335 — `.level-pill` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AX2 · Stateful singletons · Process-global static state · ×1
  • Process-global static state: RuntimeFontBootstrap RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:13 — `RuntimeFontBootstrap` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_activeFont, _overridePrefix; e.g. `_activeFont` at line 97). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
D1 · Cyclomatic Complexity · LlmTranslationService.TranslateDetailedAsync (cyclomatic 170) · ×1
  • LlmTranslationService.TranslateDetailedAsync (cyclomatic 170) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:240 — LlmTranslationService.TranslateDetailedAsync has cyclomatic complexity 170 (threshold 15). Of this number, 169 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GameEndpoints.MapGameEndpoints (cyclomatic 115) · ×1
  • GameEndpoints.MapGameEndpoints (cyclomatic 115) REDACTED:12 — GameEndpoints.MapGameEndpoints has cyclomatic complexity 115 (threshold 15). Most of this is not in the body itself: 1 of the 115 points is its own statement and the rest belongs to 33 function literals inside it that branch (lines 181, 110, 528, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ImageEndpoints.MapImageEndpoints (cyclomatic 73) · ×1
  • ImageEndpoints.MapImageEndpoints (cyclomatic 73) REDACTED:8 — ImageEndpoints.MapImageEndpoints has cyclomatic complexity 73 (threshold 15). Most of this is not in the body itself: 1 of the 73 points is its own statement and the rest belongs to 22 function literals inside it that branch (lines 66, 529, 29, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · TmpFontGeneratorService.InjectIntoTemplate (cyclomatic 65) · ×1
  • TmpFontGeneratorService.InjectIntoTemplate (cyclomatic 65) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:508 — TmpFontGeneratorService.InjectIntoTemplate has cyclomatic complexity 65 (threshold 15). Of this number, 64 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FontGenerationEndpoints.MapFontGenerationEndpoints (cyclomatic 53) · ×1
  • FontGenerationEndpoints.MapFontGenerationEndpoints (cyclomatic 53) REDACTED:16 — FontGenerationEndpoints.MapFontGenerationEndpoints has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 1 of the 53 points is its own statement and the rest belongs to 14 function literals inside it that branch (lines 250, 286, 154, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · ToolboxAgentToolExecutor.ApplySafeSetting (cyclomatic 49) · ×1
  • ToolboxAgentToolExecutor.ApplySafeSetting (cyclomatic 49) XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:493 — ToolboxAgentToolExecutor.ApplySafeSetting has cyclomatic complexity 49 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · top-level statements (cyclomatic 41) · ×1
  • top-level statements (cyclomatic 41) Updater/Program.cs:4 — top-level statements has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FontReplacementService.ReplaceFontsAsync (cyclomatic 41) · ×1
  • FontReplacementService.ReplaceFontsAsync (cyclomatic 41) XUnityToolkit-WebUI/Services/FontReplacementService.cs:948 — FontReplacementService.ReplaceFontsAsync has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 13 of the 41 points are its own statements and the rest belongs to one function literal inside it that branches (line 1023). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FontReplacementEndpoints.MapFontReplacementEndpoints (cyclomatic 38) · ×1
  • FontReplacementEndpoints.MapFontReplacementEndpoints (cyclomatic 38) REDACTED:63 — FontReplacementEndpoints.MapFontReplacementEndpoints has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 183, 79, 227, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · BepInExPluginEndpoints.MapBepInExPluginEndpoints (cyclomatic 33) · ×1
  • BepInExPluginEndpoints.MapBepInExPluginEndpoints (cyclomatic 33) REDACTED:15 — BepInExPluginEndpoints.MapBepInExPluginEndpoints has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 37, 80, 123, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · Program.BuildApplicationAsync (cyclomatic 32) · ×1
  • Program.BuildApplicationAsync (cyclomatic 32) XUnityToolkit-WebUI/Program.cs:66 — Program.BuildApplicationAsync has cyclomatic complexity 32 (threshold 15). Of this number, 18 points are the body's own statements and 14 belong to 7 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · TmpFontGeneratorService.GenerateCore (cyclomatic 29) · ×1
  • TmpFontGeneratorService.GenerateCore (cyclomatic 29) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:204 — TmpFontGeneratorService.GenerateCore has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ToolboxAgentHostAccessService.ParseOperationsAsync (cyclomatic 29) · ×1
  • ToolboxAgentHostAccessService.ParseOperationsAsync (cyclomatic 29) XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:333 — ToolboxAgentHostAccessService.ParseOperationsAsync has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UpdateService.DownloadUpdateAsync (cyclomatic 29) · ×1
  • UpdateService.DownloadUpdateAsync (cyclomatic 29) REDACTED:339 — UpdateService.DownloadUpdateAsync has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FontReplacementService.ProcessBundleFile (cyclomatic 28) · ×1
  • FontReplacementService.ProcessBundleFile (cyclomatic 28) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2059 — FontReplacementService.ProcessBundleFile has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ToolboxAgentService.ChatAsync (cyclomatic 28) · ×1
  • ToolboxAgentService.ChatAsync (cyclomatic 28) XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:97 — ToolboxAgentService.ChatAsync has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LLMTranslateEndpoint.ParseTranslationsArray (cyclomatic 27) · ×1
  • LLMTranslateEndpoint.ParseTranslationsArray (cyclomatic 27) TranslatorEndpoint/LLMTranslateEndpoint.cs:334 — LLMTranslateEndpoint.ParseTranslationsArray has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FileExplorerEndpoints.MapFileExplorerEndpoints (cyclomatic 26) · ×1
  • FileExplorerEndpoints.MapFileExplorerEndpoints (cyclomatic 26) REDACTED:10 — FileExplorerEndpoints.MapFileExplorerEndpoints has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 83, 54, 14, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · SettingsEndpoints.MapSettingsEndpoints (cyclomatic 25) · ×1
  • SettingsEndpoints.MapSettingsEndpoints (cyclomatic 25) REDACTED:16 — SettingsEndpoints.MapSettingsEndpoints has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 120, 166, 223, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FontReplacementService.ProcessBundleFile (cyclomatic 25) · ×1
  • FontReplacementService.ProcessBundleFile (cyclomatic 25) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1665 — FontReplacementService.ProcessBundleFile has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · InstallOrchestrator.ExecuteInstallAsync (cyclomatic 25) · ×1
  • InstallOrchestrator.ExecuteInstallAsync (cyclomatic 25) XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:147 — InstallOrchestrator.ExecuteInstallAsync has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FontReplacementService.ScanAssetsInstance (cyclomatic 24) · ×1
  • FontReplacementService.ScanAssetsInstance (cyclomatic 24) XUnityToolkit-WebUI/Services/FontReplacementService.cs:310 — FontReplacementService.ScanAssetsInstance has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LocalLlmService.DownloadLlamaAsync (cyclomatic 24) · ×1
  • LocalLlmService.DownloadLlamaAsync (cyclomatic 24) REDACTED:1216 — LocalLlmService.DownloadLlamaAsync has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PluginDiagnosticAgentService.ValidateRepairPlan (cyclomatic 24) · ×1
  • PluginDiagnosticAgentService.ValidateRepairPlan (cyclomatic 24) XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs:351 — PluginDiagnosticAgentService.ValidateRepairPlan has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · SimpleJson.ExtractString (cyclomatic 23) · ×1
  • SimpleJson.ExtractString (cyclomatic 23) TranslatorEndpoint/ToolkitConnectionManager.cs:435 — SimpleJson.ExtractString has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UpdateService.CheckForUpdateAsync (cyclomatic 23) · ×1
  • UpdateService.CheckForUpdateAsync (cyclomatic 23) REDACTED:140 — UpdateService.CheckForUpdateAsync has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TranslateEndpoints.MapTranslateEndpoints (cyclomatic 22) · ×1
  • TranslateEndpoints.MapTranslateEndpoints (cyclomatic 22) REDACTED:10 — TranslateEndpoints.MapTranslateEndpoints has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 12, 42, 165, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FontReplacementService.ReplaceFontsAsync (cyclomatic 22) · ×1
  • FontReplacementService.ReplaceFontsAsync (cyclomatic 22) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1250 — FontReplacementService.ReplaceFontsAsync has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1299, 1279). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PluginHealthEndpoints.MapPluginHealthEndpoints (cyclomatic 20) · ×1
  • PluginHealthEndpoints.MapPluginHealthEndpoints (cyclomatic 20) REDACTED:8 — PluginHealthEndpoints.MapPluginHealthEndpoints has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 86, 54, 28, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FontReplacementService.ScanFontsAsync (cyclomatic 20) · ×1
  • FontReplacementService.ScanFontsAsync (cyclomatic 20) XUnityToolkit-WebUI/Services/FontReplacementService.cs:136 — FontReplacementService.ScanFontsAsync has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 176). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FontReplacementService.ClearAddressablesCrcAsync (cyclomatic 20) · ×1
  • FontReplacementService.ClearAddressablesCrcAsync (cyclomatic 20) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2732 — FontReplacementService.ClearAddressablesCrcAsync has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 2813). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PluginPackageService.ImportAsync (cyclomatic 20) · ×1
  • PluginPackageService.ImportAsync (cyclomatic 20) XUnityToolkit-WebUI/Services/PluginPackageService.cs:135 — PluginPackageService.ImportAsync has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RunDataReset (cyclomatic 19) · ×1
  • RunDataReset (cyclomatic 19) Updater/Program.cs:286 — RunDataReset has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FontReplacementService.LoadTmpSourcePayload (cyclomatic 19) · ×1
  • FontReplacementService.LoadTmpSourcePayload (cyclomatic 19) XUnityToolkit-WebUI/Services/FontReplacementService.cs:822 — FontReplacementService.LoadTmpSourcePayload has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PluginHealthCheckService.CheckDoorstopConfigAsync (cyclomatic 19) · ×1
  • PluginHealthCheckService.CheckDoorstopConfigAsync (cyclomatic 19) XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:393 — PluginHealthCheckService.CheckDoorstopConfigAsync has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FontReplacementService.ReplaceSingleFont (cyclomatic 18) · ×1
  • FontReplacementService.ReplaceSingleFont (cyclomatic 18) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2307 — FontReplacementService.ReplaceSingleFont has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LocalLlmService.StartAsync (cyclomatic 18) · ×1
  • LocalLlmService.StartAsync (cyclomatic 18) REDACTED:358 — LocalLlmService.StartAsync has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PluginAutoRepairService.SetIniValue (cyclomatic 18) · ×1
  • PluginAutoRepairService.SetIniValue (cyclomatic 18) XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:296 — PluginAutoRepairService.SetIniValue has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TermAuditService.AuditTranslation (cyclomatic 18) · ×1
  • TermAuditService.AuditTranslation (cyclomatic 18) XUnityToolkit-WebUI/Services/TermAuditService.cs:9 — TermAuditService.AuditTranslation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GameEndpoints.DetectAndAddAsync (cyclomatic 17) · ×1
  • GameEndpoints.DetectAndAddAsync (cyclomatic 17) REDACTED:969 — GameEndpoints.DetectAndAddAsync has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ToolboxAgentEndpoints.MapToolboxAgentEndpoints (cyclomatic 17) · ×1
  • ToolboxAgentEndpoints.MapToolboxAgentEndpoints (cyclomatic 17) REDACTED:8 — ToolboxAgentEndpoints.MapToolboxAgentEndpoints has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 37, 76, 19, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · LocalLlmLaunchPathResolver.Resolve (cyclomatic 17) · ×1
  • LocalLlmLaunchPathResolver.Resolve (cyclomatic 17) XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:37 — LocalLlmLaunchPathResolver.Resolve has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RuntimeFontBootstrap.Initialize (cyclomatic 17) · ×1
  • RuntimeFontBootstrap.Initialize (cyclomatic 17) RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:29 — RuntimeFontBootstrap.Initialize has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RuntimeFontBootstrap.TryCreateRuntimeFont (cyclomatic 17) · ×1
  • RuntimeFontBootstrap.TryCreateRuntimeFont (cyclomatic 17) RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:141 — RuntimeFontBootstrap.TryCreateRuntimeFont has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · games.useGamesStore.loadPreferences (cyclomatic 17) · ×1
  • games.useGamesStore.loadPreferences (cyclomatic 17) XUnityToolkit-Vue/src/stores/games.ts:72 — games.useGamesStore.loadPreferences has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · LLMTranslateEndpoint.Translate (cyclomatic 16) · ×1
  • LLMTranslateEndpoint.Translate (cyclomatic 16) TranslatorEndpoint/LLMTranslateEndpoint.cs:118 — LLMTranslateEndpoint.Translate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConfigurationService.ApplyModifications (cyclomatic 16) · ×1
  • ConfigurationService.ApplyModifications (cyclomatic 16) XUnityToolkit-WebUI/Services/ConfigurationService.cs:383 — ConfigurationService.ApplyModifications has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RuntimeTmpFontService.InstallAsync (cyclomatic 16) · ×1
  • RuntimeTmpFontService.InstallAsync (cyclomatic 16) XUnityToolkit-WebUI/Services/RuntimeTmpFontService.cs:27 — RuntimeTmpFontService.InstallAsync has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RuntimeFontConfig.Load (cyclomatic 16) · ×1
  • RuntimeFontConfig.Load (cyclomatic 16) RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:474 — RuntimeFontConfig.Load has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · useAddGameFlow.useAddGameFlow.addGameCore (cyclomatic 16) · ×1
  • useAddGameFlow.useAddGameFlow.addGameCore (cyclomatic 16) XUnityToolkit-Vue/src/composables/useAddGameFlow.ts:26 — useAddGameFlow.useAddGameFlow.addGameCore has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · No assertions · ×1
  • No assertions: ValidateAppPackageInventory_ShouldAcceptMatchingPackageAndManifest XUnityToolkit-WebUI.Tests/Services/UpdateManifestFileSetTests.cs:197 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D17 · Explicit Debt · DeadPreprocessorBranch · ×1
  • DeadPreprocessorBranch XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:166 — #if false — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
D2 · Cognitive Complexity · LlmTranslationService.TranslateDetailedAsync (cognitive 446) · ×1
  • LlmTranslationService.TranslateDetailedAsync (cognitive 446) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:240 — LlmTranslationService.TranslateDetailedAsync has cognitive complexity 446 (threshold 15). Of this number, 445 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TmpFontGeneratorService.InjectIntoTemplate (cognitive 166) · ×1
  • TmpFontGeneratorService.InjectIntoTemplate (cognitive 166) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:508 — TmpFontGeneratorService.InjectIntoTemplate has cognitive complexity 166 (threshold 15). Of this number, 165 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · GameEndpoints.MapGameEndpoints (cognitive 127) · ×1
  • GameEndpoints.MapGameEndpoints (cognitive 127) REDACTED:12 — GameEndpoints.MapGameEndpoints has cognitive complexity 127 (threshold 15). None of this is in the body itself: all 127 points belong to 33 function literals inside it that branch (lines 181, 110, 30, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.ReplaceFontsAsync (cognitive 81) · ×1
  • FontReplacementService.ReplaceFontsAsync (cognitive 81) XUnityToolkit-WebUI/Services/FontReplacementService.cs:948 — FontReplacementService.ReplaceFontsAsync has cognitive complexity 81 (threshold 15). Of this number, 18 points are the body's own statements and 63 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ImageEndpoints.MapImageEndpoints (cognitive 72) · ×1
  • ImageEndpoints.MapImageEndpoints (cognitive 72) REDACTED:8 — ImageEndpoints.MapImageEndpoints has cognitive complexity 72 (threshold 15). None of this is in the body itself: all 72 points belong to 22 function literals inside it that branch (lines 66, 529, 29, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.ProcessBundleFile (cognitive 68) · ×1
  • FontReplacementService.ProcessBundleFile (cognitive 68) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2059 — FontReplacementService.ProcessBundleFile has cognitive complexity 68 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontGenerationEndpoints.MapFontGenerationEndpoints (cognitive 61) · ×1
  • FontGenerationEndpoints.MapFontGenerationEndpoints (cognitive 61) REDACTED:16 — FontGenerationEndpoints.MapFontGenerationEndpoints has cognitive complexity 61 (threshold 15). None of this is in the body itself: all 61 points belong to 14 function literals inside it that branch (lines 154, 250, 286, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.ScanAssetsInstance (cognitive 59) · ×1
  • FontReplacementService.ScanAssetsInstance (cognitive 59) XUnityToolkit-WebUI/Services/FontReplacementService.cs:310 — FontReplacementService.ScanAssetsInstance has cognitive complexity 59 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ProcessBundleFile (cognitive 59) · ×1
  • FontReplacementService.ProcessBundleFile (cognitive 59) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1665 — FontReplacementService.ProcessBundleFile has cognitive complexity 59 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginPackageService.ImportAsync (cognitive 57) · ×1
  • PluginPackageService.ImportAsync (cognitive 57) XUnityToolkit-WebUI/Services/PluginPackageService.cs:135 — PluginPackageService.ImportAsync has cognitive complexity 57 (threshold 15). Of this number, 35 points are the body's own statements and 22 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · top-level statements (cognitive 56) · ×1
  • top-level statements (cognitive 56) Updater/Program.cs:4 — top-level statements has cognitive complexity 56 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TermAuditService.AuditTranslation (cognitive 56) · ×1
  • TermAuditService.AuditTranslation (cognitive 56) XUnityToolkit-WebUI/Services/TermAuditService.cs:9 — TermAuditService.AuditTranslation has cognitive complexity 56 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateService.DownloadUpdateAsync (cognitive 54) · ×1
  • UpdateService.DownloadUpdateAsync (cognitive 54) REDACTED:339 — UpdateService.DownloadUpdateAsync has cognitive complexity 54 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ClearAddressablesCrcAsync (cognitive 46) · ×1
  • FontReplacementService.ClearAddressablesCrcAsync (cognitive 46) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2732 — FontReplacementService.ClearAddressablesCrcAsync has cognitive complexity 46 (threshold 15). Most of this is not in the body itself: 13 of the 46 points are its own statements and the rest belongs to one function literal inside it that branches (line 2813). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · InstallOrchestrator.ExecuteInstallAsync (cognitive 46) · ×1
  • InstallOrchestrator.ExecuteInstallAsync (cognitive 46) XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:147 — InstallOrchestrator.ExecuteInstallAsync has cognitive complexity 46 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolboxAgentService.ChatAsync (cognitive 46) · ×1
  • ToolboxAgentService.ChatAsync (cognitive 46) XUnityToolkit-WebUI/Services/ToolboxAgentService.cs:97 — ToolboxAgentService.ChatAsync has cognitive complexity 46 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Program.BuildApplicationAsync (cognitive 44) · ×1
  • Program.BuildApplicationAsync (cognitive 44) XUnityToolkit-WebUI/Program.cs:66 — Program.BuildApplicationAsync has cognitive complexity 44 (threshold 15). Of this number, 23 points are the body's own statements and 21 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TmpFontGeneratorService.GenerateCore (cognitive 43) · ×1
  • TmpFontGeneratorService.GenerateCore (cognitive 43) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:204 — TmpFontGeneratorService.GenerateCore has cognitive complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LLMTranslateEndpoint.ParseTranslationsArray (cognitive 38) · ×1
  • LLMTranslateEndpoint.ParseTranslationsArray (cognitive 38) TranslatorEndpoint/LLMTranslateEndpoint.cs:334 — LLMTranslateEndpoint.ParseTranslationsArray has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementEndpoints.MapFontReplacementEndpoints (cognitive 38) · ×1
  • FontReplacementEndpoints.MapFontReplacementEndpoints (cognitive 38) REDACTED:63 — FontReplacementEndpoints.MapFontReplacementEndpoints has cognitive complexity 38 (threshold 15). None of this is in the body itself: all 38 points belong to 8 function literals inside it that branch (lines 79, 183, 227, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · ToolboxAgentHostAccessService.ParseOperationsAsync (cognitive 38) · ×1
  • ToolboxAgentHostAccessService.ParseOperationsAsync (cognitive 38) XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:333 — ToolboxAgentHostAccessService.ParseOperationsAsync has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalLlmService.DownloadLlamaAsync (cognitive 37) · ×1
  • LocalLlmService.DownloadLlamaAsync (cognitive 37) REDACTED:1216 — LocalLlmService.DownloadLlamaAsync has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileExplorerEndpoints.MapFileExplorerEndpoints (cognitive 33) · ×1
  • FileExplorerEndpoints.MapFileExplorerEndpoints (cognitive 33) REDACTED:10 — FileExplorerEndpoints.MapFileExplorerEndpoints has cognitive complexity 33 (threshold 15). None of this is in the body itself: all 33 points belong to 5 function literals inside it that branch (lines 83, 14, 54, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · BepInExPluginEndpoints.MapBepInExPluginEndpoints (cognitive 32) · ×1
  • BepInExPluginEndpoints.MapBepInExPluginEndpoints (cognitive 32) REDACTED:15 — BepInExPluginEndpoints.MapBepInExPluginEndpoints has cognitive complexity 32 (threshold 15). None of this is in the body itself: all 32 points belong to 6 function literals inside it that branch (lines 37, 80, 123, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.ScanFontsAsync (cognitive 32) · ×1
  • FontReplacementService.ScanFontsAsync (cognitive 32) XUnityToolkit-WebUI/Services/FontReplacementService.cs:136 — FontReplacementService.ScanFontsAsync has cognitive complexity 32 (threshold 15). Most of this is not in the body itself: 5 of the 32 points are its own statements and the rest belongs to one function literal inside it that branches (line 176). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.LoadTmpSourcePayload (cognitive 32) · ×1
  • FontReplacementService.LoadTmpSourcePayload (cognitive 32) XUnityToolkit-WebUI/Services/FontReplacementService.cs:822 — FontReplacementService.LoadTmpSourcePayload has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ReplaceFontsAsync (cognitive 32) · ×1
  • FontReplacementService.ReplaceFontsAsync (cognitive 32) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1250 — FontReplacementService.ReplaceFontsAsync has cognitive complexity 32 (threshold 15). Most of this is not in the body itself: 6 of the 32 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 1299, 1279). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · UpdateService.CheckForUpdateAsync (cognitive 32) · ×1
  • UpdateService.CheckForUpdateAsync (cognitive 32) REDACTED:140 — UpdateService.CheckForUpdateAsync has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LLMTranslateEndpoint.Translate (cognitive 31) · ×1
  • LLMTranslateEndpoint.Translate (cognitive 31) TranslatorEndpoint/LLMTranslateEndpoint.cs:118 — LLMTranslateEndpoint.Translate has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConfigurationService.ApplyModifications (cognitive 31) · ×1
  • ConfigurationService.ApplyModifications (cognitive 31) XUnityToolkit-WebUI/Services/ConfigurationService.cs:383 — ConfigurationService.ApplyModifications has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LlmTranslationService.ApplyGlossaryPostProcess (cognitive 27) · ×1
  • LlmTranslationService.ApplyGlossaryPostProcess (cognitive 27) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2051 — LlmTranslationService.ApplyGlossaryPostProcess has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginAutoRepairService.SetIniValue (cognitive 27) · ×1
  • PluginAutoRepairService.SetIniValue (cognitive 27) XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:296 — PluginAutoRepairService.SetIniValue has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ProcessLooseFile (cognitive 26) · ×1
  • FontReplacementService.ProcessLooseFile (cognitive 26) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1915 — FontReplacementService.ProcessLooseFile has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LlmTranslationService.TranslateBatchAsync (cognitive 26) · ×1
  • LlmTranslationService.TranslateBatchAsync (cognitive 26) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1185 — LlmTranslationService.TranslateBatchAsync has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginPackageService.ExportAsync (cognitive 26) · ×1
  • PluginPackageService.ExportAsync (cognitive 26) XUnityToolkit-WebUI/Services/PluginPackageService.cs:26 — PluginPackageService.ExportAsync has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RunDataReset (cognitive 25) · ×1
  • RunDataReset (cognitive 25) Updater/Program.cs:286 — RunDataReset has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TranslateEndpoints.MapTranslateEndpoints (cognitive 25) · ×1
  • TranslateEndpoints.MapTranslateEndpoints (cognitive 25) REDACTED:10 — TranslateEndpoints.MapTranslateEndpoints has cognitive complexity 25 (threshold 15). None of this is in the body itself: all 25 points belong to 6 function literals inside it that branch (lines 12, 42, 165, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · LlmTranslationService.ApplyDoNotTranslateReplacements (cognitive 25) · ×1
  • LlmTranslationService.ApplyDoNotTranslateReplacements (cognitive 25) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1758 — LlmTranslationService.ApplyDoNotTranslateReplacements has cognitive complexity 25 (threshold 15). Of this number, 21 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TmpFontGeneratorService.AutoSizeSamplingSize (cognitive 25) · ×1
  • TmpFontGeneratorService.AutoSizeSamplingSize (cognitive 25) XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:1058 — TmpFontGeneratorService.AutoSizeSamplingSize has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · useAddGameFlow.useAddGameFlow.addGameCore (cognitive 25) · ×1
  • useAddGameFlow.useAddGameFlow.addGameCore (cognitive 25) XUnityToolkit-Vue/src/composables/useAddGameFlow.ts:26 — useAddGameFlow.useAddGameFlow.addGameCore has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 3 (5 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CharacterSetService.ResolveCharactersAsync (cognitive 24) · ×1
  • CharacterSetService.ResolveCharactersAsync (cognitive 24) XUnityToolkit-WebUI/Services/CharacterSetService.cs:16 — CharacterSetService.ResolveCharactersAsync has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ReplaceSingleFont (cognitive 24) · ×1
  • FontReplacementService.ReplaceSingleFont (cognitive 24) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2307 — FontReplacementService.ReplaceSingleFont has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginDiagnosticArtifactCollector.ReadSelectedAsync (cognitive 24) · ×1
  • PluginDiagnosticArtifactCollector.ReadSelectedAsync (cognitive 24) XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:123 — PluginDiagnosticArtifactCollector.ReadSelectedAsync has cognitive complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TranslationMemoryService.TryFuzzyMatch (cognitive 24) · ×1
  • TranslationMemoryService.TryFuzzyMatch (cognitive 24) XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:353 — TranslationMemoryService.TryFuzzyMatch has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GameEndpoints.DetectAndAddAsync (cognitive 23) · ×1
  • GameEndpoints.DetectAndAddAsync (cognitive 23) REDACTED:969 — GameEndpoints.DetectAndAddAsync has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · LocalLlmService.StartAsync (cognitive 23) · ×1
  • LocalLlmService.StartAsync (cognitive 23) REDACTED:358 — LocalLlmService.StartAsync has cognitive complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · TermMatchingService.FindMatchedTerms (cognitive 23) · ×1
  • TermMatchingService.FindMatchedTerms (cognitive 23) XUnityToolkit-WebUI/Services/TermMatchingService.cs:24 — TermMatchingService.FindMatchedTerms has cognitive complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateService.AutoCheckOnStartupAsync (cognitive 23) · ×1
  • UpdateService.AutoCheckOnStartupAsync (cognitive 23) REDACTED:647 — UpdateService.AutoCheckOnStartupAsync has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RuntimeFontBootstrap.Initialize (cognitive 23) · ×1
  • RuntimeFontBootstrap.Initialize (cognitive 23) RuntimeFontLoader/Shared/RuntimeFontBootstrap.cs:29 — RuntimeFontBootstrap.Initialize has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SimpleJson.ExtractString (cognitive 22) · ×1
  • SimpleJson.ExtractString (cognitive 22) TranslatorEndpoint/ToolkitConnectionManager.cs:435 — SimpleJson.ExtractString has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SettingsEndpoints.MapSettingsEndpoints (cognitive 22) · ×1
  • SettingsEndpoints.MapSettingsEndpoints (cognitive 22) REDACTED:16 — SettingsEndpoints.MapSettingsEndpoints has cognitive complexity 22 (threshold 15). None of this is in the body itself: all 22 points belong to 7 function literals inside it that branch (lines 120, 166, 223, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · LlmApiAdapter.ExtractOpenAiCompatibleText (cognitive 22) · ×1
  • LlmApiAdapter.ExtractOpenAiCompatibleText (cognitive 22) XUnityToolkit-WebUI/Services/LlmApiAdapter.cs:163 — LlmApiAdapter.ExtractOpenAiCompatibleText has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FontReplacementService.ValidateCustomFont (cognitive 21) · ×1
  • FontReplacementService.ValidateCustomFont (cognitive 21) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2919 — FontReplacementService.ValidateCustomFont has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalLlmService.DownloadModelInternalAsync (cognitive 21) · ×1
  • LocalLlmService.DownloadModelInternalAsync (cognitive 21) REDACTED:880 — LocalLlmService.DownloadModelInternalAsync has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SettingsEndpoints.MigrateLegacyDoNotTranslateAsync (cognitive 20) · ×1
  • SettingsEndpoints.MigrateLegacyDoNotTranslateAsync (cognitive 20) REDACTED:316 — SettingsEndpoints.MigrateLegacyDoNotTranslateAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginDiagnosticAgentService.ValidateAnalysis (cognitive 20) · ×1
  • PluginDiagnosticAgentService.ValidateAnalysis (cognitive 20) XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs:630 — PluginDiagnosticAgentService.ValidateAnalysis has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginHealthCheckService.CheckDoorstopConfigAsync (cognitive 20) · ×1
  • PluginHealthCheckService.CheckDoorstopConfigAsync (cognitive 20) XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:393 — PluginHealthCheckService.CheckDoorstopConfigAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · PluginPackageService.SanitizeIniContent (cognitive 20) · ×1
  • PluginPackageService.SanitizeIniContent (cognitive 20) XUnityToolkit-WebUI/Services/PluginPackageService.cs:330 — PluginPackageService.SanitizeIniContent has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolboxAgentToolExecutor.ApplySafeSetting (cognitive 20) · ×1
  • ToolboxAgentToolExecutor.ApplySafeSetting (cognitive 20) XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:493 — ToolboxAgentToolExecutor.ApplySafeSetting has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginHealthEndpoints.MapPluginHealthEndpoints (cognitive 19) · ×1
  • PluginHealthEndpoints.MapPluginHealthEndpoints (cognitive 19) REDACTED:8 — PluginHealthEndpoints.MapPluginHealthEndpoints has cognitive complexity 19 (threshold 15). None of this is in the body itself: all 19 points belong to 4 function literals inside it that branch (lines 86, 54, 28, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FontReplacementService.ProcessLooseFile (cognitive 19) · ×1
  • FontReplacementService.ProcessLooseFile (cognitive 19) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1523 — FontReplacementService.ProcessLooseFile has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Rollback (cognitive 18) · ×1
  • Rollback (cognitive 18) Updater/Program.cs:449 — Rollback has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ToolkitSingleInstance.TryActivateExistingAsync (cognitive 18) · ×1
  • ToolkitSingleInstance.TryActivateExistingAsync (cognitive 18) XUnityToolkit-WebUI/Infrastructure/ToolkitSingleInstance.cs:52 — ToolkitSingleInstance.TryActivateExistingAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LlmApiAdapter.AddChatReasoning (cognitive 18) · ×1
  • LlmApiAdapter.AddChatReasoning (cognitive 18) XUnityToolkit-WebUI/Services/LlmApiAdapter.cs:285 — LlmApiAdapter.AddChatReasoning has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginDiagnosticAgentService.ValidateRepairPlan (cognitive 18) · ×1
  • PluginDiagnosticAgentService.ValidateRepairPlan (cognitive 18) XUnityToolkit-WebUI/Services/PluginDiagnosticAgentService.cs:351 — PluginDiagnosticAgentService.ValidateRepairPlan has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PluginHealthCheckService.VerifyCoreAsync (cognitive 18) · ×1
  • PluginHealthCheckService.VerifyCoreAsync (cognitive 18) XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:169 — PluginHealthCheckService.VerifyCoreAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PluginPackageService.ReadTargetLanguage (cognitive 18) · ×1
  • PluginPackageService.ReadTargetLanguage (cognitive 18) XUnityToolkit-WebUI/Services/PluginPackageService.cs:382 — PluginPackageService.ReadTargetLanguage has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RuntimeTmpFontService.InstallAsync (cognitive 18) · ×1
  • RuntimeTmpFontService.InstallAsync (cognitive 18) XUnityToolkit-WebUI/Services/RuntimeTmpFontService.cs:27 — RuntimeTmpFontService.InstallAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FontReplacementService.RestoreFontsAsync (cognitive 17) · ×1
  • FontReplacementService.RestoreFontsAsync (cognitive 17) XUnityToolkit-WebUI/Services/FontReplacementService.cs:2984 — FontReplacementService.RestoreFontsAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LlmTranslationService.TranslateLocalSequentialAsync (cognitive 17) · ×1
  • LlmTranslationService.TranslateLocalSequentialAsync (cognitive 17) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1325 — LlmTranslationService.TranslateLocalSequentialAsync has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LocalLlmLaunchPathResolver.Resolve (cognitive 17) · ×1
  • LocalLlmLaunchPathResolver.Resolve (cognitive 17) XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:37 — LocalLlmLaunchPathResolver.Resolve has cognitive complexity 17 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · LocalLlmService.DetectGpusAsync (cognitive 17) · ×1
  • LocalLlmService.DetectGpusAsync (cognitive 17) REDACTED:112 — LocalLlmService.DetectGpusAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ToolboxAgentEndpoints.MapToolboxAgentEndpoints (cognitive 16) · ×1
  • ToolboxAgentEndpoints.MapToolboxAgentEndpoints (cognitive 16) REDACTED:8 — ToolboxAgentEndpoints.MapToolboxAgentEndpoints has cognitive complexity 16 (threshold 15). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 37, 76, 19, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · GameProcessHelper.KillGameProcessAsync (cognitive 16) · ×1
  • GameProcessHelper.KillGameProcessAsync (cognitive 16) XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:77 — GameProcessHelper.KillGameProcessAsync has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LlmTranslationService.ReplaceWithProtection (cognitive 16) · ×1
  • LlmTranslationService.ReplaceWithProtection (cognitive 16) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2134 — LlmTranslationService.ReplaceWithProtection has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalLlmService.EnsureLlamaExtractedAsync (cognitive 16) · ×1
  • LocalLlmService.EnsureLlamaExtractedAsync (cognitive 16) REDACTED:246 — LocalLlmService.EnsureLlamaExtractedAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TermMatchingService.EstimateTokenCount (cognitive 16) · ×1
  • TermMatchingService.EstimateTokenCount (cognitive 16) XUnityToolkit-WebUI/Services/TermMatchingService.cs:99 — TermMatchingService.EstimateTokenCount has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: index.ts → games.ts, types.ts, GameDetailView.vue XUnityToolkit-Vue/src/router/index.ts — `XUnityToolkit-Vue/src/router/index.ts` changes together with 3 other files — `XUnityToolkit-Vue/src/api/games.ts`, `XUnityToolkit-Vue/src/api/types.ts`, `XUnityToolkit-Vue/src/views/GameDetailView.vue` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) XUnityToolkit-WebUI/Services/FontReplacementService.cs:138 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:138-298 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:823-908 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:952-1248 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2739-2917 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2920-2982 | XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:514-911 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (238 corresponding lines) · ×1
  • Edited copy of a member (238 corresponding lines) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1676 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1676-1913 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2068-2305 — These two members are one piece of code written twice and then edited apart: 238 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (131 corresponding lines) · ×1
  • Edited copy of a member (131 corresponding lines) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1533 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1533-1663 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1923-2057 — These two members are one piece of code written twice and then edited apart: 131 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (58 corresponding lines) · ×1
  • Edited copy of a member (58 corresponding lines) TranslatorEndpoint/LLMTranslateEndpoint.cs:335 — TranslatorEndpoint/LLMTranslateEndpoint.cs:335-413 | TranslatorEndpoint/ToolkitConnectionManager.cs:436-493 — These two members are one piece of code written twice and then edited apart: 58 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) REDACTED:71 — REDACTED:71-121 | XUnityToolkit-WebUI/Services/BepInExLogService.cs:84-130 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (51 corresponding lines) · ×1
  • Edited copy of a member (51 corresponding lines) XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:36 — XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:36-86 | XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:89-139 — These two members are one piece of code written twice and then edited apart: 51 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 24+ corresponding lines) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2368 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2368-2391 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2394-2418 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2421-2444 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:457 — XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:457-486 | REDACTED:278-317 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:526 — XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:526-562 | XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:568-603 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) XUnityToolkit-WebUI/Services/TermService.cs:113 — XUnityToolkit-WebUI/Services/TermService.cs:113-139 | XUnityToolkit-WebUI/Services/TermService.cs:189-222 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) XUnityToolkit-WebUI/Services/GameImageService.cs:531 — XUnityToolkit-WebUI/Services/GameImageService.cs:531-578 | XUnityToolkit-WebUI/Services/WebImageSearchService.cs:83-130 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) XUnityToolkit-WebUI/Services/WebImageSearchService.cs:136 — XUnityToolkit-WebUI/Services/WebImageSearchService.cs:136-150 | XUnityToolkit-WebUI/Services/WebImageSearchService.cs:211-227 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) XUnityToolkit-WebUI/Services/ConfigurationService.cs:123 — XUnityToolkit-WebUI/Services/ConfigurationService.cs:123-171 | XUnityToolkit-WebUI/Services/ConfigurationService.cs:350-365 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:196 — XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:196-213 | XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:216-233 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 13+ corresponding lines) XUnityToolkit-WebUI/Services/GameImageService.cs:55 — XUnityToolkit-WebUI/Services/GameImageService.cs:55-67 | XUnityToolkit-WebUI/Services/GameImageService.cs:70-82 | XUnityToolkit-WebUI/Services/GameImageService.cs:265-277 | XUnityToolkit-WebUI/Services/GameImageService.cs:479-491 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:372 — XUnityToolkit-WebUI/Services/PluginAutoRepairService.cs:372-384 | XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:492-504 | XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:863-875 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) XUnityToolkit-WebUI/Services/GameLibraryService.cs:27 — XUnityToolkit-WebUI/Services/GameLibraryService.cs:27-54 | XUnityToolkit-WebUI/Services/GameLibraryService.cs:57-77 | XUnityToolkit-WebUI/Services/GameLibraryService.cs:80-100 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) XUnityToolkit-WebUI/Infrastructure/TranslationResponseParser.cs:110 — XUnityToolkit-WebUI/Infrastructure/TranslationResponseParser.cs:110-113 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2249-2252 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) XUnityToolkit-WebUI/Services/ScriptTagService.cs:138 — XUnityToolkit-WebUI/Services/ScriptTagService.cs:138-143 | XUnityToolkit-WebUI/Services/TermService.cs:168-172 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (68 lines × 2) · ×1
  • Duplicated block (68 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1947 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1947-2014 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2153-2220 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (60 lines × 2) · ×1
  • Duplicated block (60 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1557 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1557-1616 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1760-1819 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1557` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (36–37 lines × 2) · ×1
  • Duplicated block (36–37 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1676 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1676-1711 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2068-2104 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1676` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (33–36 lines × 2) · ×1
  • Duplicated block (33–36 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1869 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1869-1901 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2258-2293 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1869` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (25–33 lines × 2) · ×1
  • Duplicated block (25–33 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:873 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:873-905 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1087-1111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (23–29 lines × 2) · ×1
  • Duplicated block (23–29 lines × 2) XUnityToolkit-WebUI/Services/FontReplacementService.cs:1121 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:1121-1149 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1354-1376 — 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 `XUnityToolkit-WebUI/Services/FontReplacementService.cs:1121` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1193 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1193-1221 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1333-1360 — 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 `XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24–28 lines × 4) · ×1
  • Duplicated block (24–28 lines × 4) XUnityToolkit-WebUI/Services/GameImageService.cs:86 — XUnityToolkit-WebUI/Services/GameImageService.cs:86-113 | XUnityToolkit-WebUI/Services/GameImageService.cs:129-153 | XUnityToolkit-WebUI/Services/GameImageService.cs:166-189 | XUnityToolkit-WebUI/Services/GameImageService.cs:438-462 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/GameImageService.cs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:37 — XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:37-61 | XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:90-114 — 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 `XUnityToolkit-WebUI/Services/InstallOrchestrator.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (24–26 lines × 4) · ×1
  • Duplicated block (24–26 lines × 4) XUnityToolkit-WebUI/Services/GameImageService.cs:495 — XUnityToolkit-WebUI/Services/GameImageService.cs:495-520 | XUnityToolkit-WebUI/Services/GameImageService.cs:611-635 | XUnityToolkit-WebUI/Services/GameImageService.cs:679-702 | XUnityToolkit-WebUI/Services/GameImageService.cs:714-738 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/GameImageService.cs:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) REDACTED:199 — REDACTED:199-220 | REDACTED:415-436 — 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 `REDACTED:199` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) REDACTED:13 — REDACTED:13-33 | REDACTED:120-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:13` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) XUnityToolkit-WebUI/Services/GameImageService.cs:415 — XUnityToolkit-WebUI/Services/GameImageService.cs:415-432 | XUnityToolkit-WebUI/Services/GameImageService.cs:589-606 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17–21 lines × 2) · ×1
  • Duplicated block (17–21 lines × 2) XUnityToolkit-WebUI/Services/PluginPackageService.cs:190 — XUnityToolkit-WebUI/Services/PluginPackageService.cs:190-210 | XUnityToolkit-WebUI/Services/PluginPackageService.cs:212-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) Updater/Program.cs:72 — Updater/Program.cs:72-92 | Updater/Program.cs:331-350 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Updater/Program.cs:429 — Updater/Program.cs:429-447 | XUnityToolkit-WebUI/Services/ToolboxDataResetService.cs:89-107 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) XUnityToolkit-WebUI/Services/UnityDetectionService.cs:212 — XUnityToolkit-WebUI/Services/UnityDetectionService.cs:212-229 | XUnityToolkit-WebUI/Services/UnityDetectionService.cs:232-248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (11 lines × 6) · ×1
  • Duplicated block (11 lines × 6) REDACTED:456 — REDACTED:456-466 | REDACTED:485-495 | REDACTED:121-131 | REDACTED:150-160 | REDACTED:338-348 | REDACTED:367-377 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:456` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1
  • Duplicated block (13–16 lines × 2) REDACTED:511 — REDACTED:511-523 | REDACTED:393-408 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:511` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) XUnityToolkit-WebUI/Services/GlossaryExtractionService.cs:339 — XUnityToolkit-WebUI/Services/GlossaryExtractionService.cs:339-353 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2281-2296 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/GlossaryExtractionService.cs:339` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) REDACTED:22 — REDACTED:22-34 | REDACTED:75-87 | REDACTED:129-141 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) REDACTED:270 — REDACTED:270-284 | REDACTED:303-316 — 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 `REDACTED:270` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) REDACTED:63 — REDACTED:63-74 | REDACTED:106-117 | REDACTED:64-75 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:63` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) XUnityToolkit-WebUI/Services/FontReplacementService.cs:837 — XUnityToolkit-WebUI/Services/FontReplacementService.cs:837-849 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:1052-1064 | XUnityToolkit-WebUI/Services/FontReplacementService.cs:2942-2955 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/FontReplacementService.cs:837` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1763 — XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1763-1775 | XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1843-1856 — 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 `XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1763` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:458 — XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:458-470 | REDACTED:279-291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:458` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:471` calls `GetString` and `REDACTED:292` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–13 lines × 3) · ×1
  • Duplicated block (9–13 lines × 3) XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:34 — XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:34-45 | XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:107-115 | XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:122-134 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/CharacterSets/BuiltinCharsets.cs:34` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (10–13 lines × 2) · ×1
  • Duplicated block (10–13 lines × 2) XUnityToolkit-WebUI/Services/CharacterSetService.cs:227 — XUnityToolkit-WebUI/Services/CharacterSetService.cs:227-236 | XUnityToolkit-WebUI/Services/ConfigurationService.cs:509-521 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `XUnityToolkit-WebUI/Services/CharacterSetService.cs:227` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) REDACTED:423 — REDACTED:423-434 | REDACTED:512-523 | REDACTED:396-408 | REDACTED:459-471 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:423` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) REDACTED:799 — REDACTED:799-807 | REDACTED:820-828 | REDACTED:857-865 | REDACTED:878-886 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:799` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) REDACTED:22 — REDACTED:22-30 | REDACTED:40-48 | REDACTED:83-91 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) XUnityToolkit-WebUI/Services/CharacterSetService.cs:177 — XUnityToolkit-WebUI/Services/CharacterSetService.cs:177-186 | XUnityToolkit-WebUI/Services/CharacterSetService.cs:194-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) REDACTED:15 — REDACTED:15-20 | REDACTED:37-42 | REDACTED:55-60 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) REDACTED:57 — REDACTED:57-62 | REDACTED:288-293 | REDACTED:346-351 | REDACTED:339-344 | REDACTED:77-82 | REDACTED:540-545 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) REDACTED:57 — REDACTED:57-62 | REDACTED:288-293 | REDACTED:346-351 | REDACTED:237-242 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×1
  • Duplicated block (6 lines × 7) REDACTED:57 — REDACTED:57-62 | REDACTED:288-293 | REDACTED:346-351 | REDACTED:339-344 | REDACTED:77-82 | REDACTED:540-545 | REDACTED:237-242 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 157 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:335` calls `GetByIdAsync`, `NotFound`, `Fail` and `REDACTED:236` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net6.0 RuntimeFontLoader/Il2Cpp/RuntimeFontLoader.Il2Cpp.csproj:3 — RuntimeFontLoader/Il2Cpp/RuntimeFontLoader.Il2Cpp.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
IC1 · Incompleteness & stubs · Dead `#if false` region · ×1
  • Dead `#if false` region XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:166 — Code inside a `#if false` block is permanently excluded from the build — disabled code that should be removed or restored.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:226 — `DeleteAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (5 clone groups) XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:57 — 5 duplicated blocks under XUnityToolkit-Vue/src/ have copies in at least two of the sibling directories api, components, stores, views — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (131 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (131 matched lines × 2 locations) XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10 — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:10 — the two spans are one implementation copied and then locally edited — 812 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (99 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (99 matched lines × 2 locations) XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:10 — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:10 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:10 — the two spans are one implementation copied and then locally edited — 643 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) XUnityToolkit-Vue/src/views/FontGeneratorView.vue:349 — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:349 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:425 — 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.
R10 · Code Duplication · Duplicated block (18 lines × 3 locations) · ×1
  • Duplicated block (18 lines × 3 locations) XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:147 — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:147 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:134 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:100 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) XUnityToolkit-Vue/src/stores/update.ts:38 — XUnityToolkit-Vue/src/stores/update.ts:38 · XUnityToolkit-Vue/src/stores/update.ts:90 — 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.
R10 · Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (11 matched lines × 2 locations) XUnityToolkit-Vue/src/views/AiTranslationView.vue:194 — XUnityToolkit-Vue/src/views/AiTranslationView.vue:194 · XUnityToolkit-Vue/src/views/SettingsView.vue:130 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (11 lines × 3 locations) · ×1
  • Duplicated block (11 lines × 3 locations) XUnityToolkit-Vue/src/views/TermEditorView.vue:311 — XUnityToolkit-Vue/src/views/TermEditorView.vue:311 · XUnityToolkit-Vue/src/views/TermEditorView.vue:336 · XUnityToolkit-Vue/src/views/TermEditorView.vue:361 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (10 lines × 4 locations) · ×1
  • Duplicated block (10 lines × 4 locations) XUnityToolkit-Vue/src/api/games.ts:73 — XUnityToolkit-Vue/src/api/games.ts:73 · XUnityToolkit-Vue/src/api/games.ts:100 · XUnityToolkit-Vue/src/api/games.ts:151 · XUnityToolkit-Vue/src/api/games.ts:304 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:205 — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:205 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:166 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:277 — XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:277 · XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:307 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 3 locations) · ×1
  • Duplicated block (9 lines × 3 locations) XUnityToolkit-Vue/src/views/FontGeneratorView.vue:149 — XUnityToolkit-Vue/src/views/FontGeneratorView.vue:149 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:216 · XUnityToolkit-Vue/src/views/FontGeneratorView.vue:234 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 6 locations) · ×1
  • Duplicated block (7 lines × 6 locations) XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:58 — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:58 · XUnityToolkit-Vue/src/components/health/PluginHealthCard.vue:27 · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:34 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:28 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication · Duplicated block (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:33 — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:33 · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:27 · XUnityToolkit-Vue/src/components/library/WebImageSearchTab.vue:21 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R2 · Cyclomatic Complexity · Complex function parseCsvImport (cyclomatic 28, cognitive 16) · ×1
  • Complex function parseCsvImport (cyclomatic 28, cognitive 16) XUnityToolkit-Vue/src/views/TermEditorView.vue:624 — parseCsvImport has cyclomatic complexity 28 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function computeConnections (cyclomatic 26, cognitive 26) · ×1
  • Complex function computeConnections (cyclomatic 26, cognitive 26) XUnityToolkit-Vue/src/views/AiTranslationView.vue:437 — computeConnections has cyclomatic complexity 26 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseJsonImport (cyclomatic 24, cognitive 52) · ×1
  • Complex function parseJsonImport (cyclomatic 24, cognitive 52) XUnityToolkit-Vue/src/views/TermEditorView.vue:556 — parseJsonImport has cyclomatic complexity 24 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getReasoningHint (cyclomatic 17, cognitive 17) · ×1
  • Complex function getReasoningHint (cyclomatic 17, cognitive 17) XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:229 — getReasoningHint has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function loadPreferences (cyclomatic 17, cognitive 12) · ×1
  • Complex function loadPreferences (cyclomatic 17, cognitive 12) XUnityToolkit-Vue/src/stores/games.ts:72 — loadPreferences has cyclomatic complexity 17 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function addGameCore (cyclomatic 16, cognitive 25) · ×1
  • Complex function addGameCore (cyclomatic 16, cognitive 25) XUnityToolkit-Vue/src/composables/useAddGameFlow.ts:26 — addGameCore has cyclomatic complexity 16 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleImportClick (cyclomatic 13, cognitive 19) · ×1
  • Complex function handleImportClick (cyclomatic 13, cognitive 19) XUnityToolkit-Vue/src/views/TermEditorView.vue:514 — handleImportClick has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 12) · ×1
  • Complex function (anonymous) (cyclomatic 13, cognitive 12) XUnityToolkit-Vue/src/views/AiTranslationView.vue:614 — (anonymous) has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function doReplace (cyclomatic 12, cognitive 18) · ×1
  • Complex function doReplace (cyclomatic 12, cognitive 18) XUnityToolkit-Vue/src/views/FontReplacementView.vue:342 — doReplace has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function send (cyclomatic 12, cognitive 11) · ×1
  • Complex function send (cyclomatic 12, cognitive 11) XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:234 — send has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handleIconContextMenuSelect (cyclomatic 11, cognitive 14) · ×1
  • Complex function handleIconContextMenuSelect (cyclomatic 11, cognitive 14) XUnityToolkit-Vue/src/views/GameDetailView.vue:379 — handleIconContextMenuSelect has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 10) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 10) XUnityToolkit-Vue/src/views/TermEditorView.vue:216 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · XUnityToolkit-Vue/src/views/AiTranslationView.vue · ×1
  • XUnityToolkit-Vue/src/views/AiTranslationView.vue: 2694 lines of code XUnityToolkit-Vue/src/views/AiTranslationView.vue:1 — XUnityToolkit-Vue/src/views/AiTranslationView.vue has 2694 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/GameDetailView.vue · ×1
  • XUnityToolkit-Vue/src/views/GameDetailView.vue: 2158 lines of code XUnityToolkit-Vue/src/views/GameDetailView.vue:1 — XUnityToolkit-Vue/src/views/GameDetailView.vue has 2158 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/SettingsView.vue · ×1
  • XUnityToolkit-Vue/src/views/SettingsView.vue: 1278 lines of code XUnityToolkit-Vue/src/views/SettingsView.vue:1 — XUnityToolkit-Vue/src/views/SettingsView.vue has 1278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/FontReplacementView.vue · ×1
  • XUnityToolkit-Vue/src/views/FontReplacementView.vue: 1137 lines of code XUnityToolkit-Vue/src/views/FontReplacementView.vue:1 — XUnityToolkit-Vue/src/views/FontReplacementView.vue has 1137 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue · ×1
  • XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue: 1078 lines of code XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue:1 — XUnityToolkit-Vue/src/components/settings/LocalAiPanel.vue has 1078 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/FontGeneratorView.vue · ×1
  • XUnityToolkit-Vue/src/views/FontGeneratorView.vue: 1046 lines of code XUnityToolkit-Vue/src/views/FontGeneratorView.vue:1 — XUnityToolkit-Vue/src/views/FontGeneratorView.vue has 1046 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/TermEditorView.vue · ×1
  • XUnityToolkit-Vue/src/views/TermEditorView.vue: 1016 lines of code XUnityToolkit-Vue/src/views/TermEditorView.vue:1 — XUnityToolkit-Vue/src/views/TermEditorView.vue has 1016 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue · ×1
  • XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue: 960 lines of code XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:1 — XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue has 960 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue · ×1
  • XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue: 797 lines of code XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue:1 — XUnityToolkit-Vue/src/components/settings/AiTranslationCard.vue has 797 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue · ×1
  • XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue: 764 lines of code XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue:1 — XUnityToolkit-Vue/src/components/common/FileExplorerModal.vue has 764 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/LibraryView.vue · ×1
  • XUnityToolkit-Vue/src/views/LibraryView.vue: 755 lines of code XUnityToolkit-Vue/src/views/LibraryView.vue:1 — XUnityToolkit-Vue/src/views/LibraryView.vue has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/config/ConfigPanel.vue · ×1
  • XUnityToolkit-Vue/src/components/config/ConfigPanel.vue: 720 lines of code XUnityToolkit-Vue/src/components/config/ConfigPanel.vue:1 — XUnityToolkit-Vue/src/components/config/ConfigPanel.vue has 720 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/layout/AppShell.vue · ×1
  • XUnityToolkit-Vue/src/components/layout/AppShell.vue: 704 lines of code XUnityToolkit-Vue/src/components/layout/AppShell.vue:1 — XUnityToolkit-Vue/src/components/layout/AppShell.vue has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/LogView.vue · ×1
  • XUnityToolkit-Vue/src/views/LogView.vue: 704 lines of code XUnityToolkit-Vue/src/views/LogView.vue:1 — XUnityToolkit-Vue/src/views/LogView.vue has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue · ×1
  • XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue: 523 lines of code XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:1 — XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue has 523 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/TranslationEditorView.vue · ×1
  • XUnityToolkit-Vue/src/views/TranslationEditorView.vue: 487 lines of code XUnityToolkit-Vue/src/views/TranslationEditorView.vue:1 — XUnityToolkit-Vue/src/views/TranslationEditorView.vue has 487 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/library/IconPickerModal.vue · ×1
  • XUnityToolkit-Vue/src/components/library/IconPickerModal.vue: 427 lines of code XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:1 — XUnityToolkit-Vue/src/components/library/IconPickerModal.vue has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue · ×1
  • XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue: 418 lines of code XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue:1 — XUnityToolkit-Vue/src/components/library/BackgroundPickerModal.vue has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · XUnityToolkit-Vue/src/views/BepInExLogView.vue · ×1
  • XUnityToolkit-Vue/src/views/BepInExLogView.vue: 415 lines of code XUnityToolkit-Vue/src/views/BepInExLogView.vue:1 — XUnityToolkit-Vue/src/views/BepInExLogView.vue has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 47 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R6 · Tooling · No lint script · ×1
  • No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Wait(…)` · ×1
  • Sync-over-async (deadlock risk) through `.Wait(…)` XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:278 — `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
X18 · Disposal-pattern correctness · Owned disposable field overwritten without releasing the previous instance · ×1
  • Owned disposable field overwritten without releasing the previous instance XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs:113 — `_writer` is a `StreamWriter` this type creates itself, and here (line 113) a new instance is written over it — but `FileLoggerProvider` creates `_writer` when it is constructed, so every later call finds an instance there, and nothing earlier in `ResumeFileLog` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_writer?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×1
  • Disposable created and abandoned in the method that made it REDACTED:1169 — `listener` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 1169). Every use of it in `GetAvailablePort` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var listener = …;`), which releases it at the end of the scope on every path including a throw.
X2 · Cancellation propagation · Async delegate without CancellationToken · ×1
  • Async delegate without CancellationToken: MapFontGenerationEndpoints REDACTED:112 — Queues or hands on an async lambda whose work calls something that takes a CancellationToken, while neither this method nor the delegate supplies one — that work can't be stopped early once started. Take a CancellationToken here and let the lambda capture it, or use a delegate that is handed one (`Func<CancellationToken, Task>`).
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) XUnityToolkit-WebUI/Services/BackupService.cs:23 — `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Minor — 127 finding(s)
S1 · Web-Security Posture · No inbound model validation detected · ×36
  • No inbound model validation detected — No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
  • No inbound model validation detected REDACTED:13 — `MapGet("/")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:35 — `MapGet("/download")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:52 — `MapPost("/analyze")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:20 — `MapGet("/")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:37 — `MapPost("/install")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:80 — `MapPost("/upload")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:123 — `MapDelete("/")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:157 — `MapPost("/toggle")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:191 — `MapGet("/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:10 — `MapGet("/api/games/{id}/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:20 — `MapPut("/api/games/{id}/config")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:31 — `MapGet("/api/games/{id}/config/raw")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:42 — `MapPut("/api/games/{id}/config/raw")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:10 — `MapPost("/api/games/{id}/detect")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:14 — `MapGet("/drives")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:40 — `MapGet("/quick-access")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:54 — `MapPost("/read-text")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:83 — `MapPost("/list")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:20 — `MapPost("/upload")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:55 — `MapPost("/upload-from-path")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:84 — `MapPost("/generate")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:136 — `MapGet("/status")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:139 — `MapPost("/cancel")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • No inbound model validation detected REDACTED:145 — `MapGet("/download/{fileName}")` binds request input and nothing in this codebase validates it — no [ApiController]/ModelState check, validator or guard.
  • + 11 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×20
  • Silent fallback default in catch REDACTED:100 — `ReadTailRawLines` swallows every exception into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Infrastructure/GameProcessHelper.cs:49 — `IsGameRunning` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/FontReplacementService.cs:525 — `GetByteArrayLength` swallows every exception into `return 0;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/FontReplacementService.cs:551 — `HasObjectReference` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/FontReplacementService.cs:2978 — `ValidateCustomFont` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:144 — `CandidateMatches` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:241 — `TryCreateHardLink` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/LocalLlmLaunchPathResolver.cs:254 — `TryCreateSymbolicLink` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch REDACTED:652 — `TryGetExitCode` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/PluginDetectionService.cs:299 — `FindXUnityDll` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:482 — `TryReadAssemblyMetadata` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/PluginDiagnosticArtifactCollector.cs:693 — `IsSafePathWithoutReparse` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:763 — `IsFreshLog` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/RuntimeTmpFontService.cs:342 — `ReadManifestAsync` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/RuntimeTmpFontService.cs:356 — `ReadRuntimeStatusAsync` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs:79 — `TryReadAssetString` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs:190 — `RequiresConfirmation` swallows `UriFormatException` into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch XUnityToolkit-WebUI/Services/UnityDetectionService.cs:116 — `DetectTextMeshPro` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch REDACTED:271 — `TryReadFileVersion` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch REDACTED:313 — `TryReadEndpointAssemblyIdentity` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D24 · Comment Value · redundant comment · ×18
  • redundant comment XUnityToolkit-Vue/src/api/games.ts:271 — "Plugin Health Check" repeats the code it sits on: 3 of its 3 words (plugin, health, check) are already in `export const pluginHealthApi = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-Vue/src/api/types.ts:721 — "── BepInEx Log ──" repeats the code it sits on: 3 of its 3 words (bep, ex, log) are already in `export interface BepInExLogResponse`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:318 — "POST /charset/upload-translation — upload translation file" repeats the code it sits on: 4 of its 5 words (post, charset, upload, translation) are already in `group.MapPost("/charset/upload-translation", async (HttpRequest request, AppDataPaths appDataPaths) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:68 — "Extract icon from exe" repeats the code it sits on: 3 of its 3 words (extract, icon, exe) are already in `using var icon = Icon.ExtractAssociatedIcon(exePath);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:231 — "Try to find exe" repeats the code it sits on: 3 of its 3 words (try, find, exe) are already in `var exePath = detection.TryFindExecutable(folderPath);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:366 — "Delete custom icon" repeats the code it sits on: 3 of its 3 words (delete, custom, icon) are already in `group.MapDelete("/{id}/icon/custom", async (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Program.cs:180 — "HTTP client for SteamGridDB API" repeats the code it sits on: 5 of its 6 words (http, client, steam, grid, db) are already in `builder.Services.AddHttpClient("SteamGridDB", client =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Program.cs:218 — "HTTP client for GitHub update checks" repeats the code it sits on: 5 of its 6 words (http, client, git, hub, update) are already in `builder.Services.AddHttpClient("GitHubUpdate", client =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/CharacterSetService.cs:71 — "Custom charset file" repeats the code it sits on: 3 of its 3 words (custom, charset, file) are already in `if (!string.IsNullOrEmpty(config.CustomCharsetFileName))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/DxgiGpuDetector.cs:18 — "DXGI_ADAPTER_FLAG_SOFTWARE = 2" repeats the code it sits on: 4 of its 4 words (dxgi, adapter, flag, software) are already in `private const uint DXGI_ADAPTER_FLAG_SOFTWARE = 2;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/LlmTranslationService.cs:451 — "Term audit check if terms exist" repeats the code it sits on: 4 of its 5 words (term, audit, check, terms) are already in `if (matchedTerms is { Count: > 0 } && ai.TermAuditEnabled)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2049 — "── Glossary post-processing ──" repeats the code it sits on: 3 of its 3 words (glossary, post, processing) are already in `private static string ApplyGlossaryPostProcess(string translated, List<TermEntry> glossary,`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/LlmTranslationService.cs:2349 — "── Model list fetching ──" repeats the code it sits on: 3 of its 3 words (model, list, fetching) are already in `public async Task<IList<string>> FetchModelsAsync(LlmProvider provider, string apiBaseUrl, string apiKey, CancellationTo …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/PluginPackageService.cs:70 — "Add BepInEx directory" repeats the code it sits on: 4 of its 4 words (add, bep, ex, directory) are already in `fileCount += AddDirectoryToZip(archive, gamePath, "BepInEx", ct);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/PluginPackageService.cs:315 — "Exclude BepInEx/LogOutput.log" repeats the code it sits on: 5 of its 5 words (exclude, bep, ex, log, output) are already in `if (string.Equals(entryName, "BepInEx/LogOutput.log", StringComparison.OrdinalIgnoreCase))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:147 — "Update or add to exact index" repeats the code it sits on: 4 of its 4 words (update, add, exact, index) are already in `store.ExactIndex.AddOrUpdate(normalized, entry, (_, existing) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment XUnityToolkit-WebUI/Services/TranslationMemoryService.cs:152 — "Add to length bucket" repeats the code it sits on: 3 of its 3 words (add, length, bucket) are already in `AddToLengthBucket(store, normalized.Length, entry);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment REDACTED:813 — "Download update-check.json for this tag" repeats the code it sits on: 5 of its 5 words (download, update, check, json, tag) are already in `var checkUrl = $"https://github.com/{GitHubOwner}/{GitHubRepo}/releases/download/{tag}/update-check.json";`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X7 · Silent fallback defaults · Pending state with no failure state · ×14
  • Pending state with no failure state XUnityToolkit-Vue/src/views/BepInExLogView.vue:289 — The view draws `<div v-if="loading && !logContent" class="log-loading">` under `loading && !logContent`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/BepInExLogView.vue:318 — The view draws `工具箱智能体诊断 智能诊断使用设置页统一选择的智能体提供商。自动修复只会在检测到可修复问题时显示,并会先备份目标文件、执行受限修复工具,再重新诊断;多阶段调用可能产生模型 API 费用。 {{ repairResult.summary }} {{ repairing ? '正在诊断、备份、自动修复并复检...' : '正在选择关键资料并生成结构化诊断...' }}` under `analyzing || repairing || healthReport`, but `analyzing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/BepInExLogView.vue:336 — The view draws `{{ repairing ? '正在诊断、备份、自动修复并复检...' : '正在选择关键资料并生成结构化诊断...' }}` under `analyzing || repairing`, but `analyzing` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/ConfigEditorView.vue:106 — The view draws `<div v-if="loading" class="editor-loading">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/GameDetailView.vue:592 — The view draws `<div v-if="loading" class="detail-loading">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/GameDetailView.vue:596 — The view draws `返回 {{ game.name }} {{ isInstalled ? '已安装' : hasBepInEx ? '仅 BepInEx' : '未安装' }} 非 Unity 游戏信息 路径 {{ game.gamePath }} 可执行文件 {{ game.executableName || '未知' }} Unity 版本 {{ game.detectedInfo?.unityVersion || '未知' }} 脚本后端 {{ game.detectedInfo?.backend || '未知' }} 架构 {{ game.detectedInfo?.architecture || '未知' }} 类型 非 Unity 游戏 打开目录 运行游戏 0" class="section-card" style="animation-delay: 0.15s"> 检测到的模组框架 检测到其他模组框架,建议卸载后再安装 BepInEx 版本,避免插件冲突。 {{ frameworkDisplayNames[fw.framework] }} v{{ fw.version }} 含 XUnity{{ fw.xUnityVersion ? ` v${fw.xUnityVersion}` : '' }} 卸载 0 ? '0.2s' : '0.15s' }"> 安装管理 卸载插件 检测到 IL2CPP 游戏,将使用 BepInEx 6 (预发布版)。首次启动游戏可能需要 30-90 秒生成互操作程序集。 {{ isInstalling ? '正在安装翻译插件' : '准备安装翻译插件' }} {{ isInstalling ? `${installStepLabel} · 关闭此页面不会中断安装` : '将自动安装 BepInEx 框架和 XUnity.AutoTranslator 翻译插件' }} {{ installStepLabel }}... 点击查看详细进度 一键安装 高级选项 安装 TMP 字体(运行时 TTF 优先) 默认直接加载思源黑体 TTF;不支持时回退到匹配 Unity 版本的兼容资产 TMP 字体应用方式 全局回退保留原游戏字体;全部替换会统一 TMP 文本字体 部署 AI 翻译端点 安装 LLMTranslate.dll,允许游戏连接本工具进行 AI 翻译 启动游戏生成配置 自动启动游戏以生成 AutoTranslatorConfig.ini 配置文件 应用最佳配置 自动写入推荐的翻译插件配置(语言、字体、翻译引擎等) 验证插件状态 安装后启动游戏验证插件是否正常工作 BepInEx {{ game.installedBepInExVersion }} 模组框架 XUnity.AutoTranslator {{ game.installedXUnityVersion }} 翻译插件 如需重新安装,请先卸载当前版本 0 ? '0.25s' : '0.2s' }" /> 0 ? '0.3s' : '0.25s' }"> 翻译配置 0 ? '0.35s' : '0.3s' }"> AI 翻译引擎 {{ aiEndpointStatusLabel }} {{ aiEndpointStatus?.message }} 安装 AI 翻译引擎后,游戏将通过工具箱连接 LLM 进行实时翻译。需要在 AI 翻译页面配置 API Key。 安装 AI 翻译引擎 {{ aiEndpointActionLabel }} 卸载引擎 0 ? '0.4s' : '0.35s' }"> 游戏工具 译文编辑器 可视化编辑翻译条目,支持导入和导出翻译文件 AI 翻译术语库 管理专用术语表,自动注入翻译提示词 字体替换 修改游戏资产中的 TMP 字体,支持扫描和还原 BepInEx 日志 查看运行日志,支持搜索、过滤和 AI 分析 插件管理 安装、卸载和管理第三方 BepInEx 插件 0 ? '0.45s' : '0.4s' }"> 游戏背景描述 为该游戏填写背景信息(类型、世界观、角色等),AI 翻译时会自动参考,提升翻译的准确性和一致性。 0 ? '0.5s' : '0.45s' }"> 汉化包 将当前游戏的全部插件和翻译文件打包为 ZIP 汉化补丁,方便分享给其他玩家。其他玩家解压到游戏目录即可使用。导入汉化包会覆盖同名文件。 生成汉化包 导入汉化包` under `game`, but `game` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/GameDetailView.vue:815 — The view draws `0 ? '0.2s' : '0.15s' }"> 安装管理 卸载插件 检测到 IL2CPP 游戏,将使用 BepInEx 6 (预发布版)。首次启动游戏可能需要 30-90 秒生成互操作程序集。 {{ isInstalling ? '正在安装翻译插件' : '准备安装翻译插件' }} {{ isInstalling ? `${installStepLabel} · 关闭此页面不会中断安装` : '将自动安装 BepInEx 框架和 XUnity.AutoTranslator 翻译插件' }} {{ installStepLabel }}... 点击查看详细进度 一键安装 高级选项 安装 TMP 字体(运行时 TTF 优先) 默认直接加载思源黑体 TTF;不支持时回退到匹配 Unity 版本的兼容资产 TMP 字体应用方式 全局回退保留原游戏字体;全部替换会统一 TMP 文本字体 部署 AI 翻译端点 安装 LLMTranslate.dll,允许游戏连接本工具进行 AI 翻译 启动游戏生成配置 自动启动游戏以生成 AutoTranslatorConfig.ini 配置文件 应用最佳配置 自动写入推荐的翻译插件配置(语言、字体、翻译引擎等) 验证插件状态 安装后启动游戏验证插件是否正常工作 BepInEx {{ game.installedBepInExVersion }} 模组框架 XUnity.AutoTranslator {{ game.installedXUnityVersion }} 翻译插件 如需重新安装,请先卸载当前版本` under `game.isUnityGame`, but `game` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/LogView.vue:242 — The view draws `连接日志流...` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/PluginManagerView.vue:240 — The view draws `<div v-if="loading" class="loading-state">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/PluginManagerView.vue:267 — The view draws `<div v-else-if="loading" class="loading-state" style="padding: 80px 0">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/TermEditorView.vue:795 — The view draws `<div v-if="loading" class="loading-state">` under `loading`, but `loading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/TermEditorView.vue:813 — The view draws `保存中...` under `autoSaving`, but `autoSaving` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/views/TermEditorView.vue:946 — The view draws `<div v-if="loadingGames" class="loading-state" style="min-height: 120px">` under `loadingGames`, but `loadingGames` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state XUnityToolkit-Vue/src/components/agent/ToolboxAgentWindow.vue:569 — The view draws `正在读取历史...` under `historyLoading`, but `historyLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
X10 · Duplicated predicate · Duplicated predicate · ×10
  • Duplicated predicate XUnityToolkit-WebUI/Services/FontReplacementService.cs:849 — `!mbBase["m_GlyphTable"].IsDummy && !mbBase["m_Version"].IsDummy` appears character-identically in 2 files — XUnityToolkit-WebUI/Services/FontReplacementService.cs, XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:60 — `(magic[0] == 0x00 && magic[1] == 0x01 && magic[2] == 0x00 && magic[3] == 0x00) || (magic[0] == 0x4F && magic[1] == 0x54 && magic[2] == 0x54 …` appears character-identically in 2 files — RuntimeFontLoader/Shared/RuntimeFontFileValidator.cs, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Infrastructure/EndpointSelector.cs:16 — `e.Enabled && !string.IsNullOrWhiteSpace(e.ApiKey)` appears character-identically in 2 files — XUnityToolkit-WebUI/Infrastructure/EndpointSelector.cs, XUnityToolkit-WebUI/Services/LlmEndpointResolver.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs:712 — `element.ValueKind != JsonValueKind.Object || !element.TryGetProperty(propertyName, out var value) || value.ValueKind != JsonValueKind.String` appears character-identically in 2 files — XUnityToolkit-WebUI/Services/ToolboxAgentHostAccessService.cs, XUnityToolkit-WebUI/Services/ToolboxAgentToolExecutor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs:359 — `endpoint.Enabled && !string.IsNullOrWhiteSpace(endpoint.ApiKey) && !string.Equals(endpoint.ApiKey, "local", StringComparison.OrdinalIgnoreCa…` appears character-identically in 2 files — XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs, XUnityToolkit-WebUI/Services/ToolboxAgentEndpointResolver.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Services/FontReplacementService.cs:250 — `entryName.EndsWith(".resource", StringComparison.OrdinalIgnoreCase) || entryName.EndsWith(".resS", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — XUnityToolkit-WebUI/Services/FontReplacementService.cs, XUnityToolkit-WebUI/Services/TmpFontGeneratorService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-Vue/src/stores/aiTranslation.ts:14 — `connection && connection.state !== signalR.HubConnectionState.Disconnected` appears character-identically in 4 files — XUnityToolkit-Vue/src/stores/aiTranslation.ts, XUnityToolkit-Vue/src/stores/localLlm.ts, XUnityToolkit-Vue/src/stores/log.ts, XUnityToolkit-Vue/src/stores/update.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Services/CharacterSetService.cs:234 — `line.StartsWith('[') && line.EndsWith(']')` appears character-identically in 4 files — XUnityToolkit-WebUI/Services/CharacterSetService.cs, XUnityToolkit-WebUI/Services/ConfigurationService.cs, XUnityToolkit-WebUI/Services/PluginHealthCheckService.cs, XUnityToolkit-WebUI/Services/PluginPackageService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Updater/Program.cs:445 — `string.Equals(candidate, path, StringComparison.OrdinalIgnoreCase) || path.StartsWith(prefix, StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — Updater/Program.cs, XUnityToolkit-WebUI/Services/ToolboxDataResetService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate XUnityToolkit-WebUI/Services/CharacterSetService.cs:171 — `string.IsNullOrWhiteSpace(line) || line.StartsWith("//")` appears character-identically in 2 files — XUnityToolkit-WebUI/Services/CharacterSetService.cs, XUnityToolkit-WebUI/Services/XUnityTranslationFormat.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D12 · Dependency Hygiene · Outdated (npm) · ×5
  • Outdated (npm): eventsource — eventsource 2.0.2 → 5.1.5 available.
  • Outdated (npm): nanoid — nanoid 3.3.18 → 6.0.2 available.
  • Outdated (npm): tr46 — tr46 0.0.3 → 7.0.0 available.
  • Outdated (npm): webidl-conversions — webidl-conversions 3.0.1 → 8.0.1 available.
  • Outdated (npm): whatwg-url — whatwg-url 5.0.0 → 17.3.0 available.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×3
  • Silent fallback default on parse failure TranslatorEndpoint/ToolkitConnectionManager.cs:511 — `ExtractInt` falls back to `-1` when `index > start && int.TryParse(json.Substring(start, index - start), out value)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure XUnityToolkit-WebUI/Services/LlmTranslationService.cs:1478 — `CalculateScore` falls back to `500` when `stats.SuccessfulCalls > 0` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
  • Silent fallback default on parse failure REDACTED:94 — `IsNewerVersion` returns `true` when `long.TryParse(i < remoteParts.Length ? remoteParts[i] : "0", out var r)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
R7 · Dead Code · Unused module-local declaration 'handleFileSelect' · ×2
  • Unused module-local declaration 'handleFileSelect' XUnityToolkit-Vue/src/components/library/CoverPickerModal.vue:153 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
  • Unused module-local declaration 'handleFileSelect' XUnityToolkit-Vue/src/components/library/IconPickerModal.vue:119 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
S1 · Web-Security Posture · No security response headers detected · ×2
  • No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
  • No security response headers detected XUnityToolkit-WebUI/Program.cs:84 — This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
  • No app-layer HTTPS enforcement detected XUnityToolkit-WebUI/Program.cs:84 — This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
D21 · Naming Consistency · `OpenAI` spells `AI` where 13 names in the project spell it `Ai` · ×1
  • `OpenAI` spells `AI` where 13 names in the project spell it `Ai` XUnityToolkit-WebUI/Models/AiTranslationSettings.cs:3 — 13 of 14 names in project XUnityToolkit-WebUI spell the token `Ai` (13 of 14; unit: names in project XUnityToolkit-WebUI containing `Ai`). Peers: InstallProgressHub.JoinAiTranslationGroup (REDACTED:13); InstallProgressHub.LeaveAiTranslationGroup (REDACTED:16); InstallOptions.AutoDeployAiEndpoint (XUnityToolkit-WebUI/Models/InstallOptions.cs:7); InstallStep.InstallingAiTranslation (XUnityToolkit-WebUI/Models/InstallationStatus.cs:10); LlmApiAdapter.BuildOpenAiCompatibleRequest (XUnityToolkit-WebUI/Services/LlmApiAdapter.cs:14). Rename to `OpenAi`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion XUnityToolkit-WebUI/XUnityToolkit-WebUI.csproj:1 — `XUnityToolkit-WebUI` overshoots its size bounds (30039 LoC, 274 public types across 7 namespaces). 1 of 8 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. Review these for cohesion — draw the boundary inside the assembly first (group each responsibility into its own namespace/folder and keep the cross-boundary members internal), since splitting a published assembly moves types between packages and breaks consumers.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj:9 — `RuntimeFontLoader.Tests/RuntimeFontLoader.Tests.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused module-local declaration 'handleUpload' · ×1
  • Unused module-local declaration 'handleUpload' XUnityToolkit-Vue/src/views/FontGeneratorView.vue:120 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 307/404 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 2/3 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions override nullable warnings · ×1
  • Null-forgiving operator (`!`) suppressions override nullable warnings — ~1.1 `!` suppressions per 1k syntax nodes — 4 suppression(s) across the 3733 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via string slicing · ×1
  • Hand-rolled JSON/XML parsing via string slicing XUnityToolkit-WebUI/Infrastructure/LlmResponseParser.cs:16 — A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Minor — 85 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×76
  • Outdated (npm): @babel/generator — @babel/generator 8.0.0 → 8.1.2 available.
  • Outdated (npm): @babel/helper-string-parser — @babel/helper-string-parser 8.0.0 → 8.1.2 available.
  • Outdated (npm): @babel/helper-validator-identifier — @babel/helper-validator-identifier 8.0.4 → 8.0.6 available.
  • Outdated (npm): @babel/parser — @babel/parser 8.0.4 → 8.1.2 available.
  • Outdated (npm): @babel/types — @babel/types 8.0.4 → 8.1.2 available.
  • Outdated (npm): @emotion/hash — @emotion/hash 0.8.0 → 0.9.2 available.
  • Outdated (npm): @jridgewell/resolve-uri — @jridgewell/resolve-uri 3.1.2 → 3.1.3 available.
  • Outdated (npm): @jridgewell/sourcemap-codec — @jridgewell/sourcemap-codec 1.5.5 → 1.6.0 available.
  • Outdated (npm): @microsoft/signalr — @microsoft/signalr 10.0.11 → 11.0.0 available.
  • Outdated (npm): @oxc-project/types — @oxc-project/types 0.144.0 → 0.159.0 available.
  • Outdated (npm): @rolldown/binding-android-arm64 — @rolldown/binding-android-arm64 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-darwin-arm64 — @rolldown/binding-darwin-arm64 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-darwin-x64 — @rolldown/binding-darwin-x64 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-freebsd-x64 — @rolldown/binding-freebsd-x64 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-arm-gnueabihf — @rolldown/binding-linux-arm-gnueabihf 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-arm64-gnu — @rolldown/binding-linux-arm64-gnu 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-arm64-musl — @rolldown/binding-linux-arm64-musl 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-ppc64-gnu — @rolldown/binding-linux-ppc64-gnu 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-s390x-gnu — @rolldown/binding-linux-s390x-gnu 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-x64-gnu — @rolldown/binding-linux-x64-gnu 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-linux-x64-musl — @rolldown/binding-linux-x64-musl 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-openharmony-arm64 — @rolldown/binding-openharmony-arm64 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-win32-arm64-msvc — @rolldown/binding-win32-arm64-msvc 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/binding-win32-x64-msvc — @rolldown/binding-win32-x64-msvc 1.2.4 → 1.3.2 available.
  • Outdated (npm): @rolldown/pluginutils — @rolldown/pluginutils 1.0.1 → 1.1.1 available.
  • + 51 more in this group — see findings.md.
D12 · Dependency Hygiene · Outdated · ×9
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 18.8.1 → 18.12.0 available (referenced by RuntimeFontLoader.Tests).
  • Outdated: xunit.analyzers — xunit.analyzers 1.27.0 → 2.3.0 available (referenced by RuntimeFontLoader.Tests).
  • Outdated: xunit.runner.visualstudio — xunit.runner.visualstudio 3.1.5 → 4.0.1 available (referenced by RuntimeFontLoader.Tests).
  • Outdated: AssetRipper.TextureDecoder — AssetRipper.TextureDecoder 2.6.2 → 2.6.3 available (referenced by XUnityToolkit-WebUI).
  • Outdated: Microsoft.Bcl.Memory — Microsoft.Bcl.Memory 10.0.11 → 11.0.0 available (referenced by XUnityToolkit-WebUI).
  • Outdated: Microsoft.Web.WebView2 — Microsoft.Web.WebView2 1.0.4129.50 → 1.0.4314.35 available (referenced by XUnityToolkit-WebUI).
  • Outdated: Microsoft.WindowsAppSDK.WinUI — Microsoft.WindowsAppSDK.WinUI 2.3.2 → 2.6.5 available (referenced by XUnityToolkit-WebUI).
  • Outdated: System.Management — System.Management 10.0.11 → 11.0.0 available (referenced by XUnityToolkit-WebUI).
  • Outdated: System.Reflection.MetadataLoadContext — System.Reflection.MetadataLoadContext 10.0.11 → 11.0.0 available (referenced by XUnityToolkit-WebUI).

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-75bec94fcba44cc5a9c13f8d95148bcd/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=572" --report-format json --report-path /tmp/watchdog-gitleaks-75bec94fcba44cc5a9c13f8d95148bcd/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-75bec94fcba44cc5a9c13f8d95148bcd/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .293artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .4artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 47 file(s) — `REDACTED`, `XUnityToolkit-WebUI/Infrastructure/AppDataPaths.cs`, `XUnityToolkit-WebUI/Infrastructure/FileLoggerProvider.cs`, `XUnityToolkit-WebUI/Services/AppSettingsService.cs`, `XUnityToolkit-WebUI/Services/BackupService.cs`, … (+42 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1e53e-d2ee-7ad0-a36a-9a3c1d129923 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md